I have a few issues with new AJAX features. All below concerns Firefox 4, I haven't tested in other browsers.
SQL tab: 1. When executing a query from the SQL tab, "Loading" is shown much too long, I started wondering whether something was broken - it disappeared 3 seconds after the result was shown. It should do it as fast as when it does when changing page in Browse. 2. I executed a query which returns no rows multiple times, when a new message arrives the previous one is faded out. It makes elements of the screen to move, and for a short while I have two result messages. What about removing this effect and just deleting old result? The hiding of "Loading" message should be an appropriate indicator for saying whether the result we see is the one pertaining to the last query. 3. When I issue a CREATE TABLE query the navigation frame is not refreshed - it should be. 4. I executed two queries: SELECT * FROM information_schema.tables where 0=1 I got "MySQL returned an empty result set (i.e. zero rows).", ok. Next query: SELECT * FROM information_schema.tables Message from previous execution stays on screen, it should disappear.
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1] 6. In previous PMA versions after creating a new table I landed on new table's Structure tab, it doesn't happen now, I see only a popup message saying that table was created (to get to table creation page, click "Create table" in navigation frame). 7. It just struck me, we have a header saying "Create table on database <dbname>", shouldn't it be "Create table in database <dbname>"? Tables reside in databases, not on them.
[1] http://img808.imageshack.us/img808/5011/ajaxss1.png
On Thu, Apr 7, 2011 at 9:00 PM, Piotr Przybylski piotr.prz@gmail.com wrote:
I have a few issues with new AJAX features. All below concerns Firefox 4, I haven't tested in other browsers.
SQL tab:
- When executing a query from the SQL tab, "Loading" is shown much
too long, I started wondering whether something was broken - it disappeared 3 seconds after the result was shown. It should do it as fast as when it does when changing page in Browse. 2. I executed a query which returns no rows multiple times, when a new message arrives the previous one is faded out. It makes elements of the screen to move, and for a short while I have two result messages. What about removing this effect and just deleting old result? The hiding of "Loading" message should be an appropriate indicator for saying whether the result we see is the one pertaining to the last query.
Did you check the dev version in the Git Repository? Those 2 problems should be remedied there.
- When I issue a CREATE TABLE query the navigation frame is not
refreshed - it should be. 4. I executed two queries: SELECT * FROM information_schema.tables where 0=1 I got "MySQL returned an empty result set (i.e. zero rows).", ok. Next query: SELECT * FROM information_schema.tables Message from previous execution stays on screen, it should disappear.
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1] 6. In previous PMA versions after creating a new table I landed on new table's Structure tab, it doesn't happen now, I see only a popup message saying that table was created (to get to table creation page, click "Create table" in navigation frame). 7. It just struck me, we have a header saying "Create table on database <dbname>", shouldn't it be "Create table in database <dbname>"? Tables reside in databases, not on them.
[1] http://img808.imageshack.us/img808/5011/ajaxss1.png
-- Piotr Przybylski
Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Thu, 7 Apr 2011 21:00:40 +0200 Piotr Przybylski piotr.prz@gmail.com napsal(a):
I have a few issues with new AJAX features. All below concerns Firefox 4, I haven't tested in other browsers.
SQL tab:
- When executing a query from the SQL tab, "Loading" is shown much
too long, I started wondering whether something was broken - it disappeared 3 seconds after the result was shown. It should do it as fast as when it does when changing page in Browse. 2. I executed a query which returns no rows multiple times, when a new message arrives the previous one is faded out. It makes elements of the screen to move, and for a short while I have two result messages. What about removing this effect and just deleting old result? The hiding of "Loading" message should be an appropriate indicator for saying whether the result we see is the one pertaining to the last query. 3. When I issue a CREATE TABLE query the navigation frame is not refreshed - it should be. 4. I executed two queries: SELECT * FROM information_schema.tables where 0=1 I got "MySQL returned an empty result set (i.e. zero rows).", ok. Next query: SELECT * FROM information_schema.tables Message from previous execution stays on screen, it should disappear.
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1] 6. In previous PMA versions after creating a new table I landed on new table's Structure tab, it doesn't happen now, I see only a popup message saying that table was created (to get to table creation page, click "Create table" in navigation frame). 7. It just struck me, we have a header saying "Create table on database <dbname>", shouldn't it be "Create table in database <dbname>"? Tables reside in databases, not on them.
If you can reproduce these issues with latest git, please file bugs into bug tracker.
2011/4/8 Michal Čihař michal@cihar.com:
Hi
Dne Thu, 7 Apr 2011 21:00:40 +0200 Piotr Przybylski piotr.prz@gmail.com napsal(a):
I have a few issues with new AJAX features. All below concerns Firefox 4, I haven't tested in other browsers.
SQL tab:
- When executing a query from the SQL tab, "Loading" is shown much
too long, I started wondering whether something was broken - it disappeared 3 seconds after the result was shown. It should do it as fast as when it does when changing page in Browse. 2. I executed a query which returns no rows multiple times, when a new message arrives the previous one is faded out. It makes elements of the screen to move, and for a short while I have two result messages. What about removing this effect and just deleting old result? The hiding of "Loading" message should be an appropriate indicator for saying whether the result we see is the one pertaining to the last query. 3. When I issue a CREATE TABLE query the navigation frame is not refreshed - it should be. 4. I executed two queries: SELECT * FROM information_schema.tables where 0=1 I got "MySQL returned an empty result set (i.e. zero rows).", ok. Next query: SELECT * FROM information_schema.tables Message from previous execution stays on screen, it should disappear.
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1] 6. In previous PMA versions after creating a new table I landed on new table's Structure tab, it doesn't happen now, I see only a popup message saying that table was created (to get to table creation page, click "Create table" in navigation frame). 7. It just struck me, we have a header saying "Create table on database <dbname>", shouldn't it be "Create table in database <dbname>"? Tables reside in databases, not on them.
If you can reproduce these issues with latest git, please file bugs into bug tracker.
I can still reproduce all of them, tested with clean browser cache (Firefox) and a browser in which I never run PMA before (IE9). Thanks to that we got a few more IE9-specific bugs/annoyances in bug tracker :)
Piotr Przybylski a écrit : (...)
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1]
Piotr, even without Ajax (therefore without a jQuery dialog) the window is too small unless you have a monster screen (I don't).
"Mandatory" fields are the column name and type (maybe length/values); what about introducing a mechanism to hide the other fields by default, and revealing then in a clever way (just for one column when the user needs them) ?
2011/4/8 Marc Delisle marc@infomarc.info:
Piotr Przybylski a écrit : (...)
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1]
Piotr, even without Ajax (therefore without a jQuery dialog) the window is too small unless you have a monster screen (I don't).
I too don't have it, but the dialog is much smaller than frame.
"Mandatory" fields are the column name and type (maybe length/values); what about introducing a mechanism to hide the other fields by default, and revealing then in a clever way (just for one column when the user needs them) ?
Probably a bad idea, I believe most users would like to have all options available instead of having to look for some "more" button each time they create a table.
Le 2011-04-08 18:56, Piotr Przybylski a écrit :
2011/4/8 Marc Delisle marc@infomarc.info:
Piotr Przybylski a écrit : (...)
Database Structure tab: 5. When creating a new table with 10 columns the window is just too small: this window should show only for simple cases when only vertical scrolling is necessary. [1]
Piotr, even without Ajax (therefore without a jQuery dialog) the window is too small unless you have a monster screen (I don't).
I too don't have it, but the dialog is much smaller than frame.
"Mandatory" fields are the column name and type (maybe length/values); what about introducing a mechanism to hide the other fields by default, and revealing then in a clever way (just for one column when the user needs them) ?
Probably a bad idea, I believe most users would like to have all options available instead of having to look for some "more" button each time they create a table.
Let's hear what "most users" have to say on this :)
Looking at my own behavior when I create a table, I can assure you that I would not use the "More" button very often (once on the primary key and on columns having a default value). Also it would be in the same direction as the new 3.4 Export Quick/Custom interface (set to Quick by default).
We could have a user preference to turn off this behavior.
We already have a similar behavior for ENUM/SET columns (Get more editing space).
2011/4/7 Piotr Przybylski piotr.prz@gmail.com: 6. In previous PMA versions after creating a new table I landed on new
table's Structure tab, it doesn't happen now, I see only a popup message saying that table was created (to get to table creation page, click "Create table" in navigation frame). 7. It just struck me, we have a header saying "Create table on database <dbname>", shouldn't it be "Create table in database <dbname>"? Tables reside in databases, not on them.
What about these two?
Le 2011-04-08 19:00, Piotr Przybylski a écrit :
2011/4/7 Piotr Przybylski piotr.prz@gmail.com: 6. In previous PMA versions after creating a new table I landed on new
table's Structure tab, it doesn't happen now, I see only a popup message saying that table was created (to get to table creation page, click "Create table" in navigation frame).
You can enter this one as a bug.
- It just struck me, we have a header saying "Create table on
database <dbname>", shouldn't it be "Create table in database <dbname>"? Tables reside in databases, not on them.
I think "in" would be better, but Google reports 17300 results for "Create table on database".
Message strings are now frozen so it might be better to delay this change until version 3.5.
-
Marc Delisle -
Michal Čihař -
Piotr Przybylski -
Tyron Madlener