Hi Dieter,
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
Bye, Rouslan
2012/6/18 Rouslan Placella rouslan@placella.com:
Hi Dieter,
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
Hi Rouslan,
As we're dropping non-JS mode in PMA 4.0, I'm inclined to agree to remove the AjaxEnable config option. But I think this is a decission that has to be made by the team. What do you think, guys?
Do you have an idea what would be more work : removing the AjaxEnable and AJAX-ifying some necessary functionality; or keeping the AjaxEnable option and having to rewrite code for two modes? Also, how will AJAX-ifying some functionality impact your schedule? Do you plan to do it during GSoC or can it be done afterwards?
Le 2012-06-18 13:55, Dieter Adriaenssens a écrit :
2012/6/18 Rouslan Placella rouslan@placella.com:
Hi Dieter,
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
Hi Rouslan,
As we're dropping non-JS mode in PMA 4.0, I'm inclined to agree to remove the AjaxEnable config option. But I think this is a decission that has to be made by the team. What do you think, guys?
Some users wrote in the lists/forum to tell us that they prefer to disable Ajax, mostly because they don't like "popups"; examples:
https://sourceforge.net/tracker/?func=detail&aid=3528204&group_id=23...
http://article.gmane.org/gmane.comp.php.phpmyadmin.devel/7783/match=ajax
Do you have an idea what would be more work : removing the AjaxEnable and AJAX-ifying some necessary functionality; or keeping the AjaxEnable option and having to rewrite code for two modes? Also, how will AJAX-ifying some functionality impact your schedule? Do you plan to do it during GSoC or can it be done afterwards?
On 18/06/12 20:16, Marc Delisle wrote:
Le 2012-06-18 13:55, Dieter Adriaenssens a écrit :
2012/6/18 Rouslan Placellarouslan@placella.com:
Hi Dieter,
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
Hi Rouslan,
As we're dropping non-JS mode in PMA 4.0, I'm inclined to agree to remove the AjaxEnable config option. But I think this is a decission that has to be made by the team. What do you think, guys?
Some users wrote in the lists/forum to tell us that they prefer to disable Ajax, mostly because they don't like "popups"; examples:
https://sourceforge.net/tracker/?func=detail&aid=3528204&group_id=23...
I have to agree that some jQueryUI dialogs aren't necessary. For example: create table, add column, change column, insert into table, etc. I am planning to remove the custom ajaxifications of these and any other similar features in my branch. Then these pages will be simply processed by a generic page handler on the client side, which I'm currently working on.
http://article.gmane.org/gmane.comp.php.phpmyadmin.devel/7783/match=ajax
In this post, the use of the Back button came up as the reason for disabling ajax. I think this won't be much of a problem in 4.0 as I will implement microhistory in jQuery as described in my proposal.
Do you have an idea what would be more work : removing the AjaxEnable and AJAX-ifying some necessary functionality; or keeping the AjaxEnable option and having to rewrite code for two modes?
Keeping AjaxEnable would be way more work as far as I can see.
Also, how will AJAX-ifying some functionality impact your schedule? Do you plan to do it during GSoC or can it be done afterwards?
There isn't much missing there, a few days of work I think.
Bye, Rouslan
On 18/06/12 22:25, Rouslan Placella wrote:
On 18/06/12 20:16, Marc Delisle wrote:
Le 2012-06-18 13:55, Dieter Adriaenssens a écrit :
2012/6/18 Rouslan Placellarouslan@placella.com:
Hi Dieter,
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
Hi Rouslan,
As we're dropping non-JS mode in PMA 4.0, I'm inclined to agree to remove the AjaxEnable config option. But I think this is a decission that has to be made by the team. What do you think, guys?
Some users wrote in the lists/forum to tell us that they prefer to disable Ajax, mostly because they don't like "popups"; examples:
https://sourceforge.net/tracker/?func=detail&aid=3528204&group_id=23...
I have to agree that some jQueryUI dialogs aren't necessary. For example: create table, add column, change column, insert into table, etc. I am planning to remove the custom ajaxifications of these and any other similar features in my branch. Then these pages will be simply processed by a generic page handler on the client side, which I'm currently working on.
http://article.gmane.org/gmane.comp.php.phpmyadmin.devel/7783/match=ajax
In this post, the use of the Back button came up as the reason for disabling ajax. I think this won't be much of a problem in 4.0 as I will implement microhistory in jQuery as described in my proposal.
Do you have an idea what would be more work : removing the AjaxEnable and AJAX-ifying some necessary functionality; or keeping the AjaxEnable option and having to rewrite code for two modes?
Keeping AjaxEnable would be way more work as far as I can see.
By the way, the non ajax versions of some functionalities have previously been deliberately dropped in current master. Examples are the enum editor and the gis data editor.
Also, how will AJAX-ifying some functionality impact your schedule? Do you plan to do it during GSoC or can it be done afterwards?
There isn't much missing there, a few days of work I think.
Bye, Rouslan
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Mon, 18 Jun 2012 15:58:42 +0100 Rouslan Placella rouslan@placella.com napsal(a):
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
I think major reason for introducing this option were popup dialogs, which even more reduce available space for entering data. I don't think it's necessary to really support operation without AJAX, but getting rid of these dialogs is definitely something what should be done and then this option can disappear.
Le 2012-06-19 04:47, Michal Čihař a écrit :
Hi
Dne Mon, 18 Jun 2012 15:58:42 +0100 Rouslan Placella rouslan@placella.com napsal(a):
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
I think major reason for introducing this option were popup dialogs, which even more reduce available space for entering data. I don't think it's necessary to really support operation without AJAX, but getting rid of these dialogs is definitely something what should be done and then this option can disappear.
What about the Create table dialog? Previous version was not wide enough but the current version is correct.
On 19/06/12 11:28, Marc Delisle wrote:
Le 2012-06-19 04:47, Michal Čihař a écrit :
Hi
Dne Mon, 18 Jun 2012 15:58:42 +0100 Rouslan Placellarouslan@placella.com napsal(a):
as I just wrote in my blog post, I'm considering dropping the $cfg['AjaxEnable'] directive as in my opinion it will considerably complicate the processing of some pages and doesn't seem to any real benefits. Your thoughts on this appreciated.
I think major reason for introducing this option were popup dialogs, which even more reduce available space for entering data. I don't think it's necessary to really support operation without AJAX, but getting rid of these dialogs is definitely something what should be done and then this option can disappear.
What about the Create table dialog? Previous version was not wide enough but the current version is correct.
My plan is to load the create table dialog straight into the page instead of a popup. Maximum screen width would therefore be maintained.
Bye, Rouslan
Hi
Dne Tue, 19 Jun 2012 06:28:28 -0400 Marc Delisle marc@infomarc.info napsal(a):
What about the Create table dialog? Previous version was not wide enough but the current version is correct.
It is indeed better, but still I don't see need to have a dialog in such case at all.
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař -
Rouslan Placella