Hello, You can find here [1] a tutorial about implementing a new action. In order to add a new toolbar you have to listen for the "sync.api.Workspace.EventType.BEFORE_EDITOR_LOADED" event [2] and modify the "actionsConfiguration" field of the event to match the desired structure ...

We are going to make this change in the next version of oXygen XML Web Author. If you want this functionality in 18.0 you will need to patch our WebDAV plugin available on GitHub [1] and install it in Web Author [2]. You will have to use webdav-http instead of http when passing the URL to the Web Au...

Hello, To be sure I understand your context: you are using oXygen XML Web Author 18.0.0 (as part of the SDK) and using the "http" or "webdav" protocol to load and save document. Right? In Web Author we currently ignore the server response on HTTP requests since sometimes it conta...

Hello, Thanks for sharing your solution! A solution which in essence is the same as yours, but is intended to be used from a plugin.js file and which uses uses only the API is the following: goog.events.listen(workspace, sync.api.Workspace.EventType.EDITOR_LOADED, function(e) { setInterval(function(...

Hello,

We released the SDK project version 17.1.0.4. It contains the fix for the smart quotes problem.

You can use it by changing the oxygen.sdk.version in the pom.xml of your SDK project to 17.1.0.4. After that you should rebuild the SDK project.

Best,
Cristian

Hello, Regarding the first issue with the "autosave" option. I confirm that it is not currently supported in Web Author. It is on our priority list, but since the 18.0 release will be out very soon I cannot promise it may be postponed for the next version. Regarding the smart quotes issue,...

Hello, You'll have to annotate and re-compile only your custom operations. This annotation is intended to tell us whether the actions are webapp-compatible or not. For example, if you show a swing dialog while performing one of the operations, it will not work in webapp, so you may want to disable t...

Hello, One possible cause is that your custom actions use custom Java operations. These Java operations need to be annotated with @WebappCompatible in order to be used in WebApp. More details here [1]. If you added some JS code to your framework, it may help looking for errors in the browser console...

Hello, The problem with 16.1 is that it does not have a toolbar and context menu. These are features we added in 17.0. Anyway, I don't see any problems in having an extension for oXygen Eclipse plugin 16.1 and one for oXygen XML WebApp 17.0 - you can still reuse a lot of code between them. The Java ...

Hello, oXygen XML WebApp can be customized using plugins [1] which have the same format as oXygen Standalone plugins. They are similar but different from Eclipse plugins. In order to add libraries to the classpath you can check the "Referencing Libraries" section here [2]. The GUI of the c...

Hello, Regarding the oXygen Author WebApp support for text mode, as Alex said, a full-featured Text mode is not a priority for us right now. However, we plan to support an Author-mode action that is available when you right-click an XML element (e.g. paragraph, section, etc.) and edits its content i...

Hello Frank, Thanks for taking time to try our WebApp product. It seems you managed to do the hard part - building the oxygen-sdk-sample-webapp.war file. The deployment is not detailed in the documentation because is very sever-specific. For Tomcat, you basically have to drop the war file in the web...

Hello, First of all please make sure that the "options.xml" and "application.layout" are not inside the "template" folder; they should be next to it. Secondly, I noticed a bug in our SDK. The options.xml and application.layout and the template folder don't get included ...

Hello, The error you are getting seems to be related to network connectivity. Maven requires an Internet connection in order to download the archetype from the Maven central repository. In order to troubleshoot the networking problem please check the following things: - The <proxy> tag should be add...

Hello, In order to integrate with the oXygen Eclipse plugin you should develop another Eclipse plugin which communicates with the oXygen plugin. You have to declare a dependency between your plugin and the oXygen plugin by adding a "Require-Bundle: com.oxygenxml.editor" entry in your MANIF...

Hello, Starting from version 16.0, oXygen provides the SDK as a Maven archetype. You can use it to create projects for any kind of oXygen customization including plugins for the standalone distribution, plugins Eclipse IDE integration, frameworks. More details about all kinds of customizations can b...