By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,285 Members | 2,109 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,285 IT Pros & Developers. It's quick & easy.

Why aren't master pages part of themes?

P: n/a
I may be missing something, but why aren't master pages part of themes?
i.e. why don't they go in the App_Themes or global Themes directory, and be
referenced just by name (not full path) in the declaration for a page?

That way, you can change the complete layout by just applying the theme to a
page or a whole site.

I know that if your master pages are XHTML, then you can change the layout
significantly with CSS, but there are situations where that doesn't give you
enough control.

What am I missing?
Jan 5 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Missing the fact that a loosely coupled architecture can be beneficial. We
can programmatically change MasterPages very much like we can Themes both
independently of one another.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/
"Seefor" <in*****@email.address> wrote in message
news:Bx*******************@text.news.blueyonder.co .uk...
I may be missing something, but why aren't master pages part of themes?
i.e. why don't they go in the App_Themes or global Themes directory, and
be
referenced just by name (not full path) in the declaration for a page?

That way, you can change the complete layout by just applying the theme to
a
page or a whole site.

I know that if your master pages are XHTML, then you can change the layout
significantly with CSS, but there are situations where that doesn't give
you
enough control.

What am I missing?



Jan 6 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.