You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Cagatay Civici <ca...@gmail.com> on 2006/11/26 23:58:25 UTC
[VOTE] s:selectItems to tomahawk
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
Re: [VOTE] s:selectItems to tomahawk
Posted by Bruno Aranda <br...@gmail.com>.
+1
On 27/11/06, Martin Marinschek <ma...@gmail.com> wrote:
> +1
>
> and yes, Volker, no rendering specific stuff involved.
>
> regards,
>
> Martin
>
> On 11/27/06, Volker Weber <we...@googlemail.com> 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 <ca...@gmail.com>:
> > > 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
> > >
> > >
> > >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Martin Marinschek <ma...@gmail.com>.
+1
and yes, Volker, no rendering specific stuff involved.
regards,
Martin
On 11/27/06, Volker Weber <we...@googlemail.com> 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 <ca...@gmail.com>:
> > 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
> >
> >
> >
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: [VOTE] s:selectItems to tomahawk
Posted by Volker Weber <we...@googlemail.com>.
Why not having a "commons-component" library?
For converters and validators we neet also another TDL with another prefix.
I prefer to follow Bernds suggestion of having multiple commons artifacts.
Alternativly we can put all tag-components
(components/converters/validators/...?)
together into a single artifact.Or just all into a myfaces-commons jar,
but IMHO we can't go without at least one new TLD.
> 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.
The suggested common-component is really a component-library with
components completly independend of any jsf-implementation or
renderkit,
and the converter/validator artifacts are tag-librarys.
Regards,
Volker
2006/11/27, Manfred Geiler <ma...@gmail.com>:
> 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 <we...@googlemail.com> 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 <ca...@gmail.com>:
> > > 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
> > >
> > >
> > >
> >
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Sean Schofield <se...@gmail.com>.
+1 for promoting to tomahawk now and perhaps moving stuff to commons
later. Now I need to read the commons proposal ...
sean
On 11/27/06, Manfred Geiler <ma...@gmail.com> wrote:
> 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 <zw...@gmail.com> 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 <ma...@gmail.com> 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 <be...@atanion.com> 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 < weber.volker@googlemail.com> 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 <ca...@gmail.com>:
> > > > >> > 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
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
> >
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Manfred Geiler <ma...@gmail.com>.
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 <zw...@gmail.com> 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 <ma...@gmail.com> 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 <be...@atanion.com> 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 < weber.volker@googlemail.com> 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 <ca...@gmail.com>:
> > > >> > 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
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >
> > >
> >
>
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Volker Weber <we...@googlemail.com>.
This are two related threads,
Cagatay wants to promote the component into tomahawk.
Some (at least me) want to have the component in a renderkid indepenend commons.
I don't like to put it now into tomahawk and next month (or so) from
tomahawk into the new commons.
If we decide to have commons-component/validators/converters in the
near future,
it makes imho no sense to put such a component into tomahawk in the meantime.
2006/11/27, Zubin Wadia <zw...@gmail.com>:
> 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 <ma...@gmail.com> 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 <be...@atanion.com> 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 < weber.volker@googlemail.com> 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 <ca...@gmail.com>:
> > > >> > 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
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >
> > >
> >
>
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Zubin Wadia <zw...@gmail.com>.
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 <ma...@gmail.com> 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 <be...@atanion.com> 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 <we...@googlemail.com> 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 <ca...@gmail.com>:
> > >> > 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
> > >> >
> > >> >
> > >> >
> > >>
> > >
> >
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Manfred Geiler <ma...@gmail.com>.
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 <be...@atanion.com> 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 <we...@googlemail.com> 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 <ca...@gmail.com>:
> >> > 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
> >> >
> >> >
> >> >
> >>
> >
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Bernd Bohmann <be...@atanion.com>.
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 <we...@googlemail.com> 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 <ca...@gmail.com>:
>> > 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
>> >
>> >
>> >
>>
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Manfred Geiler <ma...@gmail.com>.
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 <we...@googlemail.com> 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 <ca...@gmail.com>:
> > 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
> >
> >
> >
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Matthias Wessendorf <ma...@apache.org>.
that would be great;
from what I got out of that commons thread is that they wanna have
*common utils* in that jar first. no response to the "adding
validators/converters" proposal so far.
Only Bernd had also something similar (security;fileupload,...)
-M
On 11/27/06, Volker Weber <we...@googlemail.com> 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 <ca...@gmail.com>:
> > 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
> >
> >
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] s:selectItems to tomahawk
Posted by Volker Weber <we...@googlemail.com>.
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 <ca...@gmail.com>:
> 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
>
>
>
Re: [VOTE] s:selectItems to tomahawk
Posted by Matthias Wessendorf <ma...@apache.org>.
+1 for that great component
On 11/26/06, Cagatay Civici <ca...@gmail.com> wrote:
> 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
>
>
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [VOTE] s:selectItems to tomahawk
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> I'm planning to promote s:selectItems to tomahawk. Component satisfies
> all of the requirements needed for promotion.
+1
Ciao,
Mario
Re: [VOTE] s:selectItems to tomahawk
Posted by Manfred Geiler <ma...@gmail.com>.
+1
we already have been using this component in production for some time
without any issues
Manfred
On 11/26/06, Cagatay Civici <ca...@gmail.com> wrote:
> 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
>
>
>