Hi, Hope I attracted people into skins, design and core. Some of us have seen challanges in controling individual module font's and colors through CSS files as it comes to core modules and others.

Say following scenario. You have a simple module that reads a temperature and present the value. the presented string is controled in a CSS file with the class .Temperature { ... }

in the module you can select a sorce probe. Probe A and Probe B.

you place TWO temperature modules in the leftPane. you like the temperature A module to be bold blue, and the B module to be Italic yellow.

Hard to do.

if we could have the option to specify a prefix if needed to each module we could make individual classes by module, and the CSS files would be somewhat persistent.

Ex.
Class Prefix: APROBE

Action: module would concatenate the given Prefix to the class in the HTML code that would be called APROBETemperature

Hope it's understandable, and is easy to implement in the .ascx code directly.

<td Class"<% = Me.Class.Prefix %>Temperature">10 F</td>

Cheers,
/Rob

If I understand you correctly you can do this with CSS (using #). It has allready been discussed here: view post 482513. Search for first accurance of "#" character as it's a long thread.

or in short... put on some TD or DIV in one container an ID="something" and then in CSS use something like this:

.title{


...something...


}





#something .title{


...something differnet...


}

Now use this container in some page and also use other, regular one (without ID="something") on the same page - you'll find out they have different style for titles! You can do same for .Normal class or any other class ofcourse.

Now you can put ID in container or somewhere above Pane so styles of modules can change after moving from pane to pane! Many interesting things can be done this way.

I hope this is what you searched for.

Hi, sorry I should have continued on the thread pointed out.

Yes that is a valid solution, requires a little more job and some (Almost redundant) containers that will show up in the list, but valid.

Positive things for an added prefix in module settings:

The bandwith required for the reflection of the prefix and the injection of it's occurence "in code" is very small. This also makes the skining solution migrate neatly with the core and CSS. (Makes more sence from a user/designer perspective)
(Remember all people involved in a DNN site launch are not developers. Btw the skin designers needs a little more support from module designers. ie. what classes exist, and how are they used. "saves the local dev guy some rev.engin.")

Sorry again, should have continued on the thread. I was trying to simplify the problem and point out the relatively low effort to make it happen in the core modules, and serve as a suggestion for "3.rd parties" as new modules appear.

But the solution in the previous thread works fine, maybe a little extra complex (from a human perspective) but we all have to evolve ;o)

Cheers,
/Rob