Richard Lewis-Shell <[EMAIL PROTECTED]>wrote:
Maybe (and I'm thinking out loud here) it would be better to have a
page-spec define its name instead of defining its name in the
application/library file? If there was some way to associate a page with a
library-spec (can a page belong to more than one application/library?) then
perhaps Tapestry could just go looking for all .page files, and save having
to put them in a application/library file.
The problem that I see here is collecting all pages into a .application file.
Personally I do not think this belongs in Tapestry (the runtime costs would be huge), but in a pre-processing tool such as Ant or Spindle. Coding an Ant task that finds all .page files in the project and adds them to the .application should not be hard to do at all, and I think it would resolve your issue.
In a sense, this is similar to what 'make depend' or the Visual Studio IDE do for C/C++.
What do you think?
-mb
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos, & more
faith.yahoo.com
