[TransWarp] PROPOSAL: New peak.web.template terminology/explanation

[Phillip J. Eby]

At 08:09 AM 7/22/03 +0200, Roché Compaan wrote:
>Whats wrong with "view" again? "View" can be quite general and less
>helpful than one wants but maybe the context we use it in saves it here.

You answered your own question.  :)  It's too general.  The concept of view 
could be applied to a lot of things in peak.web: location components are 
"views" on domain objects.  I'd rather save view as a descriptive term that 
I can apply to both location components and DOMlets.

I suppose we could use 'template' instead of 'as', though it's a lot more 
verbose, and runs the risk of confusion with the idea of a template 
itself.  We could also use 'factory', 'generator', or any number of other 
terms.


>The concept of DOMlet is fine but I must still get used to the name. If
>I don't by the end of the day I'll let you know ;-)

Well, we need to have some kind of decision by the end of the day.  At this 
point I'm tempted to just do what I threatened yesterday and have a way to 
use alternate vocabularies, so people who want model/view/pattern 
compatibility with Twisted can do that, etc.  The main reason I don't want 
to do that is that if people put examples out there using an alternate 
vocabulary, it's going to be harder for new users to figure out what's 
going on.

For me, the leading contenders are still data, as, and format-of.

If the folks who don't like 'as' could suggest a similar part of speech 
(e.g., 'with', 'in', 'using') that they're happy with, I could go with 
that.  I'd suggest "class" but that is also used by HTML and so seems a 
dangerous choice.  "type" I think is only used for input tags, so that 
might be a safer choice.  And of course we could be explicit, and just say 
"domlet".  (But then capitalization is somewhat in question, if the proper 
noun is DOMlet.)

Anyway...  something has to be decided, so if the community can rally 
around a firm choice that I don't fatally dislike (i.e. "view" is right 
out), I'll consider it.  Otherwise, at the end of the day I've got to go 
with what Ty and I worked on.