[Catalyst-commits] r13866 - trunk/examples/CatalystAdvent/root/2010/pen

[dhoss at dev.catalyst.perl.org]

Author: dhoss
Date: 2010-12-16 23:07:15 +0000 (Thu, 16 Dec 2010)
New Revision: 13866

Modified:
   trunk/examples/CatalystAdvent/root/2010/pen/cat-rest-and-jqgrid.pod
Log:
middle-authoring commit

Modified: trunk/examples/CatalystAdvent/root/2010/pen/cat-rest-and-jqgrid.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2010/pen/cat-rest-and-jqgrid.pod	2010-12-16 22:51:52 UTC (rev 13865)
+++ trunk/examples/CatalystAdvent/root/2010/pen/cat-rest-and-jqgrid.pod	2010-12-16 23:07:15 UTC (rev 13866)
@@ -1 +1,5 @@
 =head1 Catalyst::Controll::REST, jQgrid, and You.
+
+Datagrids are a pretty big thing nowadays.  Every reasonable JavaScript framework has a solution for creating them, and for good reason.  You can get a really simple, data-agnostic CRUD interface up and running that has quick sorting features, pagination, bulk create/delete/update, and easy search features.  These are all extremely useful for situations in which you have large datasets you have to deal with in big chunks at a time.  Tangible scenarios include admin interfaces, store product inventory lists, email listings, etc.  This is all good and gravy, given we have a JavaScript UI solution to *displaying* the data, but how do we get data *into* it, reasonbly, and extensibly? We use my good friend L<Catalyst::Controller::REST|http://search.cpan.org/~bobtfish/Catalyst-Action-REST-0.87/lib/Catalyst/Controller/REST.pm>.  Folks have talked about this fella before, but not exactly in this capacity. See, things like flexigrid from jQuery also give you a nice grid interface, but the CRUD factor isn't quite as easy as with jQgrid.  So I'd like to take some time and explain how to use jQgrid for your datagrid instances, and show you why it's a bit easier.
+
+=head2 PACKING LIST