On Sun, Jul 24, 2011 at 9:53 PM, Marc Delisle marc@infomarc.info wrote:
Le 2011-07-24 14:32, Rouslan Placella a écrit :
Hi there,
I planning to integrate the Routines, Triggers and Events into the navigation frame. To achieve this I'm thinking about adding another level to the navigation tree in non-light mode (light mode is unaffected). So that after expanding a database you might be left with more items like 'tables', 'indexes', 'routines', 'triggers' and 'events', which you have in turn expand. Even though triggers are per-table items and every thing else is a per-database item, I think that it's best to show these on a per-database basis in order to avoid another level in the navigation. Please find an initial mock-up for this feature in the attachment. Your thoughts?
Rouslan
It's interesting but as the light mode is the default, I'm afraid that this feature won't be seen by many.
Can't you show routines, triggers and events also in light mode, (maybe) with an expansion mechanism?
The main idea of the light mode is not to avoid displaying expansion mechanisms, it's to avoid performance issues so it fetches only the tables of the current database.
I agree, but I think they should only be displayed if they have been set up previously. (e.g. don't show triggers when there's no triggers for that database), assuming that checking this doesn't affect the performance too much.
-- Marc Delisle http://infomarc.info
Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel