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
Skinning contest: One month to go
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="bodiroga" data-source="post: 677794" data-attributes="member: 63563"><p>Many thanks to both for your help, I really appreciate all your effort with the development and the teaching part <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>I think that I'm understanding it, so I will write what I've understood till now to see if I'm correct or not.</p><p></p><p>For the HelloWorld plugin example we have two workflow files: the action and state workflow files.</p><p></p><p>As I understand, the workflow state is the main screen itself, which includes the general information about it, such as: an "ID" indicator to identify the screen over the program, the screen title,... In this "main screen" is where the "screen" itself (the folder has that name) will be added with all the skinning possibilities: dockpanels, grids, stackpanels, buttons,... So we can say that the workflow state is just like a white paper that has to be written, but with it's own identification to distinguish it from all the different white papers we have. (I hope that you are understanding what I'm saying, because with the difficulty of the concepts and my basic level of english...)</p><p></p><p>The workflow action is a link to that workflow state, just like a bridge between one workflow state (in this case the home menu workflow state) and the other (the helloworld workflow state). It's only a "jump" indicator, right?</p><p></p><p>The only thing that I don't understand is: what are then the workflow models???? Are they a bunch of workflow states connected between them and the model tells them how they are organized? I can't find any workflow model file to have a look at it...</p><p></p><p>And the last question... which are the differences between a workflow state and a file containing <window></window>?? Baboonanza said that workflow state were "stopping points in the GUI, like Windows or Dialogs", but which are the differences between them?</p><p></p><p>I hope that I'm in the right direction and I haven't said too many stupid things, please correct me if I'm wrong <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>Many thanks again for all your help, this is the main reason why I love Mediaportal so much: developers, skinners, normal users,... are always ready to help and do their best for others. Great work guys, you are just awesome!!!</p><p></p><p>Best regards,</p><p></p><p>Aitor</p><p></p><p>PS: Having a better look at the Plugins folder I can see that there aren't much folders that can be skinned. Configuration, HelloWorld (not in standard release), Media, SkinBase, SkinEngine (I can forget this folder) and Weather are the only folders with skin subfolders! Things are getting cleaner with the time <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p></blockquote><p></p>
[QUOTE="bodiroga, post: 677794, member: 63563"] Many thanks to both for your help, I really appreciate all your effort with the development and the teaching part ;) I think that I'm understanding it, so I will write what I've understood till now to see if I'm correct or not. For the HelloWorld plugin example we have two workflow files: the action and state workflow files. As I understand, the workflow state is the main screen itself, which includes the general information about it, such as: an "ID" indicator to identify the screen over the program, the screen title,... In this "main screen" is where the "screen" itself (the folder has that name) will be added with all the skinning possibilities: dockpanels, grids, stackpanels, buttons,... So we can say that the workflow state is just like a white paper that has to be written, but with it's own identification to distinguish it from all the different white papers we have. (I hope that you are understanding what I'm saying, because with the difficulty of the concepts and my basic level of english...) The workflow action is a link to that workflow state, just like a bridge between one workflow state (in this case the home menu workflow state) and the other (the helloworld workflow state). It's only a "jump" indicator, right? The only thing that I don't understand is: what are then the workflow models???? Are they a bunch of workflow states connected between them and the model tells them how they are organized? I can't find any workflow model file to have a look at it... And the last question... which are the differences between a workflow state and a file containing <window></window>?? Baboonanza said that workflow state were "stopping points in the GUI, like Windows or Dialogs", but which are the differences between them? I hope that I'm in the right direction and I haven't said too many stupid things, please correct me if I'm wrong ;) Many thanks again for all your help, this is the main reason why I love Mediaportal so much: developers, skinners, normal users,... are always ready to help and do their best for others. Great work guys, you are just awesome!!! Best regards, Aitor PS: Having a better look at the Plugins folder I can see that there aren't much folders that can be skinned. Configuration, HelloWorld (not in standard release), Media, SkinBase, SkinEngine (I can forget this folder) and Weather are the only folders with skin subfolders! Things are getting cleaner with the time :D [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Skins and Design
Skinning contest: One month to go
Contact us
RSS
Top
Bottom
