Glavs Blog - All Comments

re: MaintainScrollPositionOnPostback Property - I love it.

jpitt57488 — Fri, 16 May 2008 22:24:58 GMT

I have to edit my previous comment...I did actually get this to work in a mobile form. It did not seem to work when I added as a page directive; however when I added in code in the page_init event

Page.MaintainScrollPositionOnPostBack = True

It worked!

One small note...still doesn't work in firefox.

re: MaintainScrollPositionOnPostback Property - I love it.

jpitt57488 — Thu, 15 May 2008 19:53:14 GMT

I too have found that this does not work in Mobile Web Forms. It is very frustrating how so many things don't work in mobile web forms (such as setfocus). You have to spend a great deal of extra time with custom java script if you want a user-friendly interface.

Mobile support is actually built into all asp.net 2.0 controls. Thus, you can actually just build regular asp.net pages and they will work. However, I found that the pages are much larger than the mobile pages thus they take a long time to load on a mobile device. That is probably why microsoft chose to keep the Mobile Web forms.

Hopefully they will get this right one day!

re: ASP.NET Podcast Show #83 - Writing a Custom AJAX Extender

Glav — Wed, 14 May 2008 23:50:38 GMT

Thanks for the comments Christopher. Glad you enjoyed it.

re: ASP.NET Podcast Show #83 - Writing a Custom AJAX Extender

Christopher Steven — Wed, 14 May 2008 16:10:40 GMT

Excelent Video, it was presented very well. btw thanks for using the debugger statement I did not know that existed lol.

melbourne museum

melbourne museum — Mon, 12 May 2008 15:19:53 GMT

Pingback from melbourne museum

vista media player codecs

vista media player codecs — Sun, 11 May 2008 10:10:31 GMT

Pingback from vista media player codecs

re: Reducing page load times with UpdatePanels and timers

Glav — Sun, 11 May 2008 08:58:25 GMT

Hi Jacky,

Reason is because its re-active, rather than pro-active. Using timers makes use of 'dead' time, whereas using the click of a respective tab, means the user will have to wait till the content is loaded. Using timers means that potentially, trhere could be no wait (as you will NOT delay load the first tab, but delay load others). So the UI experience will be faster.

toolkit rendered

toolkit rendered — Sun, 11 May 2008 04:11:00 GMT

Pingback from toolkit rendered

re: Reducing page load times with UpdatePanels and timers

Jacky — Fri, 09 May 2008 16:42:18 GMT

Why not have each tab click load the content via ajax instead of using timers?

re: Reducing page load times with UpdatePanels and timers

Glav — Fri, 09 May 2008 04:44:02 GMT

Hi Mark,

Thanks for the comments, and like anything, it can certainly be improved upon. I am sure you can appreciate that providing a more complex example kind of detracts away from the solution at hand, being delayed loading.

Your approach sounds good, although probably quite specific to the application. The approach I have provided is a 5 minute task and pretty simple and easy to digest. Improving upon it is an excercise for whomever wishes to do it :-)

BTW, The tab control has some drawbacks, but its a really useful and timesaving control. Anything generic like this, tends to have some bloat unfortunately.

Again, I certainly apprciate your comments and look forward to your improved version. Send me the link :-)