public interface ReifyCustomComponents
You can customize Reify by adding your own custom components, and even adding custom editors for properties of those components.
The Component Library on the right hand side of Reify loads component definitions from two XML files in the [webroot]/tools/visualBuilder directory: customComponents.xml and defaultComponents.xml. customComponents.xml is empty and is intended for developers to add their own components. defaultComponents.xml can also be customized, but the base version will change between Smart GWT releases.
As can be seen by looking at defaultComponents.xml, components are specified using a tree structure similar to that shown in the tree XML loading example. The properties that can be set on nodes are:
type: name of the Smart GWT Class on which create() will be called in order to construct the component.
typecan be omitted to create a folder that cannot be dropped
title: title for the node
defaults: an Object specifying defaults to be passed to create(). For example, you could add an "EditableGrid" node by using
type: "ListGrid"and specifying:
<defaults canEdit="true"/>NOTE: if you set any defaults that are not Canvas properties, you need to provide explicit type as documented under Custom Properties for
children: components that should appear as children in the tree under this node
icon: icon to show in the Reify component tree (if desired)
iconWidth/Height/Size: dimensions of the icon in pixels ("iconSize" sets both)
showDropIcon: for components that allow children, whether to show a special drop icon on valid drop (like
In order to use custom classes in Reify, you must modify
[webroot]/tools/visualBuilder/globalDependencies.xml to include:
component schemafor the custom component
When you provide
custom schema for a
uses that schema to drive component editing (Component Properties pane) and to drive drag
and drop screen building functionality.
Newly declared fields will appear in the Component Editor in the "Other" category at the bottom by default. You can create your own category by simply setting field.group to the name of a new group and using this on multiple custom fields.
The ComponentEditor will pick a FormItem for a custom field by the
same rules used for ordinary databinding,
including the ability to
set field.editorType to use a custom FormItem.
When properties are changed by the user, Reify will look for an appropriate "setter
function" for the custom field, for example, for a field named "myProp", Reify will
look for "setMyProp". The target component will also be
Designing Components for Editing & Using Placeholders
When Reify creates your custom component, no properties are provided at
construction, and all necessary properties will be provided after construction via calling
setter methods (for example,
setPropertyName) as users assign them
via the Property Sheet.
Often a custom component has been implemented to expect that certain properties are passed at construction, and the constructor may crash if they are absent. Similarly, setters may not exist for properties assumed to be provided at construction, or may crash. Any such errors are caught by Reify and reported under the "componentExceptions" log category, however, Reify has several features to make it possible to work with misbehaving components without requiring refactoring.
If a component requires certain properties before it can be validly created, you can set
PaletteNode.requiredProperties as a comma-separated list of property names on the
paletteNode for the component, and Reify will use a placeholder until
the designer has provided each of the required properties. The placeholder will just show
the className of the real component and the list of remaining required properties. In
order to take up the right amount of space, the placeholder will use the same sizing-related
settings that the real component would use (such as
If a component lacks appropriate setters for some properties but would work properly if
re-created from scratch, in the Component Schema you can set
on any fields that should cause the component to be re-created. You can also set
paletteNode to cause any property
change to cause the component to be re-created.
You may also have components that you don't want to try to use within Reify at all. In
this case, just set
PaletteNode.alwaysUsePlaceholder to true, and Reify will never
try to create the component, and always show a placeholder. You can also set
to the URL of an image file to use in lieu of the usual
Note that when you use the Run within Reify, Placeholders will appear (otherwise
your screen would presumably crash!) - this is because Reify is using the
LoadProjectSettings.allowPlaceholders option. If you export a Reify project or
load it dynamically,
allowPlaceholders will be false,
and your screen will use the real target components.
Event -> Action Bindings
The Component Properties pane contains an Events tab that allows you wire components events to actions on any other component currently in the project.
Events are simply
StringMethods defined on the
order to be considered events, method definitions must have been added to the class via
Class.registerStringMethods() and either be publicly documented Smart GWT methods or,
for custom classes, have a methods definition in the
Examples of events are:
Actions are methods on any component that have a method definition in the
component schema and specify action="true".
All available events (stringMethods) on a component are shown in the Events tab of the Component Editor. Clicking the plus (+) sign next to the event name brings up a menu that shows a list of all components currently in the project and their available actions. Selecting an action from this submenu binds the action to the selected event. When an event is bound to an action in this manner, automatic type matching is performed to pass arguments from the event to the action as follows:
typeattribute on the method param in the
component schemadefinition of a custom component.
Component Drag and Drop
Reify uses component schema to determine whether a given drop is allowed and what
methods should be called to accomplish the drop. For example, any Canvas-based component
can be dropped on a VLayout because VLayout has a "members" field of type "Canvas", and an
Because of these rules, any subclass of Canvas will be automatically eligible to be dropped into any container that accepts a Canvas (eg, a Layout or Tab). Any subclass of a FormItem will be, likewise, automatically eligible to be dropped into a DynamicForm.
NOTE: after modifying component schema, it may be necessary to restart the servlet engine and reload Reify
Presenting simplified components
Smart GWT components expose many methods and properties. For some environments, it is
more appropriate to provide a simplified list of properties, events, and actions on either
built-in Smart GWT components or your custom components. This can be done by providing a
component schema for an existing
component that exposes
your minimal set. You also need to provide a trivial subclass of the class you're exposing
so that it can be instantiated.
For example, let's say you want to make a simplified button called EButton that exposes only the 'title' property and the 'click' event of a standard Button. The following steps will accomplish this:
1. Edit /tools/visualBuilder/customComponents.xml and add a block similar to the following to make your custom component appear in the Component Library:
<PaletteNode> <title>EButton</title> <type>EButton</type> <icon>button.gif</icon> </PaletteNode>2. Next, create a custom schema: /isomorphic/system/schema/EButton.ds.xml as follows:
<DataSource ID="EButton" inheritsFrom="Button" Constructor="EButton" showLocalFieldsOnly="true" showSuperClassActions="false" showSuperClassEvents="false"> <fields> <field name="title" type="HTML"/> </fields> <methods> <method name="click"> <description>Fires when this button is clicked.</description> </method> </methods> </DataSource>See documentation above and also
component schemafor what the properties above do.
3. Finally, you'll need to define an EButton class as a simple subclass of Button, as follows: