I have been thinking for a while that there are a lot of menu items in the context menu that I rarely use and that my customer almost never use. Maybe it would be a nice feature to have a second level in the context menu where the more advanced and rarely used items could reside?
I realise its more of a nice-to-have feature. Still I think it would be very much in the spirit of 'a friendly cms' : )
You could file that as a feature request on Codeplex, hope for people to vote for it. But honestly, I don't think the umbraco hq will ever implement a multilevel context menu (I've seen forum posts and twitter tweets on that)
you could however register for the BeforeNodeRender event on the BaseTree object and remove rarely used features (altho maybe not what you need) - or build the multilevel context menu yourself?
As Dirk has mentioned we've had discussions on twitter about the context menu, and we've also had offline discussions about it too. Most of us agree that the context menus are getting very large in certain places in Umbraco, but additionally to that context menus aren't a great UI design choice. They aren't overly discoverable, which (seeing their role) isn't really that great.
I personally think that a 2 level context menu would be even less discoverable, but that's just my opinion :)
My personal solution to the ever expanding context menu is to remove permissions for typically unused items, and then have a fully priviledged account for use when something more advanced needs doing. This can also help you to not do anything accidentally (no delete permissions)
Just my two pence worth on this, one thing that bjawnie's screen shot shows is how far down the list the "Reload Nodes" option in. I am sure that is currently used far more than the items that were suggested to be moved into the Advanced section, so maybe a good idea to be slightly re-ordered in the normal menu, although this might not be required option when the new menu goes live in v4.1 ?
The Idea with only giving permission for the actions that the customer needs to access good and ensures fewer mishaps, but that would only go for one or two actions. Having several accounts is of course an option though not ideal.
I think that the context menu is already very long especially on the newer smaller laptop screens. If only a few custom actions are added to the context menu or the user has some toolbars in their browser it becomes crammed.
Chris > Yes, personally I use the reload action a lot since the tree menu often don't react to changes such as delete and create. Maybe this problem will disappear with the jTree component used in the latest version.
2 levels in context menu?
Hi,
I have been thinking for a while that there are a lot of menu items in the context menu that I rarely use and that my customer almost never use. Maybe it would be a nice feature to have a second level in the context menu where the more advanced and rarely used items could reside?
I realise its more of a nice-to-have feature. Still I think it would be very much in the spirit of 'a friendly cms' : )
Perhaps something like the below
No image posting I see, lets try with a link instead http://img134.imageshack.us/img134/6743/2levelcontextmenu.gif
You could file that as a feature request on Codeplex, hope for people to vote for it. But honestly, I don't think the umbraco hq will ever implement a multilevel context menu (I've seen forum posts and twitter tweets on that)
you could however register for the BeforeNodeRender event on the BaseTree object and remove rarely used features (altho maybe not what you need) - or build the multilevel context menu yourself?
Cheers,
/Dirk
As Dirk has mentioned we've had discussions on twitter about the context menu, and we've also had offline discussions about it too. Most of us agree that the context menus are getting very large in certain places in Umbraco, but additionally to that context menus aren't a great UI design choice. They aren't overly discoverable, which (seeing their role) isn't really that great.
I personally think that a 2 level context menu would be even less discoverable, but that's just my opinion :)
My personal solution to the ever expanding context menu is to remove permissions for typically unused items, and then have a fully priviledged account for use when something more advanced needs doing. This can also help you to not do anything accidentally (no delete permissions)
That's the best way, if the user doesn't need it don't give them it ;)
Just my two pence worth on this, one thing that bjawnie's screen shot shows is how far down the list the "Reload Nodes" option in. I am sure that is currently used far more than the items that were suggested to be moved into the Advanced section, so maybe a good idea to be slightly re-ordered in the normal menu, although this might not be required option when the new menu goes live in v4.1 ?
Cheers,
Chris
The Idea with only giving permission for the actions that the customer needs to access good and ensures fewer mishaps, but that would only go for one or two actions. Having several accounts is of course an option though not ideal.
I think that the context menu is already very long especially on the newer smaller laptop screens. If only a few custom actions are added to the context menu or the user has some toolbars in their browser it becomes crammed.
Chris > Yes, personally I use the reload action a lot since the tree menu often don't react to changes such as delete and create. Maybe this problem will disappear with the jTree component used in the latest version.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.