The extensive effort I put into my skin.css file wasn't primarily done to make the FCKeditor work.
It was done in order to be able to quickly build tables CSS skins for my site. I had discovered that changing the type sizes, color, physical layout on an existing skin to get a new skin was much more work than it should be. By separating this correctly once, I can focus on the effort at hand, and limit both the number places to tweak the number of side effects.
The fact that I figured out some of the witchcraft required to make the FCKeditor see the same view of the world was a pleasant side effect.
Now i need to figure out how to put several related skins in the same zip file and how I should name the .css files. For example, DNN has several "blue" sinks in the same zip file. They even have both horizontal and vertical menus in the same zip file. This can be done because there is a lot of context for the tables in the .aspx file.
With an all css (div based) skin it is mostly in the .css file. So do I:
Create matching aspx and .css files (design1.aspx & design.css) for each design and have no skin.css? - This will make for lots of duplicate code/classes and many places to fix an error
Do I have several aspx files and a single combined skin.css with lots of classes and complexity?
Can I have the physical layout and colors in the design1 pair and common code for classes in skin.css?
So many choices and so little time ---
/DaveS
/DaveS