<html><body bgcolor="#FFFFFF"><div><br></div><div>On 16 Mei 2011, at 01:33, Tyron Madlener <<a href="mailto:tyronx@gmail.com">tyronx@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><span>On Sun, May 15, 2011 at 6:56 PM, Aris Feryanto <<a href="mailto:aris_feryanto@yahoo.com">aris_feryanto@yahoo.com</a>> wrote:</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On 15 Mei 2011, at 16:17, Tyron Madlener <<a href="mailto:tyronx@gmail.com">tyronx@gmail.com</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Fri, May 13, 2011 at 10:06 PM, Aris Feryanto <<a href="mailto:aris_feryanto@yahoo.com">aris_feryanto@yahoo.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Hi,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>The recently used tables is now using ajax. I've just pushed to my repo, so</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>the demo [0] will be available in an hour later. Comment and suggestion are</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>welcome, mainly regarding the ajax-related code:</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>- ajax request in navigation.js</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>- ajax response in navigation.php</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>- ajax trigger in header.inc.php (the triggering is done by adding <script></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>tag to call js function in the navigation frame, any better way?)</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>[0] <a href="http://demo.phpmyadmin.net/gsoc-aris/"><a href="http://demo.phpmyadmin.net/gsoc-aris/">http://demo.phpmyadmin.net/gsoc-aris/</a></a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Cheers,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>--</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Aris Feryanto</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>What if, instead of a 'recently used tables drop down list' there</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>would be a bunch of icons that allow (ajax request-)sorting of</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>tables/databases by different criterias such as:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- most recently used</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- most commonly used</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- table/db size</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I think we can add sorting criteria in settings page. But, IMO, list is still more intuitive than using icons.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Similar to chromes omnibar that suggests addresses that are most</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>commonly used, this seems somehow more intuitive than a drop down</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>list.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>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.</span><br></blockquote><span></span><br><span>Yea I think this was a bad example. What I meant is, those 3 Icons</span><br><span>(and saving the last sort order in a cookie) sorting the list, thus</span><br><span>having the list of tables/dbs just once (not in the list + partially</span><br><span>in the drop down list), feel more intuitive for me. And saves the user</span><br><span>a additional mouse click once the table is sorted to his liking.</span><br><font class="Apple-style-span" color="#005001"><font class="Apple-style-span" color="#0023A3"><br></font></font></div></blockquote><div><br></div><div>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:</div><div><br></div><div>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).</div><div><br></div><div>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.</div><div><br></div><div>In the full version, list of tables are grouped by their dbs. Sorting will messed up the list.</div><div><br></div><div>2. The users will be confused by the "always changing" dbs/tables list.</div><div><br></div><div><br></div><div>--</div><div>Aris Feryanto</div></body></html>