Jesse Kuhnert wrote:
I think I'm ready to start doing actual development work and was wondering
what the best way to go about developing an example app would be? Should I
just start enhancing the workbench or create a brand new example? If brand
new, did anyone have any ideas on what it should do ? ;)
It would also be nice to be able to reference running demo's in the
component documentation the way that tacos is doing, but I'm not sure if
javaforge will be able to handle that kind of load, I guess we'll find out ?
Does this sound like a bad idea?
jesse
Jesse, IMO it'd be better to continue work in documentation (in the form
of user guides, developer guides, etc) than to do
yet-another-example-application - as much fun those could be.
Besides, there's one thing that I'm actually looking forward to in
Tapestry 4.1, and that's component contributions. As my Tacos lists's
comment was saying, I'm trying to implement a mask edit solution using
Dojo's event connect and render contributions (as in the AjaxEventSubmit
component). But that Tacos-specific render contribution could go as a
standard way of "decorating" base components.
Some things I think should be done using decorators (I know, some of
them already are, but the mechanism is not very clear to me - there's no
developer's documentation):
- Validation (Tacos's is more dynamic but a bit more stiff, Tapestry's
doesn't use standard Javascript libraries, that bugs me)
- Formatting (There's a pluggable implementation already, right?)
- Ajax Events (Already implemented in Tacos)
- DHTML Events (With this I'm talking about pure client-side events,
such as disabling a field when another one is selected, etc).
- Masks: That's DHTML but it's a specific concern of mine so I put that
separately :P.
etc....
So, this is a suggestion of where I think effort could be better spent.
I know I'll actually be implementing the mask solution ASAP.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
