I've just put up 2.2-alpha-3. Along with a bunch of bug fixes by me and
Richard Lewis-Shell, the major improvement is component libraries.
Applications can now add libraries. Libraries contribute components, pages
and engine services to the application. Libraries can, themselves, use
libraries.
Here's an example; in a .application file:
<library id="contrib"
specification-path="/net/sf/tapestry/contrib/Contrib.library"/>
In a .jwc (component specification) or .page (page specification), you may
then use:
<component id="inputStuff" type="contrib:Palette"> ....
The "contrib:" portion of the type identifies the library in which component
Palette is defined.
If you have to, you can still have a compenent named "Palette" defined in
your application, that prefix allows Tapestry to disambiguate the name; that
is, to precisely know which Palette you will use.
When there is no prefix, the application is searched first, then the
Tapestry framework (for basic components such as Insert, Conditional, etc.).
This means that you can now override the components provided by the
framework if you like (not advised, however).
I think this is a big step forward for Tapestry; It will now be possible to
create and distribute extremely complex components; components that require
their own pages or engine services., This really brings Tapestry's "drop in
a component and forget about it" quotient to a new level.
I think there's still a few more alphas in 2.2; there are a couple of other
things I may want to get implemented in the next few weeks.
These changes are going to make poor Geoff's life hell; it may be a while
before Spindle catches up to Tapestry 2.2. Don't forget to send him notes
of thanks and encouragement!
Howard
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
