Bill said: ... > What about examples using those macros? yeah, we should probably either work them into existing example apps or create a new example app just for demonstrating all these. (i'm leaning toward the latter.)
... > Agreed. As you suggest, keep separate where possible and use Ant to > generate one template. The generated macro template for each type > should probably be named differently for each of tools, view and struts. > > Also, instead of concatenating all the macros into one template, why not > create a template that does a #parse() to load each macro file? This > also makes it easier to comment out macros as it's only a single line > change. hmm. yeah, as long as that works and no one has any complaints, i think that sounds like a pretty good way to go. > If a tool requires macro support, does that change anything? Can't see > how it would. I don't think i'd support creating any tool that required the support of macros. ... > Did someone write a javadoc like tool for Velocity that could be used to > generate HTML docs? ... you know, it seems to me that i remember hearing about something like that too, but i don't remember where or what exactly it was. it might come in real handy. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
