[Zope3-dev] IMPORTANT RFS: Through the Web Site Development

[Jean Jordaan]

> Because of the way TAL uses XML namespaces, you can call an element 
> "tal:whateveryoulike". 

This is supercool, but Mozilla Composer [1], for one, screws up pages
with <tal:tags /> in them :((   I suppose it's inevitable that you'd
have to check your source editor to make sure that it doesn't screw
with either tal tags or attributes. It can be a pain if some users
later start using Composer, and finding that pages that always worked
now break.

[1] Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20021030

>   <tal:foo tal:replace="name" />
> 
> Which is equivalent to
> 
>   <tal:bar tal:replace="name" />

Now this I'm not so mad about. I'm sure TAL will learn to distinguish
the foo/bar bits and to do something with them. For example, I might
want to define a controlled vocabulary for my project so that I don't
get stuff like <tal:display .. /> in one place and <tal:show ... /> in
the next. Used purely for documentation purposes it would be worthwhile
already.

Possibly this could be used for shortcuts: instead of

   <span class="author" tal:content="here/Author">A.N. Author</span>

one could have

   <tal:author content="here/Author" />

This does influence what a DreamWeaver user would see, but I don't
think it's worse than

   <span tal:replace="here/Author">A.N. Author</span>

where the DreamWeaver user would see a <span> tag, possibly with CSS
styling, that wouldn't show up in the rendered view. To say nothing
of the results of <tal:replace="structure here/whatever" />. You could
do this to give the DreamWeaverer something to edit:

   <span class="author" tal:replace="nothing">A.N. Author</span>
   <tal:author content="here/Author" />

-- 
jean@upfrontsystems.co.za