Yes, d'accord!
I agree with Zubin that these are two different pairs of shoes.
+1 for moving s:selectItems out of the tomahawk(!) sandbox to tomahawk core
Let's keep an eye on a future
alltogether-compatible-with-everything-components-set but do not not
mix up with the "commons jsf utils" package proposal. If there is need
for this "common components" project, we should start a new thread and
bring this to a higher level, because there might be other
renderkit-independent or standalone component like goodies as well,
not only s:selectItems.
Manfred
On 11/27/06, Zubin Wadia <[EMAIL PROTECTED]> wrote:
Aren't these 2 different threads? All Cagatay wants to do is promote the
component...
Then there was a thread just a few days ago about the commons-util, we
should continue that conversation there...
On 11/27/06, Manfred Geiler <[EMAIL PROTECTED]> wrote:
> Ok, now I do not understand anything anymore as well... :-)
> Seems, like we got our wires crossed.
>
> What is your exact proposal for the s:selectItems stuff. Moving it to
> both tomahawk as well as commons means what?
> Having a <t:selectItems> in tomahawk together with a
>
org.apache.myfaces.tomahawk.custom.selectitems.SelectItemsTag
> that uses a common
> org.apache.myfaces.commons.component.UISelectItems
> ?
>
> Sorry, I didn't get it. :-(
>
> Manfred
>
>
>
>
> On 11/27/06, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
> > Hello Manfred,
> >
> > i don't understand you. What is wrong to move all the common renderkit
> > stuff to a common package. This does't keep you to include this tag in
> > the tomahawk tld.
> >
> > Here is my
> >
> > +1 for moving to tomahawk
> >
> > and
> >
> > +1 for moving in a common whatever artifact.
> >
> > and
> >
> > +1 for starting a myfaces common project.
> >
> > Regards
> >
> >
> > Bernd
> >
> > Manfred Geiler wrote:
> > > Even if there is no renderer specific stuff involved, this goody is
> > > quite component like. Particularly the tag definition is the thing
> > > that makes it diffult to integrate into commons. We should not have
> > > another TLD in commons with another recommended prefix ("c" ?!).
> > > Wouldn't that be really confusing for the end user. He would have to
> > > define another TLD in his JSP headers which is not really a component
> > > collection but rather a... what?
> > > Therefore my feeling is, that this one belongs more to a component
> > > library than the common jsf utilities collection.
> > > This component being a goody that is nice for the tomahawk as well as
> > > the trinidad and tobago user is no argument IMO. This should be more a
> > > signal for us that we have to compass a one-that-plays-everything
> > > component library in the far (bright) future. i.e. Melt together our
> > > great component sets.
> > >
> > > So, I'm
> > > -0.5 for putting it into (future) commons, and I'am still
> > > +1 for moving it to tomahawk
> > >
> > > Manfred
> > >
> > >
> > > On 11/27/06, Volker Weber < [EMAIL PROTECTED]> wrote:
> > >> Hi,
> > >>
> > >> i didn't know this component before, looks very usefull.
> > >>
> > >> I prefer to have this in the new commons project, to enabel the use
in
> > >> non tomahawk applications e.g. tobago. There is no renderer specific
> > >> stuff involed?
> > >>
> > >> Regards,
> > >> Volker
> > >>
> > >>
> > >> 2006/11/26, Cagatay Civici <[EMAIL PROTECTED]>:
> > >> > Hi,
> > >> >
> > >> > I'm planning to promote s:selectItems to tomahawk. Component
> > >> satisfies all
> > >> > of the requirements needed for promotion.
> > >> >
> > >> > Regards,
> > >> >
> > >> > Cagatay
> > >> >
> > >> >
http://myfaces.apache.org/sandbox/selectItems.html
> > >> >
> > >> >
> > >> >
> > >>
> > >
> >
>
