We'd want to be able to have custom skins in the editor.
There will be a new menu "Skins", which will have all installed skins (we can have "Classic" and "Dark" as the first two available skins), and also " "Custom Skin", "Import" and "Export".
Classic: The current look of the editor.
Dark: The dark look implemented in Alan's version.
Custom Skin: Will enable to create a new custom skin.
Import/Export: Will load&install/save the skin to/from dedicated xml files.
In addition, the windows menu will have a new window "Skin" which will show/hide the skin editor.
Skin Editor: to be implemented as a property viewer (similar to the properties window we have now) with a combo box for different zones for the skin (we could make it all in one property viewer, but I suspect we can reach hundreds of different customizations to the skin so it would be too long).
Zones could be: general, script editor, docking panels, plugins, project tree, room designer, sprites, etc.
The 'general' zone should have basic properties (like font) that can be overriden by specific zones if desired.
Changing the skins should change the look in run-time (if possible).
The skin should be exposed to the plugins so that they could alter their look to match.
Also, a "SkinChanged" event should be fired so that plugins could register and change their look in run-time when the skin is changed.
The infrastructure should be written in a way that will make it easy for developers to add new properties to the skin, without hurting backwards compatability with existing skins.
There will be a new menu "Skins", which will have all installed skins (we can have "Classic" and "Dark" as the first two available skins), and also " "Custom Skin", "Import" and "Export".
Classic: The current look of the editor.
Dark: The dark look implemented in Alan's version.
Custom Skin: Will enable to create a new custom skin.
Import/Export: Will load&install/save the skin to/from dedicated xml files.
In addition, the windows menu will have a new window "Skin" which will show/hide the skin editor.
Skin Editor: to be implemented as a property viewer (similar to the properties window we have now) with a combo box for different zones for the skin (we could make it all in one property viewer, but I suspect we can reach hundreds of different customizations to the skin so it would be too long).
Zones could be: general, script editor, docking panels, plugins, project tree, room designer, sprites, etc.
The 'general' zone should have basic properties (like font) that can be overriden by specific zones if desired.
Changing the skins should change the look in run-time (if possible).
The skin should be exposed to the plugins so that they could alter their look to match.
Also, a "SkinChanged" event should be fired so that plugins could register and change their look in run-time when the skin is changed.
The infrastructure should be written in a way that will make it easy for developers to add new properties to the skin, without hurting backwards compatability with existing skins.
Logged
