http://blog.gmane.org/gmane.editors.oxygen.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.editors.oxygen.user/2900 <pre>Hi Radu, Thanks for your prompt and constructive response. Yes that type of interface would work for us. A couple of alternative API's for your consideration would be: (1) newEditor(String extension); (2) newEditor(String extension, Reader reader); Alternative (1) would create a new editor with an empty document and alternative (2) would create a new editor with a document being read from the reader. In the case of the plugin I am currently developing, I would use whatever interface that might be provided in the future to create a new editor whose 'final' content was read in from a reader. Here, 'final' is used to represent the content shown to the user after the plugin has completed its output. Thanks again, Anthony. </pre> Michael Smith 2010-11-03T13:56:51 http://permalink.gmane.org/gmane.editors.oxygen.user/2899 <pre>Hi Michael, See some answers below: On 11/3/2010 12:33 PM, Michael Smith wrote: Yes, just use the ro.sync.exml.workspace.api.Workspace.open(URL url); method. Oxygen cannot open an URL twice inside it so calling the method on an URL which is already opened will result in the editor tab getting selected. This cannot be done using the current API for now. So you would like something like: newEditor(String extension, String xmlContent); Is this right? Maybe we can improve the API to contain such a method in a future version. Regards, Radu Radu Coravu &lt;oXygen/&gt; XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com </pre> Radu Coravu 2010-11-03T12:21:51 http://permalink.gmane.org/gmane.editors.oxygen.user/2898 <pre>Hello, I have recently been developing a standalone oXygen 12.0 workspace plugin that produces an XML document containing oXygen's track-change processing instructions. Currently this plugin can write its results either to an existing editor or to a file. In the latter case the file is opened in an oXygen editor once it has been written. In the former case, the editor is correctly updated but not selected as the current editor. Is there a way of selecting this output editor as the current editor from within the plugin? I would also like to allow the user to send the output to a "new" freshly constructed editor window with an appropriate "untitled #number" name, where the action of "saving" the document would prompt the user for the location to save the file in. There may be cases where the user just wants to view the result, rather than save it to a file. We generally know the type of document that is being generated (e.g. DITA, DocBook, general XML) so could supply this to the oXygen editor creation API, if this is helpful. Any pointers on how this - or something similar - could be achieved would be welcome. I am new to the oXygen plugin development and this mailing list; and have done my best to search both the API and archive for answers to the issues I have just raised. I apologise in advance for missing previous answers to these questions. Regards, Anthony. </pre> Michael Smith 2010-11-03T10:33:15 http://permalink.gmane.org/gmane.editors.oxygen.user/2897 <pre>Ni Nigel, You're right about the first issue, resolvePathThroughCatalogs does not resolve public IDs, so better try the solution suggested below: Indeed, the XMLUtilAccess.newNonValidatingXMLReader() returns an XML Reader which already has an entity resolver set up through the Oxygen catalogs. So as alternatives either you can use our XML Reader to parse resources or create an XML reader through our code and then do a XMLReader.getEntityResolver() on it to access the Entity Resolver set to it on our side. I will add as a feature request the possibility to get an EntityResolver or an URIResolver through our API. Regards, Radu Radu Coravu &lt;oXygen/&gt; XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 10/29/2010 6:32 PM, Nigel Whitaker wrote: </pre> Radu Coravu 2010-11-01T06:59:41 http://permalink.gmane.org/gmane.editors.oxygen.user/2896 <pre>Hi Radu, Thanks for your quick answer. The catalog behaviour background info was very useful. We're still trying to work out the best way of using it: Radu Coravu wrote: ... If we try to plug resolvePathThroughCatalogs into: InputSource org.xml.sax.EntityResolver.resolve(String publicId, String systemId) and then configure our parser with .setEntityResolver(), then wouldn't we be loosing the ability to do catalog resolving based on the publicId of editors/files? Alternatively, would the XMLUtilAccess.newNonValidatingXMLReader() method return an XMLReader already configured with the resolver and the framework/user/default catalogs you described? Thanks, Nigel </pre> Nigel Whitaker 2010-10-29T15:32:04 http://permalink.gmane.org/gmane.editors.oxygen.user/2895 <pre>Hi Nigel, Anthony, Oxygen has a single Catalog Resolver and all catalogs are added to it (catalogs from each document type + user defined catalogs + Oxygen default catalog file). So even if a document type contributes only with 2-3 catalogs files, the associated editor will be validated/processed by Oxygen using all catalogs. Indeed conflicts may appear but the user can disable individual document types, thus removing their list of catalogs from the Catalog Resolver. My suggestion for you is to use XMLUtilAccess.resolvePathThroughCatalogs() because besides some very little extra tests that's just what it does, it questions the EntityResolver or the URIResolver (depending on the paramters it receives) to resolve the reference. Regards, Radu Radu Coravu &lt;oXygen/&gt; XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 10/29/2010 5:22 PM, Nigel Whitaker wrote: </pre> Radu Coravu 2010-10-29T14:44:26 http://permalink.gmane.org/gmane.editors.oxygen.user/2894 <pre>Hello, We're developing a workspace plugin which reads form either existing editors or on-disk files. We're using all the catalogs in the standard 12.0 release using this rather brute-force approach: &lt;configProperty name="cat_dita" value="${install.dir}/../../../frameworks/dita/catalog.xml" /&gt; &lt;configProperty name="cat_docbook" value="${install.dir}/../../../frameworks/docbook/catalog.xml" /&gt; ... &lt;configProperty name="cat_xmlspec" value="${install.dir}/../../../frameworks/xmlspec/catalog.xml" /&gt; &lt;configProperty name="xml.catalog.files" value="${cat_dita};${cat_docbook};...${cat_xmlspec}" /&gt; However, we dont know about any user defined frameworks. Is there a way of knowing the framework associations of editors/files so that we could use the specific catalog file (also reducing the possibility of conflicts between the catalogs). Alternatively access to a URI/Entity resolver appropriate for the type of file which we could use when parsing (xerces) may be useful. We know about XMLUtilAccess and its resolvePathThroughCatalogs method, but we'd like something we can use with the resolver/xerces directly. We've also seen some references to a 'grammarCache' object but are unsure how to use it. Is there something we can use to improve our catalog handling. Many thanks, Nigel &amp; Anthony (working on a comparison plugin) </pre> Nigel Whitaker 2010-10-29T14:22:14 http://permalink.gmane.org/gmane.editors.oxygen.user/2893 <pre>Hi Bill, If you can't install Oxygen from the Eclipse update site, please download the appropriate zip distribution for your Eclipse version. You can find it here: Editor: http://www.oxygenxml.com/download_oxygenxml_editor.html (Eclipse tab) Author: http://www.oxygenxml.com/download_oxygenxml_author.html (Eclipse tab) After downloading the zip, unpack it in the Eclipse dropins folder and start Eclipse with the "-clean" command line argument. Regards, Adrian Bill wrote: </pre> Adrian Buza 2010-10-29T11:14:32 http://permalink.gmane.org/gmane.editors.oxygen.user/2892 <pre>Hi Ted -- I'm having the same problem (on Windows). Have you figured this out yet? I've wasted a lot of time because of this. It's maddening! </pre> Bill 2010-10-28T19:44:55 http://permalink.gmane.org/gmane.editors.oxygen.user/2891 <pre>oXygen XML Author 12.0.0.v201010011 is the latest build of the Author plugin. So you can keep that. If you unpacked the zip file in the Eclipse dropins folder then you won't be able to uninstall it from the Installed Software window. You also won't be able to update it from the Eclipse update site. In the future you will have to manually delete it from the dropins and download and unpack a new version there. If all else fails, simply delete and redeploy Eclipse from scratch. In the future avoid deleting from the file system plugins that have been installed from Eclipse update sites. Eclipse also keeps an install history of the plugins installed from update sites so you can quickly revert to a previous version. Regards, Adrian Ted Kuster wrote: </pre> Adrian Buza 2010-10-28T14:29:56 http://permalink.gmane.org/gmane.editors.oxygen.user/2890 <pre>Thanks, Adrian. I put the plugin back (via the file system) and got Oxygen working normally again. Then I tried the uninstall routine that you described. When I click Unininstall, the Installed Software window flashes briefly and then closes. Nothing else appears to happen. The plugin is still there. I should note that the Installed Software list shows two different Oxygen plugins (neither of which I can uninstall): This one: oXygen XML Author12.0.0.v2010100114com.oxygenxml.author.feature.group And this one: oXygen XML Editor and XSLT Debugger11.2.0.v2010090711 com.oxygenxml.editor.feature.group On 10/27/2010 06:27 AM, Adrian Buza wrote: </pre> Ted Kuster 2010-10-27T18:58:11 http://permalink.gmane.org/gmane.editors.oxygen.user/2889 <pre>Hello, You probably installed Oxygen via the Eclipse update site but afterwards removed it directly from the file system without uninstalling it. As a result Eclipse still believes it's installed. Try to uninstall Oxygen from Help -&gt; About -&gt; Installation Details, Installed Software. Then try again to install it from the update site. If this doesn't work, you can download the appropriate Eclipse plugin zip distribution from the web site: http://www.oxygenxml.com/download_oxygenxml_author.html (Eclipse tab) and unpack the zip file in the Eclipse dropins folder. Regards, Adrian Adrian Buza oXygen XML Editor and Author support support-xj0E2L9sap8S+FvcfC7Uqw&lt; at &gt;public.gmane.org http://www.oxygenxml.com Ted Kuster wrote: </pre> Adrian Buza 2010-10-27T13:27:37 http://permalink.gmane.org/gmane.editors.oxygen.user/2888 <pre>Hello, Apple has marked as deprecated their Java Virtual Machine (JVM) implementation. This means that starting with the next version of Mac OS X 10.7, this JVM may be removed [on Mac OS X 10.5 and 10.6 Java will remain built-in]. Starting with Mac OS X 10.7 all Java applications will most likely have to use another third party JVM. Unfortunately, at this time, no other JVM has a user interface integration in the operating system anywhere as good as the one currently offered by Apple. Current situation: oXygen has two distributions: - the standalone AWT/Swing application - the SWT plugin for Eclipse. AWT/Swing based applications like Netbeans, JDeveloper and the standalone version of oXygen, will all be affected. The result will be a user interface that is not smoothly integrated in the Mac look and feel, and possibly the entire application being displayed using the X Window System. Eclipse has the nice feature of using native user interface controls on each platform, directly, without the need of AWT. So, an application using SWT will look and perform exactly the same, no matter the JVM it uses. What we can do: 1. If no JVM rises to the challenge of implementing AWT/Swing support with the appropriate Mac look and feel, we'll pack a stripped down version of Eclipse (called a Rich Client Platform) with the oXygen XML Editor plugin and the OpenJDK JVM. This has already been tested and works on the current Mac OS X operating systems independent from the Apple JVM. This may very well be the new oXygen distribution for Mac OS X 10.7. 2. If things go as they should, Oracle will pick up where Apple left off and will provide a JVM for the Mac, with full AWT/Swing integration. In this case, the standalone oXygen distribution will continue its existence on the Mac OS X platform in its current form, possibly with the JVM built-in to make it work out-of-the-box. So, unless Apple completely closes Mac OS X to Java applications, which is very unlikely, Oxygen will continue to have a Mac OS X distribution that integrates as well as possible with the operating system and its graphical interface. Regards, Adrian Adrian Buza oXygen XML Editor and Author support support-xj0E2L9sap8S+FvcfC7Uqw&lt; at &gt;public.gmane.org http://www.oxygenxml.com Roger wrote: </pre> Adrian Buza 2010-10-27T13:11:33 http://permalink.gmane.org/gmane.editors.oxygen.user/2887 <pre>Dear oXygen Users, Apple recently announced that future versions of Mac OS X may no longer include a Java runtime: &lt;http://developer.apple.com/library/mac/#releasenotes/Java/JavaSnowLeopardUpdate3LeopardUpdate8RN/NewandNoteworthy/NewandNoteworthy.html%23//apple_ref/doc/uid/TP40010380-CH4-SW1&gt; Any idea what that will mean for the future of Java-based apps like oXygen? Will a Mac version of oXygen bring its own JRE, or will we need to download one from somewhere else to run oXygen? I know it's a long way off, but just curious what this announcement will mean... Roger </pre> Roger 2010-10-26T22:00:54 http://permalink.gmane.org/gmane.editors.oxygen.user/2886 <pre>I need to reinstall Oxygen Author 12, in Eclipse 3.5.2 on Ubuntu 10.4. I have completely cleaned any traces of Oxygen from my Eclipse installation --a file search reveals no files with any form of the string "oxygen" anywhere in the file system. I have restarted Eclipse with the -clean option. No Oxygen-related options or settings are available anywhere in the Eclipse UI. However, when I try to use Help &gt; Install New Software to install Oxygen, Eclipse refuses on the grounds that Oxygen is already installed. What am I doing wrong? </pre> Ted Kuster 2010-10-26T18:40:58 http://permalink.gmane.org/gmane.editors.oxygen.user/2885 <pre>Hi, Thank you for the feedback. I've added an improvement request on our issue tracking tool to allow the user to hide that bar. This will be analyzed and if found appropriate will be implemented in a future version of Oxygen. Regards, Adrian Adrian Buza oXygen XML Editor and Author support support-xj0E2L9sap8S+FvcfC7Uqw&lt; at &gt;public.gmane.org http://www.oxygenxml.com Shannon wrote: </pre> Adrian Buza 2010-10-26T11:48:41 http://permalink.gmane.org/gmane.editors.oxygen.user/2884 <pre>Hello, The XDBC configuration from the MarkLogic connection is used for the transformation/debugging engine. This seems to work fine from your description. However in the Data Source Explorer it is used the WebDAV URL from the MarkLogic connection with the same user and password as the ones for the XDBC host. This URL has to point to a WebDAV server(not XDBC) configured on the MarkLogic server. Regards, Adrian Adrian Buza oXygen XML Editor and Author support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support-xj0E2L9sap8S+FvcfC7Uqw&lt; at &gt;public.gmane.org http://www.oxygenxml.com Shannon wrote: &gt; </pre> Adrian Buza 2010-10-25T14:25:46 http://permalink.gmane.org/gmane.editors.oxygen.user/2883 <pre>Hi, please consider giving the user the option to hide the Text/Grid/Author controls to increase available space to the editor. I often use a tiny screen on a notebook and have configured a minimal layout--no toolbars or panels whatsoever--; since I never change the view, I'd like to get rid of those buttons too. Thanks, Shannon </pre> Shannon 2010-10-22T22:24:27 http://permalink.gmane.org/gmane.editors.oxygen.user/2882 <pre>Hello, I searched the site and mailing list archive for this error with no results. In the XML Databases perspective, the Data Source Explorer panel returns, "Error: Invalid authority" when I attempt to explore by expanding any one of the Connections, after briefly showing, "Pending…"--these are the same Connections that execute successfully in every other perspective for transforming, querying, and debugging. The Database Source is type MarkLogic. Running Oxygen 11.2 on OS X 10.6.4. Please let me know if you need more information, or what I am doing wrong, thanks, Shannon </pre> Shannon 2010-10-22T15:20:26 http://permalink.gmane.org/gmane.editors.oxygen.user/2883 <pre>Hi, please consider giving the user the option to hide the Text/Grid/Author controls to increase available space to the editor. I often use a tiny screen on a notebook and have configured a minimal layout--no toolbars or panels whatsoever--; since I never change the view, I'd like to get rid of those buttons too. Thanks, Shannon </pre> Shannon 2010-10-22T22:24:27 http://permalink.gmane.org/gmane.editors.oxygen.user/2882 <pre>Hello, I searched the site and mailing list archive for this error with no results. In the XML Databases perspective, the Data Source Explorer panel returns, "Error: Invalid authority" when I attempt to explore by expanding any one of the Connections, after briefly showing, "Pending…"--these are the same Connections that execute successfully in every other perspective for transforming, querying, and debugging. The Database Source is type MarkLogic. Running Oxygen 11.2 on OS X 10.6.4. Please let me know if you need more information, or what I am doing wrong, thanks, Shannon </pre> Shannon 2010-10-22T15:20:26 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.editors.oxygen.user