Skip to main content

Themes in Whidbey...Is it worth it????

Theme management, how were u doing it previously??? I was using simple css files. I define classes for objects, or ids. Go ahead and just mention the styles for these classes in the CSS file. Ok, I want to change the theme??? I change the CSS style sheet. Was happy with the way things were going on. Then came along Whidbey. They even had a simple to use theme management, ok thats what they said.
I rushed forward, got to learn how to use it, and went ahead and implemented it. Wow, I can change themes, on the fly, by just changing the property. Finally, some really cool way of doing this. Great they will be generating a css file automatically. Cool!!!! Something in me decided i need to have a look as to how this css file.
So went ahead and executed the page. Good old IE started up, the goody good looking page opened up, and I did a view source.
Searched for keyword
  • <link,....no matches found
  • stylesheet...no matches

Wow, then how is it done??? I go to one of the text box. Wait a minute, i never put style property for this text box, or maybe i had.......Hey, I am sure I did not mention style for this one and this one. Oh God, all my text boxes have the same style..meaning THE SERVER IS INSERTING STYLE FOR EACH AND EVERY CONTROL I AM DEFINING SKIN FOR, and that means....if i use 10 text boxes, it will put the same style for all text boxes!!! Further, it is doing it at server side, meaning performace degradation. I have been a major performance freak, and this, nope i wont talk about what this feels like. Imagine 10 such controls on your page, 100 users accessing this page. All at the same time, with different themes. I wonder how the performance is. Lets see. I used ACT, simulated 100 users for 5 minutes with 10 second warm up using 2 pages

  • one with 10 textbox page with css
  • another 10 text box page with theming concepts of Whidbey

      • Compared the time to first bytes.

      Second page gives 196.56ms

      First page gives 33.09ms

      So I guess you know what I will be using throughout my life, good old CSS.

      Anyway have lots of other things to do.

      Until the next blog....


      Comments

      Post a Comment

      Popular posts from this blog

      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

      My first problem with AJAX

      I was using Callback (AJAX) to retrieve a page i had developed . Lets start all over, I was using AJAX to retrieve a part of the contents of a web page. Cool, simple, it downloaded without a pain, then I innerHTMLed it to a span tag. Worked fine, successful, clapped my hands etc.etc. Clicked on the button which had seemed to appear out of nowhere. And then, it all fell apart. The feared exclamatory symbol appeared on the status bar.... And for the newbies, thats an indication of a JavaScript error in IE. Of course, as usual i was all curses at my IE window......Anyway to make a long story short (i AM quite sleepy u know). the scripts which i seemed to be innerHTMLing to the span tag are not executed. And what i mean is anything between the script tags which have been innerHTMLed to that span tag are not executed. Of course i can see a ray of hope in the distance. I mean the distance till tomorrow morning. And just for kicks, check out a hi-fundoo flash file titled EPIC 2004 . And for...
      4 comments
      Read more