McBainUK Wrote:The main menu I think might be a special case.
Skins talking to plugins and visa versa is always problematic. Maybe skintools could concentrate on manageging the creation of a skin, and leave the preview to using gbpvr itsleft. You could always have a preview of each composite image?
I was thinking about something like that, too. Maybe if a special element has a size and location hardcoded, we can display it, otherwise, let the user know somehow that certain items are not displayable. Kind of sucks, though.
Also, I think it would be great to have a "code view", so in case our preview can't handle something, at least you could go back and tweak it. This opens up all kinds of possibilities - we could eventually have tag insight, so if SkinTools knew all of the possible options to display for a tag, it could tell you in a little context menu (again, like Visual Studio).
i.e., as you're typing:
<SpecialElement Name="MenuType" Type="
it could have a menu saying:
GBPVR.HorizontalMenuTask
GBPVR.VerticalMenuTask
that you could choose from.
Or instead of building this into we could include handling XML extensions in the preferences (probably better for phase 1), which may look something like this:
Associate File Types with Editors:
".xml - Eclipse"
".jpg,.png - Photoshop"
Then, back in the main app you could just right click on the XML file in the object viewer and select "Edit".
gruskada