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
ControlProperti es
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. 11 6600
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, programmaticall y 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@p.comwrote in message
news:eB******** ******@TK2MSFTN GP04.phx.gbl...
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
ControlProperti es
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.
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" <un**********@n othinks.comwrot e in message
news:%2******** ********@TK2MSF TNGP06.phx.gbl. ..
>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, programmaticall y 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@p.comwrote in message
news:eB******** ******@TK2MSFTN GP04.phx.gbl...
>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.
StyleSheetThem e ControlPropert ies Theme
So I am at a bit of a loss as how and where one would use a StyleSheetThem e 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.
There is a compelling reason to use themes over skins.
For one, you can use User Properties and save user-selected Themes which can
be applied on a per-user basis once they are logged in. This is so because a
Theme is a collection of images, css files as well as skin files that allow
for in-built grouping of UI elements.
For another, by using skins, you can apply consistent UI settings on web
controls.
I find the use of themes a maintenance helper for large websites.
"New Bee" <p@p.comwrote in message
news:eB******** ******@TK2MSFTN GP04.phx.gbl...
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
ControlProperti es
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.
Hi Brandon,
The question wasnt really about Themes Vs Skins, moreover it was (
Themes/Skins ) Vs Css.
Skins allow only some formatting, while css allows the full style
seperation. Having done a lot of CSS I know how powerful it is. But getting
a good Css design is not allways as easy as it sounds. Esp when you are
designing scalable web sites.
I understand the concept of skins, but Im trying to evaluate how much value
there is in using them over css. Granted, there are elements you cant set in
css, but I wonder actually how much value there is in this.
I can change css just as easily for a user as I can a theme. Im looking for
expert direction.
"Brandon Driesen" <de*********@us er.comwrote in message
news:13******** *****@corp.supe rnews.com...
There is a compelling reason to use themes over skins.
For one, you can use User Properties and save user-selected Themes which
can be applied on a per-user basis once they are logged in. This is so
because a Theme is a collection of images, css files as well as skin files
that allow for in-built grouping of UI elements.
For another, by using skins, you can apply consistent UI settings on web
controls.
I find the use of themes a maintenance helper for large websites.
"New Bee" <p@p.comwrote in message
news:eB******** ******@TK2MSFTN GP04.phx.gbl...
>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.
StyleSheetThem e ControlPropert ies Theme
So I am at a bit of a loss as how and where one would use a StyleSheetThem e 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.
i use themes and skins to apply css only. the theme picks the
stylesheet, the skin picks css classes when necessary.
-- bruce (sqlwork.com)
New Bee wrote:
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
ControlProperti es
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.
OK, so if I understand you here, what you are saying is that you dont
actually use the skin markup, you simply use that functionality to connect
css pages to controls ?
"bruce barker" <no****@nospam. comwrote in message
news:%2******** ********@TK2MSF TNGP05.phx.gbl. ..
>i use themes and skins to apply css only. the theme picks the stylesheet, the skin picks css classes when necessary.
-- bruce (sqlwork.com)
New Bee wrote:
>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.
StyleSheetThem e ControlPropert ies Theme
So I am at a bit of a loss as how and where one would use a StyleSheetThem e 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.
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@p.comwrote in message
news:uk******** *****@TK2MSFTNG P06.phx.gbl...
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" <un**********@n othinks.comwrot e in message
news:%2******** ********@TK2MSF TNGP06.phx.gbl. ..
>>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, programmaticall y 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@p.comwrote in message news:eB******* *******@TK2MSFT NGP04.phx.gbl.. .
>>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.
StyleSheetThe me ControlProper ties Theme
So I am at a bit of a loss as how and where one would use a StyleSheetThe me 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.
Yeah ok
"Kevin Spencer" <un**********@n othinks.comwrot e in message
news:u2******** *****@TK2MSFTNG P03.phx.gbl...
>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@p.comwrote in message
news:uk******** *****@TK2MSFTNG P06.phx.gbl...
>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" <un**********@n othinks.comwrot e in message news:%2******* *********@TK2MS FTNGP06.phx.gbl ...
>>>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, programmaticall y 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@p.comwrote in message news:eB****** ********@TK2MSF TNGP04.phx.gbl. .. 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.
StyleSheetTh eme ControlPrope rties Theme
So I am at a bit of a loss as how and where one would use a StyleSheetTh eme 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.
Ultimately, skins and themes are methods of simplifying UI look and feel
(aka customization or personalization ). You can accomplish everything you
need with CSS, but you will have to be in control, so you lose a bit of the
drag and drop. But, this is not as bad as it seems, as you have found out,
since few people seem to really be grabbing the whole theme and skin idea
(more so for themes than skins). CSS is not going away, not sure about the
rest and with WPF/E (aka Silverlight) on the horizon, it is likely our UIs
will change (that could be bleeding edge as well, just like themes and
skins).
My advice: Focus on CSS first. You can always combine it with the Microsoft
specific stuff, but a good solid understanding of CSS will take you far no
matter which way the ship turns. I would then delve into Themes and SKins if
time allows.
Personally, other than my experimentation in the beta, I have not used
Themes and Skins and I have multiple sites using the exact same engine (ie,
skinnable). I have found the Themes/Skins direction to be half-baked. It is
great for someone without the time for the learning curve to build his own,
but it is so half-baked as to be unusable in Enterprise level software. Your
mileage may vary.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA http://gregorybeamer.spaces.live.com
*************** *************** ***************
Think outside the box!
*************** *************** ***************
"New Bee" <p@p.comwrote in message
news:eB******** ******@TK2MSFTN GP04.phx.gbl...
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
ControlProperti es
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.
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Karsten |
last post by:
Hi
Is it possible to create applications with Java that support user skins /
themes, (like eg. Winamp does, except it's not a Java app).
Thanks
|
by: Sol |
last post by:
Hi Guys,
I'm looking for some advice / guidelines on using Themes with an application
I am working on. The application needs to allow people to customize the
appearance utilizing what I would consider to be a Themeing and Skinning
mechanism. What is critical is that this should be as flexible as possible.
What I would like to do is use...
|
by: Griff |
last post by:
We're replacing a CLASSIC ASP application.
In this application, we presented a dialogue box that allowed end users to
specify exactly how they wanted their screen to look. So, they could set
the font size, font colour, border widths/style/colour etc, etc.
This information was then held in a database.
When the ASP page was loaded, it...
|
by: Manso |
last post by:
Hi,
We're developing an application that should render well on both IE and
Firefox and should be based on Themes. Does anyone have any good tips on how
to maintain different CSS-files for different browsers and still use themes?
How/where do you select the CSS to use as this is autogenerated?
Thanks,
Manso
|
by: Sean |
last post by:
My experience now working with master pages on and off for 6 months is that
they can be very dangerous when working with themes.
One example in particular is the changes I made to my banner menu which now
work just fine with all my themes on my development machine but on my
production server my non-standard themes are showing effects that are...
| |
by: Clinton Farleigh |
last post by:
Hi,
I was going to ask a question, but I think I've answered it so now I am
going to rant about how crappy ASP.NET themes are instead.
As I've indicated above, my problem today is with themes. Per
microsoft "Only one theme can be applied to each page. You cannot apply
multiple themes to a page, unlike style sheets where multiple style...
|
by: qhaut |
last post by:
Hello out here,
Does anyone know a company which sells Themes/Skins for ASP.NET
portals? (not DotNetNuke, but pure ASP.NET 2.0 like the Starter Kits?)
Thank you in advance and Happy new Year!
|
by: Qweertz |
last post by:
Does anybody know where to find list of all attributes I can set for each
Control in .skin file?
I've been searching for it whole afternoon without any luck.
Thanks,
Tomica Gril
|
by: mike |
last post by:
Hi. I am having trouble grasping the concept of applying a consistent
theme to an ASP.net website. I didn't used to like ASP because it was
too hard to apply a theme from a common theme folder like I could do
easily in PHP, but now I see that it has some nicer theming features
and master files.
So I want to use web.config to switch which...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
| |
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating...
| |