Hello, Nathan Bubna wrote:
So, to get the ball rolling... i see three 'F's we need to address:FOLDER(S) - do we want each library (view/tools/struts) to have their own macro library? certainly different macros will be associated with different tools (some struts, some general tools, and some needing no tools at all). - or should the macros have a completely separate folder(s) all to themselves? <suggestion>i'm think it'd be best to associate macros with the library they'll be using. (general ones in view/src/macros, ones that use tools in tools/src/macros, and struts ones in struts/src/macros)</suggestion>
Agreed. What about examples using those macros?
FILE(S)
- should each macro have it's own file? this would make it easy to find
them and update them individually. of course, this would make the
velocimacro.library property (in the velocity.properties) a nightmare. then
again, Ant does have a <concat> task that could combine various ones at
build time.
- or should we keep similar and/or dependent ones in the same file?
(i'm thinking that if we allow macros to depend on other ones at all, they
pretty much have to be kept together to avoid serious headaches.)
- or should we keep them in one big template? (please don't support this
:)
<suggestion>my preference is to try and keep them separate for the most
part. any macros that depend on another should probably be put in same file
(e.g. #macro( foo ) foo! #end and #macro( bar ) #foo() #end should be kept
together)</suggestion>
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.
If a tool requires macro support, does that change anything? Can't see how it would.
FORMAT
- should we have a coding convention? what should it be?
- how do we want to doc these things so that they come with proper use
instructions and due credit?
<suggestion>
#**
* this macro is just meant to demonstrate my
* favorite macro style. btw, this style is meant
* to produce readable output while still having
* readable code.
*
* @author <a href="mailto:[EMAIL PROTECTED]";>Some Fool</a>
*#
#macro( example $whatever $whatNot )
#set( $output = 'Actual content' )
$!output is best non-tabbed.<br>
#if( $whatever )
$!whatever is safer with the '!'<br>
#end##
#foreach( $woogie in $whatNot )
Curious about the empty line-comments and extra line above these
$!{woogie}s?<br>##
#end
Then you should try this macro out with and without them.
#end
</suggestion>
did i miss any questions/issues?
Nathan Bubna [EMAIL PROTECTED]
-Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
