I've set up a new project on Tapestry360 called tapx (Tapestry Extensions). This is where I can put code that can't live at Apache (due to licensing problems).
The first module is a DHTML calendar component, a wrapper around Dynarch Calendar, an LGPL calendar widget. I consider it the "Cadillac" of this space, and it snaps into Tapestry quite nicely.
Just dropping this new JAR into the classpath not only makes the new DateField available, but also enables it as the default date editor when using BeanEditForm.
The library requires Tapestry 5.1.0.1 or better.
I expect to add many small utlilities here.
Thanks for all the great work. I come accross the project chenillekit and want to know if some of the components they develop could not make it to TapX too?
ReplyDeleteBest great from Germany
CheilleKit is now hosted at Tapestry360 as well. Tapestry is built to allow lots of little pieces to "stack" together, there's no overwhelming advantage to grouping them together, and having them individual gives the developers, like myself, more lattitude to track against changes in the core framework.
ReplyDeleteHi Howard,
ReplyDeleteLooks nice.
How about exposing some configurability of the underlying component, such as the date/time format? (which would also allow enabling the time chooser within the calender)
The templating library sounds really exciting. I'm currently using Velocity to send email messages from a quartz job (like "your account is about to expire" etc) and it would be great to use the same template syntax for those messages as we use in the webapp.
ReplyDeletewow, thnx u for making me loves tapestry...
ReplyDeleteThe component already supports a format parameter. Adding a parameter to enable time editting would be a snap ... at it to the Tapestry360 JIRA!
ReplyDelete