Reply to thread

Message

<blockquote data-quote="mbuzina" data-source="post: 1002990" data-attributes="member: 12382">I never understood why creating a universal menu editor should be so difficult. Yes, in some skins the top entries have hyperlinks, in others only submenu (if there are sub entries), like Titan. Some have one overlay, some have more than one. Some are horizontal, some vertical, and maybe even some will support more than 2 menu hierarchies. But still: basically we have a tree with options.&nbsp;That is either a general XML sheet, which can be translated using XLT or used in expressions. I am now working on the last version.&nbsp;With regard to expressions in hyperlinks (and many others!): @<a href="https://forum.team-mediaportal.com/members/pog.97724/" target="_blank">Pog</a> has suggested something that works, at least for the top level of my menu, it also works for actions (I wanted to configure what Shutdown does, either ask, Power Off, Hybernate or Sleep). For my submenu each expression needs to be evaluated on click - so that will not work.&nbsp;&nbsp;&nbsp;Great idea - if MP can not provide the info (which it should in my opinion, the plugin manager should know what is there) we need to build something. Still I hope MP will provide resolution for the bugs I logged. If you can confirm them, I will provide a mantis for each.&nbsp;Another thing that really irks me, is that we have 2 script languages in MP skins. There are the # expressions, which allow quite complex calculations and there is the visibility / animation condition language, which does not have proper constructs, but provides a lot of pre built conditions. Both should be harmonized and provide the best of each to everyone (pretty please?).&nbsp;If we can get some commitment from a core MP dev who knows his way around the skin engine I would say let us build a team that makes MP skinning great. If that is not possible I would suggest to go the plugin route. @Developers : Any takers?</blockquote>

[QUOTE="mbuzina, post: 1002990, member: 12382"] I never understood why creating a universal menu editor should be so difficult. Yes, in some skins the top entries have hyperlinks, in others only submenu (if there are sub entries), like Titan. Some have one overlay, some have more than one. Some are horizontal, some vertical, and maybe even some will support more than 2 menu hierarchies. But still: basically we have a tree with options. That is either a general XML sheet, which can be translated using XLT or used in expressions. I am now working on the last version. With regard to expressions in hyperlinks (and many others!): @[URL='https://forum.team-mediaportal.com/members/pog.97724/']Pog[/URL] has suggested something that works, at least for the top level of my menu, it also works for actions (I wanted to configure what Shutdown does, either ask, Power Off, Hybernate or Sleep). For my submenu each expression needs to be evaluated on click - so that will not work. Great idea - if MP can not provide the info (which it should in my opinion, the plugin manager should know what is there) we need to build something. Still I hope MP will provide resolution for the bugs I logged. If you can confirm them, I will provide a mantis for each. Another thing that really irks me, is that we have 2 script languages in MP skins. There are the # expressions, which allow quite complex calculations and there is the visibility / animation condition language, which does not have proper constructs, but provides a lot of pre built conditions. Both should be harmonized and provide the best of each to everyone (pretty please?). If we can get some commitment from a core MP dev who knows his way around the skin engine I would say let us build a team that makes MP skinning great. If that is not possible I would suggest to go the plugin route. @Developers : Any takers? [/QUOTE]

Verification