Reply to thread

Message

<blockquote data-quote="Albert" data-source="post: 677020" data-attributes="member: 67886">AW: Skinning contest: One month to goHi Aitor and thanks for all your effort! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />You're right, bindings are very complicated. But most of the bindings functionality can be compared to how it works in WPF. We just have some extensions which makes it even more flexible.The navigation part is new and MP2 specific, and there is a concept page for it in the wiki. Go to the Wiki -&gt; MP2 developers guide -&gt; Developers and skinners documentation. Here, in the &quot;Concepts&quot; section, read the &quot;Workflow&quot; concept. You need that to understand what a workflow state is. You're right, unfortunately, actions are not documented here (I'll do that in the next days).An action (or: MenuAction) is bound to one or more source workflow states where it is visible in the menu. There are many types of workflow actions, the simplest one is &quot;PushNavigationTransition&quot; which just pushes another workflow state onto the workflow navigation stack. &quot;PopNavigationTransition&quot; removes a workflow state from the stack. &quot;MethodCallAction&quot; calls a method.The action's &quot;Id&quot; ist just a unique guid (just generate one). It is currently not referenced from anywhere.&quot;DisplayCategory&quot; and &quot;SortOrder&quot; control the order in the menu. &quot;Source-&quot;/&quot;TargetState&quot; are guids of the referenced workflow states, as they are defined in the states file.Btw: In the background, we're moving to a new wiki. I hope that our docs people will officially switch to it soon, because we don't change the old one any more. So you'll hopefully find more docs in the new wiki when it is available.</blockquote>

[QUOTE="Albert, post: 677020, member: 67886"] [b]AW: Skinning contest: One month to go[/b] Hi Aitor and thanks for all your effort! :-) You're right, bindings are very complicated. But most of the bindings functionality can be compared to how it works in WPF. We just have some extensions which makes it even more flexible. The navigation part is new and MP2 specific, and there is a concept page for it in the wiki. Go to the Wiki -> MP2 developers guide -> Developers and skinners documentation. Here, in the "Concepts" section, read the "Workflow" concept. You need that to understand what a workflow state is. You're right, unfortunately, actions are not documented here (I'll do that in the next days). An action (or: MenuAction) is bound to one or more source workflow states where it is visible in the menu. There are many types of workflow actions, the simplest one is "PushNavigationTransition" which just pushes another workflow state onto the workflow navigation stack. "PopNavigationTransition" removes a workflow state from the stack. "MethodCallAction" calls a method. The action's "Id" ist just a unique guid (just generate one). It is currently not referenced from anywhere. "DisplayCategory" and "SortOrder" control the order in the menu. "Source-"/"TargetState" are guids of the referenced workflow states, as they are defined in the states file. Btw: In the background, we're moving to a new wiki. I hope that our docs people will officially switch to it soon, because we don't change the old one any more. So you'll hopefully find more docs in the new wiki when it is available. [/QUOTE]

Verification