2011/5/2 Marc Delisle marc@infomarc.info:
Tyron Madlener a écrit :
On Mon, May 2, 2011 at 4:44 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
In phpMyAdmin 3.3 most of the export settings were visible in one page without scrolling, hence requiring only very few clicks to export what you need. But in 3.4 when I try to export the table structure I first need to click '(o) custom' then scroll down and search through all the text where in order to find where I select '(o) structure'. It feels very unintuitive for me.
Tyron, what do you mean "export the table structure"? Do you mean "export _just_ the table structure" ?
Yes, just the table structure without data.
In 3.4, most of the time I leave it in Quick mode and am happy with the results.
This panel in 3.4 was built this way by a GSoC 2010 student, based on the results of usability testings.
Oh, I see. Still seems unintuitive for me.
It can be improved but I feel that it's too late to change this in 3.4.x.
About jQuery tabs, I'm not sure because the options vary, depending on the chosen format. Feel free to further discuss by explaining how many tabs there would be and their names.
What about: a) We put all the settings in jquery tabs b) On the first tab will be the most used options: Format, Output type (File / as Text) and what to dump (2 checkboxes for each data and structure)
Here's a demo of the tabs: http://jqueryui.com/demos/tabs/
I think that using jQuery UI Tabs is an overkill. It's nice in applications built completely on top of this UI library, but it has a lot of options that we don't really need. Simple custom made tabs take around 25 lines of JavaScript and the code is already in PMA (js/config.js, setTab).