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: 728384" data-attributes="member: 67886"><p><strong>AW: Separation of menu items</strong></p><p></p><p>Smeulf, the "display category" is just a simple string which is defined as an XML attribute of a workflow action declaration. Thus a display category is not a first-class object which needs to be declared or even hard coded somewhere. A display category is just a simple string which exists if at least one workflow action defines that category string.</p><p></p><p>That's the current implementation. I'm not sure if it's correct that way. It just seemed to me the simplest way to achieve a logical grouping of menu items and additionally, a sorting of those groups without the need of too much declaration overhead.</p><p></p><p>The former system (before my display categories were introduced) was using a half-order for menu items; for each menu item, a "before" and/or an "after" attribute was defined which told the system a relative ordering of items, but which could lead to unstable sort orders, off course.</p></blockquote><p></p>
[QUOTE="Albert, post: 728384, member: 67886"] [b]AW: Separation of menu items[/b] Smeulf, the "display category" is just a simple string which is defined as an XML attribute of a workflow action declaration. Thus a display category is not a first-class object which needs to be declared or even hard coded somewhere. A display category is just a simple string which exists if at least one workflow action defines that category string. That's the current implementation. I'm not sure if it's correct that way. It just seemed to me the simplest way to achieve a logical grouping of menu items and additionally, a sorting of those groups without the need of too much declaration overhead. The former system (before my display categories were introduced) was using a half-order for menu items; for each menu item, a "before" and/or an "after" attribute was defined which told the system a relative ordering of items, but which could lead to unstable sort orders, off course. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Skins and Design
Separation of menu items
Contact us
RSS
Top
Bottom