On Thu, Mar 09, 2006 at 02:38:48PM +0100, Paul Everitt wrote:
> One little Python script, maintained as part of the standard
> distribution, referred to ubiquitously as the right way to start, would
> have more impact on Zope adoption than nearly any other software
> activity (save, perhaps, for zope.bobo). All IMO, of course.
We do already have bin/pyskel, which is useful as far
as it goes, but that's of course not very far.
I'd really like to see some more scaffolding.
Unfortunately there are so many use cases, we could
easily get bogged down on the details.
For example, I can imagine:
* Create a skeletal package structure.
input: name of package, e.g. foo
creates (if they don't exist):
* Given interface(s), generate a skeletal class
and supporting files.
creates (but warns and exits if files exist):
create an interface test in
add some wiring to
create a view class in
create a template for that view class?
create an edit form using a template? or
zope.formlib? or what?
create an add form using zope.formlib?
or a template? or...??
Lots of options here!
Probably the best initial approach would be
to make it modest but trivially extensible so
you could write scripts that leverage it but
do what *you* want for *your* project.
Several obvious candidates for implementing stuff like this:
Paste Script and Paste Templates
Zope3-dev mailing list