|
.net
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
ASP.NET 2.0 Themes are not WYSIWYGHello,
I'm starting to use Themes. I skin some Web controls, like a WebPart and a CatalogPart. While browsing my Web page, I can see that the Theme is working, in VS 2005, in design view, I don't see the Theme styles being applied. Neither are the properties reflected in the Properties window. Am I doing something wrong? Should the skin properties be reflected in the Properties Window and in the Design view. I do hope so, because otherwise I see this as a big problem. Probably making Themes useless for me. Thanks. Michael I don't know of any way to make that work - it always displays controls
however they are on a page, without applying a specific theme. Themes are really for client-side presentation - how could not-seeing the corrent fonts/colors make this concept useless to you, I wonder? Show quoteHide quote "Michael" <nospam@nospam.com> wrote in message news:uWBvUAu$FHA.1268@TK2MSFTNGP11.phx.gbl... > Hello, > > I'm starting to use Themes. I skin some Web controls, like a WebPart and a > CatalogPart. While browsing my Web page, I can see that the Theme is > working, in VS 2005, in design view, I don't see the Theme styles being > applied. Neither are the properties reflected in the Properties window. > > Am I doing something wrong? Should the skin properties be reflected in the > Properties Window and in the Design view. I do hope so, because otherwise > I see this as a big problem. Probably making Themes useless for me. > > Thanks. > Michael > Hi RCS,
Here is an example. I have a skin file where I define WebPartZone's WebPartVerbRenderMode to "TitleBar", like: <asp:WebPartZone runat="server" WebPartVerbRenderMode="TitleBar"> In my Web page where I'm using a WebPartZone, in the properties window, the WebPartVerbRenderMode is "Menu". Clearly this is wrong. VS2005 designer mode should be reading from the appropriate Skin file and change the properties in the properties window accordingly. If it does not render correctly, maybe I can live with that; but showing the wrong perperty values in the properties window is not acceptable. As I said, maybe I'm doing something wrong. Or maybe this is a bug with some controls, like WebPartZone. Maybe simpler controls implement this correctly; I haven't tried yet. Thanks, Michael Show quoteHide quote "RCS" <rse***@gmail.com> wrote in message news:Vbfnf.3697$fO5.811@newssvr33.news.prodigy.com... >I don't know of any way to make that work - it always displays controls >however they are on a page, without applying a specific theme. > > Themes are really for client-side presentation - how could not-seeing the > corrent fonts/colors make this concept useless to you, I wonder? > > "Michael" <nospam@nospam.com> wrote in message > news:uWBvUAu$FHA.1268@TK2MSFTNGP11.phx.gbl... >> Hello, >> >> I'm starting to use Themes. I skin some Web controls, like a WebPart and >> a CatalogPart. While browsing my Web page, I can see that the Theme is >> working, in VS 2005, in design view, I don't see the Theme styles being >> applied. Neither are the properties reflected in the Properties window. >> >> Am I doing something wrong? Should the skin properties be reflected in >> the Properties Window and in the Design view. I do hope so, because >> otherwise I see this as a big problem. Probably making Themes useless for >> me. >> >> Thanks. >> Michael >> > > in your web.config file the <pages> element have an attribute called
styleSheetTheme. Defind you default theme there and you will get your theme to show up in designer. e.g. <pages styleSheetTheme="BlueTheme" /> Thanks!
I had <pages theme="LightBlue"> in my Web.config. Now I changed it to <pages theme="LightBlue" styleSheetTheme="LightBlue">. I can now see the styles being applied in VS Design view. My properties are still showing the wrong values though. Do you know what is the difference between "theme" and "styleSheetTheme"? I read the help file, but I'm still unclear about the difference, if any. The help file seems to say that both are the same. Thanks again. Michael Show quoteHide quote "tdavisjr" <tdavi***@gmail.com> wrote in message news:1134415510.629670.53470@z14g2000cwz.googlegroups.com... > in your web.config file the <pages> element have an attribute called > styleSheetTheme. Defind you default theme there and you will get your > theme to show up in designer. > > e.g. > > <pages styleSheetTheme="BlueTheme" /> > It looks like the way to go for me is to use the StyleSheetTheme instead.
Thanks. Show quoteHide quote "tdavisjr" <tdavi***@gmail.com> wrote in message news:1134419917.103225.318820@g43g2000cwa.googlegroups.com... > Here you go! > > http://weblogs.asp.net/vimodi/articles/WhatIs_StyleSheetTheme.aspx > styleSheetTheme - Ha! You learn something new everyday - nice one!
Show quoteHide quote "Michael" <nospam@nospam.com> wrote in message news:uZ%23Lok1$FHA.140@TK2MSFTNGP12.phx.gbl... > Thanks! > > I had <pages theme="LightBlue"> in my Web.config. Now I changed it to > <pages theme="LightBlue" styleSheetTheme="LightBlue">. I can now see the > styles being applied in VS Design view. My properties are still showing > the wrong values though. > > Do you know what is the difference between "theme" and "styleSheetTheme"? > I read the help file, but I'm still unclear about the difference, if any. > The help file seems to say that both are the same. > > Thanks again. > Michael > > > > "tdavisjr" <tdavi***@gmail.com> wrote in message > news:1134415510.629670.53470@z14g2000cwz.googlegroups.com... >> in your web.config file the <pages> element have an attribute called >> styleSheetTheme. Defind you default theme there and you will get your >> theme to show up in designer. >> >> e.g. >> >> <pages styleSheetTheme="BlueTheme" /> >> > > I wasn't thinking in terms of using the SkinID - I only uses themes in the
web.config where you do <pages Theme="LightBlue" /> or something like that.. And in that particular case, I don't ever see the designer load the appropriate theme... Show quoteHide quote "Michael" <nospam@nospam.com> wrote in message news:OUQKxg0$FHA.912@TK2MSFTNGP11.phx.gbl... > Hi RCS, > > Here is an example. > > I have a skin file where I define WebPartZone's WebPartVerbRenderMode to > "TitleBar", like: > <asp:WebPartZone runat="server" WebPartVerbRenderMode="TitleBar"> > > In my Web page where I'm using a WebPartZone, in the properties window, > the WebPartVerbRenderMode is "Menu". Clearly this is wrong. VS2005 > designer mode should be reading from the appropriate Skin file and change > the properties in the properties window accordingly. If it does not render > correctly, maybe I can live with that; but showing the wrong perperty > values in the properties window is not acceptable. > > As I said, maybe I'm doing something wrong. Or maybe this is a bug with > some controls, like WebPartZone. Maybe simpler controls implement this > correctly; I haven't tried yet. > > Thanks, > Michael > > > "RCS" <rse***@gmail.com> wrote in message > news:Vbfnf.3697$fO5.811@newssvr33.news.prodigy.com... >>I don't know of any way to make that work - it always displays controls >>however they are on a page, without applying a specific theme. >> >> Themes are really for client-side presentation - how could not-seeing the >> corrent fonts/colors make this concept useless to you, I wonder? >> >> "Michael" <nospam@nospam.com> wrote in message >> news:uWBvUAu$FHA.1268@TK2MSFTNGP11.phx.gbl... >>> Hello, >>> >>> I'm starting to use Themes. I skin some Web controls, like a WebPart and >>> a CatalogPart. While browsing my Web page, I can see that the Theme is >>> working, in VS 2005, in design view, I don't see the Theme styles being >>> applied. Neither are the properties reflected in the Properties window. >>> >>> Am I doing something wrong? Should the skin properties be reflected in >>> the Properties Window and in the Design view. I do hope so, because >>> otherwise I see this as a big problem. Probably making Themes useless >>> for me. >>> >>> Thanks. >>> Michael >>> >> >> > > Well, if the page has a default theme and the control has a skinID,
then it should render in design mode. This happens for me as I was working on a project with themes earlier today. So, I don't have a clue why its not rendering for you. Sounds like you are doing this incorrectly.
The control formatting properties are defined in the skin file. The content pages, holding the controls for display, reference the "skinid" for formatting. In the properties for the design view, you should specify the skinid to be applied. ------------------------------------------- I would much rather chew on tinfoil than try to code in C#. Hi Jon,
I'm not specifying the SkinID because I'm pulling from the default skin. Thanks, Michael Show quoteHide quote "Jon Paal" <Jon nospam Paal @ everywhere dot com> wrote in message news:uaahLM0$FHA.532@TK2MSFTNGP15.phx.gbl... > Sounds like you are doing this incorrectly. > The control formatting properties are defined in the skin file. > > > The content pages, holding the controls for display, reference the > "skinid" for formatting. > In the properties for the design view, you should specify the skinid to be > applied. > > > > ------------------------------------------- > I would much rather chew on tinfoil than try to code in C#. > the default skin is where the skinid's are defined.
You have to create this file or get one from another website. The "default" is not automatic from anywhere, it must be created or brought in. Show quoteHide quote "Michael" <nospam@nospam.com> wrote in message news:%23fTK2b0$FHA.3140@TK2MSFTNGP14.phx.gbl... > Hi Jon, > > I'm not specifying the SkinID because I'm pulling from the default skin. > > Thanks, > Michael > > > "Jon Paal" <Jon nospam Paal @ everywhere dot com> wrote in message news:uaahLM0$FHA.532@TK2MSFTNGP15.phx.gbl... >> Sounds like you are doing this incorrectly. >> The control formatting properties are defined in the skin file. >> >> >> The content pages, holding the controls for display, reference the "skinid" for formatting. >> In the properties for the design view, you should specify the skinid to be applied. >> >> >> >> ------------------------------------------- >> I would much rather chew on tinfoil than try to code in C#. >> > >  
Other interesting topics
|
|||||||||||||||||||||||
