home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Skins and Design
Separation of menu items
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Albert" data-source="post: 728305" data-attributes="member: 67886"><p>Hi all,</p><p>morpheus wrote a PM about how we could separate different kinds of menu items. I think that discussion should be public because it contains many interesting points.</p><p></p><p>The point is, in the current MP2 system/skin, there are different kinds of menu items. There are menu items which are bound to the current workflow state (for example the menu point "Music" is bound to the "Home" workflow state), while there are other menu points which are bound to other internal states (for example the "Fullscreen Video" menu point is only visible if there is a primary player which is a video player).</p><p></p><p>We had some discussions before that perhaps such kinds of menu items should be separated, maybe into two different menus or by displaying menu items of different kinds in a different way.</p><p></p><p>Morpheus' PM was this:</p><p></p><p></p><p></p><p>Now comes my answer.</p><p></p><p>First: It's a very good idea to have different data templates for the different menu item types, although the separation between "normal" and "global" items is a bit arbitrary. The separation you have choosen (based on the "SourceStateId==null" check) is maybe the most sensible separation, but I could also imagine to separate NavigatePush/NavigatePop actions from programmatic actions (WorkflowContributor actions), as another example. There could be many other sensible ways to filter the list.</p><p></p><p>Currently, menu items are also organized into so called "display categories" like "a-Media", "z-WorkflowContributors" etc. Those categories are currently used for two things: First to group items of the same category and second to sort the categories in the menu. If we create a way for the skin designer to filter special menu items by arbitrary expressions, he could also separate the menu items per category, for example. Maybe the skin designer could always use a separate menu for the menu items from the "z-WorkflowContributors" menu.</p><p></p><p>What I want to say is: I wouldn't hard code the separation in the menu model. But the idea to have provide such a filter mechanism for the skin designer is very good.</p></blockquote><p></p>
[QUOTE="Albert, post: 728305, member: 67886"] Hi all, morpheus wrote a PM about how we could separate different kinds of menu items. I think that discussion should be public because it contains many interesting points. The point is, in the current MP2 system/skin, there are different kinds of menu items. There are menu items which are bound to the current workflow state (for example the menu point "Music" is bound to the "Home" workflow state), while there are other menu points which are bound to other internal states (for example the "Fullscreen Video" menu point is only visible if there is a primary player which is a video player). We had some discussions before that perhaps such kinds of menu items should be separated, maybe into two different menus or by displaying menu items of different kinds in a different way. Morpheus' PM was this: Now comes my answer. First: It's a very good idea to have different data templates for the different menu item types, although the separation between "normal" and "global" items is a bit arbitrary. The separation you have choosen (based on the "SourceStateId==null" check) is maybe the most sensible separation, but I could also imagine to separate NavigatePush/NavigatePop actions from programmatic actions (WorkflowContributor actions), as another example. There could be many other sensible ways to filter the list. Currently, menu items are also organized into so called "display categories" like "a-Media", "z-WorkflowContributors" etc. Those categories are currently used for two things: First to group items of the same category and second to sort the categories in the menu. If we create a way for the skin designer to filter special menu items by arbitrary expressions, he could also separate the menu items per category, for example. Maybe the skin designer could always use a separate menu for the menu items from the "z-WorkflowContributors" menu. What I want to say is: I wouldn't hard code the separation in the menu model. But the idea to have provide such a filter mechanism for the skin designer is very good. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Skins and Design
Separation of menu items
Contact us
RSS
Top
Bottom