oXygen has all the reviewing tools our authors and editorial staff depend on, with change-tracking and commenting and many features needed behind the scenes. Tools that are so powerful and so easy to learn are rare.
In Crane's experience, the <oXygen/> editor has the widest and most complete spectrum of functionality across multiple ISO and W3C specifications for XML documents. This comprehensive tool appeals to both our novice and expert clients, from simply editing and publishing XML documents in a styled angle-bracket-free interface to intricately diagnosing, debugging and profiling transformations. In particular, the cross-platform implementation ensures all users have the same functionality. Crane Softwrights Ltd. is proud to offer different hands-on <oXygen/> training classes where we share with students our own experiences of using this tool on a day-by-day basis.
<oXygen/> is the premier text editor for XML geeks, and an indispensable tool for O'Reilly's Production group. My team uses <oXygen/> for everything from simple XML editing to Schema validation and XSLT transformations. The digital production staff especially loves oXygen's built-in EPUB support, which eliminates a great deal of the grunt work that is usually entailed in editing EPUB files. The more we use oXygen, the more realize what a powerful tool it can be in digital and XML-based workflows.
Choosing <oXygen/> XML Editor for worldwide deployment throughout Amdocs was easy: it's highly versatile, multiplatform and packed-full of features. Since its adoption in 2007 we received positive feedback from our employees, praising its great documentation, low learning curve, neat interface and a very enthusiastic technical support team. We will most definitely keep on using this great XML editor in the future.
Maybe it's time to update the endorsement of oXygen that appears under my name on your web site, as I've been using the product for considerably longer than six months now. oXygen still hits a sweet spot -- but a wider one than ever. The feature set, performance and interfaces get better with every release, while its core virtues remain, including the portability across platforms and the enlightened licensing (to users, not machines). Bravo for creating a product that needs no apology.
I've been using <oXygen/> for about six weeks now. I really like it. I agree with Norm Walsh that it hits a sweet spot. I hope it continues to be available on all the major platforms: that's a key feature long-term, I think.
I just wanted to pass on my congratulations on the very professional way the upgrade letter made it easy for me to see all the ways in which Oxygen has improved over the last few versions. I appreciated the reminder of features which I should spend some time exploring. In particular, the DocBook and DITA authoring will help us with our cross-platform help requirements. I continue to be a very happy multi-platform user of Oxygen and recommend it to all my clients and contacts who need to work with XML and particularly XPath or XSLT.
My favorite XML editor is becoming scary good. I've been an Oxygen convert for a long time, and every iteration it just seems to get better and better. The Oxygen XML 7.0 Editor has just been released by SyncRO Soft SRL., and already its reached the stage where I find it very, very difficult to shift back to the older version. Oxygen has been in a continual state of evolution, since I first encountered it as a 3.0 product, and it seems like even minor upgrades brings significant improvements to the application.
My goal was to produce a user interface that has basic similarities to my current favorite XML editor, Oxygen (http://www.oxygenxml.com/). I had first encountered Oxygen when I was playing around with Eclipse, and soon became enamored of it. You can easily assign schemas or DTDs to XML to get full intellisense functionality, you could customize the XSLT engine so that it could easily use third party tools such as Saxon (something that was VERY useful for working with XSLT 2.0), it has a first-class debugger, and it is quite reasonably priced ($79, last I checked). Moreover, it integrates cleanly with Oxygen, and is the first XML tool of any quality that works as well in Linux as it does in Windows.
I have just downloaded, installed and tested the upgrade and I can tell you've made my day! <oXygen/> is the first graphical schema editor which is at the same time:
One tool I have grown quite fond of is the Java-based XML editor, <oXygen/>. I have reviewed this product in the past, and since then it has continued to get better. In addition to being one of the first XML editors to incorporate RELAX NG support, the newest version of <oXygen/> now includes a nice set of TEI templates -- just select one, and <oXygen/> creates a document skeleton (and assists you in validation and tag entry as you go along). But most impressive of all, the XSL-FO stylesheets that also come bundled just work. I was able to create a couple of nice looking PDFs out of my TEI tests without spending hours configuring tool chains and reading obscure HOWTO-s.
oXygen XML Editor is an editor that enables you to develop everything needed for publishing XML documents. It is a complete platform-independent solution for creating many types of XML documents, validating them, editing schema, generating HTML documentation, converting one XML type to another, and much more.
We develop complex XQueries using SAXON, Java code extensions and Oracle XML DB. oXygen has given us full debugging and profiling against our data with out custom code and data sources too. Using it saves days of development effort in every project we undertake. The queries are developed more quickly, run faster and more reliably as a result. In diagnosis of faults with the live data from our client sites it has also proved invaluable.
The included integrated tools for XPath construction, XML diff, general editing (XML, XQuery, XPath and Schemas) add more value and the documentation generation is also a great advantage particularly as we publish our schemas to external parties. Our technical writers even use oXygen as it has excellent DocBook integration. Support has been first rate offering prompt help, problem diagnosis and resolution, and suggestions for productivity improvements.
In short I have no hesitation in recommending oXygen to XML developers at all levels for use with all XML technology!
I am extremely pleased to tell you that the team I conducted and I are working with documents in XML format. With the increasing popularity of XML, the number of XML editors is growing exponentially and it can be extremely difficult to choose the convenient editor that suits NeuroML users. Considering a long list of criteria we've chosen <oXygen/> for many reasons. The <oXygen/> 7.0 XML editor is an excellent addition to any professional Web programmer's program suite. It has a very well laid out, aesthetically pleasing GUI and, where certain other programs in this category have an old look, this program has that up-to-date quality!
I wanted to drop a note of thanks for your product, Oxygen, and your company. I admire that you offer reduced costs and licenses for companies which are actively engaged in supporting the environment and ecology in varying ways. My wife and I just moved to Dallas, and they do not do curb-side recycling, so we chose Green Mountain as our electricity provider -- a company which provides 100% renewable resource energy. So, I choose and appreciate companies with similar interests. I learned about Oxygen through my new employer -- Innodata-Isogen. We use Oxygen for a great deal of XML work. I have used Altova's XML Spy up to this point, but really enjoy the features Oxygen provides and the lower cost, as well as the focus on our planet. I just purchased a license for the personal version + 1 year of maintenance -- and glad to do it!
I've been using XSLT a lot in the last year. There are several things I like about it. Insanely good documentation leads the list, closely followed by excellent tool support (I use the Oxygen XML / XSLT / schema editor.)
Oxygen starts what will (I predict) become a trend - especially in document centric XML (and you know in your heart that all XML should be document centric don't you:-)