Claude said:
>
> > Is everyone happy with the toolbox stuff?
>
> Are we speaking of the veltools subproject, or of the velstruts
subsubproject ?
>
> (release grannulosity annoying question ?)
a good question. this does make a difference for me. i'm very happy with
the velocity-struts package. i think that's working great. as for the rest
of the tools subproject, i still have a few changes i'd really like to see.
the biggest one is the ParameterParser in the tools package. i still find
its current state to be needlessly unwieldy. i submitted a patch to make
it more user-friendly and fix a bug in getNumber(String), but i haven't
gotten any feedback on it nor seen it committed.
apart from that, the only other issue i know of is Tim's question:
Tim said:
> How would I disallow an HTML designer from invoking any public method
> they please on that $application variable? (ex.
> $application.removeAttribute("it_would_be_bad_to_remove_me")
i also submitted a more hesitant patch/answer for this. it worked for me,
but perhaps it needs further review/discussion?
overall, i'm pretty happy with things. i did a fairly simple
proof-of-concept app with velocity tools/struts some time back, and now i'm
actually in the middle of rewriting a very large/complex app with it. it's
going quite well so far. this time i've had to extend the VVS to do some
more fancy things (layouts, custom error screen, etc.), but the rest is
pretty much sufficient as is (except, of course, the current
ParameterParser. i'm using my patched version.).
Nathan Bubna
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
