Plugin Article/Pamphlet, was: Re: Googlecode Maven Repository for External Struts 2 Plugins

[Dave Newton <ne...@yahoo.com>]

I'm writing a short (30-40pp) Lulu PDF on creating
plugins-with-tags as part of the jQuery tags.

d.

--- Musachy Barroso <mu...@gmail.com> wrote:

> We do need an article explaining how to write
> plugins, specially how
> to create tags in those plugins. People email me a
> lot asking how to
> get started with a plugin.
> 
> musachy
> 
> On Nov 27, 2007 12:35 PM, Philip Luppens
> <ph...@gmail.com> wrote:
> > On 11/27/07, Matt Raible <ma...@raibledesigns.com>
> wrote:
> > > Marketing is easy - finding the time to do it is
> the hard part. Maybe
> > > someone should write a Developer Works article
> on Struts Plugins? I
> > > say DW because it seems to have the widest reach
> among online
> > > articles. I have connections if anyone is
> interested in doing this.
> > >
> > > I'd also like to see Don write an article on the
> REST plugin - his
> > > presentation at ApacheCon was pretty impressive.
> >
> > Voila, that's the kind of thing that we'd need
> more.
> >
> > Struts 2 must be the most 'quiet' framework I have
> ever encountered
> > (for such a big & mature framework) It's like
> there never was a hype
> > fase (probably due to the webwork inheritance) -
> note: hype is used in
> > a positive. And yes, I'm as guilty as the next one
> for not raving
> > about it more on the internet (probably even more
> lately).
> >
> > We have quite some plugins, some have been
> downloaded over a 1000
> > times, yet it seems unnaturally quiet on the
> plugin front. Is it
> > indeed due to 'bad marketing' ? Or do users just
> don't care ?
> >
> > - Phil
> >
> >
> > > On Nov 27, 2007 10:15 AM, Philip Luppens
> <ph...@gmail.com> wrote:
> > > > On 11/27/07, Frank W. Zammetti
> <fz...@omnytex.com> wrote:
> > > > > I don't disagree with most of what you say
> here, and what Phillip says in
> > > > > his reply, so let me make a more concrete
> suggestion: make the plugin
> > > > > registry much more prominent on the Struts
> home page (that is to say,
> > > > > mention it at all, since I don't see it on
> the front page anywhere at
> > > > > present).
> > > >
> > > > It has a 150px wide button in yellow on the
> homepage [1] ;-)
> > > > But I agree that it might need a bit more
> 'marketing'.
> > > >
> > > > - Phil
> > > >
> > > > [1] http://struts.apache.org/2.x/
> > > >
> > > >
> > > > > That way, it looks much more "official" and
> "endorsed", but
> > > > > still retains the benefits you outline here.
>  Again, it's really just a
> > > > > matter of perception in the end, and if this
> helps make it look like
> > > > > something more than just some outside and
> yet completely independent
> > > > > entity, as does the Sourceforge project
> (which is at least mentioned on
> > > > > the home page), then that might be all
> that's needed to make it work.
> > > > >
> > > > > Frank
> > > > >
> > > > > --
> > > > > Frank W. Zammetti
> > > > > Founder and Chief Software Architect
> > > > > Omnytex Technologies
> > > > > http://www.omnytex.com
> > > > > AIM/Yahoo: fzammetti
> > > > > MSN: fzammetti@hotmail.com
> > > > > Author of "Practical Ajax Projects With Java
> Technology"
> > > > >  (2006, Apress, ISBN 1-59059-695-1)
> > > > > and "JavaScript, DOM Scripting and Ajax
> Projects"
> > > > >  (2007, Apress, ISBN 1-59059-816-4)
> > > > > Java Web Parts -
> http://javawebparts.sourceforge.net
> > > > >  Supplying the wheel, so you don't have to
> reinvent it!
> > > > >
> > > > > On Tue, November 27, 2007 11:54 am, Ted
> Husted wrote:
> > > > > > On Nov 27, 2007 11:22 AM, Frank W.
> Zammetti <fz...@omnytex.com> wrote:
> > > > > >> It may be nothing more than a matter of
> perception and nothing more, but
> > > > > >> I
> > > > > >> think externally-hosted projects will
> automatically have a connotation
> > > > > >> of
> > > > > >> not being "golden" as you say, no matter
> what else is done to say
> > > > > >> otherwise, as I believe happened with the
> Sourceforge-hosted items.  I
> > > > > >> may
> > > > > >> be wrong, but that's what I believe to be
> the case.
> > > > > >
> > > > > > Not all ASF projects are "golden", and
> there are many "golden"
> > > > > > projects that have not joined the ASF.
> Though, quite a few ASF
> > > > > > projects are popular; certainly more than
> the average open-source
> > > > > > startup. One reason is probably the ASF
> project management style, or
> > > > > > the "Apache Way".
> > > > > >
> > > > > > One  effect of the Apache Way is that it
> tends to favor a conservative
> > > > > > approach. We need multiple people to agree
> to an implementation, or at
> > > > > > least agree to a release, and forging that
> agreement can work against
> > > > > > innovation.
> > > > > >
> > > > > > To help promote innovation at the ASF, we
> even started an Apache Labs
> > > > > > project, so that ASF committers could
> experiment with new code before
> > > > > > proposing an actual project. But, the
> Apache Labs are only open to
> > > > > > committers, and sometimes, we want to
> collaborate on a codebase with
> > > > > > someone who isn't a committer (at least,
> not yet).
> > > > > >
> > > > > > An important aspect of an external project
> is that it makes it easier
> > > > > > for Struts committers to work with other
> volunteers, without fussing
> > > > > > with the ASF brouhaha. The Apache Way is a
> great way to manage a
> > > > > > mature stable project, but it is not a
> great way to experiment with
> > > > > > new plugins.
> > > > > >
> > > > > > As an Struts PMC member, I am *very*
> concerned about plugin
> > > > > > proliferation in the standard
> distribution, mainly because the kids
> > > > > > need shoes, and we don't have enough
> volunteer hours to apply all the
> > > > > > patches that people already submit. I
> would like to encourage a plugin
> > > > > > commuity, and a shared external project
> seemed like one way to do
> > > > > > that.
> > > > > >
> > > > > > -Ted.
> > > > > >
> > > > > >
>
---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> dev-unsubscribe@struts.apache.org
> > > > > > For additional commands, e-mail:
> dev-help@struts.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
>
---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> dev-unsubscribe@struts.apache.org
> > > > > For additional commands, e-mail:
> dev-help@struts.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Software Architect - Hydrodesk
> > > > "Always code as if the guy who ends up
> maintaining your code will be a
> 
=== message truncated ===


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org