Hi Alex! You make some very valid points.

You said:

"During template development process designer do not know which modules are installed and can not include css, images etc files for modules."

That is true. My point is that by using CSS standards for module design and creation, and by offering a separate CSS file to install into the templates directory, then the same problem that is currently (every module has it's own CSS parameters and needs, etc.) will be MORE EASILY solved, see more because the CSS will be in exactly the place it needs to be to find it and modify it.

In addition, with such standards, it would also be easy to note in the CSS code which pieces of the CSS are "new to dolphin," instead of inherited. This could make it very easy for moderate newbies even to change their code.

For example, a new module has a certain type of image for background. This would be noted in the CSS, and it could be changed or not, based on the template maintainer's desire.

You said:

"But it will make modules development, installation, uninstallation, support, upgrade and so on more complex and difficult. Site owner will have more work too - remove, upload files to different directories every time a little module is installed/removed."

Ahhh, one small upload into the CSS directory? Not such a difficult addition, IMO. 10 seconds, tops. Small price to pay for knowing where all of the non-code design changes reside.

As far as Dolphin 7, I cannot speak to that or it's ease. I know that if I continue with Dolphin, I will find a way to style it to my liking. I always have, LOL!

I just read what others have said, and the code in the templates I have looked at, and I see an extreme lack of flexibility in layout and design that will hold Dolphin back. If this software truly does get huge, it will be a problem with people having sites that look (essentially) like everyone else's.

Thanks for making me think this early in the AM! *smiles8