<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>jQuery Grid Plugin - jqGrid - Topic: Support an "All" option for the rowList parameter</title>
	<link>http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter</link>
	<description><![CDATA[Grid plugin]]></description>
	<generator>Simple:Press Version 5.7.5.3</generator>
	<atom:link href="http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter/rss" rel="self" type="application/rss+xml" />
        <item>
        	<title>OlegK on Support an "All" option for the rowList parameter</title>
        	<link>http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p25775</link>
        	<category>Feature Request</category>
        	<guid isPermaLink="true">http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p25775</guid>
        	        	<description><![CDATA[<p>Hello <strong>fabamb</strong>,</p>
<p>I don&#39;t think that one should include in the code of jqGrid any changes which break the current server code. Your suggestion require changes on the server side because the code <strong>SELECT TOP(0)</strong> will work not good. On the other side if you use "SQL Server Management Studio" for example it uses per default <strong>TOP(1000)</strong> in all your selects of the tables. It&#39;s good because mostly you will not look through all returened rows and examine only some first rows. So I think that the usage of some large enough value like 5000 will be better. One can include the value as a new jqGrid option together with the text &#39;All&#39;&#160;and make it configuratable. In the way one will receive full flexibility, but still don&#39;t break existing server code. So all users can update to the new version of jqGrid without additional compatibility problems.</p>
<p>Best regards<br />Oleg&#160;</p>
]]></description>
        	        	<pubDate>Tue, 24 Jan 2012 12:45:44 +0200</pubDate>
        </item>
        <item>
        	<title>fabamb on Support an "All" option for the rowList parameter</title>
        	<link>http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p25772</link>
        	<category>Feature Request</category>
        	<guid isPermaLink="true">http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p25772</guid>
        	        	<description><![CDATA[<p>May I suggest an improvement?<br /> Instead of setting an arbitrary value, which is always wrong, you can set as a sentinel value 0 for &#39;All&#39; and manage server-side, correctly. On the other hand, often in paging systems, it works without having to do anything.</p>
<p><input type='button' class='sfcodeselect' name='sfselectit214' value='Select Code' data-codeid='sfcode214' /></p>
<div class='sfcode' id='sfcode214'>rowList: [5, 10, 20, 50, 1000, 0],<br />pager: &#39;#pager</div>
</p>
<p><input type='button' class='sfcodeselect' name='sfselectit1503' value='Select Code' data-codeid='sfcode1503' /></p>
<div class='sfcode' id='sfcode1503'>$(&#34;#pager option[value=0]&#34;).text(&#39;All&#39;);</div></p>
]]></description>
        	        	<pubDate>Tue, 24 Jan 2012 09:35:39 +0200</pubDate>
        </item>
        <item>
        	<title>OlegK on Support an "All" option for the rowList parameter</title>
        	<link>http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p24624</link>
        	<category>Feature Request</category>
        	<guid isPermaLink="true">http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p24624</guid>
        	        	<description><![CDATA[<p>Hello!</p>
<p>I agree with you. The same requirement have the most customers. The usage of "-1" is <em>not allowed</em> and <em>can&#39;t be used</em>, but one can use some large enough value and&#160;change the corresponding text value <strong>only for the user</strong>. For example I used mostly</p>
<p><input type='button' class='sfcodeselect' name='sfselectit6503' value='Select Code' data-codeid='sfcode6503' /></p>
<div class='sfcode' id='sfcode6503'>rowList: [5, 10, 20, 50, 1000, 5000],<br />pager: &#39;#pager&#39;&#160;</div>
<p>in the jqGrid definition and includes the following line after the grid creation:</p>
<p><input type='button' class='sfcodeselect' name='sfselectit260' value='Select Code' data-codeid='sfcode260' /></p>
<div class='sfcode' id='sfcode260'>$(&#34;#pager option[value=5000]&#34;).text(&#39;All&#39;);</div>
<p>It&#39;s a workaround, but it improves the visibility of the grid.</p>
<p>Best regards<br />Oleg&#160;</p>
]]></description>
        	        	<pubDate>Thu, 15 Sep 2011 13:21:13 +0300</pubDate>
        </item>
        <item>
        	<title>boogey100 on Support an "All" option for the rowList parameter</title>
        	<link>http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p24623</link>
        	<category>Feature Request</category>
        	<guid isPermaLink="true">http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p24623</guid>
        	        	<description><![CDATA[<p>Perhaps allowing it to be an object rather than an array would do it, so you could have { &#39;10&#39;:10,&#39;20&#39;:20,&#39;50&#39;:50,&#39;All&#39;:-1 }. My gues is the only thing that would need changing is the bit that builds the &#60;select&#62; in the pager.</p>
]]></description>
        	        	<pubDate>Thu, 15 Sep 2011 12:34:28 +0300</pubDate>
        </item>
        <item>
        	<title>dw on Support an "All" option for the rowList parameter</title>
        	<link>http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p15330</link>
        	<category>Feature Request</category>
        	<guid isPermaLink="true">http://www.trirand.com/blog/?page_id=393/feature-request/support-an-all-option-for-the-rowlist-parameter#p15330</guid>
        	        	<description><![CDATA[<p>I&#160;typically configure the rowList option for all grids in our application with the following value:</p>
<p><span style="font-size: x-small;"></span></p>
<p><input type='button' class='sfcodeselect' name='sfselectit7578' value='Select Code' data-codeid='sfcode7578' /></p>
<div class='sfcode' id='sfcode7578'>
<p><span style=&#34;font-size: x-small;&#34;>properties.rowList = [10,20,50,100,</span><span style=&#34;font-size: x-small; color: #800000;&#34;>&#39;All&#39;</span><span style=&#34;font-size: x-small;&#34;>];</span></p>
</div>
<p>This allows users to display all items without putting a hard limit on the number of rows.&#160;&#160;Although the rowList option doesn&#39;t explictly say that it requires an array of numeric values, there are several places in the code that assume rowNum will be a number.&#160; It seems more of these have been added over time.</p>
<p>In jqGrid 3.4,&#160;I was able to use the rowList above with no changes to the the jqGrid code and&#160;I did not receive any errors.&#160; Upon upgrading to jqGrid 3.5&#160;I had to make the following slight modification to the updatepager method, but this approach still worked.&#160; <span style="font-size: x-small;"></span></p>
<p><input type='button' class='sfcodeselect' name='sfselectit6474' value='Select Code' data-codeid='sfcode6474' /></p>
<div class='sfcode' id='sfcode6474'><span style=&#34;font-size: x-small;&#34;></p>
<p>updatepager =</p>
</p>
<p></span></p>
<p><span style=&#34;font-size: x-small; color: #0000ff;&#34;>function</span><span style=&#34;font-size: x-small;&#34;>(rn) { </span></p>
<p><span style=&#34;font-size: x-small; color: #0000ff;&#34;>var</span><span style=&#34;font-size: x-small;&#34;> cp, last, base,bs, from,to,tot,fmt;</span><span style=&#34;font-size: x-small;&#34;></span></p>
<p><span style=&#34;font-size: x-small; color: #0000ff;&#34;>if</span><span style=&#34;font-size: x-small;&#34;>(isNaN(ts.p.rowNum)</span><span style=&#34;font-size: x-small;&#34;>){ </span></p>
<p>&#160;&#160; base = 0;</p>
<p>}</p>
<p><span style=&#34;font-size: x-small; color: #0000ff;&#34;>else</span><span style=&#34;font-size: x-small;&#34;>{ </span></p>
<p>&#160;&#160; base = (parseInt(ts.p.page)-1)*parseInt(ts.p.rowNum);</p>
<p>}</p>
<p>&#160;</p>
</div>
</p>
<p>With the upgrade to 3.6, it appears that there are more places in the code that would need to be updated.&#160;</p>
<p>Would it be possible to do one of the following:</p>
<p>1) add code to support nonnumeric value for rowList option (this seems like it would be harder and possibly less desirable)</p>
<p>OR</p>
<p>2) add another parameter rowListLabels or something like this or another mechanism that would allow the label for the select options to be set.&#160; This would allows us to specify an arbitrary high number like 1000000 and give it the label of &#39;All&#39; (this seems like an easy change)&#160; Of course, I could write some code to go set this label manually after the pager is rendered, which is what i will probably do in the short term, but i thought i would throw it out there as a possible enhancement.&#160;</p>
<p>Thanks for considering the change.</p></p>
]]></description>
        	        	<pubDate>Wed, 03 Mar 2010 09:53:46 +0200</pubDate>
        </item>
</channel>
</rss>