Re: [E-devel] elm menu (probably need to break theme and extend api)

[Lucas De M. <luc...@pr...>]

On Mon, Aug 12, 2013 at 4:05 AM, Michael Blumenkrantz
<mic...@gm...> wrote:
> please don't just copy the E menus into elm. while they may be better
> overall, they're really not that great...certainly not something I would
> hold up as the sterling standard of menus. here's just some of the huge
> issues with e menus that stand out as reasons why they're bad (and why I
> will eventually need to overhaul them):
>
> * the whole "separate mouse handler" thing creates a giant race condition
> for showing/hiding submenus which is a GIANT nightmare
> * e menus can't scroll (obviously) and adding scrolling would turn them
> into even more of a nightmare
> * submenu deletion is also a huge race condition
> * the whole menu item callback design is broken since they can be called
> repeatedly instead of just the one time they were intended to be called
> (currently hacked around)
> * oh jesus the menu category/augmentation system kill it with fire
> * interceptors for move/resize? really? just to show menus in the right
> place?
> * adding items to a menu asynchronously is seriously infuriating--just look
> at the fileman menu system to see what a clusterfuck it is
>
> while I agree that the elm menu api/internals/design needs work, I am
> strongly opposed to anything related to copying the E menu system into elm.
> a much better solution would be a new menu design which works properly
> (without all these hacks and flaws) and can be used in both places.
>
> this doesn't need to be rushed in just to make it before the 1.8 release;
> menus are important, and we should spend some time on them.

+1


Lucas De Marchi