It seems to me that what we need to do is combine the component
libraries into one place. Also, if none of those sites has all that's
needed, expand the new site's capabilities.
We should probably move this discussion over to the developer list as well.
Jamie
Ron Piterman wrote:
+1
What I noticed is that many times you have to create components which
are trivial, but are not there.
Examples:
A Date component consisting of three Inputs instead of the JavaScript one.
A Property Selection which submits also on disable.
A Property Selection which shows values depending on another property
selection.
aso.
Tassel is at the moment a good repository, but has very limited
functionality.
I think a repository which is something like the eclipseplugins.org is
needed, + enabling hosting of components, improved documentation,
example and download of each component.
I wish I had the time to help realize such a site...
ציטוט Juan Esteban Maya:
I have been working with tapestry for almost 3-4 months and its really
nice. The development process and the productivity incressed a lot.
But what i really miss (well i wish) is to have a big and robust
component library.
This has been already discussed in the mailing list, but i guess it
deserves more attention. JSF, which i think is the biggest Tapestry
competitor has already a lot of Subprojects, componentes libraries,
even comercial ones(Well, yes is sun i know!) and i havent seen a new
tapestry Components in a while. I think this issue is fundamental to
new tapestry users. If i have to choose a new component technology the
first thing that i will look are the components that the technology
can offers...Tapestry is clearly behind JSF in this aspect.
Any thoughts about how can we, Tapestry users, have big component
library? Not just a repository.
Juan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
