Nathan asked:
> I'd like to know if people still see this dvsl
> documentation of tools as really useful and
> worth the significant effort it
-1
(I appreciate that Gabe created docs, but I think the content could be
presented more plainly for users.)
-1 on Nathan's suggestion to ONLY use Javadoc.
Why? I think we have two audiences (Developers & Designers) and believe
each need different documentation. I think we could create for
Developers a single-page doc on tools and configuration. And for
Designers, something more tangible like the User-Guide doc.
Cheers,
Timo
------
Developers need to know:
<tool>
<key>msg</key>
<scope>request</scope>
<class>org.apache.velocity.tools.struts.MessageTool</class>
</tool>
Designers need to know:
----
Struts provides localization of 'messages' using a message resource
file. It can also substitute up to five 'replacement parameters' into
the message.
Assuming that the message resource files contain the following messages:
title=Welcome to Velocity for Struts
test=This message has five replacement parameters: {0}, {1}, {2}, {3},
{4}
then the following Velocity script:
$msg.get("title")
$msg.title
$msg.get("test", ["bear", "wolf", "tiger"])
produces this output:
Welcome to Velocity for Struts
Welcome to Velocity for Struts
This message has five replacement parameters: bear, wolf, tiger, {3},
{4}
-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
