1 2 Previous Next 25 Replies Latest reply on Oct 12, 2011 12:44 PM by ccerb Go to original post
      • 15. Re: rich:comboBox and rich:suggestionbox should support h:se
        deanhiller

        I spent the past hour reading through
        https://jira.jboss.org/jira/browse/RF-4293
        https://jira.jboss.org/jira/browse/RF-5046
        http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4172548#4172548
        and this forum

        I have not seen one single instance where people wanted functionality of typing something NOT in the list as someone suggested above. I WELCOME the new component and I do believe that usage of the old component will be EXTREMELY rare and many many more people will use the new component...in fact, I would deprecate the old component after and see if anyone screams to bring it back...my guess would be no except for backward compatibility as they hacked some solution together themselves.

        Any status on this new component? that would rock!!!!

        oh yeah, also wikipedia is not clear at all on whether a combobox should let you type something in the list so I am not sure what the wikipedia link was trying to imply. It does state "allowing the user to either type a value directly" but does not clarify whether this value has to be in the list and I think most people believe it should be in the list (otherwise I would not want to use the component in 99% of cases). I am sure there is a case where I will want it in 5 years or so, just majority here is it is not needed.

        If you want to point me to a post of a developer saying they need it, I would be very interested in that post(more out of curiosity) though I bet you won't find one ;).

        thanks,
        Dean

        • 16. Re: rich:comboBox and rich:suggestionbox should support h:se
          deanhiller

          This component could go forward now if you vote for it...

          https://jira.jboss.org/jira/browse/RF-5046

          • 17. Re: rich:comboBox and rich:suggestionbox should support h:se
            jbalunas

             

            "deanhiller" wrote:

            I have not seen one single instance where people wanted functionality of typing something NOT in the list as someone suggested above.


            One that immediately comes to my mind is a search field. Suggest regular or typical search options, but allow the user to type something not in the select.


            Any status on this new component? that would rock!!!!


            We are reviewing components for 4.0, and are currently discussing combo and suggestion boxes here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=163267.

            Although I am not sure how much new/extra functionality we'll be adding for the first release of 4.0, but I welcome your comments and suggestions.


            • 18. Re: rich:comboBox and rich:suggestionbox should support h:se
              nbelaevski

              Dean et al.,

              Just to clarify: scope of RF 3.3.3 includes only critical browser, JSF 2.0 and backward compatibility issues. We are not planning to do RFCs in this version, especially such as development of new component.

              P.S.

              I have not seen one single instance where people wanted functionality of typing something NOT in the list as someone suggested above

              I think I can give the case on this: imagine you are going to enter post address somewhere on the Internet. You are starting to type in your city name, system is prompting a list of cities, but... there's no yours in the list - it's too small. And you can't type it in - items are restricted to the predefined list.


              • 19. Re: rich:comboBox and rich:suggestionbox should support h:se
                ilya_shaikovsky

                 

                I have not seen one single instance where people wanted functionality of typing something NOT in the list as someone suggested above


                or tags addition to some blog entry. The component proposes you popular tags while you start typing but you are free to input non-existent tag for sure.

                or some form for entering user details.. e.g. job title.. you will be proposed with some list - but you could add some custom title if need.

                etc..

                • 20. Re: rich:comboBox and rich:suggestionbox should support h:se

                  Ok ok, fine, you guys found some good exemple, I give you 5 points for this !  Heh..joke apart, it's obvious that the community 'is requesting/is in need' of a new component that is a mix between the standard jsf h:selectOneMenu and the rich:comboBox, and at the moment of this writing, community doesn't have that component.  It's not that rich:comboBox is not useful at all, as I said, you stated some good exemples where we could use it.......BUT, the question is (and this is, to me, one of the most important question to ask yourself when you're offering some sort of 'services' to people...), are those exemples(or are those components, combo/suggestion box) the 'M'ost in demand by the community ???

                   

                  Well, here's my point, I don't think so....

                  • 21. Re: rich:comboBox and rich:suggestionbox should support h:se
                    jbalunas

                    Lets add this to the review for 4.0, but Nick is right in regards to 3.3.3.  This is a point release with very focused changes.

                    • 22. Re: rich:comboBox and rich:suggestionbox should support h:se
                      deanhiller

                      "Well, here's my point, I don't think so...."

                       

                      I can agree with that as long as the issue is not closed again.  Please keep it open.  Feel free to prioritize how you like(ie. low).  For us, it is high priority but it takes many in the community to make it high overall on the roadmap, I agree.  i am not sure how many votes make something high.  I think there was only about 8 votes or so thus far which seemed like medium priority compared to other tickets and their votes(ie. not high priority but not too low, just in the middle it seemed like).

                       

                      later,

                      Dean

                      • 23. Re: rich:comboBox and rich:suggestionbox should support h:select
                        luiggitama

                        Hi guys...

                         

                        As stated by Ilya, rich:combobox does what it was designed to (an input text component with client-side suggestions).

                         

                        If we want to use it for selecting of values based on selected labels (rendered by the component), we must wait for a new component to be designed (or design it)... or enhance it on the client-side (as I did)...

                         

                        In this article I share my (working) approach:

                         

                        Enhanced rich:comboBox: Values (not only Text) and RegExp Suggestions

                         

                        So please test it and let me know what you think.

                         

                        God bless you.

                         

                        Best regards,

                        Luis Tama

                        • 24. Re: rich:comboBox and rich:suggestionbox should support h:select
                          jbalunas

                          Wow, that is a detailed write up :-)

                           

                          I'll have time for a closer review once we get past the push for M1 code freeze ( July 12th ).

                          • 25. Re: rich:comboBox and rich:suggestionbox should support h:select
                            ccerb

                            I was wondering if there is any plan to add limitRender attribute to autocomplete component? Autocomplete triggers ajax requests and all the components having ajaxRendered=true are affected. I had a case when I wanted to limit rendering, so limitRender would have been great. I used a workaround, but limitRender would be nicer.

                             

                            thank you

                            1 2 Previous Next