Chris Withers wrote:
>
> Ken Manheimer wrote:
> >
> > Python Zopelet
> > Perl Zopelet
> > XSLT Zopelet
> >
> > Zope-specific, runs on the server, shows the implementation language,
> > won't be confused with non-remotely-editable functions, methods, scripts,
> > code in general.
>
> ... Zopelet means absolutely nothing, and will just add to
> confusion :-(
I agree with Ken: I think it's a good choice because it *is*
Zope-specific -- I think Zope should be in the name. If you
are using Zope, it will be meaningful; if not, it won't -- and
shouldn't be.
I also think "Zopelet" does not "mean absolutely nothing"
in terms of connotation -- it carries the connotations that
Ken mentioned, which is good.
My $0.02.
-- Steve.
oo _\o
\/\ \
/
____________________________________________ oo _________________
"Sometime you're the windshield; sometime you're the bug."
- Knopfler
Stephen C. Waterbury Component Technologies
Code 562, NASA/GSFC and Radiation Effects Branch
Greenbelt, MD 20771 Engineering Web/Database Specialist
Tel: 301-286-7557 FAX: 301-286-1695
WWW: http://misspiggy.gsfc.nasa.gov/people/waterbug.html
_________________________________________________________________
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )