How to put only templates in one directory tree for itself, separate it from the code, yml files and

I suppose it would be fairly easy to implement in symfony
framework that 
it seek after templates using a specified template root like
app/templates.
What do developers say about this ?
Maybe we should post this to dev list as well


Tim Hawkins wrote:
> Im also interested in this concept, It would be cool to
have a 
> separate tree for all template, layout and view code,
and also place 
> the database config into a similar tree.
>
> This would as well as separating the views etc for web
devs to work 
> on, allow the same app to have switched roots and thus
expose 
> different interfaces/skins on different URLs,
particularly for 
> international implementations where multiple languages
are used ie 
> www.xxx.co.uk, www.xxx.fr etc. This would enable intl
sites to share 
> the same code-base but have unique databases and
presentations.
>
> Perhaps something in the routing configuration that
sets the root of 
> the template tree and the name of the database config
file, based on 
> the host-name of the service.
>
> On 15 Sep 2006, at 23:18, Haris Zukanović wrote:
>
>> I wish to let a web designer work on templates.
>> Can I somehow separate all templates, partials and
stuff in one 
>> separate directory so that he is not allowed to
change any code in 
>> the project?
>>
>>
>> HAris
>>
>> -- 
>> To unsubscribe, e-mail: user-unsubscribesymfony-project.com
>> For additional commands, e-mail: user-helpsymfony-project.com
>>
>
> Tim Hawkins - Solution Architect
> yim: tim_hawkins4
>
>
>
>
> -- 
> To unsubscribe, e-mail: user-unsubscribesymfony-project.com
> For additional commands, e-mail: user-helpsymfony-project.com
>


--
To unsubscribe, e-mail: dev-unsubscribesymfony-project.com
For additional commands, e-mail: dev-helpsymfony-project.com

Dev

I think symfony needs to be able to handle themes in the
core, so a  
user can be given a theme just as they can a culture
(default, by  
default).

If the theme changes, then symfony first looks to find the
template  
theme.template.php, if it exists it uses this, otherwise it
uses just  
template.php.

A theme should also be able to override the view, so
therefore a  
theme should also have it owns view.yml.

view.yml
...
   javascripts: [default]
   stylesheets: [default]
   layout:      [default]

fr.view.yml:
...
  javascripts:  [default]
  stylesheets:  [fr]
  layout:       [fr]

The themes view.yml is merged with the defaults, so if you
don't  
override a setting the default one is used.

This change would be also be BC.

A theme could then be created for different cultures,
different  
colour schemes etc, and if the theme doesn't override the
default  
view, then the default is loaded.

Any feedback?

Thanks

Joe

--
To unsubscribe, e-mail: dev-unsubscribesymfony-project.com
For additional commands, e-mail: dev-helpsymfony-project.com