|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
IPropertyProvider | |
ISession | |
IValueBean | |
IValueBeanList | |
IValueBeanTable |
Class Summary | |
---|---|
AbstractWidget | |
Admin | |
Application | |
Constants | For now all these magic constants are collected here. |
Driver | |
DynamideEvaluationExceptionHandler | |
DynamideFilter | |
DynamideHandler | |
DynamideObject | The base class for all Objects that would normally descend from java.lang.Object. |
DynamideServlet | |
Field | |
HandlerResult | |
JDOMFile | |
JDOMTest | |
Page | See how the WidgetType class is used for Page default properties, and look at the class javadoc for Widget. |
Persistent | |
Property | This class handles reading of XML properties that are embedded in XML files for Widget and Page (and, in theory, Session). |
Session | This class manages the user interaction across Page objects, and is the Java-side representation of the application.xml file, which has the page list, page order, and the application-level events. |
Session.ErrorURI | |
SessionLite | This class stands in place of a real session when things need to be expanded from a static page context. |
SessionWebMacroLogTarget | |
TestServlet | |
Widget | Runtime object representing a Widget. |
WidgetType | Each widget type, represented by the WidgetType class, corresponds to an xml file, called something like com.dynamide.button (which may be physically stored as com.dynamide.button.xml), which defines the type. |
XMLWidgetOutputter |
Exception Summary | |
---|---|
ApplicationNotFoundException | |
DynamideException | |
PageLoadException | |
SessionBusyException | |
TemplateSyntaxException | |
XMLFormatException |
Error Summary | |
---|---|
DynamideLoggedException | |
DynamideUncaughtException |
The core of the Dynamide Framework: Session, Widget, Page, Property, etc. To build a web application in Dynamide, you create Application, Session Widget, Page and Property entities. The classes in this package represent the runtime version of those objects. Using the Dynamide API, you can manipulate all of these entities in memory, and, if you have permission, cause each entity to persist itself to a resource (such as an XML file on disk). The entities can be created entirely from the API. There are Beanshell scripts to show how this is done in the scripts directory of the distribution, and there is a DHTML Integrated Development Environment (IDE) that runs on an Internet Explorer client and manipulates the API on a remote server. This is a Dynamide application, called "ide", and, if available on your installation, is accessible via the URI /dynamide/ide . There is also a Java Swing GUI (in the com.dynamide.gui package) that manipulates the API, but it is under development.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |