Ammar Yasir a écrit : Hi Ammar, my answer is based on the assumption that the table Search page is more known than the multi-table query generator -- it's been my experience so far, anyway. I suggest to add in table Search, Options section a checkbox "Zoom search"; when checked, another section would reveal itself, containing particular options for this feature.

Also, when checked, the "Select columns" section could be changed to guide the user into selecting exactly two columns. Not sure if the current "select multiple" control is the best in this case, it's up to you to propose something suitable. However I'm not sure how this would integrate with the multi-table query generator.

On Wed, May 18, 2011 at 9:10 PM, Marc Delisle &lt;marc(a)infomarc.info <mailto:marc@infomarc.info>> wrote: Marc Delisle a écrit : discussed generator is less need to be more put the is more experience so containing Or the Zoom search checkbox could be always visible, to better promote it. Maybe we could put two sub tabs on the table_select page. One will allow for table search and the other for zoom search.

up to multi-table query -- Marc Delisle http://infomarc.info

Hi, I pushed my work. I just tried to add a sub-tab on the table search page, one for the normal search and the other for zoom search. I just wanted to get back feedback on whether the design will be okay to proceed? Please don't mind how I have coded for now, just coded very quickly to get a basic design of the interface. I'll code it properly after suggestions. Since user needs to select only two columns in the zoom search page, instead of listing out all columns I provided two select boxes where user will select the two columns first and I'll display the field type, collation, operator and value based on that later. Also since we don't need to display the results, the options link on that page was removed. One more thing: For tabs, if I am not providing any link then the mouse cursor changes to X and they appear as disabled. How to change that? Regards, Ammar Yasir http://repo.or.cz/w/phpmyadmin/ammaryasirr.git

On Mon, May 23, 2011 at 8:11 PM, Marc Delisle &lt;marc(a)infomarc.info <mailto:marc@infomarc.info>> wrote: Ammar Yasir a écrit : proceed? quickly to type, don't removed. mouse Ammar, I think that the two-tabbed interface will do the job. A few remarks: - you have a few undefined variables; in case you are not seeing them, please use "$cfg['Error_Handler']['display'] = true" in your config.inc.php - please merge the original master to your repository, today and regularly; from http://wiki.phpmyadmin.net/pma/Git#Publishing_changes_for_merge You should also regularly merge back the changes done in official repository: git checkout yourbranch git remote update origin # assuming official repository is called origin git merge origin/master - in your jQuery you are comparing with "Table Search" and this won't work with localization - in pmahomme theme, labels "Table Search", "Zoom search" are difficult to read - the red X comes from the "error" class so try to find out why your element has this class -- Marc Delisle http://infomarc.info Hi, I pushed my work. I have added a new file tbl_zoom_select.php which contains the interface. I tried to code everything in tbl_search page but the code becomes very complicated and I had to use a lot of If/else conditions, so i think it will become even more complicated when I'll experiment with plotting libraries. With a new form its better to switch between the normal table search and zoom search forms without using jQuery. Also, in this form a user can select two same columns but with different search criteria (for example, a film with rating G and a film with rating PG-13) so the query generation for this case cannot be handled in tbl_select.php. It generates a wrong query, so the query generation part of this interface also works a bit differently. It generates two queries, one for each column criteria. I know some code has to be duplicated, but I think its better to develop it as a different component. Otherwise if there are some modifications in the zoom-search part, a lot of changes have to be done in the tbl_select.php page. Its just what I thought, I'll do the interface again if code duplication is an issue.

1) As you proposed, Getting the list and number of fields. 2) The where clause generation in the query-building part. Should we also do for the HTML part? Some part of that (for example the foreign keys display part) is common but also has HTML content embedded. Apart from that since the zoom-search form takes the field as input so rest of the form is based on that constraint. So I was thinking that the HTML part can stay as it is.

Parts refactored are: - Setting titles (titles['Browse']]) - getting fields list (getting column details) - setting sub-tabs (Table search and Zoom search) - setting table header of QBE display - displaying foreign data - search criteria input elements (HTML content generation for the input elements)

In libraries/tbl_select.lib.php, please describe for each function the parameters and return values; see an example in libraries/server_synchronize.lib.php. About the syntax, please use spaces around operators. Instead of $i-1 use $i - 1

On Tue, May 31, 2011 at 10:14 PM, Marc Delisle &lt;marc(a)infomarc.info <mailto:marc@infomarc.info>> wrote: Ammar Yasir a écrit : input Very good! Another trick you can use: when a function returns an array, like your PMA_tbl_getFields(), to fill all the returned values in one statement you can use this syntax: list($fields_list, $fields_type, $fields_collation, $fields_null) = PMA_tbl_getFields($table,$db); I made some more changes.

Should I proceed now to try the charting libraries?

On Wed, Jun 1, 2011 at 1:55 AM, Marc Delisle &lt;marc(a)infomarc.info&gt; wrote: Madhura is using it for his GIS visualization. Tyron proposed real-time charting but I don't think it'll be of much help in our case. > > Hi Ammar,

On Wed, Jun 1, 2011 at 4:30 PM, Madhura Jayaratne &lt;madhura.cj(a)gmail.com <mailto:madhura.cj@gmail.com>> wrote: On Wed, Jun 1, 2011 at 2:10 AM, Ammar Yasir &lt;ammaryasir.88(a)gmail.com <mailto:ammaryasir.88@gmail.com>> wrote: On Wed, Jun 1, 2011 at 1:55 AM, Marc Delisle &lt;marc(a)infomarc.info <mailto:marc@infomarc.info>> wrote: Ammar Yasir a écrit : &lt;marc(a)infomarc.info <mailto:marc@infomarc.info> wrote: generation for the array, like your in one statement $fields_null) = OK. There are still a few tab characters (found some in libraries/tbl_select.lib.php). Yes but in your proposal you wrote that you preferred jQuery-SVG so I assume you'll try this one first? I'll try SVG first. I'm following what others have to say about SVG, Madhura is using it for his GIS visualization. Tyron proposed real-time charting but I don't think it'll be of much help in our case. Hi Ammar, I'm not sure what exactly your requirement is. But pls have a look at the visualization of data at [1] by clicking on the 'Visualize GIS data' link in the 'Query results operations' section towards the bottom of the page. Try out zooming by double clicking and panning by dragging. I believe you are looking for something like this for your zoom search feature.

Madhura Jayaratne a écrit : Madhura, I have issues operating panning and zooming. Here is the scenario: 1. Browse world_cities and click Visualize GIS data 2. Click-drag: pans OK 3. Double-click: this is a zoom out, I guess 4. Click-drag: no panning 5. Click "zoom out": data points are enlarging, isn't this a zoom-in? Marc,

Madhura Jayaratne a écrit : (...) 'Visualize Madhura, ok, panning and zooming are fine now. Is the saving feature ready? I tried to save in PNG and got a bunch of binary data on-screen. Saving in PDF generates Fatal error: Call to undefined method PMA_GIS_Visualization::toFileAsPdf() in /srv/http/pma.cihar.com/gsoc-madhura/libraries/gis_visualization.lib.php on line 161 -- Marc Delisle http://infomarc.info Hi Marc,

On Thu, Jun 2, 2011 at 4:27 AM, Madhura Jayaratne &lt;madhura.cj(a)gmail.com&gt; wrote: a Meanwhile pma.cihar.com/gsoc-madhura/libraries/gis_visualization.lib.php yet of the Just in case I'm allowed to use Highcharts, could you make your conversion code generic enough so I could use it too? :) And just for your information, the current SVG converter of highcharts uses following post variables to a php file that calls a java tool (source is available btw): * $tempName string The desired filename without extension * $type string The MIME type for export. * $width int The pixel width of the exported raster image. The height is calculated. * $svg string The SVG source code to convert. Hi Tyron,