> A good portion of the items on our TODO-1.0.txt list are done now. We plan
> on doing a 1.0b1 release sometime today (Monday).
Great! I'll be a 1.0b1 tester.
> This is one hell of a great piece of software. It is feature complete,
> tested, and documented. Cool!
Ditto!
Great work done! Velocity is *wonderfully* usable the way it is now!
Next are just notes to avoid having simple requirements being
forgotten which might go into a post 1.0 release.
A. I beleive we should tackle the introspection problem (package
protected Http* interfaces...) I'm offering to look at it and
find the *correct* solution. I can schedule it to be done by June.
This has bugged me already in an earlyer project with XML classes...
B. Whitespace handling:
#if( $foo )
#set( $bar = "woobie" )
#if( $bar )
Velocity is great! (but why did the spaces on the lines above indent this one?)
#end
#end
As I've stated earlyer I believe standalone directives should be
transparent to the output. Or even have a flag within the directive
telling if it should gobble whitespaces around it (only when standalone -
e.g. "\n\s*#\w+\s+\(.*\)\s*\n" ).
Since this is not priority to html output (is just an option to get
it nicely formatted), it should wait past 1.0 release... Currently
I do :
#if( $foo )#*
*##set( $bar = "woobie" )
Velocity is great!
#end
--- or ---
#if( $foo )
#**##set( $bar = "woobie" )
Velocity is great!
#end
C. We might think of having a parser simplification and
orthogonalization. Velocity syntax is *really* simple now and
should be able to be parsable by *simple* rules.
It would be fun to parse a VTL template into a JDOM-XML tree and
to use the visitor pattern render it!
Just my 2c for a Velocity 1.1 or 2.0 release...
Cheers,
Chirstoph
