Is there a need for a skin editor? (2 Viewers)

trevor

Portal Pro
October 17, 2006
1,600
950
Chelmsford
Home Country
United Kingdom United Kingdom
thanks!

for now I started with the basics and infrastructure of the tool.
here an updated screenshot. I try to really get as much as possible WYSIWYG with some nice added features.

Waiting for some feedback/comments how you like it so far.

Been watching this thread with interest and must say looking good, nice as screen shots are getting access to the WIP would be good.

Not suggesting me here, but you may want ask some of the skinners out there if they would like to test/try and provide feedback, consider a closed test group.

Keep up the great work, it is much appreciated.
 

NoBugS

Portal Pro
August 22, 2009
91
54
Hoover, AL
Home Country
United States of America United States of America
I think thats a good idea. But how to get in touch with some skinners. Maybe everybody that wants to help me testing and giving me feedback should contact me.

Puh, more work than expected, but still fun :). Somebody still working on the wiki?
 

NoBugS

Portal Pro
August 22, 2009
91
54
Hoover, AL
Home Country
United States of America United States of America
Ok guys,

here is the very first alpha-version.... it works with the folder-structure present in V1.02
just unzip and run exe

some comments about what it can and what not:

you can:
  • open a skin-folder (file -> open -> select root folder of skin)
  • view fonts, images and screens
  • all supported controls show up in the tree under controls (whats not in there is not supported so far)
  • the list of controls is not long but I started with the most important
  • to open a screen/image/font double-click on it

you can not:
  • save changes made to the xmls
  • not all attributes are reflected in the WYSIWYG gui (feedback is appreciated about whats missing)

you need the java runtime V1.6.xx as your default JRE (to check: open dos-shell and type java -version).

I get

java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)

so anything stating 1.6.x is fine.


hope somebody likes it so far...

:D for the feedback (either here in the forum or via PM)
 

Attachments

  • MPESkinEditor_1.00 alpha 1.zip
    30.7 KB

ltfearme

Community Plugin Dev
  • Premium Supporter
  • June 10, 2007
    6,751
    7,196
    Sydney
    Home Country
    Australia Australia
    I like what I see so far....this will make it much easier to create/modify skins. What would also be nice is to be able to load a file containing property strings instead of seeing #TVSeries.Title...esp for very long ugly properties which most are e.g.

    properties.xml:

    Code:
    <property name="#TVSeries.Title">
      <value>The IT Crowd</value>
    </property>
    <property name="#TVSeries.Episode.Runtime">
      <value>43 mins</value>
    </property>

    or something similar. Maybe that's what that 'String' entry is for :)
     

    NoBugS

    Portal Pro
    August 22, 2009
    91
    54
    Hoover, AL
    Home Country
    United States of America United States of America
    great idea.
    I implemented support for the following attached file.
    I goes along side the the other xmls.
    It can be adapted/extended as needed.

    It will be part of the next version (which already has some more improvements).

    The file will look like that:

    Code:
    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <properties>
    	<property name="#highlightedbutton">TV</property>
    	<property name="#whatever">TextToDisplay</property>
    </properties>
     

    Attachments

    • properties.xml
      30.6 KB

    ltfearme

    Community Plugin Dev
  • Premium Supporter
  • June 10, 2007
    6,751
    7,196
    Sydney
    Home Country
    Australia Australia
    Another functionality I would like to see is for the visibility conditions to be evaluated for controls. The user could create a few templates/scripts which set the visibility of controls when loaded and those controls referenced in the skin designer will update accordingly i.e. will be visible or invisible.

    e.g.

    set Control.IsVisible(1235)=true
    set Control.IsVisible(1236)=true
    set Control.IsVisible(1237)=false
    set Control.HasFocus(50)=true
    set Control.HasText(222)=true

    There is more you can change but thats just a rough idea. This would make it particularly useful for creating skins for advanced plugins.
     

    infinite.loop

    Retired Team Member
  • Premium Supporter
  • December 26, 2004
    16,163
    4,133
    127.0.0.1
    Home Country
    Austria Austria
    looks very good!

    even though it might not become as powerful as required to develop new screens from scratch, it would be a bit timesaver to be able do the alignment / finetuning inside such an editor. :)

    keep up the good work!
     

    catavolt

    Design Group Manager
  • Team MediaPortal
  • August 13, 2007
    14,363
    10,399
    Königstein (Taunus)
    Home Country
    Germany Germany
    That looks really great - but I don´t see any buttons listed and displayed which would be the most important thing for the user to change e.g. basichome?
     

    pilehave

    Community Skin Designer
  • Premium Supporter
  • April 2, 2008
    2,566
    521
    Hornslet
    Home Country
    Denmark Denmark
    I just compiled the old editor from the SVN-repository and while it seems outdated on some areas, I think most of the "stuff" it does should be "ported". This includes resizing controls with mouse, right-click to bring to front etc.

    In the old editor there was also included animation-controls to set timings, effects and other things :)
     

    Users who are viewing this thread

    Top Bottom