Upgrade to Pro Version 2.2.0

[paramvir]

Dear All

It's time to upgrade to Pro version 2.2.0 as it adds many tempting features to a powerful grid asked for by ParamQuery's members which make it behave like MS Excel spreadsheet and Google docs, most prominent among them are as follows:

1) Copy / paste functionality: At times we have useful data in an Excel spreadsheet, Google spreadsheet or any other spreadsheet program which we want to move to ParamQuery Grid easily. And at other times we wish to do the opposite i.e., we want to move the data from ParamQuery to those applications and sometimes to move the data from one ParamQuery spreadsheet to another ParamQuery spreadsheet! 

Copy / paste functionality of ParamQuery provides fuss free ability to do it with shortcut keys Ctrl - C, Ctrl - V, thus breaking the barrier between desktop applications and web applications.

Due to browser restrictions, copy / paste should be limited to few dozen thousand cells. As an example, this demo supports copy / paste for 1,00,000 cells.

http://paramquery.com/pro/demos/infinite
 

2) Support for undo / redo. Many a times we wish to revert the changes we recently made in the grid during inline editing, copy / paste or through addRow/updateRow/deleteRow API. It's during these moments that undo comes to the rescue and sends the grid data back in time

Please check the change log included in the SDK and API for 2.2.0 for more details. Also check out the new demos to see the application of new features:

http://paramquery.com/pro/demos/copy_paste
http://paramquery.com/pro/demos/editing_instant

Best Regards
The ParamQuery Team

[paramvir]

Migration notes from 2.1.0 to 2.2.0:

1) commit refreshes the view only when rows having different data( than already present in grid) are passed to commit method. So in some cases it may be required to call refreshRow or other variants of refresh methods after commit. For example in this demo http://paramquery.com/pro/demos/editing it's required to call refreshRow after commit in update function ajax success callback.

2) Validations: there is no need to call isValid method from cellBeforeSave event to run validations.

3) code in cellSave event ( which fires only after inline editing of cell ) may be required to be moved to change event if compatibility  of changes due to copy / paste is required.