Hi Bauke,
I have no preference on the solution.
Feel free to work on this with Cagatay.
Thanks!
Kind regards,
Manfred Riem
On 9/1/15, 7:13 AM, Bauke Scholtz wrote:
>
> No problem.
>
> I only wonder which direction we should go? The same approach as
> Tomahawk and PrimeFaces, with a new sub component like
> <h:radioButton>, or reusing the existing <h:selectOneRadio> and adding
> one or two new attributes? The difference is only in the XHTML markup.
>
> Cheers, Bauke
>
>
> On 15:39, Mon, Aug 31, 2015 manfred riem <manfred.riem_at_oracle.com
> <mailto:manfred.riem_at_oracle.com>> wrote:
>
> Hi Cagatay,
>
> I have no problem waiting until then.
>
> Anyone else objections?
>
>
> Thanks!
>
> Kind regards,
> Manfred Riem
>
> On 8/31/15, 7:32 AM, Cagatay Civici wrote:
>> Hi,
>>
>> I sure can work on it however I’m on vacation until 21 September.
>> How much time we have for this?
>>
>> Also I’d like to call Bauke for help, maybe we can do it together?
>>
>> Regards,
>>
>> Cagatay Civici
>> PrimeFaces Lead
>> PrimeTek Informatics
>> www.primefaces.org <http://www.primefaces.org>
>>
>> On Thursday 27 August 2015 at 15:20, manfred riem wrote:
>>
>>> Hi Cagatay,
>>>
>>> As Ryan has expressed he feels he is in over his head I like
>>> Cagatay to
>>> take this one.
>>>
>>> Cagatay, can you please specify and implement this?
>>>
>>> Thanks!
>>>
>>> Kind regards,
>>> Manfred Riem
>>>
>>> On 8/25/15, 5:18 AM, arjan tijms wrote:
>>>> On Tue, Aug 25, 2015 at 6:18 AM, Josh
>>>> Juneau<juneau001_at_gmail.com <mailto:juneau001_at_gmail.com>> wrote:
>>>>> These trivial
>>>>> issues with JSF have led to many arguments against using the
>>>>> framework. The
>>>>> easier it is made for beginners, the better in my opinion.
>>>> For beginners especially, but moderately advanced users as
>>>> well. We've
>>>> seen this time and again with OmniFaces. Trivial functionality
>>>> that in
>>>> essence encapsulates only a few lines of code using the
>>>> standard JSF
>>>> API. Yet, users greatly appreciate it.
>>>>
>>>>
>>>>
>>>>
>>>>> Josh Juneau
>>>>> juneau001_at_gmail.com <mailto:juneau001_at_gmail.com>
>>>>> http://jj-blogger.blogspot.com
>>>>> https://www.apress.com/index.php/author/author/view/id/1866
>>>>>
>>>>>
>>>>> On Wed, Aug 19, 2015 at 1:08 PM, arjan
>>>>> tijms<arjan.tijms_at_gmail.com <mailto:arjan.tijms_at_gmail.com>> wrote:
>>>>>> I agree with Bauke, this has been asked for a lot of times by
>>>>>> users. I
>>>>>> had a bunch of personal messages in response to my JSF 2.3
>>>>>> wish list
>>>>>> asking for exactly this.
>>>>>>
>>>>>> Such a component seems to be "basic" enough to be a good
>>>>>> candidate for
>>>>>> inclusion in the JSF standard component set.
>>>>>>
>>>>>> Kind regards,
>>>>>> Arjan Tijms
>>>>>>
>>>>>> On Wed, Aug 19, 2015 at 7:27 PM, Bauke
>>>>>> Scholtz<balusc_at_gmail.com <mailto:balusc_at_gmail.com>> wrote:
>>>>>>> I vote against. This is one of most common requirements from the
>>>>>>> community.
>>>>>>> I'd like to see this to end up in standard component set
>>>>>>> too. A custom
>>>>>>> renderer is not trivial to starters, for sure not if you'd
>>>>>>> like to use
>>>>>>> it in
>>>>>>> an repeater component
>>>>>>> like<h:dataTable><h:column><h:selectOneRadio>
>>>>>>> and/or
>>>>>>> if you want to have a separate<h:outputLabel> for each item.
>>>>>>>
>>>>>>> Cheers, B
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Aug 19, 2015 at 7:16 PM, manfred
>>>>>>> riem<manfred.riem_at_oracle.com <mailto:manfred.riem_at_oracle.com>>
>>>>>>> wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I like to close this one as "Won't fix" as well as it is
>>>>>>>> fairly easy to
>>>>>>>> register your own renderer.
>>>>>>>>
>>>>>>>> To introduce a new component for it seems overkill.
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> Note I like to close the loop on this one before 8/26.
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> Kind regards,
>>>>>>>> Manfred Riem
>>