Howard,
Is that possible for us to have a site as
http://eclipse-plugins.2y.net/eclipse/index.jsp, which
will allow us upload componets, download them, comment
on them, rate them. I believe that will encourage more
people to participate in this great project. As every
one knows the power of tapestry components, but still
it is too difficult to find components from the net.
I think the following will make a component
useful,
1. component archive
2. component doc
3. dependency and supported tapestry version
4. sample code/template
5. screen snapshot
6. user comments, rating, download counts
Tapestry is a technically superior project, we now
need some kind of effort non-technically to make it a
perfect project. :-)
Yunfeng Hou
--- Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Actually, he was making some suggestions to go
> beyond what Tapestry
> provides today, some of which would be useful to
> tools like Spindle
> and Palette, or even to distro communities like
> Tacos.
>
> On 7/25/05, Nick Westgate <[EMAIL PROTECTED]>
> wrote:
> > Hi.
> >
> > Howard's book "Tapestry In Action" explains how to
> do this in
> > chapter 6.9 "Packaging components into libraries".
> >
> > Components are (1) packaged in a jar, (2)
> specified in a
> > ".library" file, (3) included in the classpath and
> configured
> > in the ".application" file, just like the contrib
> library
> > (bundled with Tapestry) and the base library (from
> T-Deli).
> >
> > Cheers,
> > Nick.
> >
> >
> > Yunfeng Hou wrote:
> > > I am thinking about that if Tapestry could have
> a
> > > consistent component packaging mechanism, which
> will
> > > ease the development, the usage and tools such
> as
> > > spindle. Here's what I thought.
> > >
> > > 1. components should be packaged into a jar
> file, or,
> > > may be we can name it as tapestry archive(tar)
> :-)
> > > 2. components should have an entry in META-INF,
> just
> > > as hivemind.xml, it will list all libabry files
> this
> > > archive contains.
> > > 3. component archives can be put into
> > > WEB-INF/components directory, this can be
> default or
> > > be configured in tapestry.application file, or
> as
> > > servlet parameter. I prefer the latter, since
> most the
> > > time my tapestry.application file contains only
> the
> > > library reference. I think tools like spindle
> can easy
> > > find all components there.
> > > 4. tapestry servlet should have a context class
> loader
> > > including these archives which can be referenced
> by
> > > all pages it serves.
> > >
> > >
> > > Yunfeng Hou
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail - You care about security. So do we.
> > > http://promotions.yahoo.com/new_mail
> > >
> > >
>
---------------------------------------------------------------------
> > > 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]
> >
> >
>
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
