8 Replies Latest reply on Nov 3, 2009 4:54 AM by Ilya Shaikovsky

    OrderingList : rows attribute

    S P Newbie

      Hi all,

      The problem of the day is the following:
      I'm using orderling list, everything works fine except the list size. Let me explain. I'd like to set a number of rows, but the list doesn't seems to use it. Value "5" or "1000" display the same number of line => 8!.

      <rich:orderingList value="#{library.songsList}" var="lib" listWidth="350" converter="orderingListConverter" rows="5">
      


      Does anyone can explain me what's wrong?

      Thanks a lots,

      Sebastien


        • 1. Re: OrderingList : rows attribute
          Nick Belaevski Master

          Hi Sebastien,

          "rows" attribute is not supported for rich:orderingList and rich:listShuttle components.

          • 2. Re: OrderingList : rows attribute
            S P Newbie

            Thanks for this reply,

            That's a pity...

            Does listHeigth accept anything else a size in pixel?

            Regards,

            Sebastien

            • 3. Re: OrderingList : rows attribute
              Ilya Shaikovsky Master

              If you mean count of items - also no. Wanted to create RFC for such case but later revised the case and think it probably should remains as designed. These just selects components and it not looks simple and native to provide pagination and rows limitation functionality there.

              • 4. Re: OrderingList : rows attribute
                S P Newbie

                Hello Ilya,

                Ok, but mixing pagination and ordering capabilities should be nice.

                Let me know if you plan do to that!

                Thanks,

                Sebastien

                • 5. Re: OrderingList : rows attribute
                  S P Newbie

                  Hi all,

                  Another question about list size,

                  I want to limit the visible list height (to 400px for example), and allow the rest of the list to be present in the same page but with a scroll bar.
                  Is there a way to do that please?

                  Thanks,

                  Sébastien

                  • 6. Re: OrderingList : rows attribute
                    Ilya Shaikovsky Master

                     

                    "spiau" wrote:
                    Hello Ilya,

                    Ok, but mixing pagination and ordering capabilities should be nice.

                    Let me know if you plan do to that!

                    Thanks,

                    Sebastien


                    you could try to implement it using extendedDataTable which has selection sorting and filtering support and add a4j:buttons to make reordering via ajax.

                    • 7. Re: OrderingList : rows attribute
                      Ilya Shaikovsky Master

                       

                      "spiau" wrote:
                      Hi all,

                      Another question about list size,

                      I want to limit the visible list height (to 400px for example), and allow the rest of the list to be present in the same page but with a scroll bar.
                      Is there a way to do that please?

                      Thanks,

                      Sébastien



                      listHeight attribute.

                      • 8. Re: OrderingList : rows attribute
                        Ilya Shaikovsky Master

                         

                        "ilya_shaikovsky" wrote:
                        "spiau" wrote:
                        Hello Ilya,

                        Ok, but mixing pagination and ordering capabilities should be nice.

                        Let me know if you plan do to that!

                        Thanks,

                        Sebastien


                        you could try to implement it using extendedDataTable which has selection sorting and filtering support and add a4j:buttons to make reordering via ajax.


                        sorry but after second look on it - it even seems easier and more convenient solution for me - to use OrderingList component but place a4j:* controls in headers and add sorting capabilities to the ordering list from your code. In this case ordering will remain client side and more fast for end user. And sorting will be done as it should via ajax.