[oXygen-user] [Ann] oXygen XML Editor version 12 beta
Mon Aug 30 00:56:13 CDT 2010
Thanks for the feedback.
We already have plans to enhance the current profiling conditions
feature by providing foreground and background colors for different
profile values (hopefully in Oxygen 12.1).
Do you have any advice for when an element has multiple profile values?
Merge the colors probably?
For now, Oxygen 12 will only have the "Show Profiling Attributes" action
which shows a border around elements which have profiling attributes and
also renders the profiling attributes and their values.
About automatically detecting profiling attribute names from the DITA DTD's:
For now the attributes which are considered as profiling attributes in
the "Editor / Pages / Author / Profiling/Conditional Text" preferences
page are all hard-coded.
So either each user edits the values and adds his specialization
attributes or an administrator does that, then passes the entire page to
the Project level and shares it with everybody else.
Our original intent for DITA was auto-detection, given a set of
DTD's/XML Schemas, this is not hard to do, but we encountered several
What is the set of DTD's/XML Schemas to perform the auto-detection upon?
The user may be using a different DITA Open Toolkit installation.
Maybe perform the auto-detection on the opened DITA Maps but then all
these detected attribute names (and values, which most of the times are
not specified) needed to be customized by the user anyway so I think
editing the Oxygen Preferences was unavoidable.
If you have enhancement ideas about this, they are welcomed.
So for Oxygen 12 we preferred to propose some default attribute names
and values (for DITA, Docbook) and leave each user configure his own
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
On 8/27/2010 6:51 PM, Eliot Kimber wrote:
> Looks good.
> Tried out the new profiling support. Nice.
> One feature I didn't see was a way to associate specific colors with
> specific conditions.
> That is, I'd like to be able to associate specific conditions with specific
> foreground or background colors, so for example I can make one audience blue
> and a different one green in the editor.
> Also, it wasn't clear how or if Oxygen was aware of @props specializations
> currently available. In my test I was editing a document that uses a shell
> that integrates a @props specialization (the new d4p_renditionTarget
> attribute I just added to the D4P vocabulary).
> I sort of expected to get a list of all declared @props specializations, at
> least those available for the document I had open.
> I was able to add the attribute by simply manually typing its name and then
> it configured just fine.
More information about the oXygen-user