>
> I would also like to change the structure of the layout for
> an app in the TDK. Scarab has some good ideas and there model
> is working well for them. But I'd like to hear all the ideas
> and then push to get a unified, agreed upon setup into the
> TDK before we release 2.1.
>
I really like the way that Scarab has the src directory at the top of
the tree. The one thing it suffers from is having to build in order to
move a modified template into the webapp directory for changes to show
up. (You could say it suffers the same problem wrt java code, but that
requires a build anyway.) I actually don't find it that much of a
hassle, but some might.
Jon has improved this a bit in that the CVS dir is copied into the
webapp directory as well, so that you can make modifications directly in
the webapp directory. I find it too easy to just delete the target
directory and do not want to have to worry about throwing away changes,
but I guess it should be easy enough to make the mental adjustment. It
is probably preferrable for template engineers to work within the webapp
directory, to avoid the build step. You definitely want your project in
CVS to work on templates directly in the webapp directory with a Scarab
like setup.
Not sure if a web.xml could be setup to look for templates rooted
outside the serlvet engine. And if it could be done, it would be
desirable to have a build property to switch things to a production
mode.
So I vote for a Scarab like structure, but there is still room for
improvement.
John McNally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
