Saturday, March 31, 2012
Themes/Skins
Control in .skin file?
I've been searching for it whole afternoon without any luck.
Thanks,
Tomica GrilWe've got to drag each control into the IDE and use the properties window
and then go back and forth and back and forth. Nice huh?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"Qweertz" <qweertz@.net.hr> wrote in message
news:enu1q9$6g4$1@.news1.carnet.hr...
> 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
>
This isn't exactly what you asked for, but you can enable Intellisense for
the skin files.
http://www.ckcmoss.com/archives/18-...0.htm
l
I had to close and re-open the project - in addition to the original
instructions - to get it to stick, but there it is.
"You actually can add intellisense to any file in Visual Studio 2005
providing you have a schema. Just drop it in the ~\Xml\Schemas folder."
Good info from a comment on the same page, in case you miss it.
Oh yea -- that's the kind of wrong I like to be. Thanks for bringing this to
our attention.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"mank1327" <mcwadsworth@.hotmail.com> wrote in message
news:04806EE5-3E62-472D-B2D7-91ED80D3980A@.microsoft.com...
> This isn't exactly what you asked for, but you can enable Intellisense for
> the skin files.
> http://www.ckcmoss.com/archives/18-...0.h
tml
> I had to close and re-open the project - in addition to the original
> instructions - to get it to stick, but there it is.
> "You actually can add intellisense to any file in Visual Studio 2005
> providing you have a schema. Just drop it in the ~\Xml\Schemas folder."
> Good info from a comment on the same page, in case you miss it.
>
>
> We've got to drag each control into the IDE and use the properties window
> and then go back and forth and back and forth. Nice huh?
>
Yeah, I know that.
Intellisense is all I needed, but I didn't know that I can user it in skins
as well.
Thanks to both.
Themes/Skins
Control in .skin file?
I've been searching for it whole afternoon without any luck.
Thanks,
Tomica GrilWe've got to drag each control into the IDE and use the properties window
and then go back and forth and back and forth. Nice huh?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"Qweertz" <qweertz@.net.hrwrote in message
news:enu1q9$6g4$1@.news1.carnet.hr...
Quote:
Originally Posted 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
>
This isn't exactly what you asked for, but you can enable Intellisense for
the skin files.
http://www.ckcmoss.com/archives/18-...ins-in-2.0.html
I had to close and re-open the project - in addition to the original
instructions - to get it to stick, but there it is.
"You actually can add intellisense to any file in Visual Studio 2005
providing you have a schema. Just drop it in the ~\Xml\Schemas folder."
Good info from a comment on the same page, in case you miss it.
Oh yea -- that's the kind of wrong I like to be. Thanks for bringing this to
our attention.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"mank1327" <mcwadsworth@.hotmail.comwrote in message
news:04806EE5-3E62-472D-B2D7-91ED80D3980A@.microsoft.com...
Quote:
Originally Posted by
This isn't exactly what you asked for, but you can enable Intellisense for
the skin files.
>
http://www.ckcmoss.com/archives/18-...ins-in-2.0.html
>
I had to close and re-open the project - in addition to the original
instructions - to get it to stick, but there it is.
>
"You actually can add intellisense to any file in Visual Studio 2005
providing you have a schema. Just drop it in the ~\Xml\Schemas folder."
>
Good info from a comment on the same page, in case you miss it.
>
>
>
We've got to drag each control into the IDE and use the properties window
Quote:
Originally Posted by
and then go back and forth and back and forth. Nice huh?
>
Yeah, I know that.
Intellisense is all I needed, but I didn't know that I can user it in skins
as well.
Thanks to both.
Themes, Skins, and Masters
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 theme I'm using, and I
want to be able to have several themes. My understanding of themes is
that I can only define styling in them as I could with CSS, but I
can't define code for the header, footer, etc with them. And that's
where master files come in, right? I'd like to switch which set of
master files is in use as the theme changes. IE, I'd like to put
several master pages that match in looks but have different functions
in each theme's folder along with the skins. But I don't think that it
will automatically switch to those masters when the theme is switched
in web.config. Can I use a variable in the <%@dotnet.itags.org. Page
MasterPageFile="... part? Specifically, can I include Page.Theme into
the middle of a path, like:
<%@dotnet.itags.org. Page MasterPageFile="App_Themes/{Page.Theme}/m1.master" %>
I can't make the themes very varied if all I can edit is the skins and
they all have the same xHTML code.
Also, what is the difference between global themes in the /Themes/
directory and page themes in the /App_Themes/ directory?
So is this possible? Or am I thinking along the wrong lines to do such
a thing?
-Mike PIIBriefly, we use the Page_PreInit event handler to change Themes and
MasterPages noting K. Scott Allen has documented the most helpful
information regarding this topic at http://odetocode.com/ but if you want to
master ASP.NET you need to delve into the page life cycle and learn it well
as it is fundamental to this and related tasks.
When using MasterPages you will also need to learn how to reference controls
which can be and is somewhat convoluted when using the FindControl method.
Try to get the hang of writing public properties to avoid using FindControl
when possible.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
<mike@.learntoprogram.info> wrote in message
news:1178930483.643472.134670@.h2g2000hsg.googlegroups.com...
> 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 theme I'm using, and I
> want to be able to have several themes. My understanding of themes is
> that I can only define styling in them as I could with CSS, but I
> can't define code for the header, footer, etc with them. And that's
> where master files come in, right? I'd like to switch which set of
> master files is in use as the theme changes. IE, I'd like to put
> several master pages that match in looks but have different functions
> in each theme's folder along with the skins. But I don't think that it
> will automatically switch to those masters when the theme is switched
> in web.config. Can I use a variable in the <%@. Page
> MasterPageFile="... part? Specifically, can I include Page.Theme into
> the middle of a path, like:
> <%@. Page MasterPageFile="App_Themes/{Page.Theme}/m1.master" %>
> I can't make the themes very varied if all I can edit is the skins and
> they all have the same xHTML code.
> Also, what is the difference between global themes in the /Themes/
> directory and page themes in the /App_Themes/ directory?
> So is this possible? Or am I thinking along the wrong lines to do such
> a thing?
> -Mike PII
>
On May 12, 5:00 pm, "clintonG" <nob...@.nowhere.com> wrote:
> Briefly, we use the Page_PreInit event handler to change Themes and
> MasterPages noting K. Scott Allen has documented the most helpful
> information regarding this topic athttp://odetocode.com/but if you want to
> master ASP.NET you need to delve into the page life cycle and learn it wel
l
> as it is fundamental to this and related tasks.
> When using MasterPages you will also need to learn how to reference contro
ls
> which can be and is somewhat convoluted when using the FindControl method.
> Try to get the hang of writing public properties to avoid using FindContro
l
> when possible.
> <%= Clinton Gallagher
> NET csgallagher AT metromilwaukee.com
> URLhttp://clintongallagher.metromilwaukee.com/
Thanks for your help. I finally got it down.
ASP.net is
-Mike PII
Themes/skins with multiple browsers
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,
MansoOn Wed, 29 Mar 2006 08:45:02 -0800, Manso wrote:
> Does anyone have any good tips on how to maintain different CSS-files
> for different browsers and still use themes?
Yes, don't do it. There is (almost) no reason to maintain different CSS
files for different browsers. The one real exception here is NN4, but
using the @.import hack is common practice.
Unless you have a very complex design, you can design a site with only
minimal hacks to work on multiple browsers. You should just stay away from
features that are problematic.
It's very difficult to accurately sniff which browser is which, and serve
the correct CSS. You can't rely on browser agent strings, because many
people have their non-IE browsers configured to report that they are IE.
Themes/skins with multiple browsers
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,
MansoOn Wed, 29 Mar 2006 08:45:02 -0800, Manso wrote:
> Does anyone have any good tips on how to maintain different CSS-files
> for different browsers and still use themes?
Yes, don't do it. There is (almost) no reason to maintain different CSS
files for different browsers. The one real exception here is NN4, but
using the @.import hack is common practice.
Unless you have a very complex design, you can design a site with only
minimal hacks to work on multiple browsers. You should just stay away from
features that are problematic.
It's very difficult to accurately sniff which browser is which, and serve
the correct CSS. You can't rely on browser agent strings, because many
people have their non-IE browsers configured to report that they are IE.