On 16 Mei 2011, at 01:33, Tyron Madlener tyronx@gmail.com wrote:
On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 15 Mei 2011, at 16:17, Tyron Madlener tyronx@gmail.com wrote:
On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
Hi, The recently used tables is now using ajax. I've just pushed to my repo, so the demo [0] will be available in an hour later. Comment and suggestion are welcome, mainly regarding the ajax-related code:
- ajax request in navigation.js
- ajax response in navigation.php
- ajax trigger in header.inc.php (the triggering is done by adding <script>
tag to call js function in the navigation frame, any better way?) [0] http://demo.phpmyadmin.net/gsoc-aris/ Cheers, -- Aris Feryanto
What if, instead of a 'recently used tables drop down list' there would be a bunch of icons that allow (ajax request-)sorting of tables/databases by different criterias such as:
- most recently used
- most commonly used
- table/db size
I think we can add sorting criteria in settings page. But, IMO, list is still more intuitive than using icons.
Similar to chromes omnibar that suggests addresses that are most commonly used, this seems somehow more intuitive than a drop down list.
So, users must type table's name in order to jump to a table? I think this is not convenient, since users may have table names with same prefix.
Yea I think this was a bad example. What I meant is, those 3 Icons (and saving the last sort order in a cookie) sorting the list, thus having the list of tables/dbs just once (not in the list + partially in the drop down list), feel more intuitive for me. And saves the user a additional mouse click once the table is sorted to his liking.
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since:
1. Current navigation frame has two kind of views: light version (dbs list first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list).
In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs.
In the full version, list of tables are grouped by their dbs. Sorting will messed up the list.
2. The users will be confused by the "always changing" dbs/tables list.
-- Aris Feryanto
On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 16 Mei 2011, at 01:33, Tyron Madlener tyronx@gmail.com wrote:
On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 15 Mei 2011, at 16:17, Tyron Madlener tyronx@gmail.com wrote:
On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
Hi,
The recently used tables is now using ajax. I've just pushed to my repo, so
the demo [0] will be available in an hour later. Comment and suggestion are
welcome, mainly regarding the ajax-related code:
ajax request in navigation.js
ajax response in navigation.php
ajax trigger in header.inc.php (the triggering is done by adding <script>
tag to call js function in the navigation frame, any better way?)
[0] http://demo.phpmyadmin.net/gsoc-aris/
Cheers,
--
Aris Feryanto
What if, instead of a 'recently used tables drop down list' there
would be a bunch of icons that allow (ajax request-)sorting of
tables/databases by different criterias such as:
most recently used
most commonly used
table/db size
I think we can add sorting criteria in settings page. But, IMO, list is still more intuitive than using icons.
Similar to chromes omnibar that suggests addresses that are most
commonly used, this seems somehow more intuitive than a drop down
list.
So, users must type table's name in order to jump to a table? I think this is not convenient, since users may have table names with same prefix.
Yea I think this was a bad example. What I meant is, those 3 Icons (and saving the last sort order in a cookie) sorting the list, thus having the list of tables/dbs just once (not in the list + partially in the drop down list), feel more intuitive for me. And saves the user a additional mouse click once the table is sorted to his liking.
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since:
- Current navigation frame has two kind of views: light version (dbs list
first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list). In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs. In the full version, list of tables are grouped by their dbs. Sorting will messed up the list. 2. The users will be confused by the "always changing" dbs/tables list.
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
-- Aris Feryanto
Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 16 Mei 2011, at 01:33, Tyron Madlener tyronx@gmail.com wrote:
On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 15 Mei 2011, at 16:17, Tyron Madlener tyronx@gmail.com wrote:
On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
Hi,
The recently used tables is now using ajax. I've just pushed to my repo, so
the demo [0] will be available in an hour later. Comment and suggestion are
welcome, mainly regarding the ajax-related code:
ajax request in navigation.js
ajax response in navigation.php
ajax trigger in header.inc.php (the triggering is done by adding <script>
tag to call js function in the navigation frame, any better way?)
[0] http://demo.phpmyadmin.net/gsoc-aris/
Cheers,
--
Aris Feryanto
What if, instead of a 'recently used tables drop down list' there
would be a bunch of icons that allow (ajax request-)sorting of
tables/databases by different criterias such as:
most recently used
most commonly used
table/db size
I think we can add sorting criteria in settings page. But, IMO, list is still more intuitive than using icons.
Similar to chromes omnibar that suggests addresses that are most
commonly used, this seems somehow more intuitive than a drop down
list.
So, users must type table's name in order to jump to a table? I think this is not convenient, since users may have table names with same prefix.
Yea I think this was a bad example. What I meant is, those 3 Icons (and saving the last sort order in a cookie) sorting the list, thus having the list of tables/dbs just once (not in the list + partially in the drop down list), feel more intuitive for me. And saves the user a additional mouse click once the table is sorted to his liking.
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since:
- Current navigation frame has two kind of views: light version (dbs list
first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list). In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs. In the full version, list of tables are grouped by their dbs. Sorting will messed up the list. 2. The users will be confused by the "always changing" dbs/tables list.
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 16 Mei 2011, at 01:33, Tyron Madlener tyronx@gmail.com wrote:
On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 15 Mei 2011, at 16:17, Tyron Madlener tyronx@gmail.com wrote:
On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
Hi,
The recently used tables is now using ajax. I've just pushed to my repo, so
the demo [0] will be available in an hour later. Comment and suggestion are
welcome, mainly regarding the ajax-related code:
ajax request in navigation.js
ajax response in navigation.php
ajax trigger in header.inc.php (the triggering is done by adding <script>
tag to call js function in the navigation frame, any better way?)
[0] http://demo.phpmyadmin.net/gsoc-aris/
Cheers,
--
Aris Feryanto
What if, instead of a 'recently used tables drop down list' there
would be a bunch of icons that allow (ajax request-)sorting of
tables/databases by different criterias such as:
most recently used
most commonly used
table/db size
I think we can add sorting criteria in settings page. But, IMO, list is still more intuitive than using icons.
Similar to chromes omnibar that suggests addresses that are most
commonly used, this seems somehow more intuitive than a drop down
list.
So, users must type table's name in order to jump to a table? I think this is not convenient, since users may have table names with same prefix.
Yea I think this was a bad example. What I meant is, those 3 Icons (and saving the last sort order in a cookie) sorting the list, thus having the list of tables/dbs just once (not in the list + partially in the drop down list), feel more intuitive for me. And saves the user a additional mouse click once the table is sorted to his liking.
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since:
- Current navigation frame has two kind of views: light version (dbs list
first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list). In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs. In the full version, list of tables are grouped by their dbs. Sorting will messed up the list. 2. The users will be confused by the "always changing" dbs/tables list.
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
How come it is not the default setting? Because it loads too slow?
-- Marc Delisle http://infomarc.info
Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 16 Mei 2011, at 01:33, Tyron Madlener tyronx@gmail.com wrote:
On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
On 15 Mei 2011, at 16:17, Tyron Madlener tyronx@gmail.com wrote:
On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
Hi,
The recently used tables is now using ajax. I've just pushed to my repo, so
the demo [0] will be available in an hour later. Comment and suggestion are
welcome, mainly regarding the ajax-related code:
ajax request in navigation.js
ajax response in navigation.php
ajax trigger in header.inc.php (the triggering is done by adding <script>
tag to call js function in the navigation frame, any better way?)
[0] http://demo.phpmyadmin.net/gsoc-aris/
Cheers,
--
Aris Feryanto
What if, instead of a 'recently used tables drop down list' there
would be a bunch of icons that allow (ajax request-)sorting of
tables/databases by different criterias such as:
most recently used
most commonly used
table/db size
I think we can add sorting criteria in settings page. But, IMO, list is still more intuitive than using icons.
Similar to chromes omnibar that suggests addresses that are most
commonly used, this seems somehow more intuitive than a drop down
list.
So, users must type table's name in order to jump to a table? I think this is not convenient, since users may have table names with same prefix.
Yea I think this was a bad example. What I meant is, those 3 Icons (and saving the last sort order in a cookie) sorting the list, thus having the list of tables/dbs just once (not in the list + partially in the drop down list), feel more intuitive for me. And saves the user a additional mouse click once the table is sorted to his liking.
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since:
- Current navigation frame has two kind of views: light version (dbs list
first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list). In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs. In the full version, list of tables are grouped by their dbs. Sorting will messed up the list. 2. The users will be confused by the "always changing" dbs/tables list.
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
How come it is not the default setting? Because it loads too slow?
At least, this was the case when the number of tables per database was computed. Also, I don't believe that this method respects the maximum number of databases in navi panel.
On 16 Mei 2011, at 19:37, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since:
- Current navigation frame has two kind of views: light version (dbs list
first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list). In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs. In the full version, list of tables are grouped by their dbs. Sorting will messed up the list. 2. The users will be confused by the "always changing" dbs/tables list.
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
Just want to make sure we all refer to the same thing. I guess "this feature" here, means only the collapsable tree (not along with the sorting). Please correct me if I am wrong.
And @Tyron: even the collapsable tree can be sorted (sort by the db first, then sort by the tables for each db), I think it is not a good idea to do so. As I've mentioned before, users will be confused by the "always changing" list (e.g. If tables are sorted from the most recently used, you do not want to spend more time to look for a table in the list because the list often change, right? :)
How come it is not the default setting? Because it loads too slow?
At least, this was the case when the number of tables per database was computed. Also, I don't believe that this method respects the maximum number of databases in navi panel.
-- Marc Delisle http://infomarc.info
Aris Feryanto a écrit :
On 16 Mei 2011, at 19:37, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto aris_feryanto@yahoo.com wrote:
The intention of providing recently used tables is to make users able to jump between tables (they used recently) in different databases. I don't think this can be achieved by sorting the main list, since: 1. Current navigation frame has two kind of views: light version (dbs list first, then if you click one db, it will display the tables list of that db) and complete version (all dbs + tables in one list). In the light version, it will displays only tables of one db (tables from other dbs are not shown). So, we can't jump between tables in different dbs. In the full version, list of tables are grouped by their dbs. Sorting will messed up the list. 2. The users will be confused by the "always changing" dbs/tables list.
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
Just want to make sure we all refer to the same thing. I guess "this feature" here, means only the collapsable tree (not along with the sorting). Please correct me if I am wrong.
You're right, I'm referring to setting LeftFrameLight to false.
And @Tyron: even the collapsable tree can be sorted (sort by the db first, then sort by the tables for each db), I think it is not a good idea to do so. As I've mentioned before, users will be confused by the "always changing" list (e.g. If tables are sorted from the most recently used, you do not want to spend more time to look for a table in the list because the list often change, right? :)
How come it is not the default setting? Because it loads too slow?
At least, this was the case when the number of tables per database was computed. Also, I don't believe that this method respects the maximum number of databases in navi panel.
Hi
Dne Mon, 16 May 2011 14:32:13 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
How come it is not the default setting? Because it loads too slow?
Yes, especially on servers with lot of databases and tables.
However it would be nice if it could be done dynamically using AJAX (show db list and load tables on demand when expanding tree).
On Fri, May 20, 2011 at 10:59 AM, Michal Čihař michal@cihar.com wrote:
Hi
Dne Mon, 16 May 2011 14:32:13 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
True, switching between tables from different dbs wouldn't work then. If the table/db list would be implemented as collapsable tree, then it would work :)
This feature exists but is not enabled by default.
How come it is not the default setting? Because it loads too slow?
Yes, especially on servers with lot of databases and tables.
However it would be nice if it could be done dynamically using AJAX (show db list and load tables on demand when expanding tree).
Yea, I was thinking about the same. But I would load the tables of all databases in the background so they are visible immediately when expanding the tree. Or the tables of the 5 most commonly used databases. Or something like that.
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-
Aris Feryanto -
Marc Delisle -
Michal Čihař -
Tyron Madlener