First of all: I have no problem with option 2. But let's just consider a few things. Do we really expect a webgui.css to huge? How large is huge? It is possible, just like YUI, to make a webgui-small.css and a webgui-explained.css. The first would have no whitespace, newlines or comments and the second would have a lots of comments and a nice readable layout.

Let's do that anyway, regardless of whether we choose #2 or #3. Diona mentioned this earlier and I think it's a good idea.

Another consideration is: we could split it up when we find out that is has grown too large. Because we can load other stylesheets from the webgui.css we had earlier.

I think I would have a slight preference for a single webgui.css because of the overview it could provide if it is well structured and well documented - which of course it will be.

But: these were just considerations. I'm fine with #2 if that is the consensus.

Let's go with #2 for now. It will be more practical in the process of rebuilding a template.

It might turn out we overestimated the amount of css needed. Then we can still go for #3; it won't be much work to put all the files together. We could even do some "speed report" testing with both options and make a final decision based on hard numbers.

Rogier | United Knowledge
www.unitedknowledge.nl · www.webgui-help.nl