Open GoogleCodeExporter opened 9 years ago
Could you be a little more specific? Where are appearing those inconsistencies?
Original comment by kounue...@gmail.com
on 7 May 2012 at 2:24
there are currently two ways to create menus. using the Smarty {{MENU}}
function, or using the Menu plugin.
both of these use different methods to define their menus.
What I would /like/, is to use the new jQuery-UI Menu plugin. I've been waiting
for it to be released (with jQuery-UI 1.9), but they're taking their time with
it.
I wonder if maybe it's a good plan to rewrite the entire menu system to use the
dev version of the jQuery-UI menu, and just add classes in the right places so
that older designs don't break?
Original comment by kae.verens@gmail.com
on 14 Jun 2012 at 11:09
possible solution.
create a new section in the admin specifically for configuring menus.
Each menu will have templateable components (html, css, for the menu wrapper,
sub-menus, items).
also, set "global" values, for those components that are not individually
customised.
as part of the upgrade script, check to see is this a new site or an old one.
For old sites, use global components similar to the existing menus, so older
sites look visually /IDENTICAL/ (VERY VERY IMPORTANT).
newer menus should use components based on the new jQuery-UI menu suggestions.
After the upgrade, all menus should work using the jQuery-UI code. fg-menu code
and my own ajaxmenu code should be removed completely.
the Menu plugin should be removed, and all functionality copied into the core.
again, make sure that upgraded websites convert their Menu-plugin-based menus
to the newer style menus so that even though the plugin is gone, the menus
still work the same.
Original comment by kae.verens@gmail.com
on 20 Jun 2012 at 4:24
Original issue reported on code.google.com by
Christof...@gmail.com
on 15 Mar 2012 at 9:40