Re: Themes and Skins Vs Css
- From: "Just Me" <news.microsoft.com>
- Date: Wed, 25 Apr 2007 22:44:40 +0100
Yeah ok
"Kevin Spencer" <unclechutney@xxxxxxxxxxxx> wrote in message
news:u2eZGi1hHHA.960@xxxxxxxxxxxxxxxxxxxxxxx
I didn't misunderstand you. You wanted to know whether you should use
Themes/Skins vs. CSS. I was pointing out that there is no disadvantage in
using CSS with regards to Controls, as the CSS for the Controls can be
managed fully with the CssClass combined with the various properties of the
Control, and indeed, any inline CSS style may be added to the Control
separately. If you take that fact, along with the sheer power of CSS
properly used, you have no disadvantage at all using CSS alone.
--
HTH,
Kevin Spencer
Microsoft MVP
Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net
"New Bee" <p@xxxxx> wrote in message
news:ukTOhN0hHHA.392@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for your reply Kevin.
//
As for the
properties of a Control not addressing all of the CSS layout properties,
you're wrong about this. Every WebControl has a CssClass property, which
//
You misunderstood me. I am fully aware that there is a CssClass property.
What I meant was that the controls do not have an attribute for each css
property, which would mean that you could not get away without using CSS
if you wanted seperation of styling. In other words, if one wanted to use
Theme's alone, one could not satisfy all the styling required and would
have to additionally resort to css for styling.
So, the question was if there was someone who 'Had' found a cogent and
resonable reason to use Themes over or With CSS, and what their
experience was.
Hopefully, I now have cleared up my question a little.
Cheers - NewBee
"Kevin Spencer" <unclechutney@xxxxxxxxxxxx> wrote in message
news:%23GA7XF0hHHA.4076@xxxxxxxxxxxxxxxxxxxxxxx
I would (and do) use CSS alone. I see no need for any additional
complexity than an external CSS style sheet. If the pages are designed
correctly, you can do an immense amount of layout manipulation using CSS
alone (see http://www.csszengarden.com for some startling examples). As
for the properties of a Control not addressing all of the CSS layout
properties, you're wrong about this. Every WebControl has a CssClass
property, which sets the "class" attribute of the client-side container
element. By using this, you can do all of your styling using a CSS style
sheet. The only reason you would need the other layout properties (which
are rendered as inline CSS styles) is to override the style sheet (inline
styles trump style sheet styles) temporarily, that is, programmatically
for a specific purpose).
CSS is immensely powerful, once you understand the Selector rules. Even
if you have a Component Control, your style sheet can specify the styles
of any child elements inside an element of a given class. Using CSS, you
get the best separation of UI elements from UI layout and styling rules.
I recently created a "Template" site which uses a very similar XHTML
layout to the www.csszengarden.com web site, and replaces divs with
panels and nested PlaceHolder controls in a MasterPage. I can use this
to create a site with virtually any layout and structure. For an example
of the site in actual practice, see http://www.miradyne.net.
--
HTH,
Kevin Spencer
Microsoft MVP
Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net
"New Bee" <p@xxxxx> wrote in message
news:eBEmmqzhHHA.1244@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have been looking at Themes and Skins today and now resonably
understand how they work at a ground level. But I have a couple of
questions.
1. ) StyleSheetTheme
I dont understand where this would be used. As I understand it the
precidence is like this.
StyleSheetTheme
ControlProperties
Theme
So I am at a bit of a loss as how and where one would use a
StyleSheetTheme over a Theme.
2.) Design Support for Skins
No Intellisense exists for this, so its a bit like stepping back in
time to a life before intellisense existed for CSS Development, you
have to either Know the properties or do it first on the page and just
copy it accross. This to me is a little archaic. Perhaps someone has a
different view ?
3.) Using CSS with or Vs Themes
What strikes me here is that the properties of a control do not address
all the layout properties of Css. So you cant really get away without
doing both if you are to have full seperation between application and
layout. This makes things rather complex in designing a web site where
all these design abstractions are being used.
I was wondering if there is someone here who has sufficient experience
with using all three to come up with some usefull and hopefully
simplistic advice which can direct a developer on at least how to
approach the task without getting tied up in all sorts of knots.
Many Thanks.
.
- References:
- Themes and Skins Vs Css
- From: New Bee
- Re: Themes and Skins Vs Css
- From: Kevin Spencer
- Re: Themes and Skins Vs Css
- From: New Bee
- Re: Themes and Skins Vs Css
- From: Kevin Spencer
- Themes and Skins Vs Css
- Prev by Date: Re: web handler or something like that
- Next by Date: Re: VS 2003 versus 2005 ASP:Textbox height difference
- Previous by thread: Re: Themes and Skins Vs Css
- Next by thread: Re: Themes and Skins Vs Css
- Index(es):
Relevant Pages
|
