1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
\r
4 <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
5 <title>Rico LiveGrid</title>
\r
6 <link href="ricoDocs.css" rel="Stylesheet" type="text/css">
10 <h1>Creating a Rico LiveGrid</h1>
\r
12 <p>Rico LiveGrid displays data in a scrolling table, with the data buffered in a
\r
13 2-dimensional JavaScript array. As the user scrolls
\r
14 vertically through the grid, data is dynamically copied from the array onto the grid.
\r
15 The buffer can can be loaded from:
\r
17 <li><a href='#model1'>a javascript array</a>
\r
18 <li><a href='#model2'>an HTML table</a>
\r
19 <li><a href='#model3'>an XML file</a>
\r
20 <li><a href='#model4'>a SQL database query</a>
\r
21 <li><a href='#model5'>a custom javascript callback function</a>
\r
25 <h2><a name='model1'>Usage Model 1: Loading data from a javascript array</a></h2>
\r
27 <ul><li>Load the data to be displayed into a javascript array.
\r
30 [1,'Cell 1:2','Cell 1:3','Cell 1:4','Cell 1:5'],
\r
31 [2,'Cell 2:2','Cell 2:3','Cell 2:4','Cell 2:5'],
\r
32 [3,'Cell 3:2','Cell 3:3','Cell 3:4','Cell 3:5'],
\r
33 [4,'Cell 4:2','Cell 4:3','Cell 4:4','Cell 4:5']
\r
37 <li>Load the Rico javascript and css files necessary to display the grid.
\r
39 Rico.loadModule('LiveGrid','LiveGridMenu','greenHdg.css');
\r
43 <dd>This loads the Rico javascript and css files necessary to display a LiveGrid
\r
44 with a static buffer (no AJAX).
\r
46 <dd>This loads the default grid menu. This menu provides access to all of the LiveGrid capabilities.
\r
47 It adjusts the selections presented to the user based on the column selected
\r
48 and the type of buffer used.
\r
49 You can also choose to use the grid with no menu at all, or to create your own menu
\r
50 customized to the needs of your application.
\r
52 <dd>Rico comes with several sample grid styles: coffee-with-milk,
\r
53 grayedout, greenHdg, iegradient (Internet Explorer only), tanChisel, and warmfall.
\r
54 You may choose one of the included styles or create one of your own.
\r
57 <li>Load the array into a Rico Buffer object:
\r
59 var buffer=new Rico.Buffer.Base();
\r
60 buffer.loadRowsFromArray(myData);
\r
63 <li>Define the grid's options, including the grid headings:
\r
67 visibleRows : 'data',
\r
69 columnSpecs : [{Hdg:'Column 1',type:'number', ClassName:'alignright'},
\r
77 <li>Instantiate the LiveGrid, passing in the base id for the grid,
\r
78 the Rico.Buffer instance, and the grid options.
\r
80 var ex1=new Rico.LiveGrid ('ex1', buffer, opts);
\r
83 <li>To enable the default pop-up menu for the grid, assign the grid's
\r
84 menu property to an instance of Rico.GridMenu.
\r
86 ex1.menu=new Rico.GridMenu();
\r
89 <li>Rico.loadModule may finish <em>after</em> the window.onload event.
\r
90 So to ensure that the grid initialization runs after the Rico modules
\r
91 have loaded, you must pass the initialization function to the
\r
92 Rico.onLoad method. Putting all of the javascript together would look like this:
\r
94 <script type='text/javascript'>
\r
95 Rico.loadModule('LiveGrid','LiveGridMenu','greenHdg.css');
\r
97 Rico.onLoad( function() {
\r
99 [1,'Cell 1:2','Cell 1:3','Cell 1:4','Cell 1:5'],
\r
100 [2,'Cell 2:2','Cell 2:3','Cell 2:4','Cell 2:5'],
\r
101 [3,'Cell 3:2','Cell 3:3','Cell 3:4','Cell 3:5'],
\r
102 [4,'Cell 4:2','Cell 4:3','Cell 4:4','Cell 4:5']
\r
106 visibleRows : 'data',
\r
108 columnSpecs : [{Hdg:'Column 1',type:'number', ClassName:'alignright'},
\r
114 var buffer=new Rico.Buffer.Base();
\r
115 buffer.loadRowsFromArray(myData);
\r
116 var ex1=new Rico.LiveGrid ('ex1', buffer, opts);
\r
117 ex1.menu=new Rico.GridMenu();
\r
122 <li>Finally, place a div element in your HTML markup at the position where the grid should go.
\r
123 Including the markup for the bookmark will cause the grid's scroll position to be displayed.
\r
125 <p class="ricoBookmark"><span id="ex1_bookmark"> </span></p>
\r
126 <div id="ex1"></div>
\r
134 <h2><a name='model2'>Usage Model 2: Loading data from an HTML table</a></h2>
\r
136 <ul><li>Define an HTML table with the headings in a <code><thead></code> section
\r
137 and the data in a <code><tbody></code> section.
\r
138 Including the markup for the bookmark will cause the grid's scroll position to be displayed.
\r
140 <p class="ricoBookmark"><span id="data_grid_bookmark"> </span></p>
\r
141 <table id="data_grid">
\r
145 <th>First column name</th>
\r
146 <th>Second column name</th>
\r
148 <th>Last column name</th>
\r
156 <td>Row 1, column 1 data</td>
\r
157 <td>Row 1, column 2 data</td>
\r
159 <td>Row 1, last column data</td>
\r
163 <td>Row 2, column 1 data</td>
\r
164 <td>Row 2, column 2 data</td>
\r
166 <td>Row 2, last column data</td>
\r
172 <td>Row n, column 1 data</td>
\r
173 <td>Row n, column 2 data</td>
\r
175 <td>Row n, last column data</td>
\r
182 <li>Load the Rico javascript and css files necessary to display the grid.
\r
184 Rico.loadModule('LiveGrid','LiveGridMenu','greenHdg.css');
\r
188 <dd>This loads the Rico javascript and css files necessary to display a LiveGrid
\r
189 with a static buffer (no AJAX).
\r
191 <dd>This loads the default grid menu. This menu provides access to all of the LiveGrid capabilities.
\r
192 It adjusts the selections presented to the user based on the column selected
\r
193 and the type of buffer used.
\r
194 You can also choose to use the grid with no menu at all, or to create your own menu
\r
195 customized to the needs of your application.
\r
197 <dd>Rico comes with several sample grid styles: coffee-with-milk,
\r
198 grayedout, greenHdg, iegradient (Internet Explorer only), tanChisel, and warmfall.
\r
199 You may choose one of the included styles or create one of your own.
\r
202 <li>Load the table's data rows into a Rico Buffer object:
\r
204 var buffer = new Rico.Buffer.Base($('data_grid').tBodies[0]);
\r
207 <li>Finally, instantiate the LiveGrid, passing in the DOM id of the HTML table
\r
208 (this allows the LiveGrid to load the column headings from the table's thead section),
\r
209 the Rico.Buffer instance, and any options (in this case the first column gets
\r
210 a width of 50 pixels and the second column gets a width of 80 pixels).
\r
212 var grid_options = { columnSpecs: [ {width:50}, {width:80} ] };
\r
213 var grid = new Rico.LiveGrid('data_grid', buffer, grid_options);
\r
216 <li>Rico.loadModule may finish <em>after</em> the window.onload event.
\r
217 So to ensure that the grid initialization runs after the Rico modules
\r
218 have loaded, you must pass the initialization function to the
\r
219 Rico.onLoad method. Putting all of the javascript together would look like this:
\r
221 <script type='text/javascript'>
\r
222 Rico.loadModule('LiveGrid','LiveGridMenu','greenHdg.css');
\r
224 Rico.onLoad( function() {
\r
225 var buffer = new Rico.Buffer.Base($('data_grid').tBodies[0]);
\r
226 var grid_options = { columnSpecs: [width:50, width:80] };
\r
227 var grid = new Rico.LiveGrid('data_grid', buffer, grid_options);
\r
235 <h2><a name='model3'>Usage Model 3: Loading data from an XML file</a></h2>
\r
237 <ul><li>Define an HTML table, supplying the table header cells, but no table body cells.
\r
238 Including the markup for the bookmark will cause the grid's scroll position to be displayed.
\r
240 <p class="ricoBookmark"><span id="data_grid_bookmark"> </span></p>
\r
241 <table id="data_grid">
\r
244 <th>First column name</th>
\r
245 <th>Second column name</th>
\r
251 <li>Load the Rico javascript and css files necessary to display the grid.
\r
253 Rico.loadModule('LiveGridAjax','LiveGridMenu','greenHdg.css');
\r
257 <dd>This loads the Rico javascript and css files necessary to display a LiveGrid
\r
258 with an AJAX-enabled buffer.
\r
260 <dd>This loads the default grid menu. This menu provides access to all of the LiveGrid capabilities.
\r
261 It adjusts the selections presented to the user based on the column selected
\r
262 and the type of buffer used.
\r
263 You can also choose to use the grid with no menu at all, or to create your own menu
\r
264 customized to the needs of your application.
\r
266 <dd>Rico comes with several sample grid styles: coffee-with-milk,
\r
267 grayedout, greenHdg, iegradient (Internet Explorer only), tanChisel, and warmfall.
\r
268 You may choose one of the included styles or create one of your own.
\r
271 <li>Create a Rico Buffer, which fetches data to populate the table.
\r
272 The AjaxXML buffer makes just one request for data to the supplied URL
\r
275 var buffer = new Rico.Buffer.AjaxXML('/controller/action?format=xml');
\r
278 The URL ("/controller/action?format=xml" in this example) must return data in the following format:
\r
280 <ajax-response>
\r
281 <response type='object' id='data_grid_updater'>
\r
282 <rows update_ui='true' offset='0'>
\r
283 <tr><td>Data for row 1, cell 1</td><td>Data for row 1, cell 2</td></tr>
\r
284 <tr><td>Data for row 2, cell 1</td><td>Data for row 2, cell 2</td></tr>
\r
287 </ajax-response>
\r
290 <li>Finally, instantiate the LiveGrid, passing in the DOM id of the HTML table,
\r
291 the Rico.Buffer instance, and any options (columnSpecs is not required,
\r
292 but shown here as a placeholder for customization of the columns).
\r
294 var grid_options = { columnSpecs: [,] };
\r
295 var grid = new Rico.LiveGrid('data_grid', buffer, grid_options);
\r
298 <li>Rico.loadModule may finish <em>after</em> the window.onload event.
\r
299 So to ensure that the grid initialization runs after the Rico modules
\r
300 have loaded, you must pass the initialization function to the
\r
301 Rico.onLoad method. Putting all of the javascript together would look like this:
\r
303 <script type='text/javascript'>
\r
304 Rico.loadModule('LiveGridAjax','LiveGridMenu','greenHdg.css');
\r
306 Rico.onLoad( function() {
\r
307 var buffer = new Rico.Buffer.AjaxXML('/controller/action?format=xml');
\r
308 var grid_options = { columnSpecs: [,] };
\r
309 var grid = new Rico.LiveGrid('data_grid', buffer, grid_options);
\r
316 <h2><a name='model4'>Usage Model 4: Loading data from an SQL database query</a></h2>
\r
318 <p>The descriptions below apply directly to the ASP and PHP implementations of the Rico LiveGrid plug-ins.
\r
319 The concepts are the same in .net, but the implementation is quite different
\r
320 (examine ex2simple.aspx to see how this gets implemented in .net).
\r
323 <li>Define a session variable that contains the query to be run. The variable name must
\r
324 match the id of the table below. When requesting data, the grid will pass its id
\r
325 to ricoXMLquery, and ricoXMLquery will use it to get the query text from
\r
326 the session variable.
\r
331 session.contents("data_grid")="select ID,Name,City from customers"
\r
338 $_SESSION['data_grid']="select ID,Name,City from customers";
\r
344 Sub Page_Load(Sender As object, e As EventArgs)
\r
345 data_grid.sqlQuery="select ID,Name,City from customers"
\r
346 ' session variable is set by the control
\r
352 <li>Define an HTML table, supplying the table header cells, but no table body cells.
\r
353 Including the markup for the bookmark will cause the grid's scroll position to be displayed.
\r
355 <p class="ricoBookmark"><span id="data_grid_bookmark"> </span></p>
\r
356 <table id="data_grid">
\r
359 <th>Customer #</th>
\r
360 <th>Customer Name</th>
\r
361 <th>City</th>
\r
367 <li>Load the Rico javascript and css files necessary to display the grid.
\r
369 Rico.loadModule('LiveGridAjax','LiveGridMenu','greenHdg.css');
\r
373 <dd>This loads the Rico javascript and css files necessary to display a LiveGrid
\r
374 with an AJAX-enabled buffer.
\r
376 <dd>This loads the default grid menu. This menu provides access to all of the LiveGrid capabilities.
\r
377 It adjusts the selections presented to the user based on the column selected
\r
378 and the type of buffer used.
\r
379 You can also choose to use the grid with no menu at all, or to create your own menu
\r
380 customized to the needs of your application.
\r
382 <dd>Rico comes with several sample grid styles: coffee-with-milk,
\r
383 grayedout, greenHdg, iegradient (Internet Explorer only), tanChisel, and warmfall.
\r
384 You may choose one of the included styles or create one of your own.
\r
387 <li>Create a Rico Buffer, which fetches data to populate the table.
\r
388 Unlike the AjaxXML buffer which fetches all grid data at once, the AjaxSQL
\r
389 buffer fetches data in chunks. This makes it possible for LiveGrid to
\r
390 efficiently display query results containing thousands, or even hundreds of thousands
\r
393 var buffer = new Rico.Buffer.AjaxSQL('ricoXMLquery.asp');
\r
396 The URL ("ricoXMLquery.asp" in this example) utilizes one of the included plug-ins to
\r
397 fetch data from the database and return it to the grid in this XML format:
\r
399 <ajax-response>
\r
400 <response type='object' id='data_grid_updater'>
\r
401 <rows update_ui='true' offset='0'>
\r
402 <tr><td>Data for row 1, cell 1</td><td>Data for row 1, cell 2</td></tr>
\r
403 <tr><td>Data for row 2, cell 1</td><td>Data for row 2, cell 2</td></tr>
\r
405 <rowcount>99</rowcount>
\r
407 </ajax-response>
\r
410 The <rowcount> tag is optional, but should be returned whenever the "get_total"
\r
411 querystring parameter is present in the request.
\r
413 <li>Finally, instantiate the LiveGrid, passing in the DOM id of the HTML table,
\r
414 the Rico.Buffer instance, and any options (columnSpecs is not required,
\r
415 but shown here as a placeholder for customization of the columns).
\r
417 var grid_options = { columnSpecs: [,,] };
\r
418 var grid = new Rico.LiveGrid('data_grid', buffer, grid_options);
\r
421 <li>Rico.loadModule may finish <em>after</em> the window.onload event.
\r
422 So to ensure that the grid initialization runs after the Rico modules
\r
423 have loaded, you must pass the initialization function to the
\r
424 Rico.onLoad method. Putting all of the javascript together would look like this:
\r
426 <script type='text/javascript'>
\r
427 Rico.loadModule('LiveGridAjax','LiveGridMenu','greenHdg.css');
\r
429 Rico.onLoad( function() {
\r
430 var buffer = new Rico.Buffer.AjaxSQL('ricoXMLquery.asp');
\r
431 var grid_options = { columnSpecs: [,,] };
\r
432 var grid = new Rico.LiveGrid('data_grid', buffer, grid_options);
\r
439 <h2><a name='model5'>Usage Model 5: Loading data using a custom callback function</a></h2>
\r
441 <p>This model works the same way as models 3 and 4 except that, rather than fetching
\r
442 data using an xmlHTTPrequest, the data is fetched using javascript callback functions.
\r
443 This allows you to do creative things in the callback function - like call Google Gears.
\r
444 Setting up the callback is very easy. Rather than passing a string containing the data provider's URL
\r
445 to the AjaxXML or AjaxSQL constructor, you just pass the callback function instead.
\r
447 <p>The code that follows is taken from
\r
448 <a href='client/gridJSbuffer.html'>examples/client/gridJSbuffer.html</a>,
\r
449 which uses the AjaxXML buffer. The "jsfetch" callback function
\r
450 returns a 2-dimensional array that is 100 rows long by 5 columns wide.
\r
451 Note that AjaxXML only loads its buffer once (at grid startup), so
\r
452 jsfetch will only be called once.
\r
453 The options hash is identical in structure to the options hash used
\r
454 by Prototype's <a href='http://prototypejs.org/api/ajax/options'>Ajax.Request</a> method.
\r
457 buffer=new Rico.Buffer.AjaxXML(<strong>jsfetch</strong>);
\r
459 function <strong>jsfetch</strong>(options) {
\r
460 Rico.writeDebugMsg("jsfetch");
\r
461 var newRows=[], offset=options.parameters.offset;
\r
462 for (var r=0; r<100; r++) {
\r
464 row.push(offset.toString());
\r
465 row.push(new Date().toString());
\r
466 for (var c=2; c<5; c++) row.push('cell '+r+':'+c);
\r
469 options.onComplete(newRows);
473 <p>The code that follows is taken from
\r
474 <a href='client/gridJSbuffer2.html'>examples/client/gridJSbuffer2.html</a>,
\r
475 which uses the AjaxSQL buffer. The "jsfetch" callback function
\r
476 simulates a 2-dimensional array that is 500 rows long by 5 columns wide.
\r
477 However, only a section of that array is returned during any one callback --
\r
478 just the rows from <code>options.parameters.offset</code> to
\r
479 <code>options.parameters.offset + options.parameters.page_size</code>.
\r
482 buffer=new Rico.Buffer.AjaxSQL(<strong>jsfetch</strong>);
\r
484 function <strong>jsfetch</strong>(options) {
\r
485 var newRows=[], totrows=500;
\r
486 var offset=options.parameters.offset;
\r
487 var limit=Math.min(totrows-offset,options.parameters.page_size)
\r
488 for (var r=0; r<limit; r++) {
\r
490 row.push(new Date().toString());
\r
491 row.push(offset.toString());
\r
492 for (var c=2; c<5; c++) row.push('cell '+(r+offset)+':'+c);
\r
495 options.onComplete(newRows,false,totrows);
499 <p>options.onComplete takes the following parameters:
\r
501 <li>newRows - 2-dimensional array where each item is a string
\r
502 <li>newAttr - 2-dimensional array where each item is an object containing acceptAttr values for the cell,
\r
503 or false if acceptAttr is not being used
\r
504 <li>totalRows - an integer representing the total number of rows in the dataset
\r
505 <li>errMsg - if an error occurs, this is the message text to be displayed to the user
\r
509 <h2><a name='debug'></a>Debugging</h2>
\r
510 <p>Rico 2.0 includes the ability to route time-stamped debug messages to a message log.
\r
511 The log may be an html textarea or the browser's javascript console.
\r
513 <li>If a textarea exists with the id of the LiveGrid table plus '_debugmsgs', i.e.
\r
514 <pre style='margin:3px;'><textarea cols="100" rows="5" id="data_grid_debugmsgs" /></pre>
\r
515 then this textarea will be used for the message log.
\r
516 <li>Alternatively, the textarea may be designated by a call to Rico.setDebugArea()
\r
519 <textarea id='debug' rows='5' cols='80'></textarea>
\r
520 <script type='text/javascript'>
\r
521 Rico.setDebugArea('debug');
\r
525 <li>If no textarea is designated, Rico will attempt to use the browser's
\r
526 built-in javascript console. The following consoles are known to work:
\r
528 <li>The console in Firefox's <a href='http://www.getfirebug.com/'>Firebug</a> add-on
\r
529 <li>The Opera javascript console
\r
530 <li>The Safari javascript console
\r
531 <li>The console in <a href='http://blogs.msdn.com/ie/archive/2008/09/03/developer-tools-in-internet-explorer-8-beta-2.aspx'>IE8's Developer Toolbar</a> (under the Script tab)
\r
535 <p>LiveGrid is programmed to send a number of messages to the message log that may prove helpful in debugging.
\r
536 You can also send your own messages by using Rico.writeDebugMsg(). For example:
\r
538 Rico.writeDebugMsg('My debug message');
\r
541 <h2>Grid Menus</h2>
\r
543 <p>Rico LiveGrids come with a lot of functionality built in. To access that functionality,
\r
544 Rico includes a default set of menus -- defined in ricoLiveGridMenu.js.
\r
545 To use the default menu, simply load the 'LiveGridMenu' module and then
\r
546 assign the grid's menu property to an instance of the Rico.GridMenu class.
\r
548 Rico.loadModule('LiveGridMenu');
\r
550 var ex1=new Rico.LiveGrid ('ex1', buffer, grid_options);
\r
551 ex1.menu=new Rico.GridMenu();
\r
553 <p>By default, the menu will open when a user double-clicks on a grid cell.
\r
554 To change the event that opens the menu, assign a value to the grid's
\r
555 <a href='#menuEvent'>menuEvent</a> option. The following code will open the menu on a right-click:
\r
557 Rico.loadModule('LiveGridMenu');
\r
559 var grid_options = {
\r
560 menuEvent: 'contextmenu'
\r
562 var ex1=new Rico.LiveGrid ('ex1', buffer, grid_options);
\r
563 ex1.menu=new Rico.GridMenu();
\r
565 <p>Rico.GridMenu provides a callback (dataMenuHandler) so that additional menu items can be added.
\r
566 The grid menu is always built dynamically -- customized to the row and column the user
\r
567 has clicked on. So the callback function is called every time the menu is invoked and
\r
568 must add the desired menu items at each invocation.
\r
570 Rico.loadModule('LiveGridMenu');
\r
572 var ex1=new Rico.LiveGrid ('ex1', buffer, grid_options);
\r
573 ex1.menu=new Rico.GridMenu();
\r
574 ex1.menu.options.dataMenuHandler=myCustomMenuItems;
\r
576 function myCustomMenuItems(grid,r,c,onBlankRow) {
\r
577 if (buffer.getWindowValue(r,c)=='Special Value')
\r
578 grid.menu.addMenuItem("Special menu item", specialAction);
580 function specialAction() {
\r
585 <p>It is also possible to create completely custom menus. For an example,
\r
586 see ex5.php/asp/aspx.
\r
592 <li>If you create an element with a DOM id matching the name of the LiveGrid table
\r
593 plus '_bookmark', it will be updated with text indicating
\r
594 the number of records displayed in the grid. The LiveGrid examples typically use
\r
597 <p class="ricoBookmark"><span id="data_grid_bookmark"> </span></p>
\r
599 <li>In order to display properly, a browser displaying a LiveGrid must be operating in
\r
600 <a href="http://www.quirksmode.org/css/quirksmode.html">strict (aka standards) mode</a>.
\r
601 Therefore, you must include a doctype declaration just before the
\r
602 <code> <html> </code> tag. For example:
\r
604 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
\r
605 "http://www.w3.org/TR/html4/strict.dtd">
\r
612 <h3>Constructor</h3>
\r
615 var grid = new Rico.LiveGrid (table_id, rico_buffer, grid_options);
\r
620 <li><strong>table_id</strong> is the DOM id of the table (or div) that will be replaced by a LiveGrid
\r
621 <li><strong>rico_buffer</strong> is a Rico Buffer object, e.g.
\r
623 <li>Rico.Buffer.Base (for non-AJAX tables)
\r
624 <li>Rico.Buffer.AjaxXML
\r
625 <li>Rico.Buffer.AjaxSQL
\r
626 <li>Rico.Buffer.AjaxJSON
\r
628 <li><strong>grid_options</strong> (see below)
\r
631 <h3><a name="options"></a>Options</h3>
\r
636 <dt>visibleRows (rows in .net plug-in)
\r
637 <dd>How many rows of the grid are made visible?
\r
638 A positive integer specifies that the grid should always contain exactly that many rows.
\r
639 <p>Negative values have the following meanings:
\r
641 <li>-1: size grid to client window (default)
\r
642 <li>-2: size grid to whichever is smaller: the client window or the data
\r
643 <li>-3: size grid so that the page body does not have a scrollbar
\r
644 <li>-4: size grid to the parent node in the DOM
\r
646 <p>String values have the following meanings:
\r
648 <li>'window': size grid to client window (default)
\r
649 <li>'data': size grid to whichever is smaller: the client window or the data
\r
650 <li>'body': size grid so that the page body does not have a scrollbar
\r
651 <li>'parent': size grid to the parent node in the DOM
\r
652 <li>'XX%': size grid to XX percent of the total window height
\r
653 <li>'XXpx': size grid to XX pixels
\r
657 <dd>Minimum # of visible rows. Used only when visibleRows < 0. (default: 2 - after Rico 2b3, 1 - up to Rico 2b3)
\r
660 <dd>Maximum # of visible rows. Used only when visibleRows < 0. (default: 50)
\r
662 <dt><a name="defaultWidth"></a>defaultWidth
\r
663 <dd>An integer used in setting the initial width of columns.
\r
664 See the <a href='#width'>column width option</a> for an explanation.
\r
665 (default: -1 if initializing from an HTML table, 100 otherwise)
\r
668 <dd>For some calculations, LiveGrid needs to know the width of scrollbars on the page. (default: 19)
\r
671 <dd>Minimum scroll area width in pixels when width of frozen columns exceeds window width. (default: 100)
\r
677 <dt>offset<dd>First row of data to be displayed (default: 0)
\r
678 <dt>prefetchBuffer<dd>Load the buffer (and therefore the grid) on page load? (default: true)
\r
679 <dt>sortCol<dd>Name or index of column for initial sort
\r
680 <dt>sortDir<dd>Direction of initial sort
\r
681 <br>possible values: 'ASC', 'DESC'
\r
682 <dt>getQueryParms<dd>If true, check the web page's query string for filter parameters and apply
\r
683 any filter that is found. Filter parameters must be of the form "f[x]=" where x is the column index.
\r
687 <h4>Header Configuration</h4>
\r
690 <dd>number of columns on the left side of the grid that should be
\r
691 frozen (like Excel).
\r
694 <dd>A string that defines how headings are displayed to facilitate sorting.
\r
696 <li>'link' -- make headings a link that will sort columns (default)
\r
697 <li>'hover' -- user can click in any part of the heading cell to sort.
\r
698 Heading changes background color when cursor hovers over cell.
\r
699 <li>'none' -- events on headings are disabled
\r
703 <dd>Put sort and filter icons before or after header text (default: true)
\r
705 <dt><a name='allowColResize'>allowColResize</a>
\r
706 <dd>Allow columns to be resized by the user? If true, then resizing for individual columns
\r
707 can be disabled using <a href='#noResize'>noResize</a> in columnSpecs[].
\r
710 <dd>An array of strings that can serve as secondary headings.
\r
711 In LiveGrid Forms, they also serve as the headings for the tabbed panels on the input form.
\r
713 <dt>PanelNamesOnTabHdr
\r
714 <dd>Set to 'true' for the strings in panels[] to be used as secondary headings.
\r
715 In LiveGrid Forms, it may be set to 'false' so that panels[] is only used on the input form.
\r
717 <dt><a name='FilterLocation'>FilterLocation</a>
\r
718 <dd>Specifies the heading row where filters should be placed.
\r
719 -1 causes a new row to be appended to the header and that new row used for filtering.
\r
720 See also the <a href='#filterUI'>filterUI</a> option.
\r
723 <dd>Token in select filters used to indicate "show all values" (default: "___ALL___").
\r
726 <h4>Cookie options</h4>
\r
729 <dt><a name='saveColumnInfo'>saveColumnInfo</a>
\r
730 <dd>Specifies which details to save in the grid's cookie. Only one cookie is used for each grid.
\r
731 Note that the width setting includes the hide/show status of the column.
\r
732 (default: {width:true, filter:false, sort:false})
\r
733 <br>In the .net plug-in, this option is represented by 3 separate properties:
\r
734 saveColumnWidth, saveColumnFilter, saveColumnSort
\r
737 <dd>A string that is prepended to the cookie name. (default: 'RicoGrid.')
\r
740 <dd>Number of days before the cookie expires.
\r
741 If you don't specify it, then the cookie is only maintained for the current session. (default: null)
\r
744 <dd>Sets the top level directory from which the grid cookie can be read.
\r
745 If you don't specify it, it becomes the path of the page that sets the cookie. (default: null)
\r
748 <dd>Tells the browser to which domain the cookie should be sent.
\r
749 If you don't specify it, it becomes the domain of the page that sets the cookie. (default: null)
\r
753 <h4>Highlighting and selection</h4>
\r
757 <dd>a string that specifies what gets highlighted/selected
\r
759 <li>'cursorRow' -- the grid row under the cursor
\r
760 <li>'cursorCell' -- the grid cell under the cursor
\r
761 <li>'menuRow' -- the grid row where the menu is displayed
\r
762 <li>'menuCell' -- the grid cell where the menu is displayed
\r
763 <li>'selection' -- allow the user to select cells
\r
764 <li>'none' -- never highlight
\r
767 <dt>highlightSection
\r
768 <dd>an integer that specifies which section of the table is highlighted
\r
772 <li>3 -- all (default)
\r
776 <dt>highlightMethod
\r
777 <dd>Method used to highlight cells & rows. Possible values:
\r
779 <li>'outline' -- least CPU-intensive on client-side
\r
780 <li>'class' -- adds CSS class to highlighted cell/row (default)
\r
781 <li>'both' -- highlight using both outline and class
\r
785 <dd>When highlighting by class, this is the class name used (default: 'ricoLG_selection')
\r
789 <h4>Export and print</h4>
\r
793 <dd>The maximum number of rows that the user is allowed
\r
794 to Print/Export. Set to 0 to disable print/export. (default: 1000)
\r
797 <dd>Options string passed to <a href='http://www.w3schools.com/htmldom/met_win_open.asp'>window.open()</a>
\r
798 when the export window is created. (default: "height=400,width=500,scrollbars=1,menubar=1,resizable=1")
\r
800 <dt>exportStyleList
\r
801 <dd>An array of CSS attributes that will be extracted from the first visible row of the grid and used
\r
802 to format all rows of the exported table.
\r
803 (default: ['background-color', 'color', 'text-align', 'font-weight', 'font-size', 'font-family'])
\r
807 <h4>Behavior Defaults</h4>
\r
809 <dt><a name='canHideDefault'>canHideDefault</a>
\r
810 <dd>Controls whether columns can be hidden/shown (default: true).
\r
811 Hide/show can be disabled for individual columns using the <a href='#canHide'>canHide</a> property in columnSpecs.
\r
813 <dt><a name='canSortDefault'>canSortDefault</a>
\r
814 <dd>Controls whether columns can be sorted (default: true).
\r
815 Sorting can be disabled for individual columns using the <a href='#canSort'>canSort</a> property in columnSpecs.
\r
817 <dt><a name='canFilterDefault'>canFilterDefault</a>
\r
818 <dd>Controls whether columns can be filtered (default: true).
\r
819 Filtering can be disabled for individual columns using the <a href='#canFilter'>canFilter</a> property in columnSpecs.
\r
821 <dt><a name='dndMgrIdx'>dndMgrIdx</a>
\r
822 <dd>Specifies which drag-and-drop management zone should be used for drag operations (default: 0).
\r
823 This only needs to be specified if the web page uses multiple distinct zones.
\r
828 <h4>Event control</h4>
\r
830 <dt><a name='menuEvent'>menuEvent</a>
\r
831 <dd>A string that specifies when the grid's menu should be invoked
\r
833 <li>'click' -- invoke menu on single-click
\r
834 <li>'dblclick' -- invoke menu on double-click (default)
\r
835 <li>'contextmenu' -- invoke menu on right-click
\r
836 <li>'none' -- no pop-up menu
\r
840 <dd>A boolean value specifying whether to resize the grid during a window.resize event.
\r
841 This should be set to false when the grid is embedded in an accordian. (default: true)
\r
845 <h4>Event handles</h4>
\r
847 <dt style='font-weight:normal;'>Event handlers cannot be passed in options to the constructor, but may be set after the LiveGrid has been constructed.
\r
848 <dt>sortHandler<dd> (default: Rico.LiveGridMethods.sortHandler -- bound)
\r
849 <dt>filterHandler<dd> (default: Rico.LiveGridMethods.filterHandler -- bound)
\r
850 <dt>onRefreshComplete<dd> (default: Rico.LiveGridMethods.bookmarkHandler -- bound)
\r
851 <dt>rowOverHandler<dd> (default: Rico.LiveGridMethods.rowMouseOver -- bound as event listener)
\r
852 <dt>mouseDownHandler<dd> (default: Rico.LiveGridMethods.selectMouseDown -- bound as event listener)
\r
853 <dt>mouseOverHandler<dd> (default: Rico.LiveGridMethods.selectMouseOver -- bound as event listener)
\r
854 <dt>mouseUpHandler<dd> (default: Rico.LiveGridMethods.selectMouseUp -- bound as event listener)
\r
855 <dt>onscroll<dd> called whenever the grid is scrolled vertically. (default: null)
\r
856 <dt>onscrollidle<dd> called 1.2 seconds after the grid is scrolled vertically. (default: null)
\r
857 <dt>click<dd> called when a grid cell is clicked. (default: null, unless menuEvent='click')
\r
858 <dt>dblclick<dd> called when a grid cell is double-clicked. (default: null, unless menuEvent='dblclick')
\r
859 <dt>contextmenu<dd> called when a grid cell is right-clicked. (default: null, unless menuEvent='contextmenu')
\r
862 <h4><a name="column"></a>Per-column configuration</h4>
\r
864 <dt style='font-weight:normal;'>Options for each individual column are contained in the columnSpecs option.
\r
865 columnSpecs is an array with an entry for each column.
\r
866 Each column entry can either be:
\r
869 <li>null (default) -- in which case the column is formatted according to the spec in Rico.TableColumn.DEFAULT.
\r
870 If most columns in your grid share common formatting, then it may make sense to override
\r
871 the default column spec for that grid:
\r
873 Rico.TableColumn.DEFAULT = {ClassName:'aligncenter', width:50};
\r
875 In this case, any column with no spec will have content aligned to the center and a width of 50 pixels.
\r
877 <li>a string -- provides a simple way to specify a column format.
\r
878 These values are built-in: DOLLAR, EURO, PERCENT, QTY, DEFAULT.
\r
879 It is also possible to define your own. This example, which defines a temperature format,
\r
880 is taken from weather.php:
\r
882 Rico.TableColumn.TEMP = {type:'number', decPlaces:0,
\r
883 ClassName:'alignright', suffix:'&deg;C', width:50};
\r
886 columnSpecs : [{width:120},{width:70},{width:70},{width:100},
\r
887 'TEMP','TEMP','TEMP',
\r
888 {width:150},{width:200},{width:60}]
\r
892 <li>an object -- containing entries for one or more of the properties listed below.
\r
893 Here is an example that contains specifications for columns 0, 1, and 3.
\r
894 Column 2 would get the default spec.
\r
896 columnSpecs : [{canSort:false, noResize:true, ClassName:'alignright'},
\r
897 {ClassName:'aligncenter'},
\r
904 <dd>An alternate way of specifying the heading text for a column.
\r
905 Only used by LiveGrid if the grid id refers to a <div> instead of an html table.
\r
907 <dt><a name='canSort'>canSort</a>
\r
908 <dd>Column can be sorted. (default: <a href='#canSortDefault'>grid.options.canSortDefault</a>)
\r
910 <dt><a name='canFilter'>canFilter</a>
\r
911 <dd>Column can be filtered. (default: <a href='#canFilterDefault'>grid.options.canFilterDefault</a>)
\r
914 <dd>Column cells can serve as the source for a drag-n-drop operation. The "DragAndDrop" module must be loaded.
\r
915 The temporary drag objects have a class of "LiveGridDraggable".
\r
916 For an example, see <a href='client/drag_and_drop_grid.html'>drag_and_drop_grid.html</a>. (default: false)
\r
918 <dt><a name='canHide'>canHide</a>
\r
919 <dd>Column can be hidden/unhidden. (default: <a href='#canHideDefault'>grid.options.canHideDefault</a>)
\r
922 <dd>Controls whether the column is visible at grid startup (default: true).
\r
923 If <a href='#saveColumnInfo'>grid.options.saveColumnInfo.width</a> is true
\r
924 and there is a value in the cookie for this column, the cookie value will take precedence.
\r
926 <dt><a name='width'>width</a>
\r
927 <dd>An integer specifying the initial width (in pixels) for the column.
\r
928 Here is the algorithm LiveGrid uses for setting the initial width of each column:
\r
930 <li>If <a href='#saveColumnInfo'>options.saveColumnInfo.width</a> is true and column information is present in the grid's cookie
\r
931 (due to the user previously performing a resize on that grid's column),
\r
932 then the width in the cookie is used. Otherwise...
\r
934 <li>If there is a width spec for the column in options.columnSpecs[], then the width in the spec is used. For an example, see ex3.php/asp/aspx. Otherwise...
\r
936 <li>If <a href='#defaultWidth'>options.defaultWidth</a> is true (default) and the grid header is initialized from an html table, then the column's width in the html table is used.
\r
937 You can usually control the column widths of the initial table by using col tags (e.g. <col style='width:40px;' >).
\r
938 If the total table width is less than the browser width then this works; however if it is greater, then the browser often ignores <col width>
\r
939 and tries to squeeze all of the columns into the available window width. Thus, using this method to set the column width is unreliable. Otherwise...
\r
941 <li>If <a href='#defaultWidth'>options.defaultWidth</a> is false, then the column's width is set to options.defaultWidth (which defaults to 100).
\r
943 Therefore, the most reliable way to set column widths in LiveGrid and SimpleGrid is to specify a width for every column in options.columnSpecs[].
\r
944 If many columns share a common width, then you can shortcut this somewhat by setting options.defaultWidth=false,
\r
945 and setting options.defaultWidth to the common width.
\r
947 <dt><a name='noResize'>noResize</a>
\r
948 <dd>Allow column to be resized? (default <a href='#allowColResize'>grid.options.allowColResize</a> )
\r
951 <dd>By default, LiveGrid assigns a unique CSS class name to each
\r
952 column, which follows the naming convention: table_id + '_col' + column_index.
\r
953 For example, the fourth column in the grid 'mygrid' would have the class name
\r
954 'mygrid_col3'. The value of the ClassName option overrides this default name.
\r
955 The ClassName option is most commonly used to specify column alignment via the
\r
956 Rico-provided 'alignright' and 'aligncenter' classes.
\r
957 So, if you wanted the first 3 columns in your grid to be displayed with white
\r
958 text on a red background, you could do either of the following:
\r
962 .mygrid_col0 div.ricoLG_cell,
\r
963 .mygrid_col1 div.ricoLG_cell,
\r
964 .mygrid_col2 div.ricoLG_cell {
\r
966 background-color: red;
\r
974 .WhiteOnRed div.ricoLG_cell {
\r
976 background-color: red;
\r
980 columnSpecs : [{ClassName:'WhiteOnRed'},
\r
981 {ClassName:'WhiteOnRed'},
\r
982 {ClassName:'WhiteOnRed'},
\r
986 Finally, please note that this ClassName is not applied to the grid headings -
\r
987 use a align="right" on the <th> tag to accomplish the header alignment.
\r
989 <dt>type (DataType in .net plug-in)
\r
990 <dd>A string containing one of these values:
\r
992 <li>text (default) - plain text.
\r
993 <li>number - column value is treated as a number,
\r
994 and any <a href='#NumberFormatting'>number formatting options</a>
\r
995 supplied in the column specification are applied.
\r
996 <li>datetime - column value is treated as a date & time,
\r
997 and any <a href='#DateFormatting'>date formatting options</a>
\r
998 supplied in the column specification are applied.
\r
999 <li>utcaslocaltime - column/database value is treated as a GMT/UTC date & time, and any <a href='#DateFormatting'>date formatting options</a>
\r
1000 supplied in the column specification are applied. Before display, the value is converted to the user's local time zone.
\r
1001 <li>date - column value is treated as a date, and any <a href='#DateFormatting'>date formatting options</a>
\r
1002 supplied in the column specification are applied.
\r
1003 <li>html - column values are displayed directly to the grid cell.
\r
1004 Any HTML markup gets copied into the cell.
\r
1008 <dt><a name='control'></a>control
\r
1009 <dd>An object that can be used to provide special formatting for a column.
\r
1010 Several column controls are provided with LiveGrid. The code for them
\r
1011 resides in ricoLiveGridControls.js. Here is a brief description of the
\r
1012 provided controls:
\r
1014 <dl style='font-size:smaller;'>
\r
1015 <dt>Rico.TableColumn.checkboxKey(showKey)
\r
1016 <dd>Display unique key column as: <checkbox> <key value>
1017 and keep track of which keys the user selects.
1018 Key values should not contain <, >, or &.
1020 <dt>Rico.TableColumn.checkbox(checkedValue, uncheckedValue, defaultValue, readOnly)
\r
1021 <dd>Display column as checkboxes. Database column should contain only two-values (e.g. yes/no).
1022 The following code is taken from ex7 (column values are 1 and 0):
\r
1024 columnSpecs: [{canHide:false,
\r
1025 control:new Rico.TableColumn.checkbox('1','0'),
\r
1026 ClassName:'aligncenter'},
\r
1030 <dt>Rico.TableColumn.textbox(boxSize, boxMaxLen, readOnly)
\r
1031 <dd>Display the column value in a text box.
\r
1033 <dt>Rico.TableColumn.HighlightCell(chkcol,chkval,highlightColor,highlightBackground,chkop)
\r
1034 <dd>Highlight a grid cell when a particular value is present in the specified column.
\r
1035 chkop optionally specifies the comparison to be performed: ==, !=, <, <=, >, >=.
\r
1036 If not specified, then == is used.
\r
1037 The following code is taken from ex2highlight and highlights the entire row when column 1
\r
1040 var CustId='HANAR';
\r
1042 var highlight=Rico.TableColumn.HighlightCell;
\r
1045 { control:new highlight(CustIdCol,CustId,'red','yellow') },
\r
1046 { control:new highlight(CustIdCol,CustId,'red','yellow') },
\r
1047 { control:new highlight(CustIdCol,CustId,'red','yellow') },
\r
1048 { control:new highlight(CustIdCol,CustId,'red','yellow') },
\r
1049 { control:new highlight(CustIdCol,CustId,'red','yellow') },
\r
1050 { type:'date', control:new highlight(CustIdCol,CustId,'red','yellow') },
\r
1051 { type:'date', control:new highlight(CustIdCol,CustId,'red','yellow') }]
\r
1054 <dt>Rico.TableColumn.bgColor()
\r
1055 <dd>Database value contains a css color name/value
\r
1057 <dt>Rico.TableColumn.link(href,target)
\r
1058 <dd>Database value contains a url to another page.
\r
1059 The href parameter may contain references to grid values by including "{x}" in the string,
\r
1060 where x is a column number. The following code is taken from ex6:
\r
1063 {control:new Rico.TableColumn.link('ex2.asp?id={0}','_blank'),
\r
1068 <dt>Rico.TableColumn.image()
\r
1069 <dd>Database value contains a url to an image.
\r
1070 The following code is taken from photos.php:
\r
1072 imgctl=new Rico.TableColumn.image();
\r
1075 {control:imgctl,width:90},,,
\r
1076 {type:'datetime'},{width:200}]
\r
1079 <dt>Rico.TableColumn.lookup(map, defaultCode, defaultDesc)
\r
1080 <dd>Map a database value to a display value
\r
1082 <dt>Rico.TableColumn.MultiLine()
\r
1083 <dd>Overcomes issues when displaying multi-line content (i.e. content with <br> tags) in IE6 and IE7
\r
1087 <br>It is also possible to write your own column control, which
\r
1088 implements logic specific to your application. Here is an example:
\r
1090 // Display values white on black if
\r
1091 // first column contains the value "reverse"
\r
1092 // Usage: { control:new MyCustomColumn() }
1093 MyCustomColumn = Class.create();
1095 MyCustomColumn.prototype = {
1096 initialize: function() {},
1098 _clear: function(gridCell,windowRow) {
1099 gridCell.style.color='';
1100 gridCell.style.backgroundColor='';
1101 gridCell.innerHTML='&nbsp;';
1104 _display: function(v,gridCell,windowRow) {
1105 var col0=this.liveGrid.buffer.getWindowValue(windowRow,0);
\r
1106 if (col0=="reverse") {
\r
1107 gridCell.style.color='white';
1108 gridCell.style.backgroundColor='black';
\r
1110 gridCell.style.color='';
1111 gridCell.style.backgroundColor='';
1113 gridCell.innerHTML=this._format(v);
1118 <dt><a name='filterUI'></a>filterUI
\r
1119 <dd>If a <a href='#FilterLocation'>FilterLocation</a> option is specified for the grid, then filterUI will control
\r
1120 how each column is filtered. If filterUI is:
\r
1122 <li>null or omitted, then no filter is displayed for the column.
\r
1123 <li>'t' - will generate a text box filter and the records being displayed
\r
1124 are filtered as the user types.
\r
1125 <br>May optionally be followed by a caret (^) to
\r
1126 indicate that text box values should match the beginning of the column value.
\r
1127 Otherwise, they can match anywhere in the column's value.
\r
1128 <br>May also be followed by a number to indicate the size of the text box (default size is 10).
\r
1131 // will create a text box that is 20 characters wide
\r
1132 // text typed into the box will be compared to
\r
1133 // the beginning of each column value
\r
1135 <li>'s' - will generate a select list filter with all possible column values contained in the list.
\r
1136 Populated using a 'select distinct' query if the grid's source is a SQL query.
\r
1140 <dd>Specifies that the filter should be applied to a different column. For example, ex3livegrid.asp/aspx/php
\r
1141 uses this feature to filter the order and ship date columns by year. The full date is shown in the column
\r
1142 in which the filter appears; however, there is another hidden, calculated column containing "year(orderdate)"
\r
1143 to which the filter is applied.
\r
1147 <dt style='color:navy;'><a name='NumberFormatting'></a><em>Number formatting:</em>
\r
1150 <dd>The value is multiplied by this number before it is displayed. (default: 1)
\r
1153 <dd>Number of places to the right of the decimal point. (default: 0)
\r
1156 <dd>Boolean indicating whether to insert thousands separator. (default: true)
\r
1159 <dd>Specifies how negative numbers should be displayed. Possible values:
\r
1161 <li>L=leading minus (default)
\r
1162 <li>T=trailing minus
\r
1167 <dd>A string added to the beginning of the number. Typically a currency symbol.
\r
1170 <dd>A string added to the end of a number. For example, a "%" symbol.</dd>
\r
1174 <dt style='color:navy;'><a name='DateFormatting'></a><em>Date formatting:</em>
\r
1177 <dd>A string specifying how the date or datetime should be displayed. Default is "translateDate", which means
\r
1178 that the dateFmt and timeFmt strings in the RicoTranslate object are used
\r
1179 (this defaults to "mm/dd/yyyy" for dates and "mm/dd/yyyy hh:nn:ss a/pm" for datetimes,
\r
1180 but is overridden by the various language translation files).
\r
1181 If dateFmt="localeDate", then the value is formatted using javascript's built-in toLocaleDateString() function.
\r
1182 If dateFmt="localeDateTime", then the value is formatted using javascript's built-in toLocaleString() function.
\r
1183 The dateFmt string may contain the following special character sequences:
\r
1186 <li>yyyy - 4 digit year
1187 <li>yy - 2 digit year
1188 <li>mmmm - month name
1189 <li>mmm - 3 character month name abbreviation. In Asian languages this often doesn't make sense - in these cases it returns the full month name (same as mmmm).
1190 <li>mm - 2 digit month number (zero padded)
1191 <li>m - 1 or 2 digit month number
1192 <li>dddd - day-of-the-week
1193 <li>ddd - 3 character day-of-the-week abbreviation
1194 <li>dd - 2 digit day number (zero padded)
1195 <li>d - 1 or 2 digit day number
1196 <li>hh - 2 digit hour, 12-hour clock (zero padded)
1197 <li>h - 1 or 2 digit hour, 12-hour clock
1198 <li>HH - 2 digit hour, 24-hour clock (zero padded)
1199 <li>H - 1 or 2 digit hour, 24-hour clock
1200 <li>nn - 2 digit minutes (zero padded)
1201 <li>ss - 2 digit seconds (zero padded)
1202 <li>a/p - a or p (for am or pm)
1206 // display first column as "month year"
\r
1207 columnSpecs : [{type:date, dateFmt:'mmm yyyy'}]
\r
1212 <dd>A string added to the beginning of the date.
\r
1215 <dd>A string added to the end of a date. For example, you could use this to include a time zone:
\r
1217 // indicate that times are GMT/UTC
\r
1218 columnSpecs : [{type:datetime, suffix:' UTC'}]
\r
projects / infodrom / rico3 / blob