Oxygen XML Forum

My guess is that we would always need to parse the targetset (i.e. ${targets}), and the amount of I/O operations are probably the same at this stage, even if we use DocbookLinkTextResolver.

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 only parse ${targets} once and keep it somehow in memory (Maybe a DOM model)

do I understand correctly that I should do the following to put it in use in the extended framework?
1. In Oxygen -> framework configuration, in the Classpath tab, add a reference to the Jar file (i.e. the packed framework);
2. Perhaps go to Extensions tab, and choose {{ro.sync.ecss.extensions.api.link.LinkTextResolver}} for "Link target element finder" under "Individual extensions"?

project_Folder

-custom_frameworks

--dockook5_extension

----dockook5_extension.framework

----link_text_resolver.jar

alex_jitianu wrote: 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 performance penalties. In your customization of an DocbookLinkTextResolver you can keep an additional cache, make sure you only parse ${targets} once and keep it somehow in memory (Maybe a DOM model)

alex_jitianu wrote: 3. Create a class that extends ro.sync.ecss.extensions.docbook.DocBook5ExtensionsBundle and overwrites the methods:
3.1 ro.sync.ecss.extensions.api.ExtensionsBundle#createLinkTextResolver() and returns the extension of DocbookLinkTextResolver that handles the special anchor.
3.2 and ro.sync.ecss.extensions.api.ExtensionsBundle#createElementLocatorProvider() and returns an extension of ro.sync.ecss.extensions.commons.DefaultElementLocatorProvider that handles the special anchor

2. Also add the [OXYGEN_INSTALL_DIR]\frameworks\docbook\docbook.jar to the class path of the project.

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 for that API as well.

Another question is, after I create the new class, is this new class all that I need to pack into a .jar file (and later deploy with the custom framework)?

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

*[xlink|href]:before{

    link: oxy_url(${targets}/b.xml#myAnchor);

 }

 

*[xlink|href]:empty{

    content: oxy_link-text(${targets}/b.xml#myAnchor); /* This doesn't look right to me, but how should oxy_link-text handle the custom anchor? */

 }

• resize Oxygen window,
  refresh Oxygen window, or
  edit something in the DocBook file opened in Author view,