Skip to main content

Smart navigation

Today early monday morning, started off with a discussion, Smart Navigation. As usual research was done. google provided some intriguing material. Looks like another controversial situation.

http://www.dotnetjunkies.com/Article/5E94AB64-5CA3-4487-8678-2853E3EF850D.dcik, a good explanation of Smart navigation,
and then go through this:
SmartNavigation and why not to use it

and then AutoPostback and SmartNavigation Together Clears Form


At sometime we did enable smartnavigation for our web forms. But we did have lots of div tags in our page, and it looked like smartnavigation managed scrolls only for full body. I overcame that by disabling smartnavigation and writing javascript code of my own. Need to check as to what else smartnavigation does do. Will put up the code here after that. Until then, happy snoozing.

Comments

Popular posts from this blog

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...

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 ...