Frequently Asked Questions

Installation and Licensing

What hosting options are available for applet delivery and licensing services (for example, Apache, IIS, etc.)?
For applet delivery any web server. We currently use Apache to deploy the sample on our site. For the floating license server you would need a J2EE server, like Tomcat if you want to restrict the access to the licenses.

If you do not need the access restrictions that are possible with a J2EE server you can simplify the deployment of the floating license server by using the standalone version of this server. The standalone license server is a simple Java application that communicates with the Author Componentby TCP/IP connections.
Are there any client requirements beyond the Java VM and (browser) Java Plug-In Technology?
Oracle (formerly Sun) Java JRE version 1.6 update 10 or newer. At least 200 MB disk space and 200MB free memory would be necessary for the Author Component applet.
Are there any other client requirements or concerns that could make deployment troublesome (for example, browser security settings, client-side firewalls, and AV engines)?
The applet is signed and will request access to the user machine, in order to store customization data (frameworks). The applet needs to be signed by you with a valid certificate.
How sensitive is the applet to the automatic Java VM updates, which are typically on by default (for example, could automatic updates potentially "break" the run-time)?
The component should work well with newer Java versions but we cannot guarantee this.
How and when are "project" related files deployed to the client (for example, applet code, DTD, styling files, customizations, etc.)?
Framework files are downloaded on the first load of the applet. Subsequent loads will re-use the cached customization files and will be much faster.
For on-line demo (http://www.oxygenxml.com/demo/AuthorDemoApplet/author-component-dita.html), noted a significant wait during initial startup. Any other mechanisms to enhance startup time?
See the explanation above.
Does the Author Component support multiple documents being open simultaneously? What are the licensing ramifications?
A single AuthorComponentFactory instance can create multiple EditorComponentProvider editors which can then be added and managed by the developer who is customizing the component in a Swing JTabbedPane. A single license (floating or user-based) is enough for this.

If you need to run multiple Java Applets or distinct Java processes using the Author Component, the current floating license model allows for now only two concurrent components from the same computer when using the license servlet. An additional started component will take an extra license seat.
Is there any internet traffic during an editing session (user actively working on the content, on the client side, in the Author Component)?
No.

Functionality

How and when are saves performed back to the hosting server?
What you can see on our web site is just an example of the Author Component (which is a Java Swing component) used in an Applet.

This applet is just for demonstration purposes. It's source can be at most a starting point for a customization. You should implement, sign and deploy your custom applet implementation.

The save operation could be implemented either in JavaScript by requesting the XML content from the Applet or in Java directly working with the Author Component. You would be responsible to send the content back to the CMS.
Is there a particular XML document size (or range) when the applet would start to exhibit performance problems?
The applet has a total amount of used memory specified in the JNLP JavaWebstart configuration file which can be increased if necessary. By default it is 156 Mb. It should work comfortably with documents of 1-3 megabytes.
What graphic formats can be directly rendered in the Author Component?
GIF, JPEG, PNG, BMP and SVG.
Can links be embedded to retrieve (from the server) and "play" other types of digital assets, such as audio or video files?
You could add listeners to intercept clicks and open the clicked links. This would require a good knowledge of the oXygen SDK. The Author Component can only render static images (no GIF animations).
Does the Author Component provide methods for uploading ancillary files (new graphics, for instance) to the hosting server?
No.
Does the Author Component provide any type of autosave functionality?
By default no but you could customize the applet that contains the Author Component to save its content periodically to a file on disk.
Assuming multiple documents can be edited simultaneously, can content be copied, cut and pasted from one Author Component "instance" to another?
Yes.
Does the Author Component support pasting content from external sources (such as a web page or a Microsoft Word document and, if so, to what extent?
If no customizations are available the content is pasted as simple text. We provide customizations for the major frameworks (DITA, DocBook, TEI, etc.) which use a conversion XSLT stylesheet to convert HTML content from clipboard to the target XML.
Can UTF-8 characters (such as Greeks, mathematical symbols, etc.) be inserted and rendered?
Any UTF-8 character can be inserted and rendered provided that the font used for editing supports rendering the characters. The font can be changed by the developers but not by the users. When using a logical font (which by default is Serif for the Author Component) the JVM will know how to map all characters to glyphs. There is no character map available but you could implement one

Customization

Please describe, in very general terms, the menus, toolbars, contextual menu options, helper panes, and so on, that are available for the Author Component out-of-the box.
You can mount on your custom toolbar all actions available in the standalone Oxygen XML Editor application for editing in the Author mode. This includes custom actions defined in the framework customized for each XML type.

The Author Component also can provide the Outline, Model, Elements, and Attributes views which can be added to your own panels (see sample applet).
Please describe, in general terms, the actions, project resources (for example, DTD/Schema for validation purposes, CSS/XSL for styling, etc.) and typical level of effort that would be required to deploy a Author Component solution for a customer with a proprietary DTD.
The Author mode internal engine uses CSS to render XML.

For a special type of XML you can create a custom framework (which also works in an Oxygen XML Editor standalone version) which would also contain default schemas and custom actions. A simple framework would probably need 2-3 weeks development time. For a complex framework with many custom actions it could take a couple of months. Oxygen XML Editor already has frameworks for editing (DocBook, DITA, TEI, etc.) Sources for them are available in the Oxygen SDK.

More than one framework can coexist in the same Oxygen XML Editor instance (the desktop standalone version or the applet version) and can be used at the same time for editing XML documents.
Many customers desire a very simplistic interface for contributors (with little or no XML expertise) but a more robust XML editing environment for editors (or other users with more advanced XML expertise). How well does the Author Component support varying degrees of user interface complexity and capability?
- Showing/hiding menus, toolbars, helpers, etc.
  All the UI parts from the Author Component are assembled by you. You could provide two applet implementations: one for advanced/power users and one for technical authors.
- Forcing behaviors (for example, ensuring change tracking is on and preventing it from being shut down)
  You could avoid placing the change tracking toolbar actions in the custom applet. You could also use API to turn change tracking ON when the content has been loaded.
- Preventing access to "privileged" editor processes (for example, accept/reject changes)
  You can remove the change tracking actions completely in a custom applet implementation. Including the ones from the contextual menu.
- Presenting and/or describing XML constructs (for example, tags) in "plain-English"
  Using our API you can customize what the Outline or Breadcrumb presents for each XML tag. You can also customize the in-place content completion list.
- Presenting a small subset of the overall XML tag set (rather than the full tag set) for use by contributors (for example, allowing an author to only insert Heading, Para and inline emphasis) Could varying "interfaces", with different mixes these capabilities and customizations, be developed and pushed to the user based on a "role" or a similar construct?
  The API allows for a content completion filter which also affects the Elements view.
Does the Author Component API provide access to the XML document, for manipulation purposes, using common XML syntax (such as DOM, XPath, etc.)?
Yes, using the Author Component API.
Can custom dialog boxes be developed and launched to collect information in a "form" (with scripting behind to push tag the collection information and embed it in the XML document?
Yes.
Can project resources, customizations, etc. be readily shared between the desktop and component versions of your Author Component product line?
A framework developed for the desktop version of the Oxygen XML Editor application can then be bundled with the Author Component in a custom applet. For example, the demo applet from our web site is DITA-aware using the same framework as the Oxygen XML Editor standalone distribution.

A custom version of the applet that includes one or more customized frameworks and user options can be built and deployed for non-technical authors by a technical savvy user using a built-in tool of Oxygen XML Editor. All the authors that load the deployed applet from the same server location will share the same frameworks and options.

A custom editing solution can deploy one or more frameworks that can be used at the same time.