public interface SkinEditor
Your changes are saved in an intermediate database so the skin can be updated over time. When you are happy with your skin, export it to a zip file, drop it into your project skins/ directory and load it as you would any other skin. See below for details on exporting.
You can access the Skin Editor in one of two ways:
For Skin Editor team support,
registered users can access the tool via Reify, Isomorphic's low-code platform. The Skin Editor for Reify allows
skin-designs to be shared among users and changes you make to your skins are reflected right
away within Reify
. Note that this version of the tool may be running
bleeding-edge code, more recent then the current public release.
com.smartgwtee.tools.Tools
will make the Skin Editor available
in your SmartGWT project. Only skin resources inherited by your project will be available for
editing so you may want to add additional dependencies to your module file. For example, to
make the Obsidian skin available, add: <inherits name="com.smartclient.theme.obsidian.ObsidianResources"/>
Always run a GWT compile after
any module file change to ensure it's picked up, and then navigate to
{project_name}/tools/skinTools/skinEditor.jsp
.
isc_userSkin
must be imported to your Database using the AdminConsole
. This DataSource is used to store user skins until
exportCompass
to
recompile skin-CSS, via an operation on the isc_userSkin
DataSource which invokes
compass compile 'path-to-skin-template-dir' on the server.
A skin exported in this way
can be further edited locally in your project Skin Editor, if you have an appropriate license.
Once extracted into the skins/ directory, it will appear in Skin Editor's list of user-skins
and can be edited as normal, with changes being saved to disk rather than database. You might
want to do this, for example, in order to make non-CSS configuration to the skin, via
load_skin.js
. While future versions of Skin Editor will support non-CSS skin
configuration, these features are not yet available.
You might want to do this if you create a customized skin and you want to be able to generate several variations on it - like changing colors, to make the color schemes of multiple customers that you are creating applications for.