I also like this idea, but there are a couple problems with it:
1. It would require recoding of all of the output.
2. Only newer browsers support the XMLHttpRequest Javascript
object (the base of all AJAX web applications using
Javascript, which I am going to assume phpMyAdmin will use.)
3. Web browsers without Javascript or have Javascript
disabled will not be able to use it.
4. As of now, the Gecko rendering engine (Mozilla Suite,
Firefox, etc.) has a bug with some XMLHttpRequests not
returning any responseText or responseXML properties. (Of
course, this is a problem with the Gecko engine, and should
be fixed soon, hopefully...)
5. There would be a lot more cross-browser conflicts with
the Javascript code.
I haven't looked into phpMyAdmin's coding very much, but
depending on how the script is set up, the recoding of the
output would range from very easy to very difficult.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although I do agree with you on 1, I don't belive 2 and 3
are issues that should prevent moving to AJAX; phpMyAdmin is
made for developers to administrate their databases and
developers should have a browser that AT LEAST supports
XMLHttpRequest and have JavaScript enabled. As you said, 4
should be fixed soon, and for 5, I never found it to be an
issue as long as the JavaScript is written cross-browser
right from the start.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the bug can't be fixed for Gecko, I doubt this request
will ever get off the ground. Maybe if some people vote for
the bug, it will get noticed by the developers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
altho i would love phpmyadmin to be ajax. i think we are
jumping the gun a bit. phpmyadmin is still evolving the "old
" way. shouldnt we wait a bit for that to stabalise a bit
before expexting the developers to come up with a whole new
system? im not sure on how everything works but i would
think that the developers dont get paid for working on
phpmyadmin and do it as a "after hours" project (im not
sure about this)
the people working on phpmyadmin are bofins in their
fields. they might not have worked with ajax before. in
which case.... my vote would be that they continue with pma
the way it is. learning ajax on the side if they want to.
imagine how many bugs there will be if it goes onto ajax....
just my 2 cents worth.
for the record...... PLEASE TURN PHPMYADMIN TO AJAX!!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=752750
Yes PLEASE! There are several competing applications
(SQLyog) that I prefer over a web-based client because they
are faster.
Page refreshes are so Web 1.0! phpMyAdmin needs to evolve!
There are already some AJAX PHP/MySQL web projects going
such as TurboDbAdmin.
I would much rather have a web application that performed
like an application! Then it would be completely portable!
Logged In: YES
user_id=1278413
I also like this idea, but there are a couple problems with it:
1. It would require recoding of all of the output.
2. Only newer browsers support the XMLHttpRequest Javascript
object (the base of all AJAX web applications using
Javascript, which I am going to assume phpMyAdmin will use.)
3. Web browsers without Javascript or have Javascript
disabled will not be able to use it.
4. As of now, the Gecko rendering engine (Mozilla Suite,
Firefox, etc.) has a bug with some XMLHttpRequests not
returning any responseText or responseXML properties. (Of
course, this is a problem with the Gecko engine, and should
be fixed soon, hopefully...)
5. There would be a lot more cross-browser conflicts with
the Javascript code.
I haven't looked into phpMyAdmin's coding very much, but
depending on how the script is set up, the recoding of the
output would range from very easy to very difficult.
Logged In: YES
user_id=1467934
Although I do agree with you on 1, I don't belive 2 and 3
are issues that should prevent moving to AJAX; phpMyAdmin is
made for developers to administrate their databases and
developers should have a browser that AT LEAST supports
XMLHttpRequest and have JavaScript enabled. As you said, 4
should be fixed soon, and for 5, I never found it to be an
issue as long as the JavaScript is written cross-browser
right from the start.
Logged In: YES
user_id=1278413
I filed a bug on Bugzilla about the XMLHttpRequest bug for
Gecko, but it isn't getting a lot of attention:
https://bugzilla.mozilla.org/show_bug.cgi?id=335599
If the bug can't be fixed for Gecko, I doubt this request
will ever get off the ground. Maybe if some people vote for
the bug, it will get noticed by the developers.
Logged In: YES
user_id=1522030
altho i would love phpmyadmin to be ajax. i think we are
jumping the gun a bit. phpmyadmin is still evolving the "old
" way. shouldnt we wait a bit for that to stabalise a bit
before expexting the developers to come up with a whole new
system? im not sure on how everything works but i would
think that the developers dont get paid for working on
phpmyadmin and do it as a "after hours" project (im not
sure about this)
the people working on phpmyadmin are bofins in their
fields. they might not have worked with ajax before. in
which case.... my vote would be that they continue with pma
the way it is. learning ajax on the side if they want to.
imagine how many bugs there will be if it goes onto ajax....
just my 2 cents worth.
for the record...... PLEASE TURN PHPMYADMIN TO AJAX!!!!
There will be lot of AJAX functionality in 3.4 release.