OK, I have just sent an email with the source code to support@oxygenxml.com . Looking forward to your suggestions. Thanks!

Hi Alex, I have been able to extend the DocbookLinkTextResolver class, let it expand the editor variable {targets} and parse this target database XML, look up the nodes we need, and return the text. I am using the Java DOM XML parser and XPath for looking up the nodes. It is returning the correct te...

Hi Alex,

Yes exactly, the ${targets} variable is defined inside preferences.

The expandEditorVariables code you provided is very helpful. And yes, I think I have enough information to build the URL now. Thanks again for the help! Really appreciated.

Charles

Hi again Alex, I've run into a few more questions; can you please help again? 1. The first step is to define a custom anchor. On the link property you should specify an URL with an anchor that contains everything needed to compute, later on, the target Do you mean that in the CSS, I should write som...

Hi Alex,
Thanks for the clarification! This is very helpful.

Charles

Hi Alex, Yes, I see the samples directory, as well as DocbookLinkTextResolver.java and DocBook5ExtensionsBundle.java in their respective sub-folders now. ro.sync.ecss.extensions.api.ExtensionsBundle is not present there but, if you have the sample Maven project, then Maven will bring the source code...

The current cache maps a node to the resolved linked text. If you have a document that contains many link nodes (like you mentioned in the first post) to the same ${targets}, Oxygen will still parse the ${targets} document once for every link. Afterwards, the cache will kick in and there will be no...

Hi Radu,
Thanks for the information!

Charles

Hello, We are using Oxygen Author and Oxygen Editor version 20.0. Currently, as mentioned on this page, https://www.oxygenxml.com/oxygen_sdk/download.html "The API distributions listed in this page are compatible with the Oxygen version 20.1." Are they compatible with the Oxygen version 20...

Hi Sorin,

Yes, this looks to be a great option! Thanks for the help.

Charles

Hi Sorin, Thanks for your reply. My use case is, when the XIncluded doc content is in XMLs under certain file directories, I'd like to prevent the Oxygen users from following the xi:include links to open and edit them. One option would be to customize the CSS like this: xi|include[href^="urn:my...

We have a use case where we would like to customize the warning messages displayed in Oxygen, when a user clicks on a link that cannot open. Currently the message is: Description: :Cannot open the link. The URL is not specified. Severity: Warning To change the text in the "Description" fie...

Hello, On this page https://www.oxygenxml.com/oxygen_sdk/download.html It is mentioned that "In case your build system is not based on Maven, you can download the package with all the Oxygen SDK jar files..." Are there instructions on using the Oxygen SDK in a a build system not based on M...

It seems like that somehow I didn't reply to the thread... Just wanted to say that I really appreciated the help!

Hi, Thanks Alex, for confirming that plugin is not an option. Then most likely we'll go with this approach when deploying the extended framework, "Distribute the extended framework along with a project", as mentioned in this page: https://www.oxygenxml.com/doc/versions/19.1/ug-editor/topic...

Hi again, Can I ask some more questions, about deploying the customization discussed earlier (i.e. keeping a cache for visited targetsets): - Would it work the best if I make it a plugin, or would you recommend some other approaches? - To deploy the customization, should I follow the instructions on...

Hi Alex, Sorry for my delayed reply - and thanks for adding an issue for the enhancement. Our use case is similar to the one described in [url]Inserting an olink in DocBook Documents[/url], but we have some customization on top of it. I will send some sample files to your email address. Thanks! Char...

Thanks Alex! If you have a document that contains many link nodes (like you mentioned in the first post) to the same ${targets}, Oxygen will still parse the ${targets} document once for every link. In your customization of an DocbookLinkTextResolver you can keep an additional cache, make sure you on...

Hi Alex and Radu, Excellent, the information is really helpful. Thanks again. Do I understand correctly that even though DocbookLinkTextResolver keeps a cache, when loading the DocBook XML that contains links, the performance would be identical whether we use DocbookLinkTextResolver or doc() and oxy...

Hi Radu, Thanks for your help! Sorry I didn't reply sooner. Yes, it makes perfect sense that avoiding the use of oxy_xpath() and doc() could give us a boost in Oxygen performance. I would like to try using oxy_link-text() for populating the value of CSS "content" property. Could you help w...

Hi, I notice that if the CSS custom funtions like oxy_url() and oxy_xpath() are used for resolving links in DocBook5, something like: link:empty{ content:oxy_xpath(oxy_concat('doc("', oxy_url('${pdu}/', 'a.xml'), '")//@val')) !important; } it works, but apparently when it is turned on Oxyg...