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
>
>
>
