AlexT
Very good suggestion. It is worth to discuss it.

Both implementations 1) like you offered and 2) current dolphin 7 implementation have some pros and cons.

Your suggestion is good for template maintainer only. It is not easy to develop templates in this case but only maintain it.

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

Maintain is a little bit easier, because path among templates directories see more are shorter:
/templates/tmpl_uni/modules/vendor/some_name/css/some.css
vs
/modules/vendor/some_name/templates/tmpl_uni/css/some.css
But you still have to go to different directories to change different css and other files.

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.

Another thing - main templates files, like header/footer, design boxes and many more standard design elements are still in common template directory, and in 95% cases you do not need to go to far module template directory. Before Dolphin 7 all these html code were located in raw php files and nobody changed it, now it is separated and places into different directory, it is more convenient than before IMHO.

As the summary, this choice will allow easier module development, installation, uninstallations and upgrade procedures. Also I am sure that you as a site maintainer will benefit from it too, as you have many modules and only one template.
MichelSwiss
Hello Alex :-)

Thank you for your answer ;-)

I don't want you to spend too much time with this topic... If only me, I can live with that ;-)
Just one thing. You are right in that I had to choose to use only one template. Because if I have for example a white template and a black one, I will have problems with images, icons, zodiac icons..., that are in common (templates/base) for all templates and that will not match every templates colors... (I changed all these images and icons with PNG24 see more icons that have much cleaner borders than .gif)

At least maybe can you merge templates/base and templates/tmpl_uni ???, for the modules too ???

Thanks again Alex ;-)
TheSoMeEx
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
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.046385049819946