DotNetNuke

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

JWhite — Sat, 19 Mar 2005 12:37:50 GMT

Thanks Jan,

I learned something new about DNN today. I never realized those classes were in there now. The framework has become so big with so many people altering it that it's hard to keep up with all the changes. (even some of the older ones) Thanks again for correcting me.

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

jan_olsmar — Fri, 18 Mar 2005 19:25:43 GMT

Most of the SkinObject have a class SkinObject as default.
The SkinObject class are defined in the default.css as well.

But to bee sure you get what you want its better to asign the class for each of them.

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

JWhite — Wed, 16 Mar 2005 11:12:17 GMT

There is no .skinobject css class in dnn (by default). Each skin object type can have it's css class(es) defined seperately. Please see the Appendix C in the skinning document for the list off attributes/properties for each skin object. you will notice most have a property called "CssClass" which you can set to the name of the css class you want to use for that instance of the skin object.

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

SamTanner — Wed, 16 Mar 2005 09:37:02 GMT

holger: TopStyle Lite is a great FREE visual css editor.
Go to http://www.bradsoft.com/download/

Cheers

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

yiyi2005 — Tue, 15 Mar 2005 21:46:58 GMT

Now I know how to use <%= SkinPath %>. Thanks for the explanation.

But how about skinobject css class? I did read the skinning doc but couldn't find the answer. Maybe I missed something? I assumed that .skinobject can style all the skin objects related classes... I tried but nothing happened...

holger: I use dreamweaver as the editor... but mostly I just hand code...

yiyi

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

xddg — Tue, 15 Mar 2005 20:02:36 GMT

This allows for true portability and DNN knows which path to assign for mult portal installations.

EG - If you create a new look using the wizard, you have a choice of several styles which have images already embedded, but when you apply the new template, the images appear in your portal and the portal ID is retained in the skin path using that type of token.

I prefer to see css being used,as it will always manage the path correctly now and broken image links will be a thing of the past.

Nina Meiers

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

JWhite — Tue, 15 Mar 2005 20:00:58 GMT

<%=SkinPath%> "localizes" the skin at runtime so that the skin is more "portable." The skinning document has been updated to explain this I think. Basically the skins were usually uploaded using the localized method and the skins didn't work as well when moving them from a dev xp machine where DNN existed in a virtual directory to a production server where DNN lived as the root of the website. By using the <%=SkinPath%> runtime code we get the SkinPath variable containing the location of the current skin and add it to the resource's path/filename argument and it will work in both instances.

Re: dnn3: questions for skinobject css class and <%= SkinPath %> image path

HolgMaster — Tue, 15 Mar 2005 19:54:53 GMT

Hi yiyi

i am also currently looking at the new CSS classes. Hard to find any references for it. What editor are you using to edit css style sheets?

holger

dnn3: questions for skinobject css class and <%= SkinPath %> image path

yiyi2005 — Tue, 15 Mar 2005 19:06:56 GMT

Hi,

1. I noticed that there is a new css class called skinobject and would like to know what is the best practice for that.

2. I also noticed that <%= SkinPath %> has been widely used in those sample skins that come with dnn3. Why is that?

Thanks!

yiyi