- oXygen-user - www.oxygenxml.com

Plugin testing.
by Michael Anthony Smith 04 Mar '11

04 Mar '11

Our plugin is now nearing 'feature' completion, and I am in the process of automating the manual testing. This is reasonably straightforward for those aspects of the plugin that are independent of the oXygen API, as these can be run through our TestNG framework. I was wondering if anybody had some suggestions for how to automate tests involving the use of the oXygen API (and GUI components). For example is there a mechanism to simulate the selection of windows, menu items, button presses, etc in oXygen, that could be provided as an argument to a command-line invocation? Any suggestions welcome. Regards, Anthony. -- -- ------------------------------------------------------------------------- Michael Anthony Smith, DeltaXML Ltd "Change control for XML" T: +44 1684 578751 E: anthony.smith(a)deltaxml.com http://www.deltaxml.com Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK

2 1

Feedback on experimental plugin features.
by Michael Anthony Smith 04 Mar '11

04 Mar '11

I have now made use of four of the experimental oXygen plugin workspace API options (on a Mac running OS X - Snow Leopard) : (1) getOptionsStorage - This has a straightforaward interface, which worked as expected. (2) createNewEditor - This was slightly more awkward to use in our plugin's context (more details below). (3) getEntityResolver - Works as expected (thanks). (4) getURIResolver - Appears to works as expected (but currently, not tested). I have managed to get the 'createNewEditor' API call to create a fresh document that is considered to be modified, using the following code: Writer writer = new StringWriter(); ... // Write to the string. ... URL url= workspace.createNewEditor("xml", "text/xml", writer.toString()); WSEditor ed=workspace.getEditorAccess(url, StandalonePluginWorkspace.MAIN_EDITING_AREA); ed.setModified(true); Observations: (1) This approach may be problematic for big documents, as the whole document is stored in a string. (2) The created document is not marked as modified. There are at least two ways of addressing the first of these points. One approach is to create a small blank document that is then overridden using the WSEditod's realoadContent(Reader). Here, the question I had was: what is the minimal XML document that can be overridden (and get the right document type association - e.g. DITA)? It might be that oXygen could automatically create such a document from the first two arguments of the createNewEditor method. A second approach could be to replace the third argument of the createNewEditor method with a java.io.Reader argument, such as is used when reloading a document into an existing WSEditor (editor.reloadContent(reader)). Overall, I am pleased with these experimental enhancements. Regards, Anthony. -- -- ------------------------------------------------------------------------- Michael Anthony Smith, DeltaXML Ltd "Change control for XML" T: +44 1684 578751 E: anthony.smith(a)deltaxml.com http://www.deltaxml.com Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK

2 1

Cli guide using DITA
by Surya Prabha Vallae 25 Feb '11

25 Feb '11

Hi, I am writing a cli guide using dita and oxygen. When I generate the pdf of the cli guide, I see that: 1. Contents for the cli book are not generated. The cli guide has only bookmarks. 2. The cli page is flushed right leaving a large vertical empty column on the right of each page. From the looks I understand that this is part of the rendering style for a cli guide. But is there a way to change this? Because my content is overflowing to the right and some part of it is not even visible. Can some one help? Thanks in advance. Surya.

2 1

Grid/Author/Design tabs gray
by Lee, David 24 Feb '11

24 Feb '11

Oxygen 12.1 I'm re-animating my use of Oxygen and want to use the Design mode for XML and Schemas. I cant figure out how to turn them on ! When I load an XML or an XSD file it shows in "Text" mode, and the tabs at the bottom "Grid" , "Design" , "Author" stay gray. Any suggestions on how I can enable these ? ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com <mailto:dlee@epocrates.com> 812-482-5224

2 3

Re: [oXygen-user] Grid/Author/Design tabs gray - SOLVED
by Lee, David 24 Feb '11

24 Feb '11

OK Now I figured it out ! I needed to do "Open Perspective -> Editor" Now the Text/Grid/Author/Design tabs are active. Thanks ! ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com 812-482-5224 -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Lee, David Sent: Thursday, February 24, 2011 8:15 AM To: oXygen-user(a)oxygenxml.com Subject: Re: [oXygen-user] Grid/Author/Design tabs gray OK thanks. My underlying issue is I want to use the XSD Schema diagram , and I cannot find out how to invoke it. There's lots of docs about what to do with it *after* you invoke it but I can't figure out how to show it. ( I was *guessing* that the "Diagram" would show that) Also, I recall being able to enter "Author" mode on simple XML files (like Docbook). Is there no Tree and Authoring without running XQuery or XSLT ? I am editing an XML and an XSD file (Not an XSLT or XQuery file) I just now switched to both XSLT Debugging and XQuery debugging perspectives and the Grid, Author, Design tabs are still blank. Any suggestions ? ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. dlee(a)epocrates.com 812-482-5224 -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Sorin Ristache Sent: Thursday, February 24, 2011 8:09 AM To: oxygen-user(a)oxygenxml.com Subject: Re: [oXygen-user] Grid/Author/Design tabs gray Hello, The tabs at the bottom of the editing area should be gray (disabled) only in the XSLT Debugger perspective and the XQuery Debugger one. Just switch to the Editor perspective to enable them. Regards, Sorin Lee, David wrote: > > Oxygen 12.1 > > I'm re-animating my use of Oxygen and want to use the Design mode for > XML and Schemas. > > I cant figure out how to turn them on ! > > When I load an XML or an XSD file it shows in "Text" mode, and the > tabs at the bottom "Grid" , "Design" , "Author" stay gray. > > Any suggestions on how I can enable these ? > _______________________________________________ oXygen-user mailing list oXygen-user(a)oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user _______________________________________________ oXygen-user mailing list oXygen-user(a)oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user

2 1

Shortcut key expand all children
by Karl Stubsjoen 18 Feb '11

18 Feb '11

The shortcut key is suppose to be SHIFT + = but on my keyboard the = shares the key + and what I get is the font size changing in size. Is there an alternate shortcut key to expanding all children? -- Karl Stubsjoen MeetScoresOnline.com (602) 845-0006

2 1

problems with explicit type validation from Relax NG
by Tara Athan 14 Feb '11

14 Feb '11

Request Jing bug fix to allow validation of xs:simpleType elements with an xsi:type attribute I am working on a schema where there is a need for an element <BuiltInData> which holds a literal and allows validation against any built-in type, and otherwise has no attributes. Example (simplified)- <?xml version="1.0" encoding="UTF-8"?> <wrapper xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:noNamespaceSchemaLocation="BuiltInDataXSD.xsd"> <BuiltInData xsi:type="xs:nonNegativeInteger">123</BuiltInData> <BuiltInData xsi:type="xs:token">Maple St.</BuiltInData> <BuiltInData xsi:type="xs:date">2011-01-30</BuiltInData> <BuiltInData xsi:type="xs:Name">company:Employee</BuiltInData> </wrapper> The Relax NG compact schema is fairly straightforward start = element wrapper {BuiltInData.type+} BuiltInData.type = element BuiltInData { (xsd:duration | xsd:dateTime | xsd:time | xsd:date | xsd:gYearMonth | xsd:gYear | xsd:gMonthDay | xsd:gDay | xsd:gMonth | xsd:boolean | xsd:base64Binary | xsd:hexBinary | xsd:float | xsd:decimal | xsd:double | xsd:anyURI | xsd:QName | xsd:NOTATION | xsd:string) } which converts to the XSD <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="wrapper"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" ref="BuiltInData"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="BuiltInData"> <xs:simpleType> <xs:union memberTypes="xs:duration xs:dateTime xs:time xs:date xs:gYearMonth xs:gYear xs:gMonthDay xs:gDay xs:gMonth xs:boolean xs:base64Binary xs:hexBinary xs:float xs:decimal xs:double xs:anyURI xs:QName xs:QName xs:string"/> </xs:simpleType> </xs:element> </xs:schema> Now the problem is: if I try to validate the XML directly from the Relax NG schema, using oXygen, then I get an error. *** [Jing] found attribute "xsi:type", but no attributes allowed here.*** From my perspective at least, this is a bug in Jing because the XML is valid according to the XSD schema but not according to the supposedly equivalent Relax NG schema (there is no approximation warning upon conversion). I can modifed the Relax NG schema by declaring the attribute element BuiltInData { attribute xsi:type { text }?, ... but that messes up the conversion to XSD. I don't expect Jing to check that the literal matches the datatype, but it should at least ignore the xsi:type attribute, (or better - check that the type could be derived from the element's defined datatype.) So I have 4 options, in reverse order of preference: 1. give up on validation directly from the Relax NG schema 2. maintain two versions of the RNC schema, one for direct validation and one for conversion 3. find a method for validating against the Relax NG schema other than Jing in oXygen 4. request that the validator in oXygen be modified to allow validation of xs:simpleType elements with an xsi:type attribute So I'll start with #4 - any chance this can happen? Thanks, Tara

2 2

starts-with() match on @role in Schematron error reporting?
by Tony Graham 14 Feb '11

14 Feb '11

This message from 2009 describes what happens on Schematron validation: http://www.oxygenxml.com/pipermail/oxygen-user/2009-November/002902.html I couldn't find anything similar in the oXygen documentation. Is it in there? oXygen seems to match on exactly 'warning', etc., in @role, as the 2009 message suggests. However, I am currently working with a system that already has error identifiers along the lines of WARNING_BAD_THING and ERROR_WORSE_THING. I would like to be able to put those in assert/@role and report/@role because the @role values show up in both oXygen and SVRL even when the <assert> or <report> is in an abstract rule. (I.e., there's nothing in ISO Schematron SVRL for an abstract rule firing, but there is for its <assert>s and <report>s.) Is it possible to loosen the @role value matching to set the severity when @role starts with 'warning', etc., instead of matching on the whole @role value? Regards, Tony Graham Tony.Graham(a)MenteithConsulting.com Director W3C XSL FO SG Invited Expert Menteith Consulting Ltd XML Guild member XML, XSL and XSLT consulting, programming and training Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland Registered in Ireland - No. 428599 http://www.menteithconsulting.com -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- xmlroff XSL Formatter http://xmlroff.org xslide Emacs mode http://www.menteith.com/wiki/xslide Unicode: A Primer urn:isbn:0-7645-4625-2

2 2

Support for Tar Files in Archive Browser?
by Eliot Kimber 14 Feb '11

14 Feb '11

I noticed that TAR files are not supported in the archive browser. Would it be possible to add it? When I needed it I couldn't find the equivalent Java libraries for TAR as you have for Zip so I implemented my own Tar unpacker and direct entry reading library, which I can probably share (it wasn't a huge effort). I did not have a requirement to implement writing back to tar, which is probably the hard part. Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

3 3

Getting <oXygen/> to run Calabash to run Saxon with -dtd:off or with catalogs?
by Tony Graham 14 Feb '11

14 Feb '11

I have a XSLT 2.0 stylesheet that uses 'collection()' to open multiple documents and that runs fine from within <oXygen/> 12.1 either because I have 'DTD validation of the source' set to 'off' in my preferences or because Saxon is finding the DTD because I have an <oXygen/> framework for the document type. When I try to execute the stylesheet as part of a XProc pipeline, Calabash gives the error message: E:\path\DTD.dtd (The system cannot find the file specified) where 'DTD.dtd' is the system identifier in the DOCTYPE of the documents, which makes this look a lot like it's a Saxon error message. Is there a way to get <oXygen/> to run Calabash to run Saxon with -dtd:off or with catalogs? FWIW, here's the XProc step: <p:xslt> <p:input port="source"> <p:empty/> </p:input> <p:input port="stylesheet"> <p:document href="../XSLT/test2schematron.xsl"/> </p:input> <p:with-param name="path" select="$path"> <p:empty/> </p:with-param> <p:with-option name="template-name" select="'main'"/> <p:with-option name="version" select="'2.0'"/> </p:xslt> Regards, Tony Graham Tony.Graham(a)MenteithConsulting.com Director W3C XSL FO SG Invited Expert Menteith Consulting Ltd XML Guild member XML, XSL and XSLT consulting, programming and training Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland Registered in Ireland - No. 428599 http://www.menteithconsulting.com -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- xmlroff XSL Formatter http://xmlroff.org xslide Emacs mode http://www.menteith.com/wiki/xslide Unicode: A Primer urn:isbn:0-7645-4625-2

2 5