Skin Composer Feedback

[Quillraven]

Hi,

for the first time I use skin composer for a new project I am working on and I am actually very happy with it but do have some feedback. Feel free to close the issue if you don't want to include any of it but here are the things I noticed:

• imo the popup info for Visible in the Table Properties is wrong. It is the same text as Touchable. However, I think visible is to make the widget visible/invisible and touchable make the widget clickable/touchable
  
• What is the viewport of Scene Composer? I could not find that anywhere and it actually makes a difference if I use a Stretch-, Fit- or Screenviewport when it comes to the correct representation of my game. Imo you should be allowed to set the viewport that is used for the representation to get the correct in-game behavior
• Also, I personally find it confusing that when you go to Project -> Scene Composer..., that it completely hides the skin composer UI. I found the navigation not very intuitive in that area. You then need to go to File -> Quit to get back to the skin composer UI? At least that is how I used it and I found it confusing.
  • Maybe just make a "Tab Layout"? First tab is the skin composer and if someone opens an additional "app" like scene manager, it gets opened in a separate tab? Like in a browser you can switch between the different tabs at the top?
• Would be cool if the Scene can also be exported as LibKTX's Scene2D syntax: Link
  • I can maybe help with that if you tell me where you are creating the Java syntax
• In older projects I sometimes had to adjust the leftWidth, rightWidth or topHeight properties of a drawable. I used that for Labels or TextButtons in case the Text should have some padding to be inside the background graphic. Imagine a background graphic of a table and that table has a border of 2pixels in a special color. I don't want the text to be inside that border, so I changed the properties mentioned above to keep the text inside those borders. Maybe there is a better solution to fix this problem but if there isn't then it would be nice if these properties can be set on the drawables as well

That's it! again, thank you for this tool I really like it a lot and it saves a lot of time in my UI workflow. Cool stuff :)