In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Relationship Graph

[ View Issue ] [ Dependency Graph ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0000438	[In-Portal CMS] Admin Interfaces	feature request	always	2009-12-06 22:44	2009-12-11 00:13

Reporter	alex	View Status	public
Assigned To
Priority	normal	Resolution	open
Status	active

Summary	0000438: Converting Admin Grids to Ajax
Description	1. Add "custom_blocks_template" parameter to "grid" block. The value of this parameter is template path, where all custom cell blocks, that are used in this grid are defined. 2. Move contents of current "grid" block to new template (will be one template, used on all grids) and name it "incs/ajax_grid.tpl" for example. 3. Replace current "grid" block content with container <div> element and include of "incs/ajax_grid.tpl" template (this prevents additional ajax query on initial grid load). 4. Each grid action will actually get "incs/ajax_grid.tpl" template contents (via ajax) and pass all "grid" block parameters (from template) to that template in url (around 7 parameters at most). This approach requires only one action to be taken to convert all customized (user-made) grids to work: move all user-defined grid blocks to separate template and specify it's name in "grid"'s block parameter. We need to do extra programming to be able to update static template parts (ones, that doesn't come from ajax), like search query from ajax respoce (something like that already happens in catalog). Also catalog/advanced view has quite different implementation, that also need to be converted, but we can do it later of course, because it doesn't intersect with proposed idea's implementation. Also need to move all code, that works with grid from end template (like setting dependent buttons and so on) to new jQuery event, like onAfterGridLoad and do it all there, but this is nothing comparing to the benefits we will get of converting to ajax all grids.
Additional Information

Web Development by Intechnic

In-Portal Open Source CMS