On 2014-01-26 10:06, Stefan Koch wrote:> Is the order in wich those templates are includeded not a concern ?
or should it be strictly alphabetical ?
I'm a little inspired by the joomla module positions
http://docs.joomla.org/Module_positions
You can see plenty of templates at http://www.joomlart.com/ or extensions in http://extensions.joomla.org/ and I'd be so happy if this were possible in vibe.d with dub as the install manager
For ordering, the positioning would have to be defined in the filename e.g. top1search, top2menu.
I feel like the views folder of different dub packages should be freely modifiable (including the names of files for ordering), but their source code should never be touched. Changing the source code of any dub package should always be strictly through a configuration file. And these dub packages can be made to work together if this "include" structure can work properly.
Additional restrictions could be defined as inline D code in the included diet templates assuming they're built into a framework that evaluates some variables lazily from cache or config. e.g.
- if (This.config["modulename"]["is_enabled_for_route"]){
diet code...
- }
That's what I'm working on with my framework btw but I need some adjustments to make it possible :P
So, of course, the main content of a page is still pushed into the template.dt block through a block/extends. This really just solves adding multiple modules from separate libraries regardless of the build order.