menu enhancement bugs - Githubissues

cdotyone / mochaui

development tree for MochaUI

http://mochaui.org/demo/

Other

290 stars 83 forks source link

menu enhancement bugs #89

Open shimondoodkin opened 13 years ago

shimondoodkin commented 13 years ago

the menu does not theme and it should have a delay before close on mouse out

cdotyone commented 13 years ago

delay causes unwanted effects. Colors not a bug, just left over from when it was created. Adjusted CSS, so that the menu is darker.

shimondoodkin commented 13 years ago

the problem with the menu it that it closes when entering to sub menus. it is frustrating.

cdotyone commented 13 years ago

what browser are you using?

shimondoodkin commented 13 years ago

chrome latest, i use laptop, i mean if I mouse out little bit out of a menu item on my way to the submenu the menu closes and i have to open the menu again.

cleankod commented 13 years ago

I second that! I received reports that menu is annoying for most people.

I would also like to suggest the option for the menu: close after click (after choosing element from menu).

cdotyone commented 13 years ago

You guys win. I will find a fix for this, and look into the close on click. Thanks for chiming in darkthal. -Chris

BuenGenio commented 13 years ago

In the original MochaUI, the dropdown top menu could be constructed directly from the

's in HTML. The new menu Control, judging by the source, can only be initialized with JavaScript. Has the new MochaUI retained the old functionality for constructing the top menu from the HTML files?

Otherwise, big respect for reviving the project - it's truly a piece of art.

POt

cdotyone commented 13 years ago

I have been focusing on the JSON based data. Some of the older controls had HTML. I intended to make sure as much as the older HTML routines still would work. This is coming only partially there.

BuenGenio commented 13 years ago

Thanks. The reason why I think preserving the ability to build ul/li based menus would be useful is that a) it would allow creating, editing and maintaining menu systems much quicker and easier through the use of flat HTML, and b) would allow the menu to fail gracefully, should anything go wrong.

I guess since the menu manly relies on CSS it should still be possible to make a mainmenu by assigning the right id/class combinations?

Any comments for/against?

cdotyone commented 13 years ago

I like JSON over HTML. If control needs to change its html structure, the control will still work. HTML is more limiting. Pick your poison. -Chris

shimondoodkin commented 13 years ago

You can't fail gracefully a JavaScript system. For me JavaScript based is okay

shimondoodkin commented 13 years ago

You can't fail gracefully a JavaScript system. For me JavaScript based is okay

shimondoodkin commented 13 years ago

closed it by misstake, can't reopen.