Menu
▾
▴
#1121 (ok 3.4) AJAX conversion
Would love to have the tool use AJAX to speed up the interface and usage.
I'd be willing to build the thing myself if I thought it would be adapted into the public version. Not going to go through all that work just for myself, not to mention not being able to upgrade alongside new versions of PMA. :)
Agreed, PMA should totally start using AJAX. I would also be willing to develop (or assist garethop in developing) an AJAX version, provided it really is going to be used for the public version.
If not garethop, perhaps we could do that ourselves and offer it as an add-on. Would still be way better to do directly as a part of PMA.
Great work guys!
That could be interesting to build it as an add-on or a plugin of some sort.
I need to analyze the code and find out how much of the code is re-usable, instead of inline code and functions that output HTML. :)
I'd just lose my mind to go through all the work just to have a new version come out and have to find all the differences between versions and upgrading the AJAX version separately. Especially if I was continuing it alone.
pedm: lets start some planning. I'm going to go through the functionality and start making a construct list of the existing PMA functionality...
Hi Gareth and Patrick,
one part of phpMyAdmin already uses AJAX: the Designer feature. But it's true there could be more parts. Don't be afraid, we would definitely merge your code into the public version. But to improve merging chances, please do not work in your corner many months before proposing some code.
Which part of the interface do you propose to AJAXify first?
Also, it might be prudent to add a configuration variable to activate or not the new AJAX interface.
Hey Lem,
I'm thinking of starting with the SQL input page, and expanding from there. Eventually I'd want the entire tool to be AJAX driven, and get rid of the frames in the dynamic UI. Of course having both versions of the UI available is the best way to have it setup. I'd imagine that setting should be cookie based with perhaps a default setting in the config, so that users on a central installation of the tool would be able to use it however they prefer.
For the SQL page, I'd simply want to make the query result display below the input TEXTAREA, instead of refreshing the entire page and making the user hit back to alter their statement to make a new one. Also with tabs for displaying the profiling and EXPLAIN of their query. All of course being without an entire page refresh.
Possibly allow them to create new queries into separate tabs, for comparison. I know that I open multiple browser tabs all the time, just to visually compare results from different queries.
Would it be ok for the PMA project if a DOM extender, like prototype, was used? I don't know how the rules on that goes :)
Most likely add usage of this functionality to the "Search" page, as the second addition.
Hi,
I'm interested in an AJAX interface too.
May I suggest that the best AJAX things tend to be the small in-line controls. For example, in the table structure page, deleting fields, adding and removing keys, basically, things in the "Action" column, would be easy targets to AJAXify.
The use of Prototype (or similar) would make the job a lot easier, for instead of modifying the existing code, one could use the Event.observe() function to watch the targeted controls. Thus people without Javascript (or have it turned off) would be able to use phpmyadmin as normal.
e.g.
Event.observe($('myfield_delete'), 'click', function(e) {
if(confirm ("Do you really want to delete this field?")) {
new Ajax.Request('ajax.php', {
parameters: { function: 'delete', field: 'myfield' }
});
});
The ajax request would return javascript to remove the field from the table.
Is there a wiki page for this development? I'd like to get involved.
Alex Wright.
[note I'm not a developer, but I've been around for a while and feel pretty comfortable saying the following]
alexanderwright wrote:
>Is there a wiki page for this development?
Sort of; one was started at http://wiki.cihar.com/pma/Devel:AJAX but hasn't really progressed yet. Feel free to begin using it and expanding the content (or adding pages).
>I'd like to get involved.
That would be great. As lem9 has already mentioned to garethop, the developers would be happy to merge some AJAX improvements into the code base provided it doesn't take away from the existing quality (and as long as you maintain compatibility for non-JavaScript browsers, I don't see that being a concern).
Just follow the guidelines already established for submitting other patches; develop against the current SVN version if possible, submit your patches in SourceForge's patch tracker early and often, and when in doubt ask here, in IRC, or perhaps on the mailing list (Marc, is that correct?).
To be honest I don't recall which AJAX library was implemented in the Designer feature and other AJAXy improvements, nor do I know whether the developers would prefer to continue using that library or are open to using whichever library works best.
But to everyone willing, YES, please do contribute in this way and feel free to use the wiki as a home base for communication.
Is there a data source illustrating PMA browser usage?
This is key data for compatibility conversations.
hi all,
I think we can use jquery for this.It has extensive support for AJAX
Ajaxification is a good idea.
Saves bandwidth and no Page refresh needed .
There are other js libraries too, like Moo Tools.. script.acolo.us not just jQuery
Implemented in Git by one of GSoC projects.