We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25663 MODX Staff
    • 12,272 Posts
    I wonder if &summarize isn’t a misnomer that should be deprecated... I just caught myself wondering why &limit wasn’t returning more results then took a quick pop over to the doc site to realize it’s &summarize. It’s not always Summarizing after all...

    Should &limit become &queryLimit and should &summarize become &return or &results? Or something like that...
      Ryan Thrash, MODX Co-Founder
      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
      • 18397
      • 3,250 Posts
      I was thinking of renaming it &show but I forgot about it in the heat of trying to finish 2.0. I’d be happy to make this change in 2.0.1 (still provide backwards compatibility via the new config file). Anyone else have another good idea for a name?
        • 17883
        • 1,039 Posts
        &number
        &quantity

        just a thought.
          • 19889
          • 616 Posts
          Quote from: Mark at Mar 14, 2007, 08:38 PM

          I was thinking of renaming it &show but I forgot about it in the heat of trying to finish 2.0. I’d be happy to make this change in 2.0.1 (still provide backwards compatibility via the new config file). Anyone else have another good idea for a name?

          I think &show and &limit are fine.
            • 18397
            • 3,250 Posts
            What about display?

            (I made the change in SVN so that &summarize is now &show. That does not mean I’m not open to suggestions.)
              • 17883
              • 1,039 Posts
              I think "display" could be misunderstood in a "per page" meaning and could get in conflict with pagination. What about &get?

              Because you ’get’ a certain number of docs...
                • 33372
                • 1,611 Posts
                How about &howManyItemsOnThisSummaryPageAtATimeRegardlessOfPaginationAndNotRelatedToTheDatabaseQueryLimit?
                  "Things are not what they appear to be; nor are they otherwise." - Buddha

                  "Well, gee, Buddha - that wasn't very helpful..." - ZAP

                  Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
                  • 17883
                  • 1,039 Posts
                  &howManyItemsOnThisSummaryPageAtATimeReg ardlessOfPaginationAndNotRelatedToTheDa tabaseQueryLimit?

                  THAT´S IT grin
                    • 25663 MODX Staff
                    • 12,272 Posts
                    Now that I think on it more, I think &show might get confused with paging too: "Show me five results at a time..."

                    But I can’t decide on the best choice for &summarize ... either &get or &return would be my two choices ("results" falls victim to the pagination connotation as well). I wonder if "get" might be confused with a form get, or if the MODx-practice of "returning" things in snippets would make for a good argument for using &return.

                    I do think &limit should become &queryLimit, just for clarity’s sake.
                      Ryan Thrash, MODX Co-Founder
                      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                      • 18397
                      • 3,250 Posts
                      I don’t think either &get or &return would work. However, Feedburner uses the following phrase on their BuzzBoost service "Number of items to display:". Personally, think display makes more sense than show. Because you are displaying 3 items...