It seems to me that the Tapestry developer comunity should be a big part
of the decision making process as far as this project is concerned.
Without that this project doesn't make sense.
Cheers
Hugo
Jamie Orchard-Hays wrote:
No biggie.
Jamie
Todd O'Bryan wrote:
Could you *not* move it to the developer list? Users (who are not
Tapestry developers and tremble at the mere thought of wading
through the magic that is 4.0) develop and use components and are
actually capable of helping develop this site and the components
that would make it up. The whole point of Tapestry is, after all,
that users can create their own components without being conversant
with Tapestry internals.
Unless people are freaked out by the quantity of messages (which,
given previous conversations along this topic, should peter out
fairly quickly), I'd say leave it in users. This is not about
internal stuff that only has to please the developers. This is about
exactly where users live and breathe everyday.
Todd
On Jul 5, 2005, at 12:03 PM, Jamie Orchard-Hays wrote:
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: tapestry-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[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]
---------------------------------------------------------------------
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]
