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 1
Development
General Development (no feature request here!)
Is there a need for a skin editor?
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="arion_p" data-source="post: 506816" data-attributes="member: 45945"><p>I am not a skinner either, I am a developer <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" /> but I will try to elaborate a bit more.</p><p></p><p>Case 1:</p><p>User wants to add a new screen (xml) file. He is presented with a dialog that contains the list of windows (defined in MP's own and installed window plugins) that have not been already mapped to other screens/xml files. The user may also specify a window ID by hand.</p><p></p><p>Case 2:</p><p>User has just created a screen and wishes a quick start. He chooses auto-insert window controls and he is presented with a dialog having a list of all controls defined in code for the window with the same ID as the screen being edited. For each control he sees its name (variable name in code) its ID and its type. He selects the controls to insert, and controls are inserted into the screen xml using names, IDs and control types from the above list. He can then proceed to move / resize controls to the right place.</p><p></p><p>Case 2a:</p><p>User want to see if he missed some controls (that exist in the window but not in the xml). He opens up the same dialog as in case 2. He is presented only with controls not already in the xml. He can proceed to insert any or all of those in the xml just like in case 2</p><p></p><p>Case 3:</p><p>User has finished working a screen xml and wants to validate that it will bind correctly to the window it was designed for. He presses the "Validate IDs" button/option and the skin editor matches the IDs in the control in the xml to the IDs of the controls in the window. The user is presented with a dialog containing three lists:</p><p></p><ul> <li data-xf-list-type="ul">one lists the control IDs in the xml that do not exist in the window (code)</li> <li data-xf-list-type="ul">the second lists control IDs in the window (code) that do not exist in the xml</li> <li data-xf-list-type="ul">the third lists control ID that exist in both but the control type specified in the xml is not appropriate for the control type declared in the window (code). E.g. xml specifies a control as <em>Label</em> but in the code it is declared as <em>GUIImage</em></li> </ul><p>Hope this makes it more clear.</p><p>It would be nice if a skinner could comment if such functionality is needed and/or helpful.</p></blockquote><p></p>
[QUOTE="arion_p, post: 506816, member: 45945"] I am not a skinner either, I am a developer :D but I will try to elaborate a bit more. Case 1: User wants to add a new screen (xml) file. He is presented with a dialog that contains the list of windows (defined in MP's own and installed window plugins) that have not been already mapped to other screens/xml files. The user may also specify a window ID by hand. Case 2: User has just created a screen and wishes a quick start. He chooses auto-insert window controls and he is presented with a dialog having a list of all controls defined in code for the window with the same ID as the screen being edited. For each control he sees its name (variable name in code) its ID and its type. He selects the controls to insert, and controls are inserted into the screen xml using names, IDs and control types from the above list. He can then proceed to move / resize controls to the right place. Case 2a: User want to see if he missed some controls (that exist in the window but not in the xml). He opens up the same dialog as in case 2. He is presented only with controls not already in the xml. He can proceed to insert any or all of those in the xml just like in case 2 Case 3: User has finished working a screen xml and wants to validate that it will bind correctly to the window it was designed for. He presses the "Validate IDs" button/option and the skin editor matches the IDs in the control in the xml to the IDs of the controls in the window. The user is presented with a dialog containing three lists: [LIST] [*]one lists the control IDs in the xml that do not exist in the window (code) [*]the second lists control IDs in the window (code) that do not exist in the xml [*]the third lists control ID that exist in both but the control type specified in the xml is not appropriate for the control type declared in the window (code). E.g. xml specifies a control as [I]Label[/I] but in the code it is declared as [I]GUIImage[/I] [/LIST] Hope this makes it more clear. It would be nice if a skinner could comment if such functionality is needed and/or helpful. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Is there a need for a skin editor?
Contact us
RSS
Top
Bottom