[Phpmyadmin-devel] Recently Used Tables
Tyron Madlener
tyronx at gmail.com
Mon May 16 14:32:13 CEST 2011
On Mon, May 16, 2011 at 2:08 PM, Marc Delisle <marc at infomarc.info> wrote:
> Tyron Madlener a écrit :
>> On Mon, May 16, 2011 at 12:37 PM, Aris Feryanto <aris_feryanto at yahoo.com> wrote:
>>> On 16 Mei 2011, at 01:33, Tyron Madlener <tyronx at gmail.com> wrote:
>>>
>>> On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto <aris_feryanto at yahoo.com>
>>> wrote:
>>>
>>>
>>> On 15 Mei 2011, at 16:17, Tyron Madlener <tyronx at gmail.com> wrote:
>>>
>>> On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto <aris_feryanto at 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.
>>
>> 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
>
More information about the Developers
mailing list