Hi template and themes coders,
I would like to rebirth [extension by plg] Zen. I wonder if I should create a template (heavy, complex to maintain) or a theme.
Instead of thinking on my own, I wonder how you (grum, saimon, flop25) came to the conclusion that gally, simple or flopure should be templates and not themes.
Bye
Offline
for me it's just for technical raison : you can't do all what you want with theme... this was before the prefilter etc because now with the theme juzza and swan's themes, I think I will make a complete check of all what I did. Maybe floPure will diseapear... but in a first time, I will wait the evolution, in therms of compatibility, of juzza and swan's themes
The template can also be a good idea in your case : the simplification of the structure could make the template lighter than a yoga with prefilter. So it may be a benefit for speed : faster to compute and display and also less things to store in memory for the navigator
You can also make a theme for an other existing template ... you will be the first to make a theme for a custom template not made by the same author
Last edited by flop25 (2010-01-19 14:47:41)
Offline
plg wrote:
I wonder how you (grum, saimon, flop25) came to the conclusion that gally, simple or flopure should be templates and not themes.
I was not in the list.
I will try to explain why Juza (only 1 z) is going to be a template and not a theme.
Juza: What is Juza? (for people who don't know).
Juza is an advanced theme with a lot of new concepts.
It also require Javascript and involve jQuery on visitor pages.
Several menus, undevelopped categories menus and developped categories menus, new thumbnails, new title attributes for a better SEO.
And more.
Because jQuery does not work as it should be on several browsers, because jQuery does not providing the same results depending on its versions, because Juza is doing too many things, Juza will be provided as a template (an advanced template) and its themes will provide mainly colors.
Exactly what themes should bring: colors and/or background.
What can be the improvements for coming releases?
- Avoiding tpl creation: A template could say "yoga" is my default, if I don't provide the search.tpl then use the yoga's one.
- Missing default (yoga): in such case the default will be found in template-common.
- In addition Icon-set management could be introduced (New) at template level and/or at theme level.
What could be the final result?
Template: smaller than today.
Theme: could be shared between templates (easier to produce).
Icon-set: could be shared between template and themes (Job of specialists in icons).
That's my humble o... (opinion but not asked for).
,-)
Offline
Hi,
basically I made a template because a template is the right place to modify the structure (html) whereas a theme should only modify the appearance (css). Of course you can modify the layout with css, but as I wanted to deeply modify the layout, a template was obvious: lighten the code layout, do less requests (merge css files, no icons ...).
With a theme you have the default behaviour of the template (too many css files or icons in yoga for me ;-)). You can hide icons for example, but the requests are still done.
- Avoiding tpl creation: A template could say "yoga" is my default, if I don't provide the search.tpl then use the yoga's one.
would be great ! (there is this system in dotclear 2)
Offline
The same reason than others :
- I need to change/complete the HTML page to do what I want
- I need to use JS & jQuery
- I have implemented a .conf file for each theme, allowing to set some interface options
Making Gally looks with the yoga template wasn't possible.
Offline