Hi,
there's a project with the ID 'cheetahtemplate' on
Sourceforge.net now. There was a cap of 15 char on the ID
so I couldn't make it plural. I've aded Mike and Chuck as
developers. Ian and Tom, do you want me to add you? If so,
I'll need your sourceforge login names. If you don't have
a SF account just go to their homepage and register.
cheetahtemplate.sourceforge.net is the initial homepage
(empty) and I'll get CheetahTemplate.org up as soon as
possible. sourceforge.net/projects/cheetahtemplate is the
project page with the CVS, etc.
I propose that we provide an updated copy of Chuck's
Template overview page as a start for the homepage and move
it to a sublink once something more substantial has been
built. Thoughts?
The new mailing lists are
[EMAIL PROTECTED] and
[EMAIL PROTECTED]
How should manage the mailing lists and the crossover
between Cheetah specific stuff and the more general
'templates' meta-thread that's been going on for the last 3
months?
I was thinking that we could use the new devel list for the
Cheetah-specific stuff and welcome any discussion of
Python-based templating systems/designs on the new discuss
list. Or is it best to keep the thread going on the
Webware lists?
The CVS import will take a few days. All registered
developers will have CVS read/write access. Up to this
point I've written most of the code, although most of the
ideas and decisions have come from collaborative
discussions on this list. Once the CVS is up I'd like to
open it up so you can commit your bug-fixes, docs,
examples, and extensions directly.
=========================================
- Mike, you've got great ideas for the docs
- Ian, you've got some ideas about data declarations and
the WYSIWYG issues that I'm sure could be worked out in
Cheetah. How about parsing ... of the placeholders?
- Chuck, you've got plans for the test suite.
- Anyone want to tackle the #extend / import issue?
- Anyone have more test cases? examples for the examples
dir? sections or tips to add to the docs?
- Is anyone a good artist or have ideas for a logo and a
page banner?
...
=========================================
All I ask is that:
- please discuss commits on the devel list
first, and announce them afterwards - just like Webware
- the test suite is run before and after every commit to
ensure nothing has been broken
- all changes are recorded with your initials in the change
log in Cheetah/__init__.py and in the CVS logs. The main
change log should record all changes under the version
number of the next release. Once a release has been tagged
and packaged, the next version # in this log will be
refreshed.
- all code follows the WebWare guidelines, with the
exception of using 4 spaces for all indentation levels and
lines (including docstrings) must be wrapped at 80 chars
- all var and class names are self-explanatory, nothing
cryptic or abbreviated to single letters
- all classes, funcs, and methods must have a docstring
- if you add new functionality please include examples and
documentation in the User's Guide and have someone proof
read the docs and test the examples
I'm going to be away from email for three weeks starting on
the 19th. Mike and Chuck have agreed to handle bug reports
and bug-fixes during that time. I'll be fairly silent next
week as well - knuckling down on my thesis.
I'm about to change the name over in the code. As part of
this, I'd like to change the TemplateServer class to
"Template":
"""from Cheetah.Template import Template"""
Any objections?
What about TScompile? What shall we call it now?
Cheers,
Tavis
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
