freelanceprogrammers.org Forum Index » XML / XSL
[ANN] oXygen XML Editor 6.2
Joined: 20 Jul 2005
Posts: 5
[ANN] oXygen XML Editor 6.2
Hi everybody,
I am glad to announce a new release of <oXygen/>, version 6.2 available from
http://www.oxygenxml.com
Although this is only a minor release, <oXygen/> 6.2 adds a lot of new
improvements. The most important addition is the support for dockable,
floating and auto-hideable views that allows the layout to be customized
as desired. A nice video demonstration shows exactly what this means:
http://www.oxygenxml.com/demo/dockableViews/dockableViews.html
There are a number of other features that have an impact on editing
against a framework like DocBook or TEI. One of the most useful is the
spell check as you type support that allows spelling errors to be
identified immediately, the words that are not present in the dictionary
are underlined with a red line as they are typed.
Another new addition is the support for presenting information about the
XSLT parameters that include default value, parameter location and
parameter documentation. Both TEI stylesheets and DocBook stylesheets
(here I want to thank to Sebastian Rahtz and Michael Smith for their
support) have the parameters documented, so when you configure the
parameters for a TEI or DocBook transformation you can see the
documentation for each parameter.
There are a lot of other new features, the full list and detailed
descriptions are available at
http://www.oxygenxml.com/index.html#new-version
Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Joined: 05 May 2005
Posts: 9
[ANN] oXygen XML Editor 6.2
George:
To get my interest, tell me about support for DITA.
Regards,
Hedley
--
Hedley Finger
Technical Communications Tools & Processes Specialist
MYOB Australia <http://myob.com/au>
P.O. box 371 Blackburn VIC 3130 Australia
12 Wesley Court Tally Ho Business Park East Burwood VIC 3151
Australia
<mailto:hedleyDOTfingerATmyobDOTcom>
Tel. +61 3 9222 9992 x 7421, Mob. (cell) +61 412 461 558
© MYOB Technology Pty Ltd 2005
Joined: 20 Jul 2005
Posts: 5
[ANN] oXygen XML Editor 6.2
Dear Hadley,
Oxygen does not provide special support for DITA but I downloaded
DITA-OT1.1 and gave it a try.
The sample files can be edited in oXygen and oXygen offers *content
completion* and *validation* support.
Oxygen has a feature that allows presenting the schema annotations as
documentation for the entered elements through the content completion
popup. It presents next to the content completion popup the
documentation for the current content completion selection. As DTDs do
not have annotations we use the comments. After I enabled the
Options->Preferences -- Editor / Tag Insight / Features / Use DTD
comments as annotations option I am able to see the full names of the
DITA elements as I edit the file, for instance when I select the
[stepxmp] element I see nest to it [LONG NAME: Step Example].
But the real power of this feature appears when I switch to XML Schema
as the DITA schemas have annotations for elements and attributes. I
removed the DOCTYPE declaration from a concept file and I associated the
concept.xsd schema using the associate schema action. Then I get
information for the elements, attributes and values offered by the
content completion. For instance when the [conbody] element is selected
in the content completion I get in the documentation popup:
***
The < conbody > element is the main body-level element for a concept.
Like the body element of a general topic, < conbody > allows paragraphs,
lists, and other elements as well as sections and examples. But <
conbody > has a constraint that a section or an example can be followed
only by other sections or examples.
***
After inserting the element the content completion presents the
attributes and selecting the [class] attribute I get the following in
the documentation popup:
***
The class attribute supports specialization. Its predefined values help
the output transforms work correctly with ranges of related content.
***
You can use oXygen to *transform* DITA documents. The sample files
specify a stylesheet using the xml-stylesheet PI and I used the
transform action in oXygen that asked me to confirm that I want to use
the stylesheet specified in the PI for transformation - unfortunately
that stylesheet is not present in the distribution so I got an error. I
configured then a transformation scenario to use the dita2xhtml.xsl
stylesheet and that seems to work ok. Note that oXygen allows you to
specify multiple XSLT stylesheets that will be applied like below
XML -> main XSLT -> [result -> additional XSLT ->]* result
so if you have a stylesheet that represents a preprocessing step then
you can configure a single transformation scenario for that.
One of the new addition in 6.2, the extraction and presentation of the
*documentation for the XSLT parameters* works with DITA as the
stylesheet parameters are documented. Also the *automatic XSLT parameter
detection* helps as the parameters are defined in different XSLT files.
For instance I can see that there is an ARTLBL parameter and I get the
following information:
***
default "output artwork filenames" processing parameter (`no`)
Default value: `no`
System ID: file:/F:/DITA-OT1.1/xsl/xslhtml/dita2htmlImpl.xsl
***
I get this as I try to configure the transformation, without the need to
look for possible parameters in the DITA documentation.
I opened also a few schemas. You can use Oxygen to *browse the schemas*
using the schema diagram view and to *generate schema documentation*. I
generated the chunked version of the documentation including diagrams
for concept.xsd, see a few links here:
http://www.oxygenxml.com/schemaDoc/doc-DITA-concept/concept.xsd.html
http://www.oxygenxml.com/schemaDoc/doc-DITA-concept/softwareDomain.xsd.html
http://www.oxygenxml.com/schemaDoc/doc-DITA-concept/softwareDomain.xsd.html_elem
ent_filepath.html
External processing like the execution of ant scripts can be easily
integrated using the oXygen external tools support.
I hope that these gave you a few ideas of what can be done with oXygen.
Unfortunately I do not have any experience with DITA and probably I did
not choose the best examples.
Anyway, I added a feature request on our bugzilla to look into adding
DITA support in oXygen, similar with what we have for TEI and DocBook -
XML catalog already setup, DTDs/Schemas and stylesheets shipped with
oXygen, new document templates, samples, default transformation
scenarios to different formats, etc.
Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
hedley.finger@... wrote:
> George:
>
> To get my interest, tell me about support for DITA.
>
> Regards,
> Hedley
>
> --
> Hedley Finger
> Technical Communications Tools & Processes Specialist
> MYOB Australia <http://myob.com/au>
> P.O. box 371 Blackburn VIC 3130 Australia
> 12 Wesley Court Tally Ho Business Park East Burwood VIC 3151
> Australia
> <mailto:hedleyDOTfingerATmyobDOTcom>
> Tel. +61 3 9222 9992 x 7421, Mob. (cell) +61 412 461 558
>
> © MYOB Technology Pty Ltd 2005
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
Joined: 19 Aug 2005
Posts: 4
[ANN] oXygen XML Editor 6.2
Dear Hadley, all,
You might be interested in knowing that the one of the developer of
DITA, Michael Priestley of IBM Canada, will be giving a DITA workshop
in Berlin, Germany next week on September 28 as part of a Society for
Technicial Communication conference (Sept 28 to 30).
Full details can be seen here:
http://www.stc-transalpine.org/conference/
Details of the DITA Workshop follows.
Michael Priestley on Darwin Information Typing Architecture (DITA)
Michael Priestley
Michael Priestley is one of the XML architects of DITA, with specific
focus on its specialization and map architectures. He has written
numerous papers on information design, architecture, single-sourcing,
and information development processes. He is IBM`s representative on
the OASIS DITA Technical Committee, and a co-editor of the DITA 1.0
specification.
Workshop: Introduction to Darwin Information Typing Architecture
DITA 1.0 is an OASIS standard for creating topic-oriented,
information-typed content that can be reused and single-sourced in a
variety of ways. DITA is gaining in popularity as a new standard at
OASIS with open-source processing support as well as off-the-shelf
support from a variety of content management and authoring tool
vendors.
This workshop is intended to provide a practical introduction to
using DITA as an authoring format, including the use of DITA topics
for content, DITA maps for structuring and delivering content, and
various DITA attributes to enable reuse and linking. There is no
formal prerequisite to participate in the workshop. Although prior
knowledge of XML would be beneficial, it is not absolutely needed.
Existing users of DITA will benefit primarily from the second half of
the workshop.
(You may register for the workshop separately or attend the entire
conference.)
Workshop Structure:
* Introduction to DITA
o Why DITA?
o What is DITA?
o Benefits of DITA
* Authoring DITA content
o Topic structures
o Topic hierarchies and linking
o Concepts, tasks, and reference
* Information architecture with DITA
o Understanding the user
* Audiences, roles, personas
* Goals, tasks, scenarios
o Modeling the information
* Task hierarchies
* Relationship tables
* Other groups and hierarchies
* Creating an outline
o Authoring and publishing
* Publishing with the DITA open source toolkit
There is still room available, but registration will close end of
this week.
Best regards,
Glenn Lea
www.glennjlea.ca
--- In xml-doc@yahoogroups.com, George Cristian Bina <george@o...>
wrote:
> Dear Hadley,
>
> Oxygen does not provide special support for DITA but I downloaded
> DITA-OT1.1 and gave it a try.
>
> The sample files can be edited in oXygen and oXygen offers *content
> completion* and *validation* support.
>
> Oxygen has a feature that allows presenting the schema annotations
as
> documentation for the entered elements through the content
completion
> popup. It presents next to the content completion popup the
> documentation for the current content completion selection. As DTDs
do
> not have annotations we use the comments. After I enabled the
> Options->Preferences -- Editor / Tag Insight / Features / Use DTD
> comments as annotations option I am able to see the full names of
the
> DITA elements as I edit the file, for instance when I select the
> [stepxmp] element I see nest to it [LONG NAME: Step Example].
>
> But the real power of this feature appears when I switch to XML
Schema
> as the DITA schemas have annotations for elements and attributes. I
> removed the DOCTYPE declaration from a concept file and I
associated the
> concept.xsd schema using the associate schema action. Then I get
> information for the elements, attributes and values offered by the
> content completion. For instance when the [conbody] element is
selected
> in the content completion I get in the documentation popup:
>
> ***
> The < conbody > element is the main body-level element for a
concept.
> Like the body element of a general topic, < conbody > allows
paragraphs,
> lists, and other elements as well as sections and examples. But <
> conbody > has a constraint that a section or an example can be
followed
> only by other sections or examples.
> ***
>
> After inserting the element the content completion presents the
> attributes and selecting the [class] attribute I get the following
in
> the documentation popup:
>
> ***
> The class attribute supports specialization. Its predefined values
help
> the output transforms work correctly with ranges of related content.
> ***
>
> You can use oXygen to *transform* DITA documents. The sample files
> specify a stylesheet using the xml-stylesheet PI and I used the
> transform action in oXygen that asked me to confirm that I want to
use
> the stylesheet specified in the PI for transformation -
unfortunately
> that stylesheet is not present in the distribution so I got an
error. I
> configured then a transformation scenario to use the dita2xhtml.xsl
> stylesheet and that seems to work ok. Note that oXygen allows you
to
> specify multiple XSLT stylesheets that will be applied like below
>
> XML -> main XSLT -> [result -> additional XSLT ->]* result
>
> so if you have a stylesheet that represents a preprocessing step
then
> you can configure a single transformation scenario for that.
>
> One of the new addition in 6.2, the extraction and presentation of
the
> *documentation for the XSLT parameters* works with DITA as the
> stylesheet parameters are documented. Also the *automatic XSLT
parameter
> detection* helps as the parameters are defined in different XSLT
files.
> For instance I can see that there is an ARTLBL parameter and I get
the
> following information:
> ***
> default "output artwork filenames" processing parameter (`no`)
> Default value: `no`
> System ID: file:/F:/DITA-OT1.1/xsl/xslhtml/dita2htmlImpl.xsl
> ***
> I get this as I try to configure the transformation, without the
need to
> look for possible parameters in the DITA documentation.
>
> I opened also a few schemas. You can use Oxygen to *browse the
schemas*
> using the schema diagram view and to *generate schema
documentation*. I
> generated the chunked version of the documentation including
diagrams
> for concept.xsd, see a few links here:
> http://www.oxygenxml.com/schemaDoc/doc-DITA-concept/concept.xsd.html
> http://www.oxygenxml.com/schemaDoc/doc-DITA-
concept/softwareDomain.xsd.html
> http://www.oxygenxml.com/schemaDoc/doc-DITA-
concept/softwareDomain.xsd.html_element_filepath.html
>
> External processing like the execution of ant scripts can be easily
> integrated using the oXygen external tools support.
>
> I hope that these gave you a few ideas of what can be done with
oXygen.
> Unfortunately I do not have any experience with DITA and probably I
did
> not choose the best examples.
>
> Anyway, I added a feature request on our bugzilla to look into
adding
> DITA support in oXygen, similar with what we have for TEI and
DocBook -
> XML catalog already setup, DTDs/Schemas and stylesheets shipped
with
> oXygen, new document templates, samples, default transformation
> scenarios to different formats, etc.
>
> Best Regards,
> George
> --------------------------------------------------------------------
-
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
>
>
> hedley.finger@m... wrote:
> > George:
> >
> > To get my interest, tell me about support for DITA.
> >
> > Regards,
> > Hedley
> >
> > --
> > Hedley Finger
> > Technical Communications Tools & Processes Specialist
> > MYOB Australia <http://myob.com/au>
> > P.O. box 371 Blackburn VIC 3130 Australia
> > 12 Wesley Court Tally Ho Business Park East Burwood VIC 3151
> > Australia
> > <mailto:hedleyDOTfingerATmyobDOTcom>
> > Tel. +61 3 9222 9992 x 7421, Mob. (cell) +61 412 461 558
> >
> > © MYOB Technology Pty Ltd 2005
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
Joined: 25 Sep 2005
Posts: 2
[ANN] oXygen XML Editor 6.2
wow
It is excellent. I saw the demo. The importance of dockability may be
different for different persons, but it is so nice to see a fresh idea. Makes
you also think in a new way while programming if using a tool like this !!
Congratulations.
Raj
George Cristian Bina <george@...> wrote:
Hi everybody,
I am glad to announce a new release of , version 6.2 available from
http://www.oxygenxml.com
Although this is only a minor release, 6.2 adds a lot of new
improvements. The most important addition is the support for dockable,
floating and auto-hideable views that allows the layout to be customized
as desired. A nice video demonstration shows exactly what this means:
http://www.oxygenxml.com/demo/dockableViews/dockableViews.html
There are a number of other features that have an impact on editing
against a framework like DocBook or TEI. One of the most useful is the
spell check as you type support that allows spelling errors to be
identified immediately, the words that are not present in the dictionary
are underlined with a red line as they are typed.
Another new addition is the support for presenting information about the
XSLT parameters that include default value, parameter location and
parameter documentation. Both TEI stylesheets and DocBook stylesheets
(here I want to thank to Sebastian Rahtz and Michael Smith for their
support) have the parameters documented, so when you configure the
parameters for a TEI or DocBook transformation you can see the
documentation for each parameter.
There are a lot of other new features, the full list and detailed
descriptions are available at
http://www.oxygenxml.com/index.html#new-version
Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Yahoo! Groups Links
visit http://www.devsthan.com
Premiere Temples and Travel site.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[Non-text portions of this message have been removed]
All times are GMT
Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Freelace Website Designer - Customer web design and software building.
Booking Calendar - reservation calendar script
Land Surveying - total station instruments and equipments
China Wholesale - Electronics Products
Character Studio - Tutorials and Help
Booking Calendar - reservation calendar script
Land Surveying - total station instruments and equipments
China Wholesale - Electronics Products
Character Studio - Tutorials and Help