Is there a need for a skin editor? (1 Viewer)

[NoBugS]

as I mentioned... its not done yet Just working on it since a week.
catavolt: what do you mean with: you don't see buttons? can you attach a screenshot?

 

[infinite.loop]

small note.
it might be a good idea to attach testbuilds and changelog of this tool in the first post, rather than posting it inside the thread which makes testbuilds hard to find.

 

[NoBugS]

didn't know it works. sounds good to me. Should I always remove the previous testbuild or just add the up (might get long)?
Changelog should probably add up.

 

[catavolt]

Hi steff2002, here are the screenshots - the buttons e.g. on basichome are not shown - I have no buttons displayed at all, no matter what skinfile I display.

 

[NoBugS]

The reason why the buttons are missing is that I currently not support

   <control>
      <type>group</type>
      <description>group element</description>
      <layout>StackLayout</layout>
      <posX>0</posX>
      <posY>144</posY>
      <control>
        <description>TV normal push button</description>
        <type>button</type>
        <id>2</id>
        <width>215</width>
        <height>47</height>
        <label>605</label>

I think 'group' should be the next to implement, however I have no info about it (wiki is empty).
Any skinner that can provide me a quick description about the possible layouts and the way they are displayed.

If you try for ex. Blue3 you get the buttons in BasicHome. So mainly its not a button-issue but a GUIGroup issue.

Would be great if somebody could also provide me with info about the other controls that are not described in Wiki.

 

[pilehave]

The reason why the buttons are missing is that I currently not support

   <control>
      <type>group</type>
      <description>group element</description>
      <layout>StackLayout</layout>
      <posX>0</posX>
      <posY>144</posY>
      <control>
        <description>TV normal push button</description>
        <type>button</type>
        <id>2</id>
        <width>215</width>
        <height>47</height>
        <label>605</label>

I think 'group' should be the next to implement, however I have no info about it (wiki is empty).
Any skinner that can provide me a quick description about the possible layouts and the way they are displayed.

If you try for ex. Blue3 you get the buttons in BasicHome. So mainly its not a button-issue but a GUIGroup issue.

Would be great if somebody could also provide me with info about the other controls that are not described in Wiki.

A "group" only has two attributes:

• layout
• animation

The layout can be:

• GridLayout
• StackLayout
• RingLayout

A GridLayoutis like a table, and the number of rows/columns, spacing and orientation can be set like this:

<layout>GridLayout(columns, rows, horizontalSpacing, verticalSpacing, Horizontal)</layout>


A StackLayout is a row or column of controls, and can be horizontal or vertical by defining it like:

<layout>StackLayout(spacing, Vertical)</layout>

I have never used a RingLayout, but i THINK it is used like this:

<layout>RingLayout(int horizontalSpacing, int verticalSpacing)</layout>

I think that was it

 

[Dadeo]

+1

I'm pretty confident that a skineditor would recieve a very warm welcome

Ah Spragleknas you are the master of understatement!

If you are up for advanced features -
1. A drop down box for hyperlinks and action codes
2. List of IDs used in the xml (maybe a drop down box in onup/down/left/right)
3. Properties - there are a lot more than shown in your screenshot - would be fantastic if it only showed the properties supported in that skin file, but I have no idea how you would figure that out!

 

[NoBugS]

thanks for the explaination. I will look into it.
Just saw that there is an actiongroup.

	<control>
		<type>actiongroup</type>
		<description>action menu</description>
		<defaultcontrol>4</defaultcontrol>
		<onexit>50</onexit>
		<buttonX>0</buttonX>
		<buttonY>0</buttonY>
		<buttonwidth>60</buttonwidth>
		<buttonheight>576</buttonheight>
		<textureFocus>Action_focus.png</textureFocus>
		<textureNoFocus>Action_focus.png</textureNoFocus>
		<width>60</width>
		<height>720</height>
		<dimColor>00ffffff</dimColor>
		<control>
			<type>image</type>
			<posX>15</posX>
			<posY>90</posY>
			<width>263</width>
			<height>430</height>
			<texture>Backslide.png</texture>
			<colorDiffuse>fffffffff</colorDiffuse>
			<visible>!Control.HasFocus(50)</visible>
			<animation effect="slide" time="450" start="-300,0" reversible="false">visible</animation>
			<animation effect="slide" time="450" end="-300,0" reversible="false">hidden</animation>
		</control>
		<control>
			 <type>group</type>
			 <description>button group</description>
			<animation effect="slide" time="450" start="-300,0" reversible="false">visible</animation>
			<animation effect="slide" time="450" end="-300,0" reversible="false">hidden</animation>

anybody can explain me the details about the various options?

 

[infinite.loop]

I dare to post a small request here.
It would be great if our skinners could check our ::skindesigners guide:: for missing info, and document it there.

I am sure that this would also help steff20002 with his work.

 

[arion_p]

May I suggest a feature (with implementation suggestion too) that I think would help a lot of our skinners:
Add the ability to load window plugin dlls (own and 3rd party), enumerate type infos in each assembly and provide the skinner with a list of windows defined in those plugins (the classes derived from GUIWindow) with their IDs (this can be tricky but you can have a look at PluginManager and WindowManager for clues). For each available window (class) scan for fields having the SkinControl() attribute and get those control IDs along with their class type (perhaps even map class types to xml control types). Use them to allow the skinner to choose each control ID or even automatically insert the correct controls and verify that IDs used are the same with the ones in the code.

This will save a lot of headaches with mismatched control IDs.