Yes, is a problem from the community but it affects Tapestry directly. I dont think that having a repository is enough...We should have strategies to build components. Not just wait someone need it, then build it and then upload it. The process should be more oriented in what the market and tapestry needs to survive in the market.
On 7/5/05, Pablo Ruggia <[EMAIL PROTECTED]> wrote: > This is not a Tapestry problem. It's the community (me included) the one > that should contribute with those components. I've created several > components and never upload them anywhere. I think you guys are in the same. > I think what we need is a more "official" site where to upload components, > and not personal attemps like tassel or tdelli. Perhaps a Tapestry > subproject or something like that. > > On 5 Jul 2005 15:09:07 -0000, Lennart Benoot <[EMAIL PROTECTED]> > wrote: > > > > > > I totaly agree. > > Personaly, if i had to make a technology choice now without knowing > > tapestry i would probaly go for JSF in favor of tapestry. One of the main > > reasons would indeed be the lack of immediatly available and easy to use > > advanced and nicely packaged components. > > I have the impression that a lot of effort is put into the technical > > aspacts of tapestry ( e.g. tapestry 4) but way too few in the packaging > > and presentation. > > As a matter of fact in my opinion tapestry will have to move fast or it > > will become some sort of Macintosh for web developers. Used by a small > > elite of die hards. > > > > Do not misunderstand! i absolutly love tapestry, it has potential and i > > hope for a bright future. We should be aware of stiff competition tough. > > > > Kind regards, > > Lennart > > > > > > >-----Original Message----- > > >From: Juan Esteban Maya <[EMAIL PROTECTED]> > > >Sent: 07/05/05 - 09:40 > > >To: Juan Esteban Maya <[EMAIL PROTECTED]> > > >Subject: RE: About a bigger Tapestry components library! > > > > > >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] > > > > > > -- "The passion for destruction is also a creative passion!" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
