…he original fork. Switched over to using markdown as the mark up language.
…ues from the selected master row. $name entries in the caption string will be replaced the the column with name value in the selected row. If no $name entries are present then the value for the foreign_key_column will be appended to the caption.
…r supplied option. This is now handled automatically.
… columns and master/slave detail information) has been move out of the default_options to allow more dynamic generation needed to support external controls. External controls allow buttons, drop down menus, etc. to inject additional parameters into the post data sent by the grid to the controller. This can be used in some controller specific way or to change/add to the parameters used to filter or search.
…g process to be more Rails like and to pave the way for additional search parameters to be injected into the params hash sent to the server and acted upon.
…o they no longer show data as no row is now selected in the master grid.
…e the current_page starts from 1 and not 0 as assumed by the method.
…ute holding the master foreign key to be different to the attribute in the slave detail table holding the key to be matched.
… displayed. This has some important consequences (apart from not being backwards compatible): 1. The controllers are more rails-like in that they have no knowledge about a view. 2. The same controller can respond to the same grid/model in different views and each grid/model view can show different model attributes. 3. The same controller can handle requests from master-detail views as well as slave-detail views. 4. There is less duplication because of (2 and (3) so the controllers and views are more DRY. To make existing controllers compatible just remove the second parameter to the grid_* method calls. The GRID_COLUMNS declaration can also be removed. To make existing views compatible add the :slave_detail => true attribute to the grid attributes.
…causes sections of the gird to go blank when encountered).
… it was inadvertently deleted.
… be updated if necessary to include jquery-ui as it is needed for the columnChooser option.
…d to be loaded for rails < 3.1 and rails >= 3.1
… grid option). Updated version of jquery to 1.7 and jquery-ui to 1.8.16.
…ion and if >=3.1.0 will use the new asset directory instead of public. It also selects between the source or minified version of jqgrid as rails 3.1.0 will automatically minify in production.
…olves creating a controller for each detail grid rather than using the master grid controller to do the detail grid's work. The command line syntax has changed a little so a detail model name can also be passed in. See generator file for comments and examples.
…nges in how detail grids are specified).
…used and no the minified version as the new asset pipeline in 3.1.0 will do the minification for us in deployment (and makes debugging easier in development). jqgrid options are now merged recursively so the user can change one of the sub option hashes (such as :edit_optoins) without having to replace the whole option.
Changed filter_on_params to return JSON to refactor more common code out of the views. Updated the generator to reflect this.
… so for example inline editing and master-detail views will work together, or master with multiple detail view can be used. Changed how master-detail views are defined. The options hash key is now :master_details and the value for this key is either a hash (for a single detail) or an array of hashes (for multiple details). A detail hash has the following keys: :grid_id the id of the grid to use to display the detail view :url the url string to a access the detail attributes :caption caption string
… not to test first).
… public to emphasise their importance.
There are two problems - firstly rails doesn't seem to be honouring the Date::DATE_FORMATS[:default] when dates are being converted from strings during update_attributes so the conversion are done manually now. Secondly the Date to json conversion was also ignoring the default DATE_FORMATS setting so the to string conversions are done before the data is handed off as part of the render operation.
…g from 3.8.2 to 4.0 where error messages reported from editing a row were failing to be displayed.
…odel's column definitions rather than inferring from the record as a record's attribute may be nil hence a valid type conversion couldn't be done so comparisons with other records will give spurious results.
… also excluding post_data doesn't seem necessary (at least no errors occur with it gone) so potentially strengthens security.