public interface LoadingOptionalModules
If your Smart GWT install includes an optional module, it must be added as an <inherits> tag in your moduleName.gwt.xml module file for it to be used. Some optional modules require an additional .jar file (eg analytics.jar), whereas some are bundled in smartgwt.jar automatically. Where applicable, additional module .jar files are included in Evaluation SDKs but are separate downloads when using an Optional Module with Power or Enterprise. The table below describes what <inherits> to add for each module.
| Module | Add this to your .gwt.xml file |
Drawing (included in smartgwt.jar)Required for DrawPane and DrawItem.
|
<inherits name="com.smartgwt.Drawing"/> |
PluginBridges (included in smartgwt.jar)Required for all BrowserPlugin derivatives (such as
LoadingOptionalModules.Applet and Flashlet) and
also for FusionChart support.
|
<inherits name="com.smartgwt.PluginBridgesWidgets"/> |
Charts (included in smartgwt.jar)Required for FacetChart and FusionChart.
Note that FacetChart also requires the
Drawing module to be loaded
before this module.
Note that FusionChart also requires the PluginBridges module to be
loaded before this module.
|
<inherits name="com.smartgwt.Charts"/> |
Analytics (requires analytics.jar)See CubeGrid. Note that if charting is also required,
the Charts
module should be loaded before this one. |
<inherits name="com.smartgwt.Analytics"/> |
RealtimeMessaging (requires messaging.jar) |
<inherits name="com.smartgwt.RealtimeMessaging"/> |
Workflow (included in smartgwt.jar)Required for Process. The ability to define a
workflow in XML is Pro+ only, in LGPL
the workflow engine can only be used programmatically.
|
<inherits name="com.smartgwt.Workflow"/> |
SmartGwtTools (included in smartgwt.jar)Required for the developer console. Imports
/development
Framework, including the tools module. This module should always be listed before the
SmartGwtXXX module and any other modules from above in your moduleName.gwt.xml file.
Note that the developer console has minor functionality issues unless Enterprise skin is used, so by default inheriting the SmartGwtToolsmodule pulls it in. Using SmartGwtToolsNoThemeinstead will cause the developer console to pick up the skin used by your project. |
<inherits name="com.smartgwt.tools.SmartGwtTools"/> |
Tools (included in smartgwt.jar)Required for DevTools. This module should always be listed
after any
other modules from above in your moduleName.gwt.xml file.
Using these tools to edit hierarchies of Smart GWT components and generate Component XML for them also requires the system schema to be loaded. JSP tag: <script><isomorphic:loadSystemSchema /></script> HTML tag: <SCRIPT SRC="../isomorphic/DataSourceLoader?dataSource=$systemSchema"> </SCRIPT>Certain SGWT Pro/Power/Enterprise tools pulled in by the com.smartgwtee.tools.Toolsmodule may require tool skin resources: <inherits name="com.smartclientee.toolskin.ToolSkinResources"/> <inherits name="com.smartclientee.toolskinnative.ToolSkinNativeResources"/> VisualBuilder requires inheriting Tahoe Resources:
<inherits name="com.smartclient.theme.tahoe.TahoeResources"/>See the Skinning help topic for an overview.
|
<inherits name="com.smartgwt.Tools"/> (imports "first class" tools module under /modules) <inherits name="com.smartgwtee.tools.Tools"/> (imports SGWT Pro/Power/Enterprise Edition tools) |