From support at oxygenxml.com Mon Jul 1 03:40:41 2013 From: support at oxygenxml.com (Oxygen XML Editor Support) Date: Mon, 01 Jul 2013 11:40:41 +0300 Subject: [oXygen-sdk] [Ann] New maintenance build available for oXygen 15.0 (2013062614) Message-ID: <51D14089.1090505@oxygenxml.com> Dear oXygen users, We announce the release of a new maintenance build (2013062614) for oXygen 15.0 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2013062614 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support at oxygenxml.com http://www.oxygenxml.com From jbevers at sdl.com Thu Jul 11 02:07:03 2013 From: jbevers at sdl.com (Jan Bevers) Date: Thu, 11 Jul 2013 09:07:03 +0200 Subject: [oXygen-sdk] Issue with resolving of titles with process instructions Message-ID: <9FF327331F1B284C9BAD6C548DCD069504A4855E@NL1MAIL0302.global.sdl.corp> Hi I noticed an issue in oXygen when you have process instruction inside the title element. The process instructions end up in the map as part of the resolved content. The same happens for links. Attached you can find a screenshot and sample files to reproduce the issue. The process instructions in the file are change tracker instructions created by another XML editor. Users using our CMS that switch to oXygen can get this issue. Kind regards, Jan Bevers | Developer | SDL | Content Management Technologies Division | +32 (0)15 400 970 | jbevers at sdl.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 5556 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oXygen15IssueWithProcessingInstructions.png Type: image/png Size: 145181 bytes Desc: oXygen15IssueWithProcessingInstructions.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: washingthecar.dita Type: application/octet-stream Size: 1254 bytes Desc: washingthecar.dita URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Test.ditamap Type: application/octet-stream Size: 262 bytes Desc: Test.ditamap URL: -------------- next part --------------

www.sdl.com


SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.
From support at oxygenxml.com Thu Jul 11 02:21:35 2013 From: support at oxygenxml.com (Oxygen XML Editor Support) Date: Thu, 11 Jul 2013 10:21:35 +0300 Subject: [oXygen-sdk] Issue with resolving of titles with process instructions In-Reply-To: <9FF327331F1B284C9BAD6C548DCD069504A4855E@NL1MAIL0302.global.sdl.corp> References: <9FF327331F1B284C9BAD6C548DCD069504A4855E@NL1MAIL0302.global.sdl.corp> Message-ID: <51DE5CFF.9010507@oxygenxml.com> Hi Jan, Thanks for the samples. You are right, in oxgyen 15.1 (in a couple of months) we'll try to hide in these two situations the PI text content. Regards, Radu Radu Coravu XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 7/11/2013 10:07 AM, Jan Bevers wrote: > Hi > > I noticed an issue in oXygen when you have process instruction inside > the title element. The process instructions end up in the map as part of > the resolved content. The same happens for links. > > Attached you can find a screenshot and sample files to reproduce the issue. > > The process instructions in the file are change tracker instructions > created by another XML editor. Users using our CMS that switch to oXygen > can get this issue. > > Kind regards, > > *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies > Division *| *+32 (0)15 400 970*|* jbevers at sdl.com > Description: image001 > > > > > > > > >

www.sdl.com >


> > > > SDL PLC confidential, all rights reserved. > > If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, > and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. >
> > > > _______________________________________________ > oXygen-sdk mailing list > oXygen-sdk at oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk > From nigel.whitaker at deltaxml.com Mon Jul 15 05:03:29 2013 From: nigel.whitaker at deltaxml.com (Nigel Whitaker) Date: Mon, 15 Jul 2013 11:03:29 +0100 Subject: [oXygen-sdk] Styling inside the DITA Map Manager Message-ID: <1E1032B4-9DEF-40E7-A8A4-BBCC02CE46D2@deltaxml.com> Hello, We are trying to show users the result of a DITA Map comparison (two input maps, in the result map we want to show users which topics are added/deleted/changed). We use @status on the topicrefs for example: DITA Topic Map When the map is opened in an editor window some CSS can be used to style the topics: *[status=new] { text-decoration: underline; background-color: #90ee90; /* CSS - LightGreen */ } *[status=changed] { background-color: #77ccff; /* CSS - LightCyan */ } This works great in the editor - users looking at a result map can see the changed topics, click and see the topic level changes. However, when a user chooses to open the map in the DITA Map Manager, there isn't any styling. Is there an alternative way of styling that we could be using? If not, could we request an enhancement to support CSS in the Map Manager? Thanks, Nigel -- Nigel Whitaker, Software Architect, DeltaXML Ltd. "Experts in information change" nigel.whitaker at deltaxml.com http://www.deltaxml.com +44 1684 869035 Registered in England: 02528681 Reg. Office: Monsell House, WR8 0QN, UK -------------- next part -------------- An HTML attachment was scrubbed... URL: From support at oxygenxml.com Mon Jul 15 07:04:24 2013 From: support at oxygenxml.com (Oxygen XML Editor Support) Date: Mon, 15 Jul 2013 15:04:24 +0300 Subject: [oXygen-sdk] Styling inside the DITA Map Manager In-Reply-To: <1E1032B4-9DEF-40E7-A8A4-BBCC02CE46D2@deltaxml.com> References: <1E1032B4-9DEF-40E7-A8A4-BBCC02CE46D2@deltaxml.com> Message-ID: <51E3E548.8020509@oxygenxml.com> Hello Nigel, The tree used in the DITA Maps Manager is a standard Swing JTree and does not take at all the CSS into account. But if you implement a Workspace Access Plugin type (you probably already have one) you could use our API to customize the cell renderer set by us, for example something like: > this.pluginWorkspaceAccess.addEditorChangeListener(new WSEditorChangeListener() { > /** > * @see ro.sync.exml.workspace.api.listeners.WSEditorChangeListener#editorOpened(java.net.URL) > */ > @Override > public void editorOpened(URL editorLocation) { > WSEditor ed = pluginWorkspaceAccess.getEditorAccess(editorLocation, StandalonePluginWorkspace.DITA_MAPS_EDITING_AREA); > WSDITAMapEditorPage ditaEDPage = (WSDITAMapEditorPage) ed.getCurrentPage(); > JTree tree = (JTree) ditaEDPage.getDITAMapTreeComponent(); > final TreeCellRenderer currentRenderer = tree.getCellRenderer(); > tree.setCellRenderer(new DefaultTreeCellRenderer() { > /** > * @see javax.swing.tree.DefaultTreeCellRenderer#getTreeCellRendererComponent(javax.swing.JTree, java.lang.Object, boolean, boolean, boolean, int, boolean) > */ > @Override > public Component getTreeCellRendererComponent(JTree tree, Object value, boolean sel, > boolean expanded, boolean leaf, int row, boolean hasFocus) { > JPanel panel = (JPanel) currentRenderer.getTreeCellRendererComponent(tree, value, sel, expanded, leaf, row, hasFocus); > panel.setBorder(null); > if(value instanceof AuthorElement) { > AuthorElement elem = (AuthorElement) value; > if(elem.getAttribute("status") != null) { > if("new".equals(elem.getAttribute("status").getValue())) { > panel.setBorder(BorderFactory.createMatteBorder(0, 0, 1, 0, Color.LIGHT_GRAY)); > } > } > } > return panel; > } > }); > } > }, StandalonePluginWorkspace.DITA_MAPS_EDITING_AREA); Regards, Radu Radu Coravu XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 7/15/2013 1:03 PM, Nigel Whitaker wrote: > Hello, > > We are trying to show users the result of a DITA Map comparison (two > input maps, in the result map we want to show users which topics are > added/deleted/changed). > > We use @status on the topicrefs for example: > > > DITA Topic Map > > > > > When the map is opened in an editor window some CSS can be used to style > the topics: > > *[status=new] { > text-decoration: underline; > background-color: #90ee90; /* CSS - LightGreen */ > } > > *[status=changed] { > background-color: #77ccff; /* CSS - LightCyan */ > } > > > This works great in the editor - users looking at a result map can see > the changed topics, click and see the topic level changes. > However, when a user chooses to open the map in the DITA Map Manager, > there isn't any styling. > > Is there an alternative way of styling that we could be using? > If not, could we request an enhancement to support CSS in the Map Manager? > > Thanks, > > Nigel > > > -- > Nigel Whitaker, Software Architect, DeltaXML Ltd. "Experts in > information change" > nigel.whitaker at deltaxml.com > http://www.deltaxml.com +44 1684 869035 > Registered in England: 02528681 Reg. Office: Monsell House, WR8 0QN, UK > > > > _______________________________________________ > oXygen-sdk mailing list > oXygen-sdk at oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk > From support at oxygenxml.com Thu Jul 18 05:10:12 2013 From: support at oxygenxml.com (Oxygen XML Editor Support) Date: Thu, 18 Jul 2013 13:10:12 +0300 Subject: [oXygen-sdk] [Ann] New maintenance build available for oXygen 15.0 (2013071613) Message-ID: <51E7BF04.1050207@oxygenxml.com> Dear oXygen users, We announce the release of a new maintenance build (2013071613) for oXygen 15.0 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2013071613 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support at oxygenxml.com http://www.oxygenxml.com