On Fri, Jul 01, 2005 at 03:35:50PM -0400, Cees Hek wrote:
> On 7/1/05, Brett Sanger <suppressed> wrote:
> > Not me. I agressively subclass, so there's not much to create. My
> > module just has my specific run modes, my instance script has any
> > particular configuration variables.
>
> I think the usefulness of this would come in setting up a nice
> directory structure that includes directories for libraries,
> templates, test scripts, and possibly even static html content like
> images/css/js.
A lot of this has to do with the "unique" development structure where I
work...an application does not exist in it's own directory. The module
is in the module tree, the cgi is in the htdocs tree, and the templates
are in the content tree. Those three trees have no particular
relationship. (The code tree reflects any module inheritance, the
htdocs tree the site structure, and the content tree a conceptual
struture that is sort of a mix between the two).
So there's as much work in telling a generator where to put things as to
creating it myself. Add in that I don't have any static content beyond
"$app->run()" (which my most recent superclass removes) and I'm not
winning out from a generator.
I've nothing AGAINST a generator. Anything to save time and effort for
new users of C::A is a good thing, and heck lots of experienced users
can benefit. I was just responding to the call for a show of hands.
--
SwiftOne / Brett Sanger
suppressed
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.