- oXygen-user - www.oxygenxml.com

XInclude working in beta?
by Paul Everitt 30 Apr '04

30 Apr '04

Howdy. I had an xml/xslt combo that renders correctly in 3.x but fails in 4.0 beta. I set the preference for Enable Xinclude processing, no luck. Strangely, when I used the debugger, it warned me that the namespace for XInclude needed to be changed to 2003. I did so, and still no luck. However, if I render using the *debugger*, the output window contains the right results. Stated differently, does anybody have an XML and XSLT combo of files that uses xinclude and produces correct results under the beta? --Paul

3 3

RNC-DTD problem
by LARRODE Xavier (DR&T) 27 Apr '04

27 Apr '04

Hello, i have created a XML format for a VR application and i have a problem to make the DTD of this format. I have checked the forum and seen that we have to change xsd:NCName to text, but i have another error: this is a part of the format which produces the error: <Vertices> 3 float 3 float  <Vertex> 3 float <Data Name="string" Constant="float" Vector="3 float"/>  </Vertex> </Vertices> this is the RNC after the conversion: default namespace = "" start = element Vertices { (text | element Vertex { (text | element Data { attribute Constant { text }, attribute Name { text }, attribute Vector { text } })+ })+ } When i want to convert it to DTD : error: 12.25 sorry, cannot handle this kind of "oneOrMore" But actually i don't want (text or Vertex) in my element Vertices so i change to : default namespace = "" start = element Vertices { text, element Vertex { text, element Data { attribute Constant { text }, attribute Name { text }, attribute Vector { text } } } } and now i get this error : 7.17: cannot handle this kinf of group. Any idea ? because the format is valid and well-formed Thank you Xavier

2 1

invalid tag insight
by Chris Ryland 19 Apr '04

19 Apr '04

Why, when using RNG (compact or XML) form (fully established on a document, such that pressing the "Validate" icon works fine), does the "tag insight" feature suggest elements that aren't valid in the current context? I thought that was the whole point of tag insight. Or does RNG not really work the same as a DTD or XML Schema? Cheers! --Chris Ryland / Em Software, Inc. / www.emsoftware.com

2 4

UI nit
by Chris Ryland 17 Apr '04

17 Apr '04

When oxygen (forgive me if I don't go through all the typing contortions to type <oXygen/> ;-) is not the foremost app under OS X, shouldn't the cursor stop blinking? (I realize the window is dimmed, but the blinking cursor had me fooled, and I was typing at Emacs (on another physical screen) when I thought I was typing at oxygen.) Or is that not standard HIG behavior? Cheers! --Chris Ryland / Em Software, Inc. / www.emsoftware.com

1 0

more Emacs support?
by Chris Ryland 17 Apr '04

17 Apr '04

I've already gotten some very positive feedback from the Oxygen folks about adding more Emacs support (ideally, customizable due to people's different keybindings), but who on this list would like to add their voice to mine for "deep, indulgent" Emacs key support? They already made positive noises about m-F, m-B, m-D, m-Delete for deleting and moving by words. I'm thinking of a few more things like c-U (prefix argument supplier), c-K and the first level of kill buffer behavior, etc. That'd only have to add a few basic things like that and it would be 95% of what Emacs editing does for us on a minute-by-minute basis. Any other takers? ;-) Cheers! --Chris Ryland / Em Software, Inc. / www.emsoftware.com

1 0

UI nit
by Chris Ryland 17 Apr '04

17 Apr '04

Instead of the Emacs-like asterisk after the "buffer name" in the editor, how about putting a little Mac OS-like black dot in the colored bubble before the name? It'd be easier to see, in some funny way. Cheers! --Chris Ryland / Em Software, Inc. / www.emsoftware.com

1 0

WebDAV question
by Sylvain Perchaud 09 Apr '04

09 Apr '04

Hello, I tried for the first time to edit a file via WebDAV with oXygen 3.1 (MacOS 10.3). Unfortunately it doesn't work, I can't save my file on the WebDAV server (which use Plone). When I click on "Save", oXygen returns : "400 Bad Request "sylvain@plone.ffii.org:9674/ffii/events/2004/ljub04/ index_html"" In the "Open an URL" dialog I entered my login, my password and selected the file on the WebDAV. What can I do ? -- Sylvain Perchaud Tel : +33 (0) 674 758 551 Fax : +33 (0) 251 280 898 http://www.europe-shareware.org

2 2

Initial thoughts on the 4.0 beta
by Paul Everitt 09 Apr '04

09 Apr '04

Howdy all. Just a quick note to say that 4.0 looks really exciting! I started with the XSLT debugging and found the UI layout really innovative and intuitive. Setting a breakpoint and running to it was pretty simple. Other debuggers have a local variable section that let you navigate the current context. At first I expected something similar, meaning, the current node would appear and I could browse it. However, the oxygen approach is better: it's already showing you the XML document, so it scrolls the current node into view and highlights it. I then defined a couple of variables and set a breakpoint. This worked as expected. Finally, defined a variable that matched on multiple nodes: <xsl:variable name="c" select="//company|//person"/> In the breakpoint window, I selected the variable, then in the right window, I saw all the elements that matched. That's nice! I also tested DAV with Zope 2 and Plone. Worked ok. Renaming a folder failed, so I need to put in tcpwatch and see what happened. --Paul

1 0

Re: 4.0 beta bug
by Sean Wheller 09 Apr '04

09 Apr '04

On Thursday 08 April 2004 23:19, Sean Wheller wrote: > Can't replicate this problem exactly, but sometimes when I open an xml file > (very small) the interface looks like the attached screen capture. This problem only happens when I open a file by clicking the Open button on the toolbar. When I use File > Open the file is opened as expected. -- Sean Wheller

2 1

oXygen 4.0 beta
by George Cristian Bina 08 Apr '04

08 Apr '04

Hi, As you know oXygen 4.0 will add as main feature an XSLT debugger. We have available a beta version of the all platforms distribution. Please download it from: http://www.oxygenxml.com/update/oxygenAll4.0B.tar.gz and use the following license: =================== Registration_Name=Betatester Company=Syncro Soft Ltd. Category=Professional Component=XML-Editor, XSLT-Debugger Version=4, 4 Number_of_Licenses=1 Date=04-07-2004 Duration=31 SGN=MC0CFQCCP1yEBWUtQvAMpD8y1AdTlt1IUwIUWegwL8YgkkCyzke84q+a5PMYc2o\= =================== Below there is a list of the debugger features. Along with these features there are also a lot of improvements in the editor part but they are not extracted yet from bugzilla. XSLTDebugger features: * Support for Saxon and Xalan XSLT engines. * Stepping capabilities: step in, step over, step out, run, run to cursor, run to end, pause, stop. * Breakpoints on both source and style documents. * Call stack view on both source and style documents. * Trace history on both source and style documents. * Support for XPath expression evaluation during debugging. * Step into imported/included stylesheets as well as included source entities. * Available template and hit count. * Variables view. * Dynamic output generation. Details: * Support for Saxon and Xalan XSLT engines. The debugger supports both Saxon 6.5.3 and Xalan 2.5.1 engines. * Stepping capabilities. Step in: goes to the next stylesheet node. (next step in transformation) Step over: skip the next stylesheet node (including its sub-elements). The debugger will stop on the next sibling element. Step out: steps out to the next sibling of the stylesheet parent node. If this not exists,steps out to the next node at the same level as the parent, or higher. Run: run the debug transformation run until either an enabled breakpoint is encountered (in source or stylesheet) or the end of transformation occurs. Run to cursor: run the transformation until the execution reach the line on which the cursor is currently in. Run to end: run the transformation till end, without taking into account any enabled breakpoint which might be set. Pause: interrupt the current transformation. This is useful for long transformation (Docbook like) when you want to find out in what point the transformation is. The transformation can be resumed after. Stop: end immediately the transformation process. * Breakpoints on both source and style documents. You can set breakpoints both on xml or xsl documents iterated by the transformation. * Call stack view on both source and style documents. At any point during debugging, you can see the current stack for both stylesheet and source elements. * Trace history on both source and styleasheet documents. During debugging you get the full trace history of transformation on both source or stylesheet documents. * Support for XPath expression evaluation during debugging. You can evaluate XPath expression during debugging by defining watch expressions. The debugger will update its value during stepping. (the expression are evaluated in the current context). * Step into imported/included stylesheets as well as included source entities. Once a xml entity or an imported/included stylesheet is about to be used by the transformation, you will get access to it in order to see were the current step is. * Available template and hit count. You get a list with all templates used during transformation and their correspondent number of hits. * Variables and parameters view. The debugger list all variables and parameters together with their scope and actual value. * Dynamic output generation. The output is generated dynamically during the stylesheet execution All the best, George ------------------------------------------------------------- George Cristian Bina mailto:george@oxygenxml.com <oXygen/> XML Editor - http://www.oxygenxml.com/

1 0