Raphaël Luta escribió:
>
> David Sean Taylor wrote:
> >
> > Raphaël Luta wrote:
> > > David Sean Taylor wrote:
> > > >
> > > > I checked in Ingo's WebPagePortlet in portal.portlets
> > > >
> > >
> > > I'm -1 for that.
> > >
> > Im +1 for it, thats why I checked it in.
> >
> > I wrote a WebPagePortlet a while back, and I've been using it on several of
> > our demo and internal sites.
> > I never committed since in my mind it was incomplete:
> > I was planning on collaborating with Marcus Schwarz, who had a more complete
> > solution, but did not use an html parser, but he seems to have disappeared
> > from Jetspeed recently.
> >
>
> In case, my opinion was not clear, I'm +1 on having a WebPagePortlet in CVS but
> I don't think it should live under portal.portlets unless it's considered generally
> useful by all users. IMO It should rather be under /modules/WebPagePortlet, my -1
> was only on the location of the code.
>
> Since portlets are a expansion mechanism, if we put every contributed portlets
> intop the main jetspeed.portal.portlets directory, we'll have sooner
> or later so many classes within that directory that'll be impossible to clearly
> state what purpose each fulfills, wich is maintained and which is not, etc...
>
I'm +1 on moving it to other directory. It merits a package, since there
will soon be auxiliary classes for different html parsing options. The
discussion we're having warrants it :)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
