From jbevers at sdl.com  Mon Jan  6 04:53:01 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Mon, 6 Jan 2014 10:53:01 +0000
Subject: [oXygen-sdk] Enhancement request for
	AttributeEditingContextDescription
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD61AF8B@mh-exch01.global.sdl.corp>

Hi

Since oXygen 15 it's possible to get the context for the current edited element / attribute from your own custom InputURLChooserCustomizer implementation.

In some of our cases it is important to pass the current value of the edited attribute to our own dialogs.
If I check the API of the AttributeEditingContextDescription you can only get the element and attribute name.
I can stick with the functionality that there is now but it would definitely improve the usability of our integration if the value was also available.

Is it possible to add the possibility to get the attribute value to the oXygen backlog? So we can take advantage from this in the next releases.

Cheers

Jan Bevers | Developer | SDL | Content Management Technologies Division | +32 (0)15 400 970 | jbevers at sdl.com
[image001]
</pre><font face="arial" size="2" color="#736F6E">



<a href="http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature">
<img src="http://www.sdl.com/Content/themes/common/images/SDL_logo_strapline_GCEM_EmailSig_150x68px.jpg" border=0><br><br>www.sdl.com
</a><br><br>

<font face="arial" size="1" color="#736F6E">

<b>SDL PLC confidential, all rights reserved.</b>

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.<BR>
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.<BR>
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.
</font>


This message has been scanned for malware by Websense. www.websense.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140106/0fdb6821/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 5556 bytes
Desc: image001.jpg
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140106/0fdb6821/attachment.jpg>

From support at oxygenxml.com  Mon Jan  6 06:02:37 2014
From: support at oxygenxml.com (Oxygen XML Editor Support)
Date: Mon, 06 Jan 2014 14:02:37 +0200
Subject: [oXygen-sdk] Enhancement request for
	AttributeEditingContextDescription
In-Reply-To: <B90DF52C077C454EB66E7193E2FFEACD61AF8B@mh-exch01.global.sdl.corp>
References: <B90DF52C077C454EB66E7193E2FFEACD61AF8B@mh-exch01.global.sdl.corp>
Message-ID: <52CA9B5D.5090001@oxygenxml.com>

Hi Jan,

Adding the:

> ro.sync.exml.workspace.api.standalone.AttributeEditingContextDescription.getEditedAttributeValue()

API seems feasible. We'll try to add it in time for Oxygen 15.2 which 
should be released in a couple of weeks.

A possible workaround until then would be to do something like:

>     WSEditor currentOpeneEditor = PluginWorkspaceProvider.getPluginWorkspace().getCurrentEditorAccess(PluginWorkspace.MAIN_EDITING_AREA);
>     if(currentOpeneEditor != null) {
>       WSEditorPage currentPage = currentOpeneEditor.getCurrentPage();
>       if(currentPage instanceof WSAuthorEditorPage) {
>         //Most probably we are editing the attributes for the node in which the caret is placed.
>         WSAuthorEditorPage authPage = ((WSAuthorEditorPage)currentPage);
>         try {
>           AuthorNode currentEditedNode = authPage.getDocumentController().getNodeAtOffset(authPage.getCaretOffset());
>           if(currentEditedNode.getType() == AuthorNode.NODE_TYPE_ELEMENT) {
>             AuthorElement elem = (AuthorElement) currentEditedNode;
>             //The current @href attribute value.
>             AttrValue currentHrefValue = elem.getAttribute("href");
>           }
>         } catch (BadLocationException e) {
>           e.printStackTrace();
>         }
>       }
>     }

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/6/2014 12:53 PM, Jan Bevers wrote:
> Hi
>
> Since oXygen 15 it’s possible to get the context for the current edited
> element / attribute from your own custom InputURLChooserCustomizer
> implementation.
>
> In some of our cases it is important to pass the current value of the
> edited attribute to our own dialogs.
>
> If I check the API of the AttributeEditingContextDescription you can
> only get the element and attribute name.
>
> I can stick with the functionality that there is now but it would
> definitely improve the usability of our integration if the value was
> also available.
>
> Is it possible to add the possibility to get the attribute value to the
> oXygen backlog? So we can take advantage from this in the next releases.
>
> Cheers
>
> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies
> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
> image001
>
>
>
> www.sdl.com
> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature>
>
> *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.
>
> This message has been scanned for malware by Websense. www.websense.com
> <http://www.websense.com/>
>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>


From jbevers at sdl.com  Tue Jan  7 02:59:44 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Tue, 7 Jan 2014 08:59:44 +0000
Subject: [oXygen-sdk] Enhancement request
	for	AttributeEditingContextDescription
In-Reply-To: <52CA9B5D.5090001@oxygenxml.com>
References: <B90DF52C077C454EB66E7193E2FFEACD61AF8B@mh-exch01.global.sdl.corp>
	<52CA9B5D.5090001@oxygenxml.com>
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD61BA03@mh-exch01.global.sdl.corp>

Hi Radu

Thanks for the workaround!

Another addition would be to get access to other attributes like "scope" and "class" for DITA.

For example as an integrator I can show different dialogs based on the current "scope" (external or internal) value of an "xref" element. 

"class" which is a fixed attribute is used to define what content type an element is holding. For example "glossSymbol", "hazardsymbol" and "image" have "topic/image" as part of their class attribute.
It is better to check against this than to check against the element name. Also when making a customization to DITA for a specific customer you can use the same class attribute value which does not require code changes in your oXygen integration.

Cheers
Jan


-----Original Message-----
From: oxygen-sdk-bounces at oxygenxml.com [mailto:oxygen-sdk-bounces at oxygenxml.com] On Behalf Of Oxygen XML Editor Support
Sent: maandag 6 januari 2014 13:03
To: oxygen-sdk at oxygenxml.com
Subject: Re: [oXygen-sdk] Enhancement request for AttributeEditingContextDescription

Hi Jan,

Adding the:

> ro.sync.exml.workspace.api.standalone.AttributeEditingContextDescripti
> on.getEditedAttributeValue()

API seems feasible. We'll try to add it in time for Oxygen 15.2 which should be released in a couple of weeks.

A possible workaround until then would be to do something like:

>     WSEditor currentOpeneEditor = PluginWorkspaceProvider.getPluginWorkspace().getCurrentEditorAccess(PluginWorkspace.MAIN_EDITING_AREA);
>     if(currentOpeneEditor != null) {
>       WSEditorPage currentPage = currentOpeneEditor.getCurrentPage();
>       if(currentPage instanceof WSAuthorEditorPage) {
>         //Most probably we are editing the attributes for the node in which the caret is placed.
>         WSAuthorEditorPage authPage = ((WSAuthorEditorPage)currentPage);
>         try {
>           AuthorNode currentEditedNode = authPage.getDocumentController().getNodeAtOffset(authPage.getCaretOffset());
>           if(currentEditedNode.getType() == AuthorNode.NODE_TYPE_ELEMENT) {
>             AuthorElement elem = (AuthorElement) currentEditedNode;
>             //The current @href attribute value.
>             AttrValue currentHrefValue = elem.getAttribute("href");
>           }
>         } catch (BadLocationException e) {
>           e.printStackTrace();
>         }
>       }
>     }

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

On 1/6/2014 12:53 PM, Jan Bevers wrote:
> Hi
>
> Since oXygen 15 it's possible to get the context for the current 
> edited element / attribute from your own custom 
> InputURLChooserCustomizer implementation.
>
> In some of our cases it is important to pass the current value of the 
> edited attribute to our own dialogs.
>
> If I check the API of the AttributeEditingContextDescription you can 
> only get the element and attribute name.
>
> I can stick with the functionality that there is now but it would 
> definitely improve the usability of our integration if the value was 
> also available.
>
> Is it possible to add the possibility to get the attribute value to 
> the oXygen backlog? So we can take advantage from this in the next releases.
>
> Cheers
>
> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies 
> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
> image001
>
>
>
> www.sdl.com
> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm
> _campaign=SDL%2BStandard%2BEmail%2BSignature>
>
> *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.
>
> This message has been scanned for malware by Websense. 
> www.websense.com <http://www.websense.com/>
>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>
_______________________________________________
oXygen-sdk mailing list
oXygen-sdk at oxygenxml.com
http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk


From support at oxygenxml.com  Tue Jan  7 06:45:02 2014
From: support at oxygenxml.com (Oxygen XML Editor Support)
Date: Tue, 07 Jan 2014 14:45:02 +0200
Subject: [oXygen-sdk] Enhancement request
	for	AttributeEditingContextDescription
In-Reply-To: <B90DF52C077C454EB66E7193E2FFEACD61BA03@mh-exch01.global.sdl.corp>
References: <B90DF52C077C454EB66E7193E2FFEACD61AF8B@mh-exch01.global.sdl.corp>	<52CA9B5D.5090001@oxygenxml.com>
	<B90DF52C077C454EB66E7193E2FFEACD61BA03@mh-exch01.global.sdl.corp>
Message-ID: <52CBF6CE.3040401@oxygenxml.com>

Hi Jan,

Sure, we'll look into how we can increase the API to accommodate this.

Probably we could try to come up with some API like:

> NodeContext ro.sync.exml.workspace.api.standalone.AttributeEditingContextDescription.getElementContext()

and the NodeContext would have the API methods:

>   /**
>    * Get the node name.
>    *
>    * @return Returns the node name.
>    */
>   public abstract String getNodeName();
>
>   /**
>    * Get the node namespace.
>    *
>    * @return Returns the node namespace.
>    */
>   public abstract String getNodeNamespace();
>
>   /**
>    * Returns the number of the element attributes.
>    *
>    * @return The number of the element attributes.
>    */
>   public abstract int getAttributesCount();
>
>   /**
>    * Get the qualified attribute name at index.
>    *
>    * @param index Index of the attribute.
>    * @return The qualified attribute name at index.
>    */
>   public abstract String getAttributeQName(int index);
>
>   /**
>    * Get attribute value for given attribute qualified name.
>    *
>    * @param attrQName The qualified attribute name.
>    * @return The attribute value.
>    */
>   public abstract String getAttributeValue(String attrQName);
>
>   /**
>    * Get namespace URI for a given attribute qualified name.
>    *
>    * @param attrQName The attribute qualified name.
>    * @return The attribute namespace URI.
>    */
>   public abstract String getAttributeNamespace(String attrQName);

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/7/2014 10:59 AM, Jan Bevers wrote:
> Hi Radu
>
> Thanks for the workaround!
>
> Another addition would be to get access to other attributes like "scope" and "class" for DITA.
>
> For example as an integrator I can show different dialogs based on the current "scope" (external or internal) value of an "xref" element.
>
> "class" which is a fixed attribute is used to define what content type an element is holding. For example "glossSymbol", "hazardsymbol" and "image" have "topic/image" as part of their class attribute.
> It is better to check against this than to check against the element name. Also when making a customization to DITA for a specific customer you can use the same class attribute value which does not require code changes in your oXygen integration.
>
> Cheers
> Jan
>
>
> -----Original Message-----
> From: oxygen-sdk-bounces at oxygenxml.com [mailto:oxygen-sdk-bounces at oxygenxml.com] On Behalf Of Oxygen XML Editor Support
> Sent: maandag 6 januari 2014 13:03
> To: oxygen-sdk at oxygenxml.com
> Subject: Re: [oXygen-sdk] Enhancement request for AttributeEditingContextDescription
>
> Hi Jan,
>
> Adding the:
>
>> ro.sync.exml.workspace.api.standalone.AttributeEditingContextDescripti
>> on.getEditedAttributeValue()
>
> API seems feasible. We'll try to add it in time for Oxygen 15.2 which should be released in a couple of weeks.
>
> A possible workaround until then would be to do something like:
>
>>      WSEditor currentOpeneEditor = PluginWorkspaceProvider.getPluginWorkspace().getCurrentEditorAccess(PluginWorkspace.MAIN_EDITING_AREA);
>>      if(currentOpeneEditor != null) {
>>        WSEditorPage currentPage = currentOpeneEditor.getCurrentPage();
>>        if(currentPage instanceof WSAuthorEditorPage) {
>>          //Most probably we are editing the attributes for the node in which the caret is placed.
>>          WSAuthorEditorPage authPage = ((WSAuthorEditorPage)currentPage);
>>          try {
>>            AuthorNode currentEditedNode = authPage.getDocumentController().getNodeAtOffset(authPage.getCaretOffset());
>>            if(currentEditedNode.getType() == AuthorNode.NODE_TYPE_ELEMENT) {
>>              AuthorElement elem = (AuthorElement) currentEditedNode;
>>              //The current @href attribute value.
>>              AttrValue currentHrefValue = elem.getAttribute("href");
>>            }
>>          } catch (BadLocationException e) {
>>            e.printStackTrace();
>>          }
>>        }
>>      }
>
> Regards,
> Radu
>
> Radu Coravu
> <oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
>
> On 1/6/2014 12:53 PM, Jan Bevers wrote:
>> Hi
>>
>> Since oXygen 15 it's possible to get the context for the current
>> edited element / attribute from your own custom
>> InputURLChooserCustomizer implementation.
>>
>> In some of our cases it is important to pass the current value of the
>> edited attribute to our own dialogs.
>>
>> If I check the API of the AttributeEditingContextDescription you can
>> only get the element and attribute name.
>>
>> I can stick with the functionality that there is now but it would
>> definitely improve the usability of our integration if the value was
>> also available.
>>
>> Is it possible to add the possibility to get the attribute value to
>> the oXygen backlog? So we can take advantage from this in the next releases.
>>
>> Cheers
>>
>> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies
>> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
>> image001
>>
>>
>>
>> www.sdl.com
>> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm
>> _campaign=SDL%2BStandard%2BEmail%2BSignature>
>>
>> *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.
>>
>> This message has been scanned for malware by Websense.
>> www.websense.com <http://www.websense.com/>
>>
>>
>>
>> _______________________________________________
>> oXygen-sdk mailing list
>> oXygen-sdk at oxygenxml.com
>> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>


From jbevers at sdl.com  Thu Jan  9 10:28:39 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Thu, 9 Jan 2014 16:28:39 +0000
Subject: [oXygen-sdk] Issue with custom protocol handler and href with dots
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD61C88A@mh-exch01.global.sdl.corp>

Hi

I noticed that when a reference has dots in it oXygen never asks my Custom Protocol Handler to resolve it.

I have an image tag that looks as followed:
<image href="GUID.7A23068F.1C34.46A2.849F.91FF00B9D586"/>

When I put a breakpoint on the openConnection(URL url) method I don't see any request coming in to resolve this reference. If I put ".jpg" at the end of this reference for example I can see a request coming in.

Cheers

Jan Bevers | Developer | SDL | Content Management Technologies Division | +32 (0)15 400 970 | jbevers at sdl.com
[image001]
</pre><font face="arial" size="2" color="#736F6E">



<a href="http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature">
<img src="http://www.sdl.com/Content/themes/common/images/SDL_logo_strapline_GCEM_EmailSig_150x68px.jpg" border=0><br><br>www.sdl.com
</a><br><br>

<font face="arial" size="1" color="#736F6E">

<b>SDL PLC confidential, all rights reserved.</b>

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.<BR>
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.<BR>
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.
</font>


This message has been scanned for malware by Websense. www.websense.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140109/1706bf57/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 5556 bytes
Desc: image003.jpg
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140109/1706bf57/attachment.jpg>

From support at oxygenxml.com  Fri Jan 10 02:03:23 2014
From: support at oxygenxml.com (Oxygen XML Editor Support)
Date: Fri, 10 Jan 2014 10:03:23 +0200
Subject: [oXygen-sdk] Issue with custom protocol handler and href with
 dots
In-Reply-To: <B90DF52C077C454EB66E7193E2FFEACD61C88A@mh-exch01.global.sdl.corp>
References: <B90DF52C077C454EB66E7193E2FFEACD61C88A@mh-exch01.global.sdl.corp>
Message-ID: <52CFA94B.9060408@oxygenxml.com>

Hi Jan,

So in this particular case Oxygen displays a missing image place-holder, 
right?
I created a simple JPEG image and renamed it to 
"GUID.7A23068F.1C34.46A2.849F.91FF00B9D586", then in a DITA topic opened 
via a very simple custom protocol implementation I referred to it:

> <image href="GUID.7A23068F.1C34.46A2.849F.91FF00B9D586"/>

It works for me, Oxygen calls the custom protocol and the image is 
resolved in it and displayed by Oxygen.

Could you test this issue on the local disk drive having an image file 
named "GUID.7A23068F.1C34.46A2.849F.91FF00B9D586" and referring to it 
from a local DITA topic?
Maybe your other API implementations interfere with this. Did you add a 
RelativeReferenceResolver customizer via the API?

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/9/2014 6:28 PM, Jan Bevers wrote:
> Hi
>
> I noticed that when a reference has dots in it oXygen never asks my
> Custom Protocol Handler to resolve it.
>
> I have an image tag that looks as followed:
>
> <imagehref="GUID.7A23068F.1C34.46A2.849F.91FF00B9D586"/>
>
> When I put a breakpoint on the openConnection(URL url) method I don’t
> see any request coming in to resolve this reference. If I put “.jpg” at
> the end of this reference for example I can see a request coming in.
>
> Cheers
>
> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies
> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
> image001
>
>
>
> www.sdl.com
> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature>
>
> *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.
>
> This message has been scanned for malware by Websense. www.websense.com
> <http://www.websense.com/>
>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>


From jbevers at sdl.com  Fri Jan 10 05:03:45 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Fri, 10 Jan 2014 11:03:45 +0000
Subject: [oXygen-sdk] Issue with custom protocol handler and href with
 dots
In-Reply-To: <52CFA94B.9060408@oxygenxml.com>
References: <B90DF52C077C454EB66E7193E2FFEACD61C88A@mh-exch01.global.sdl.corp>
	<52CFA94B.9060408@oxygenxml.com>
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD61C9D9@mh-exch01.global.sdl.corp>

Hi Radu

Sorry my mistake. The issue was in my code.

I'm using a RelativeReferenceResolver in my implementation which was interfering. 
I was relying on the FilenameUtils.getExtension method to check if the reference was resolved. This was not the best option off course as our identifiers can have dots in it.
I've replaced this part to be more smart and know it works fine.

Thx for pointing me out.

Cheers
Jan

-----Original Message-----
From: oxygen-sdk-bounces at oxygenxml.com [mailto:oxygen-sdk-bounces at oxygenxml.com] On Behalf Of Oxygen XML Editor Support
Sent: vrijdag 10 januari 2014 9:03
To: oxygen-sdk at oxygenxml.com
Subject: Re: [oXygen-sdk] Issue with custom protocol handler and href with dots

Hi Jan,

So in this particular case Oxygen displays a missing image place-holder, right?
I created a simple JPEG image and renamed it to "GUID.7A23068F.1C34.46A2.849F.91FF00B9D586", then in a DITA topic opened via a very simple custom protocol implementation I referred to it:

> <image href="GUID.7A23068F.1C34.46A2.849F.91FF00B9D586"/>

It works for me, Oxygen calls the custom protocol and the image is resolved in it and displayed by Oxygen.

Could you test this issue on the local disk drive having an image file named "GUID.7A23068F.1C34.46A2.849F.91FF00B9D586" and referring to it from a local DITA topic?
Maybe your other API implementations interfere with this. Did you add a RelativeReferenceResolver customizer via the API?

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

On 1/9/2014 6:28 PM, Jan Bevers wrote:
> Hi
>
> I noticed that when a reference has dots in it oXygen never asks my 
> Custom Protocol Handler to resolve it.
>
> I have an image tag that looks as followed:
>
> <imagehref="GUID.7A23068F.1C34.46A2.849F.91FF00B9D586"/>
>
> When I put a breakpoint on the openConnection(URL url) method I don't 
> see any request coming in to resolve this reference. If I put ".jpg" 
> at the end of this reference for example I can see a request coming in.
>
> Cheers
>
> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies 
> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
> image001
>
>
>
> www.sdl.com
> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm
> _campaign=SDL%2BStandard%2BEmail%2BSignature>
>
> *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.
>
> This message has been scanned for malware by Websense. 
> www.websense.com <http://www.websense.com/>
>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>
_______________________________________________
oXygen-sdk mailing list
oXygen-sdk at oxygenxml.com
http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk


From jbevers at sdl.com  Tue Jan 14 09:22:53 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Tue, 14 Jan 2014 15:22:53 +0000
Subject: [oXygen-sdk] Question about CustomComponentsValidator
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD61D598@mh-exch01.global.sdl.corp>

Hi all

In my integration with oXygen 14 I use a custom Components Validator to hide some menu items from the user.

I noticed that in oXygen 15.1 these buttons are not getting hidden anymore. I checked my code and  the constructor of my class was not getting called anymore when using oXygen 15.1

My plugin.xml contains following entry (works for 14.2, not for 15.1):
<extension type="componentsValidator" class="com.sdl.trisoft.oxygen.CustomComponentsValidatorPluginExtension"/>

Was there a change regarding the ComponentsValidator in oXygen 15.1?

Kind regards

Jan Bevers | Developer | SDL | Content Management Technologies Division | +32 (0)15 400 970 | jbevers at sdl.com
[image001]
</pre><font face="arial" size="2" color="#736F6E">



<a href="http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature">
<img src="http://www.sdl.com/Content/themes/common/images/SDL_logo_strapline_GCEM_EmailSig_150x68px.jpg" border=0><br><br>www.sdl.com
</a><br><br>

<font face="arial" size="1" color="#736F6E">

<b>SDL PLC confidential, all rights reserved.</b>

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.<BR>
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.<BR>
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.
</font>


This message has been scanned for malware by Websense. www.websense.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140114/5da56a30/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 5556 bytes
Desc: image001.jpg
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140114/5da56a30/attachment.jpg>

From support at oxygenxml.com  Wed Jan 15 01:21:25 2014
From: support at oxygenxml.com (Oxygen XML Editor Support)
Date: Wed, 15 Jan 2014 09:21:25 +0200
Subject: [oXygen-sdk] Question about CustomComponentsValidator
In-Reply-To: <B90DF52C077C454EB66E7193E2FFEACD61D598@mh-exch01.global.sdl.corp>
References: <B90DF52C077C454EB66E7193E2FFEACD61D598@mh-exch01.global.sdl.corp>
Message-ID: <52D636F5.9040806@oxygenxml.com>

Hi Jan,

Thanks for the report, you are right. We'll fix the issue in 15.2.

In the meantime your workspace access plugin extension implementation 
has access to the main JMenuBar and receives callbacks for each added 
toolbar so it could potentially be also used to filter stuff from the 
main menu and toolbars.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/14/2014 5:22 PM, Jan Bevers wrote:
> Hi all
>
> In my integration with oXygen 14 I use a custom Components Validator to
> hide some menu items from the user.
>
> I noticed that in oXygen 15.1 these buttons are not getting hidden
> anymore. I checked my code and  the constructor of my class was not
> getting called anymore when using oXygen 15.1
>
> My plugin.xml contains following entry (works for 14.2, not for 15.1):
>
> <extension type="componentsValidator"
> class="com.sdl.trisoft.oxygen.CustomComponentsValidatorPluginExtension"/>
>
> Was there a change regarding the ComponentsValidator in oXygen 15.1?
>
> Kind regards
>
> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies
> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
> image001
>
>
>
> www.sdl.com
> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature>
>
> *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.
>
> This message has been scanned for malware by Websense. www.websense.com
> <http://www.websense.com/>
>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>


From jbevers at sdl.com  Wed Jan 15 04:44:12 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Wed, 15 Jan 2014 10:44:12 +0000
Subject: [oXygen-sdk] Reading oXygen preferences
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD61D74F@mh-exch01.global.sdl.corp>

Hi

Is there a way to get the value of following oXygen preferences through an API:

*         Checked opened files for file system changes

*         Auto update unmodified editors on file system changes
And a way on subscribing to changes made on those settings?

Kind regards

Jan Bevers | Developer | SDL | Content Management Technologies Division | +32 (0)15 400 970 | jbevers at sdl.com
[image001]
</pre><font face="arial" size="2" color="#736F6E">



<a href="http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature">
<img src="http://www.sdl.com/Content/themes/common/images/SDL_logo_strapline_GCEM_EmailSig_150x68px.jpg" border=0><br><br>www.sdl.com
</a><br><br>

<font face="arial" size="1" color="#736F6E">

<b>SDL PLC confidential, all rights reserved.</b>

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.<BR>
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.<BR>
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.
</font>


This message has been scanned for malware by Websense. www.websense.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140115/fa66d008/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 5556 bytes
Desc: image001.jpg
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140115/fa66d008/attachment.jpg>

From support at oxygenxml.com  Wed Jan 15 05:57:42 2014
From: support at oxygenxml.com (Oxygen XML Editor Support)
Date: Wed, 15 Jan 2014 13:57:42 +0200
Subject: [oXygen-sdk] Reading oXygen preferences
In-Reply-To: <B90DF52C077C454EB66E7193E2FFEACD61D74F@mh-exch01.global.sdl.corp>
References: <B90DF52C077C454EB66E7193E2FFEACD61D74F@mh-exch01.global.sdl.corp>
Message-ID: <52D677B6.7050701@oxygenxml.com>

Hi Jan,

We only have some API to impose certain global preferences but not to 
get the state of certain preferences. We are reluctant to create such 
API because it would mean that a plugin could possibly read passwords 
and other sensitive user data saved in our global preferences.

If you are building the plugin for Oxygen 15.0 or newer maybe you could 
contribute your own CMS specific settings page in the Oxygen 
Preferences->Plugins category page:

> http://www.oxygenxml.com/doc/ug-oxygen/index.html#concepts/optionpage-plugin.html

The Plugins SDK should contain a Java sample class for this called 
"ro.sync.sample.plugin.workspace.CustomWorkspaceAccessOptionPagePluginExtension".

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/15/2014 12:44 PM, Jan Bevers wrote:
> Hi
>
> Is there a way to get the value of following oXygen preferences through
> an API:
>
> ·Checked opened files for file system changes
>
> ·Auto update unmodified editors on file system changes
>
> And a way on subscribing to changes made on those settings?
>
> Kind regards
>
> *Jan Bevers |* Developer *|*SDL *| *Content Management Technologies
> Division *| *+32 (0)15 400 970*|* jbevers at sdl.com
> image001
>
>
>
> www.sdl.com
> <http://www.sdl.com/?utm_source=Email&utm_medium=Email%2BSignature&utm_campaign=SDL%2BStandard%2BEmail%2BSignature>
>
> *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.
>
> This message has been scanned for malware by Websense. www.websense.com
> <http://www.websense.com/>
>
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>


From vrveerar at gmail.com  Thu Jan 16 17:01:15 2014
From: vrveerar at gmail.com (Nathan)
Date: Thu, 16 Jan 2014 15:01:15 -0800
Subject: [oXygen-sdk] Using the Author SDK
Message-ID: <CAAA7NDiF9Wjm43qiZH+ONVC33ocHcF=Ocq2ctvyUOiVbowt=Sg@mail.gmail.com>

Hi,
  I am looking at the Author API to develop some custom actions for our
Oxygen Author implementation. However, going through the javadoc of the API
doesn't strike me as being as the most productive way to know about the
possibilities of the Author API.
  Is there any plan (if something already exists, I would love to be
directed to it) to develop something like this - "
https://code.google.com/p/guava-libraries/wiki/GuavaExplained" for the
Author API?

Thanks,
Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140116/dfd5e0a5/attachment.html>

From support at oxygenxml.com  Fri Jan 17 02:12:20 2014
From: support at oxygenxml.com (oXygen XML Editor Support)
Date: Fri, 17 Jan 2014 10:12:20 +0200
Subject: [oXygen-sdk] Using the Author SDK
In-Reply-To: <CAAA7NDiF9Wjm43qiZH+ONVC33ocHcF=Ocq2ctvyUOiVbowt=Sg@mail.gmail.com>
References: <CAAA7NDiF9Wjm43qiZH+ONVC33ocHcF=Ocq2ctvyUOiVbowt=Sg@mail.gmail.com>
Message-ID: <52D8E5E4.1050509@oxygenxml.com>

Hi,

We are constantly improving our documentation and user feedback is 
always welcomed. We'll take another look at the developer related topics 
and try to structure them more intuitively.

There are several topics in the user guide that should help. Firstly 
there's the Author Developer Guide [1] which is considered the starting 
point. A more advanced API related topic is [2]. Since you already know 
that you want to create custom AuthorOperations there is also a topic 
regarding that: [3]. You can also check our general frequently asked 
questions section[4]. In the authorSDK [5] you can find the source code 
for a SimpleDocumentation framework. In it you can find examples for 
most API interfaces.

[1] http://oxygenxml.com/doc/ug-editor/#topics/author-devel-guide-intro.html
[2] http://oxygenxml.com/doc/ug-editor/#tasks/dg-configure-extensions.html
[3] http://oxygenxml.com/doc/ug-editor/#topics/dg-java-api.html
[4] http://oxygenxml.com/doc/ug-editor/#topics/api_faq_introduction.html
[5] http://oxygenxml.com/download_sdk.html?file=oxygenAuthorSDK.zip

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 17-Jan-14 1:01 AM, Nathan wrote:
> Hi,
>   I am looking at the Author API to develop some custom actions for 
> our Oxygen Author implementation. However, going through the javadoc 
> of the API doesn't strike me as being as the most productive way to 
> know about the possibilities of the Author API.
>   Is there any plan (if something already exists, I would love to be 
> directed to it) to develop something like this - 
> "https://code.google.com/p/guava-libraries/wiki/GuavaExplained" for 
> the Author API?
>
> Thanks,
> Nathan
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140117/2f483d84/attachment.html>

From vrveerar at gmail.com  Fri Jan 17 20:15:53 2014
From: vrveerar at gmail.com (Nathan)
Date: Fri, 17 Jan 2014 18:15:53 -0800
Subject: [oXygen-sdk] Custom action for results in search window
Message-ID: <CAAA7NDiDc2dBPojtH6nYudkH_5ANqT-odB9UeJ-9wmDp6y1Xng@mail.gmail.com>

Hi,
  I would like to add a custom action to items selected in the search
window using the Author API. Is this possible? Where can I find some
information on how to go about doing this?

Thanks,
Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140117/171c291d/attachment.html>

From alex_jitianu at sync.ro  Mon Jan 20 01:16:18 2014
From: alex_jitianu at sync.ro (Alex Jitianu)
Date: Mon, 20 Jan 2014 09:16:18 +0200
Subject: [oXygen-sdk] Custom action for results in search window
In-Reply-To: <CAAA7NDiDc2dBPojtH6nYudkH_5ANqT-odB9UeJ-9wmDp6y1Xng@mail.gmail.com>
References: <CAAA7NDiDc2dBPojtH6nYudkH_5ANqT-odB9UeJ-9wmDp6y1Xng@mail.gmail.com>
Message-ID: <52DCCD42.4040702@sync.ro>

Hi,

Do you want this action in the "Find/Replace" dialog, the "Open/Find 
Resource" dialog or in the "Open/Find Resource View"? Unfortunately, 
neither of them can be customized through the API. Could you also give 
more details about the intended behavior for this custom action so that 
we get a better idea about your use case? Of course, using the existing 
API, you can create your own Search author action. I've added a couple 
of links below that will help you creating such an action ([3] in 
particular).

[1] http://oxygenxml.com/doc/ug-editor/#tasks/addCustomActionHowTo.html
[2] http://oxygenxml.com/doc/ug-editor/#topics/dg-java-api.html
[3] http://oxygenxml.com/doc/ug-editor/#tasks/dg-step-by-step-example.html

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 18-Jan-14 4:15 AM, Nathan wrote:
> Hi,
>   I would like to add a custom action to items selected in the search 
> window using the Author API. Is this possible? Where can I find some 
> information on how to go about doing this?
>
> Thanks,
> Nathan
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140120/734ac5f8/attachment.html>

From vrveerar at gmail.com  Mon Jan 20 15:11:38 2014
From: vrveerar at gmail.com (Nathan)
Date: Mon, 20 Jan 2014 13:11:38 -0800
Subject: [oXygen-sdk] Custom action for results in search window
Message-ID: <CAAA7NDiKJfc_JWsJVx1VJsxvv30QcA_gHUL+F4CCot+QnimMjQ@mail.gmail.com>

Hi Alex,
   I am looking to perform this action on the results of the "Open/Find
Resource" view. So, if a particular "Open/Find Resource" operation
retrieved 5 results in the "Open/Find Resource" results and I am interested
in 3 out of the 5 results, I would like to select 3 out of the 5 and
provide a custom action on right click.
   It looked like there was no way to access to the "Open/Find Resource"
search results from the API so I wanted to check.

Regards,
Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140120/55b859e5/attachment.html>

From vrveerar at gmail.com  Tue Jan 21 21:53:17 2014
From: vrveerar at gmail.com (Nathan)
Date: Tue, 21 Jan 2014 19:53:17 -0800
Subject: [oXygen-sdk] Implementation of AuthorExtensionStateListener
Message-ID: <CAAA7NDhN9mcFk3Y-pqXioB1_XGHPnckoSt20=0E3xREuE+UtOg@mail.gmail.com>

Hi,
  I am using Oxygen 15's inbuilt DITA framework and I would like to
customize it by showing a Swing based form when Oxygen Author has been
opened. This form will be used to set custom variables which can then be
used later on.
  I am planning to do this using the Author API, specifically the
AuthorExtensionStateListener interface (I saw a sample at "
http://www.oxygenxml.com/doc/ug-author/index.html#topics/dg-author-extension-state-listener.html"
in this regard). I presume the next step would be to register an
implementation of AuthorListener (or extend the "AuthorListenerAdapter"
class) within the activate method of the implementation of
AuthorExtensionStateListener interface.
  My questions are as follows:
  a) Is this the best way to implement what I have in mind?
  b) There does not seem to be any Author window event which can be used to
popup the form. I see others for doctypeChanged(), documentChanged etc here
but nothing to record a opening-of-author event.
I feel like I am missing something here and would greatly appreciate some
help. If there is a better way to do this, I am all ears. Just a note, I
cannot use plugins since this has to work for people who use Oxygen Author
standalone and those who use the Author plugin within eclipse.

My current code structure something like this...

File 1:

public class ditaAuthorExtensionStateListener implements
AuthorExtensionStateListener{
....
....

public void activated(...){
// Add author document listeners.
ditaAuthorDocumentListener = new DitaAuthorListener();
authorAccess.getDocumentController().addAuthorListener(ditaAuthorDocumentListener);
}
File 2:
public class DitaAuthorListener implements AuthorListener{

.....
.....
// I am stuck here since I do not find any method which is triggered on
opening Oxygen Author.

Thanks a bunch!
Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140121/4037ab83/attachment.html>

From alex_jitianu at sync.ro  Wed Jan 22 04:55:13 2014
From: alex_jitianu at sync.ro (Alex Jitianu)
Date: Wed, 22 Jan 2014 12:55:13 +0200
Subject: [oXygen-sdk] Implementation of AuthorExtensionStateListener
In-Reply-To: <CAAA7NDhN9mcFk3Y-pqXioB1_XGHPnckoSt20=0E3xREuE+UtOg@mail.gmail.com>
References: <CAAA7NDhN9mcFk3Y-pqXioB1_XGHPnckoSt20=0E3xREuE+UtOg@mail.gmail.com>
Message-ID: <52DFA391.4000300@sync.ro>

Hi,

An AuthorListener is intended to receive notifications about the changes 
in the author node model. Do you want an event when the entire 
application is launched or an event every time a document is open in an 
editor in a running Oxygen Author application? Both could be achieved 
very easily using plugin level API: [1][2]. You could create a plugin 
for Oxygen standalone and use the Eclipse specific plugin support to 
write a small plugin that gets these values from the user in an Eclipse 
environment. This plugin could save these variables using [3][4] so that 
the framework code could have access to them.

If you want to do it from the framework alone then you could just 
present this dialog on 
ro.sync.ecss.extensions.api.AuthorExtensionStateListener.activated(AuthorAccess). 
You might want to invoke this code on a 
javax.swing.SwingUtilities.invokeLater(Runnable) if the editor should be 
initialized before asking the user for those values. If the user must be 
asked once the you could use Oxygen built-in options storage support to 
store these values and the fact that you already asked the user for them 
[5][6].

[1] 
ro.sync.exml.plugin.workspace.WorkspaceAccessPluginExtension.applicationStarted(StandalonePluginWorkspace)
[2] 
ro.sync.exml.workspace.api.PluginWorkspace.addEditorChangeListener(WSEditorChangeListener, 
int)
[3] ro.sync.exml.workspace.api.PluginWorkspaceProvider.getPluginWorkspace()
[4] 
ro.sync.exml.workspace.api.PluginWorkspace.setGlobalObjectProperty(String, 
Object)
[5] ro.sync.ecss.extensions.api.AuthorAccess.getOptionsStorage()
[6] ro.sync.ecss.extensions.api.OptionsStorage.setOption(String, String)

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 22-Jan-14 5:53 AM, Nathan wrote:
> Hi,
>   I am using Oxygen 15's inbuilt DITA framework and I would like to 
> customize it by showing a Swing based form when Oxygen Author has been 
> opened. This form will be used to set custom variables which can then 
> be used later on.
>   I am planning to do this using the Author API, specifically the 
> AuthorExtensionStateListener interface (I saw a sample at 
> "http://www.oxygenxml.com/doc/ug-author/index.html#topics/dg-author-extension-state-listener.html" 
> in this regard). I presume the next step would be to register an 
> implementation of AuthorListener (or extend the 
> "AuthorListenerAdapter" class) within the activate method of the 
> implementation of AuthorExtensionStateListener interface.
>   My questions are as follows:
> a) Is this the best way to implement what I have in mind?
> b) There does not seem to be any Author window event which can be used 
> to popup the form. I see others for doctypeChanged(), documentChanged 
> etc here but nothing to record a opening-of-author event.
> I feel like I am missing something here and would greatly appreciate 
> some help. If there is a better way to do this, I am all ears. Just a 
> note, I cannot use plugins since this has to work for people who use 
> Oxygen Author standalone and those who use the Author plugin within 
> eclipse.
>
> My current code structure something like this...
>
> File 1:
>
> public class ditaAuthorExtensionStateListener implements 
> AuthorExtensionStateListener{
> ....
> ....
>
> public void activated(...){
> // Add author document listeners.
> ditaAuthorDocumentListener = new DitaAuthorListener();
> authorAccess.getDocumentController().addAuthorListener(ditaAuthorDocumentListener);
> }
> File 2:
> public class DitaAuthorListener implements AuthorListener{
>
> .....
> .....
> // I am stuck here since I do not find any method which is triggered 
> on opening Oxygen Author.
>
> Thanks a bunch!
> Nathan
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140122/1ae140db/attachment.html>

From alex_jitianu at sync.ro  Wed Jan 22 09:30:00 2014
From: alex_jitianu at sync.ro (Alex Jitianu)
Date: Wed, 22 Jan 2014 17:30:00 +0200
Subject: [oXygen-sdk] Custom action for results in search window
In-Reply-To: <CAAA7NDiKJfc_JWsJVx1VJsxvv30QcA_gHUL+F4CCot+QnimMjQ@mail.gmail.com>
References: <CAAA7NDiKJfc_JWsJVx1VJsxvv30QcA_gHUL+F4CCot+QnimMjQ@mail.gmail.com>
Message-ID: <52DFE3F8.8070800@sync.ro>

Hi Nathan,

There might be an workaround for you... Using the plugin API you can get 
access to the "Open/Find Resource" view and from there on you can locate 
the JList used to present the results and take a look inside it's model. 
I don't think you can contribute an action to the contextual menu (maybe 
you could remove the mouse listener we use to show the menu and install 
your own instead). Instead, it would be easier to add a new toolbar and 
put an action in it. The code below can be put on the 
applicationStarted() method of an Workspace Access plugin. Hopefully the 
information you can get from the model of the list is enough for what 
your action need to do. Since the method used to get to that information 
is not API I also can't guarantee that the information structure wont 
change in a future Oxygen release.

If you need more information about plugins you can find it starting at: 
http://oxygenxml.com/oxygen_sdk.html#Developer_Plugins

   /**
    * @see 
ro.sync.exml.plugin.workspace.WorkspaceAccessPluginExtension#applicationStarted(ro.sync.exml.workspace.api.standalone.StandalonePluginWorkspace)
    */
   @Override
   public void applicationStarted(final StandalonePluginWorkspace 
pluginWorkspaceAccess) {
     pluginWorkspaceAccess.addViewComponentCustomizer(new 
ViewComponentCustomizer() {
       @Override
       public void customizeView(ViewInfo viewInfo) {
         if 
(MainFrameComponentProvider.OPEN_FIND_RESOURCE.equals(viewInfo.getViewID())) 
{
           JPanel component = (JPanel) viewInfo.getComponent();

           // Search for the list.
           final JList list = searchForList(component);

           JPanel newPanel = new JPanel(new BorderLayout());
           newPanel.add(component, BorderLayout.CENTER);
           JPanel northPanel = new JPanel();
           JButton button = new JButton("Process Selection");
           button.addActionListener(new ActionListener() {
             @Override
             public void actionPerformed(ActionEvent e) {
               int[] selectedIndices = list.getSelectedIndices();
               for (int i = 0; i < selectedIndices.length; i++) {
                 int index = selectedIndices[i];
                 org.apache.lucene.document.Document selValue = 
(org.apache.lucene.document.Document) list.getModel().getElementAt(index);
                   // All the information is located in these fields
                 List<org.apache.lucene.index.IndexableField> fields = 
selValue.getFields();
                 for (Iterator<org.apache.lucene.index.IndexableField> 
iterator = fields.iterator(); iterator.hasNext();) {
                   org.apache.lucene.index.IndexableField indexableField 
= iterator.next();
                   String text = selValue.get(indexableField.name());

                   System.out.println(indexableField.name() + " - " + text);
                 }
               }
             }
           });

           northPanel.add(button);
           newPanel.add(northPanel, BorderLayout.NORTH);

           viewInfo.setComponent(newPanel);
         }
       }

       private JList searchForList(JComponent component) {
         JList list = null;
         if (component instanceof JList) {
           list = (JList) component;
         } else {
           int componentCount = component.getComponentCount();
           for (int i = 0; i < componentCount; i++) {
             Component childComponent = component.getComponent(i);
             if (childComponent instanceof JComponent) {
               list = searchForList((JComponent) childComponent);
               if (list != null) {
                 break;
               }
             }
           }
         }

         return list;
       }
     });
}

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 20-Jan-14 11:11 PM, Nathan wrote:
> Hi Alex,
>    I am looking to perform this action on the results of the 
> "Open/Find Resource" view. So, if a particular "Open/Find Resource" 
> operation retrieved 5 results in the "Open/Find Resource" results and 
> I am interested in 3 out of the 5 results, I would like to select 3 
> out of the 5 and provide a custom action on right click.
>    It looked like there was no way to access to the "Open/Find 
> Resource" search results from the API so I wanted to check.
>
> Regards,
> Nathan
>
>
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-sdk/attachments/20140122/59ce0441/attachment.html>

From radu_coravu at sync.ro  Thu Jan 23 02:35:56 2014
From: radu_coravu at sync.ro (Radu Coravu)
Date: Thu, 23 Jan 2014 10:35:56 +0200
Subject: [oXygen-sdk] [ann] oXygen XML Editor 15.2
Message-ID: <52E0D46C.4070702@sync.ro>

Hi all,

I am happy to announce that a new version of oXygen XML Editor, Author
and Developer is available from our website:

http://www.oxygenxml.com

You can find the release notes and details about the new additions at
http://www.oxygenxml.com/whatisnew15.2.html


 From the developer point of view, we added more API in 15.2:

http://www.oxygenxml.com/whatisnew15.2.html#15.2Extended_API


CSS support for visual editing was vastly improved:

http://www.oxygenxml.com/whatisnew15.2.html#15.2CSS_Support

I wrote more details about the CSS improvements on the Oxygen XML Blog:

http://blog.oxygenxml.com/2014/01/oxygen-152-new-author-visual-editor-css.html


On the visual editing side:

http://www.oxygenxml.com/whatisnew15.2.html#15.2XML_Visual_Editing

We added a new Text Area form control + support to properly render JPEG 
images with CMYK profiles and pluggable support to render PDF images.


We also experimented with embedding the Author Component as a Java 
application inside a Sharepoint web application:

http://www.oxygenxml.com/whatisnew15.2.html#15.2CMS_Integration_and_Connectivity

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


From jbevers at sdl.com  Thu Jan 30 09:41:28 2014
From: jbevers at sdl.com (Jan Bevers)
Date: Thu, 30 Jan 2014 15:41:28 +0000
Subject: [oXygen-sdk] [ann] oXygen XML Editor 15.2
In-Reply-To: <52E0D46C.4070702@sync.ro>
References: <52E0D46C.4070702@sync.ro>
Message-ID: <B90DF52C077C454EB66E7193E2FFEACD62BCFC@mh-exch02.global.sdl.corp>

Hi Radu

I have a small question about following new API:
Actions Provider Access from DITA Map Editor Page
Added the API method WSDITAMapEditorPage.getActionsProvider() to obtain actions defined in the DITA Map Editor Page and mount them to custom controls.

I tried to use this api to attach a listener to the "Find/Find_replace" action but didn't see the before or afterActionPerformed called. It is working for other actions like Redo and Undo as specified in the documentation. But it doesn't seem to do anything for this specific action.

Is there a plan to also support this for the Find/Replace action?

Cheers
Jan
-----Original Message-----
From: oxygen-sdk-bounces at oxygenxml.com [mailto:oxygen-sdk-bounces at oxygenxml.com] On Behalf Of Radu Coravu
Sent: donderdag 23 januari 2014 9:36
To: oxygen-sdk at oxygenxml.com
Subject: [oXygen-sdk] [ann] oXygen XML Editor 15.2

Hi all,

I am happy to announce that a new version of oXygen XML Editor, Author and Developer is available from our website:

http://www.oxygenxml.com

You can find the release notes and details about the new additions at http://www.oxygenxml.com/whatisnew15.2.html


 From the developer point of view, we added more API in 15.2:

http://www.oxygenxml.com/whatisnew15.2.html#15.2Extended_API


CSS support for visual editing was vastly improved:

http://www.oxygenxml.com/whatisnew15.2.html#15.2CSS_Support

I wrote more details about the CSS improvements on the Oxygen XML Blog:

http://blog.oxygenxml.com/2014/01/oxygen-152-new-author-visual-editor-css.html


On the visual editing side:

http://www.oxygenxml.com/whatisnew15.2.html#15.2XML_Visual_Editing

We added a new Text Area form control + support to properly render JPEG images with CMYK profiles and pluggable support to render PDF images.


We also experimented with embedding the Author Component as a Java 
application inside a Sharepoint web application:

http://www.oxygenxml.com/whatisnew15.2.html#15.2CMS_Integration_and_Connectivity

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
_______________________________________________
oXygen-sdk mailing list
oXygen-sdk at oxygenxml.com
http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
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.



This message has been scanned for malware by Websense. www.websense.com


From support at oxygenxml.com  Fri Jan 31 06:43:50 2014
From: support at oxygenxml.com (Oxygen XML Editor Support)
Date: Fri, 31 Jan 2014 14:43:50 +0200
Subject: [oXygen-sdk] [ann] oXygen XML Editor 15.2
In-Reply-To: <B90DF52C077C454EB66E7193E2FFEACD62BCFC@mh-exch02.global.sdl.corp>
References: <52E0D46C.4070702@sync.ro>
	<B90DF52C077C454EB66E7193E2FFEACD62BCFC@mh-exch02.global.sdl.corp>
Message-ID: <52EB9A86.9010101@oxygenxml.com>

Hi Jan,

The contextual menu action called "Find/Replace in Files" which you are 
probably interested in should have the ID "Find/Find_replace_in_files" 
but unfortunately it is not yet present in the list, I will try to fix 
this in the next version.

What you could do right now would be to use the API:

> ro.sync.exml.workspace.api.editor.page.ditamap.WSDITAMapEditorPage.setPopUpMenuCustomizer(DITAMapPopupMenuCustomizer)

and before the pop-up menu is shown, iterate its components and if one
of the JMenuItem's has an action with the ID specified above:

> "WSDITAMapEditorPage.getActionsProvider().getActionID(Object)"

use the API:

> WSDITAMapEditorPage.getActionsProvider().addActionPerformedListener

  to add the listener to it.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 1/30/2014 5:41 PM, Jan Bevers wrote:
> Hi Radu
>
> I have a small question about following new API:
> Actions Provider Access from DITA Map Editor Page
> Added the API method WSDITAMapEditorPage.getActionsProvider() to obtain actions defined in the DITA Map Editor Page and mount them to custom controls.
>
> I tried to use this api to attach a listener to the "Find/Find_replace" action but didn't see the before or afterActionPerformed called. It is working for other actions like Redo and Undo as specified in the documentation. But it doesn't seem to do anything for this specific action.
>
> Is there a plan to also support this for the Find/Replace action?
>
> Cheers
> Jan
> -----Original Message-----
> From: oxygen-sdk-bounces at oxygenxml.com [mailto:oxygen-sdk-bounces at oxygenxml.com] On Behalf Of Radu Coravu
> Sent: donderdag 23 januari 2014 9:36
> To: oxygen-sdk at oxygenxml.com
> Subject: [oXygen-sdk] [ann] oXygen XML Editor 15.2
>
> Hi all,
>
> I am happy to announce that a new version of oXygen XML Editor, Author and Developer is available from our website:
>
> http://www.oxygenxml.com
>
> You can find the release notes and details about the new additions at http://www.oxygenxml.com/whatisnew15.2.html
>
>
>   From the developer point of view, we added more API in 15.2:
>
> http://www.oxygenxml.com/whatisnew15.2.html#15.2Extended_API
>
>
> CSS support for visual editing was vastly improved:
>
> http://www.oxygenxml.com/whatisnew15.2.html#15.2CSS_Support
>
> I wrote more details about the CSS improvements on the Oxygen XML Blog:
>
> http://blog.oxygenxml.com/2014/01/oxygen-152-new-author-visual-editor-css.html
>
>
> On the visual editing side:
>
> http://www.oxygenxml.com/whatisnew15.2.html#15.2XML_Visual_Editing
>
> We added a new Text Area form control + support to properly render JPEG images with CMYK profiles and pluggable support to render PDF images.
>
>
> We also experimented with embedding the Author Component as a Java
> application inside a Sharepoint web application:
>
> http://www.oxygenxml.com/whatisnew15.2.html#15.2CMS_Integration_and_Connectivity
>
> Regards,
> Radu
>
> Radu Coravu
> <oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
> 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.
>
>
>
> This message has been scanned for malware by Websense. www.websense.com
> _______________________________________________
> oXygen-sdk mailing list
> oXygen-sdk at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-sdk
>