Package smacs.xngr

Xngr derivate - an Xml browser component.

See:
Description

Interface Summary

XAction	The action specifies different ways of using an element.
XDecorator	Describes the presentation of a XElement.
XDocument	The representation of a document for the xngr application.
XDocumentListener	This interface needs to be implemented to be able to listen to specific Document events.
XElement	The interface that represents an XML element in the eXchaNGeR application.
XFactory	Factory methods that allow for document and element creation.
XManager	The Manager allows services to interact with other services and returns handles to available documents and elements.

Class Summary

XDocumentEvent	The event that is fired to a document listener when the document has been saved, changed or deleted.
XElementType	Represents an element-type in the system.
XProperties	The class that can be used by the service to set properties.
XService	The representation of a service in the system.
XUrl	The representaion of a URL in the Xngr system.
XUtilities	Utilities methods for the Xngr application.

Package smacs.xngr Description

Xngr derivate - an Xml browser component.

why and what

I had to notice that the xngr explorer is not a reusable component based on the interfaces exposed in smacs.xngr.* - instead we have a lot of intances where the parts are based on ExchangeElement.

The subdirectories rebuild the exchanger view based on our own smacs.tree.SimpleNode - allowing us to push in specialized actions for the smacs trees. However we let each of the service be still based on smacs.xngr.* interfaces - no need to duplicate.

effectivly...

Hopefully that will allow us to load xngr services based solely on the xngr exported interfaces. From the past experiences with xngr this is very unlikely but I do expect that cooperation with the xngr author will bring about changes to get at a good degree of portability of xngr plugin services.

atleast we want to see our SqlTree* services be loadable to both the plain xngr explorer and our derivate. This can be achieved by having an "instanceof SimpleNode" check on the XElements given to the XService implementation and providing a fallback implemen- tation for the "alien" (and still dom4j derived) nodetype case.