Hi, I'm posting this to both lists to get developers and users feedback.
In the phpMyAdmin 3.4 series, is it worth maintaining compatibility with non-js-enabled browsers?
Hi!
In the phpMyAdmin 3.4 series, is it worth maintaining compatibility with non-js-enabled browsers?
I very much appreciate the current efforts of improving and ajaxifying convenience features in phpMyAdmin and creating a more state-of-the-art framework.
I think PMA has always been a backend tool where certain requirements like JS can be made, so I don't think that much time should be spent on non-js fallbacks, as they are mostly very cumbersome to implement.
What I would like to mention to pay attention on is to still make phpMyAdmin be able to work in "multiple instances", so that I can open several tabs in my browser to do their separated work. Like clicking the "Edit row" link of a table to load the edit-data screen in multiple tabs, then cycle through them and save.
Typo3, as an example for a JS-heavy framework, doesn't really (easily) allow such multi-tab usage. So links on items should IMHO always respect isolated tabs and make it possible to Shift-Click. "onclick" handlers for example make it hard to spawn the underlying function in a new tab instead of the current one.
(I hope you all get what I'm talking about ;-) )
Regards, Garvin
Hi Marc,
On snein 30 Maaie 2010, Marc Delisle wrote:
I'm posting this to both lists to get developers and users feedback.
In the phpMyAdmin 3.4 series, is it worth maintaining compatibility with non-js-enabled browsers?
I don't think it's necessary to keep feature-by-feature compatibility with non-js-enabled browsers. However, I do think it would be very useful if functionality that only works with JavaScript on is limited to "extras", and that all the basic operations (login, browse databases, table structures and data, insert update and delete data, user management) is still possible without JavaScript.
I can imagine JavaScript being used for extra features that make working with pMA more convenient or that add more peripheral functionality. Some examples would be form validation, a colour picker, but there's probably more.
Cheers, Thijs
2010/5/30 Thijs Kinkhorst thijs@debian.org:
Hi Marc,
On snein 30 Maaie 2010, Marc Delisle wrote:
I'm posting this to both lists to get developers and users feedback.
In the phpMyAdmin 3.4 series, is it worth maintaining compatibility with non-js-enabled browsers?
I don't think it's necessary to keep feature-by-feature compatibility with non-js-enabled browsers. However, I do think it would be very useful if functionality that only works with JavaScript on is limited to "extras", and that all the basic operations (login, browse databases, table structures and data, insert update and delete data, user management) is still possible without JavaScript.
I can imagine JavaScript being used for extra features that make working with pMA more convenient or that add more peripheral functionality. Some examples would be form validation, a colour picker, but there's probably more.
I agree with Thijs, that basic functionality should still be possible without needing javascript. I usually think of Javascript (and AJAX) as a nice way of improving interaction with the user (f.e. autofilling a textfield while typing a search term, or showing/hiding certain parts of a page when choosing options, ...) Of course this doesn't mean that some advanced features (like the relation editor) should also work when Javascript is not enabled. This tool is very graphical, and almost impossible to implement when using just HTML. So the effort to make these kind of features work without Javascript is unnecessary.
To summarise, in my opinion, in version 3.4 it should be possible to login, get an overview of databases and tables, browse the content of tables and insert/delete/modify records/tables/databases/priviliges, without needing Javascript or AJAX.
Greetings,
Dieter
-
Dieter Adriaenssens -
Garvin Hicking -
Marc Delisle -
Thijs Kinkhorst