Re[2]: [ZPT] TALES Feature Survey

[Geir Bækholt]

Yes, i know my example seems weird , but when handing templates over
to non-technical content-editors , it suddenly makes sense again ;
basically giving them dynamic content which they can override manually
in the templates (or at least that is what it seems like to them...)

--
Geir Bækholt
Web-Developer/Zopatista
geirh@funcom.com
http://www.funcom.com

on or about, Friday, May 18, 2001, we have reason to believe that Guido van Rossum wrote something along the lines of :
>> - Please consider also adding a standard 'defaultcontent'-variable for the
>>  text-content of the element, not just the attributes..
>> 
>> ehm.. i see how this could be quite horrid for things like the 'body'
>> element, but it could be quite useful in some situations...
>> - but you could perhaps limit it to text-only-nodes ??
>> 
>> <h2 tal:content="defaultcontent | template/title">if anything is here,
>> it will display instead of the template's title</h2>

GvR> Hm, I don't like this one.  It's hard for the parser to make that
GvR> available (though I'm sure I could find a way), as you say there's the
GvR> question of what to if there's markup occurring in the text (though I
GvR> guess we could limit it to "only of there are no TAL/METAL tags in
GvR> it"), and last but not least, I don't think your example makes much
GvR> sense.  It would mean that the outcome of the choice could only be
GvR> changed by editing the template.  That seems backward.

GvR> --Guido van Rossum (home page: http://www.python.org/~guido/)

GvR> _______________________________________________
GvR> ZPT mailing list
GvR> ZPT@zope.org
GvR> http://lists.zope.org/mailman/listinfo/zpt