[Slashcode-development] text -> data templates?

[Shane <sh...@lo...>]

One of the PITA things about Slash, for me (IMHO), has always been the  
language inside the stock theme's templates.

It's a problem for me when:

1. trying to keep up with the changes in CVS and keep a non-stock-theme  
up-to-date with the code

2. it's also been a problem when setting up sites for clients, they see  
some of the language and baulk at it

And once you change the language, then when you diff your theme's  
templates against the stock-templates (to find code changes) your  
language changes always make the template show as changed, so you must  
go have a look at it.

Over time this process becomes, well, painful.

On to the reason for sending this... I would be interested to know how  
many of you have run into this as being an issue for you.

Also, I was thinking that one solution would be to move as much  
language out of the general templates, and into the data\;*\;default  
template(s).

An example of where this could be beneficial is the new Slash::Login  
plugin's template loginForm:

http://cvs.sourceforge.net/viewcvs.py/slashcode/slash/plugins/Login/ 
templates/

Instead of


[% ELSE %]
    Danger, Will Robinson!

you'd do something like

[% ELSE;
     Slash.getData('loginform_err2')

If more text/language was only shown through the getData command, it  
might have the added benefit of making internationalizing a slash  
site's text easier. Because instead of changing a ton of templates,  
you're changing the language in the data* templates (I think there may  
be error* template(s) too, I may be wrong).

Any thoughts?

  Shane

PS - It's funny, I remember discussions over the past few years about  
getting the language out of the src and into the templates... :)





--
One gadget to catch them all, and in digital darkness bind them.