Skip to main content

Theming in Whidbey using CSS

Continuing my blog titled Themes in Whidbey. I would like to mention some great points I did find out today about Whidbey featrures.
How many times have you got sick of developing Sites which have themes????
I mean every page u create has to have, maybe in ASP, something like
<link href="<%=Session["ThemeFile"]%>.css"/>
I have been doing since a long time. Do mention if you have a simpler method of defining a variable CSS for your page!!! Whidbey simplifies this further. Now in ASP.NET, all you will have to do is

  • Create Themes directory, if not aldready present,

  • Create a directory for each theme required, maybe Black, Gray,etc.
    Dump your CSS files into this directory.

  • in Page_PreInit method define the Theme as Page.Theme="<Theme directory Name>". Further can be made into Page.Theme=(string)Session["ThemeType"]


and viola, your theme management is take care by ASP.NET
When you want to change the theme, the string to be passed to the Theme property should be changed. Is'nt that great.

But beware of using the skinId property for any controls. The complexities were aldready mentioned in the other blog.
Anwyay go ahead and play around. Until the next time, happy theming!!!

Comments

Post a Comment

Popular posts from this blog

B.O.F.H.

Was browsing the net, and found some old link to BOFH. Not sure as to how many used to read PCQuest some time back when it used to come, but i remember reading them, with of course re-reads and re-re,etc...i can go on you know. Anyway, it's about a system operator who is bugged by no-brainers asking silly computer related queries, and this guy repling with wierd answers. I had never known the origin of this character, until i saw this . Anyway for those who have never read BOFH, here are two of them.
Post a Comment
Read more

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...
Post a Comment
Read more