Hello
I also think it would be good to review the structure of themes today because they are overwhelmed.
For me, many basic things missing from the theme. For example, when we want to create a menu we have to go through the theme.hml to manually write the links and forwarding addresses. This stuff is easy for someone who knows HTML only for a beginner person is a drag. It is therefore necessary that all that is related to links through the core and a smarty base is incorporated directly into the theme.html like that, people will not have to put them manually.
Regarding the structure: Currently on Xoops we in three areas to determine preferences. Left blocks, the central blocks, the blocks on the right. If we want to add for example blocks we need to add footer in theme.html and plus they are not controllable from the preferences. If we look for example joomla, any changes made to the structure theme is controllable from the core.
On joomla there are two large files to create or change a theme.
templateDetails.xml : It is he who determines the name of the position
Quote:
banner
debug
position-0
position-1
position-2
position-3
position-4
position-5
position-6
position-7
position-8
position-9
position-10
position-11
position-12
position-13
position-14
xdposition-14
footer
These positions are the basic ones present. If we want to add another we simply add more ex
xdposition-14
It's position is determined by tp=1 option which allows you to see the structure of the theme:
ex : with the code we see that we have a location under the banner nome position-8
Quote:
We have more than to select the location
index.php : Who is the equivalent of our theme.html of this file, we can build the template of our theme.
should also be an option where each widget developer themes add their own options according to their theme as is currently being done on WP.
On the framework: XOOPS 2.6 decide to make these themes with the framework, it is also very well only should any administration xoops and all modules are also developing with bootstrap because otherwise I do not see the interest.
Something which is very inconvenient currently on XOOPS is the smarty <{$xoops_contents}>. Currently with this system, we can not display the content of a module in a specific area that does not contain blocks.
Sorry for my english
