Dear all,
I inherited someone else "design" (or lack of... to be more precise) and keep bumping into increasing complexities because it uses a master page and somewhat complex Ajax logic (which is required).
This page is the only one to use that master page and I am really wondering why am I loosing my few hair left on this?
Surely, life is a lot easier with no Master Page and Ajax Proxy...
There will be quite a few much simpler pages later on and then I don't mind using a master page for them as I can easily understand the benefits.
So, I am quite tempted to ditch this master page in the complex page...
Would I upset any of you in doing so?
Eric
PS: my real expertise is SQL Server so I have not played that much with master pages, hence my "candid" question
I inherited someone else "design" (or lack of... to be more precise) and keep bumping into increasing complexities because it uses a master page and somewhat complex Ajax logic (which is required).
This page is the only one to use that master page and I am really wondering why am I loosing my few hair left on this?
Surely, life is a lot easier with no Master Page and Ajax Proxy...
There will be quite a few much simpler pages later on and then I don't mind using a master page for them as I can easily understand the benefits.
So, I am quite tempted to ditch this master page in the complex page...
Would I upset any of you in doing so?
Eric
PS: my real expertise is SQL Server so I have not played that much with master pages, hence my "candid" question
3 Answers, 1 is accepted
0
Accepted
ManniAT
Top achievements
Rank 2
Rank 2
answered on 24 Apr 2009, 05:48 PM
Hi Eric,
I'm also doing more with SQL Server than with WEB apps (or in other words - all I could solve in TSQL I do there) :)
About your masterpage thing.
From my point of view a masterpage has the same behavior like a group (role) in security.
YES if there is only one user who needs rights I can give them to the user directly.
Or I implement an extra role for this single user.
The second approach is more complex - but if the user becomes ill - (pr goes on holidays) and a different user must do his job...
And as for groups / roles the primary benefit of a masterpage is when you use it for multiple pages.
It brings some overhead (by the way with proxy the things are not too bad) recommends extra work and so on.
To compare my "user / group / role" example with the masterpage you have to think about possibilities.
A user can: leave the company, become ill, go on holidays, have an accident, die....
If there is (even a little) chance that your masterpage thing could be extended (more pages with that master needed) I would recommends you to keep the solution.
If not - I would use the pragmatic approach -- remove every overhead which consumes time, brain, CPU or nerves :)
I also have had this thoughts about one page in my current project.
This page posts elements to a payment system - and having the page in my masterpage made a lot of trouble (it post's more than expected) and to fix those things a lot of tricks would be needed.
My trick - a "rebuild" of the masterpage as background (frame) of this single problematic page.
It took me about one hour to make the single page look like the other pages (even reflecting changes in the masterpage by using the same CSS as base). After this everything worked as expected.
My first approach to fix some posting issues took much more than this - and solved only one of about 10 problematic sections.
This was the time I decided to remove the mast from this single page.
CONCLUSION:
If your page will always be the one and only - why mess around with a master page if it only makes troubles.
Regards
Manfred
I'm also doing more with SQL Server than with WEB apps (or in other words - all I could solve in TSQL I do there) :)
About your masterpage thing.
From my point of view a masterpage has the same behavior like a group (role) in security.
YES if there is only one user who needs rights I can give them to the user directly.
Or I implement an extra role for this single user.
The second approach is more complex - but if the user becomes ill - (pr goes on holidays) and a different user must do his job...
And as for groups / roles the primary benefit of a masterpage is when you use it for multiple pages.
It brings some overhead (by the way with proxy the things are not too bad) recommends extra work and so on.
To compare my "user / group / role" example with the masterpage you have to think about possibilities.
A user can: leave the company, become ill, go on holidays, have an accident, die....
If there is (even a little) chance that your masterpage thing could be extended (more pages with that master needed) I would recommends you to keep the solution.
If not - I would use the pragmatic approach -- remove every overhead which consumes time, brain, CPU or nerves :)
I also have had this thoughts about one page in my current project.
This page posts elements to a payment system - and having the page in my masterpage made a lot of trouble (it post's more than expected) and to fix those things a lot of tricks would be needed.
My trick - a "rebuild" of the masterpage as background (frame) of this single problematic page.
It took me about one hour to make the single page look like the other pages (even reflecting changes in the masterpage by using the same CSS as base). After this everything worked as expected.
My first approach to fix some posting issues took much more than this - and solved only one of about 10 problematic sections.
This was the time I decided to remove the mast from this single page.
CONCLUSION:
If your page will always be the one and only - why mess around with a master page if it only makes troubles.
Regards
Manfred
0
Accepted
Hello guys,
Actually, you are correct that deciding whether to use a MasterPage or not depends on the design and on the possibilities for future extension of your system. That is why we cannot give you a proper advise for this because we cannot predict the your future development. However, I believe that in case you do not intend to have more pages with the same template it is better to keep the simpler solution without a MasterPage. Also, in case it later turns out that you need to change the layout to use a MasterPage and you experience problems with the RadControls, you can rely on our help to get the desired result.
Greetings,
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Actually, you are correct that deciding whether to use a MasterPage or not depends on the design and on the possibilities for future extension of your system. That is why we cannot give you a proper advise for this because we cannot predict the your future development. However, I believe that in case you do not intend to have more pages with the same template it is better to keep the simpler solution without a MasterPage. Also, in case it later turns out that you need to change the layout to use a MasterPage and you experience problems with the RadControls, you can rely on our help to get the desired result.
Greetings,
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Eric
Top achievements
Rank 1
Rank 1
answered on 27 Apr 2009, 02:51 PM
I did not really learn anything new... other than I was not missing a fundamental point!
Which in itself is extremely useful.
Thank You.