Hi all,
I am new to the telerik suite of controls, and so far quite impressed after working with Ajax asp.net programming for a few years now (MS or Anthem mostly).
I am in design of a multiple active page internet customer portal (login/order creation/order status/product browser/profile..messages), hence requirement for a much better site style out of the box (I do not program CSS or JS or even muck about with HTML much) .
What I would normally do is design each 'active page' as a panel all in one .aspx, and switch the visibility on/off for each panel, but this site i'm estimating to be a little heavier in the amount of rendered html (+much more graphics) in total for one page, and the code behind will get a bit messy for the amount of server side functions that will be required.
My basic reasoning for this 'style' is that i am normally low on graphics (intranet style business applications) and I like to give a 'no page refresh ever' scenario (i.e never real postbacks, always callbacks).
This time I think my approach is going to have to be different, so I wanted to gather a little opinion from you all of a basic approach that might be reasonable given my intense dislike of page refreshing, but keep my code base and user experience expectations intact.
Should I consider master/content style (can this be done without full page refresh between each content page switch?), or something else that I havn't thought of or seen yet?
Any help would be appreciated.
Thanks,
Kevin.
I am new to the telerik suite of controls, and so far quite impressed after working with Ajax asp.net programming for a few years now (MS or Anthem mostly).
I am in design of a multiple active page internet customer portal (login/order creation/order status/product browser/profile..messages), hence requirement for a much better site style out of the box (I do not program CSS or JS or even muck about with HTML much) .
What I would normally do is design each 'active page' as a panel all in one .aspx, and switch the visibility on/off for each panel, but this site i'm estimating to be a little heavier in the amount of rendered html (+much more graphics) in total for one page, and the code behind will get a bit messy for the amount of server side functions that will be required.
My basic reasoning for this 'style' is that i am normally low on graphics (intranet style business applications) and I like to give a 'no page refresh ever' scenario (i.e never real postbacks, always callbacks).
This time I think my approach is going to have to be different, so I wanted to gather a little opinion from you all of a basic approach that might be reasonable given my intense dislike of page refreshing, but keep my code base and user experience expectations intact.
Should I consider master/content style (can this be done without full page refresh between each content page switch?), or something else that I havn't thought of or seen yet?
Any help would be appreciated.
Thanks,
Kevin.
2 Answers, 1 is accepted
0
Peter Zolja
Top achievements
Rank 1
Rank 1
answered on 02 Mar 2008, 04:31 AM
Kevin,
Without you giving us some concrete example as to how you organize your pages I can only go by what you said.
First of all, if you put multiple panels and choose to show / hide them, depending on the number of panels, it can increase your ViewState a lot. Secondly, you state that your goal is to never have post backs, but even when you use AJAX panels, you are posting back the whole page (i.e. including the probably big ViewState). The only difference is what you get back, that is only a portion of the page. If a site uses many images, this would only affect the first time you access the page. On subsequent requests those will not be re-downloaded.
I hope this helps,
Peter.
Without you giving us some concrete example as to how you organize your pages I can only go by what you said.
First of all, if you put multiple panels and choose to show / hide them, depending on the number of panels, it can increase your ViewState a lot. Secondly, you state that your goal is to never have post backs, but even when you use AJAX panels, you are posting back the whole page (i.e. including the probably big ViewState). The only difference is what you get back, that is only a portion of the page. If a site uses many images, this would only affect the first time you access the page. On subsequent requests those will not be re-downloaded.
I hope this helps,
Peter.
0
Remko
Top achievements
Rank 1
Rank 1
answered on 02 Mar 2008, 09:55 AM
Thanks for the comment Peter.
My 'postback' remark regards the user experience side, so that they never see any full page refreshing.
My concern, as you pointed out, is that by taking my normal approach (multi panel visibility) with this new site, the viewstate might be quite large, and slow down the response/performance for the user.
I am less concerned now, after delving deeper into the Telerik control suite this week, as I can also use effectively the radWindow to offset some of my main concerns (product browser etc..).
Thanks,
Kevin.
My 'postback' remark regards the user experience side, so that they never see any full page refreshing.
My concern, as you pointed out, is that by taking my normal approach (multi panel visibility) with this new site, the viewstate might be quite large, and slow down the response/performance for the user.
I am less concerned now, after delving deeper into the Telerik control suite this week, as I can also use effectively the radWindow to offset some of my main concerns (product browser etc..).
Thanks,
Kevin.