On 03/20/2013 08:02 PM, Tyrin Avery wrote:
I'm trying to upgrade from 5.1 to 5.5 (because I was really happy to see your
fix to list steps). Unfortunately, we've customized our interface and the
customization mechanism seems to have changed.
Our customizations are in three files that I replace in the DITA plugin:
common.imp, topic.css, and map.css.
The customizations are pretty simple, for example, I have the following text
in the map.css for the DITA plugin:
@property-value open-file()
command-button(icon, square,
color, blue
command, "XXE.open",
parameter, xpath("resolve-uri(@href)"));
common.imp is not the work of XMLmind. The above code is not the work of
XMLmind.
However, the above code, if properly integrated into our DITA CSS
stylesheets, works fine in XXE v5.5.
In a nutshell, this integration works as follows:
1) Insert this declaration at the very end of the stylesheet (e.g.
XXE_install_dir/addon/config/dita/css/topic.css):
---
@property-value open-file()
command-button(icon, square,
color, blue
command, "XXE.open",
parameter, xpath("resolve-uri(@href)"));
---
2) After that, add one or more CSS rules making use of this declaration:
---
link[href]:before,
xref[href]:before {
content: open-file() " ";
}
---
More information in:
http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/prop-value.html
This lets me open files in my ditamaps directly. I have something similar in
the topic.css that lets me open files from my cross-references directly. This
is functionality that is present in every other word processing tool for
technical writers that I have ever used. When I was introduced to XMLMind, it
was by someone whose department had also customized XMLMind in the same way.
XXE v5.5 can do that without any customization. Simply the user
interface for doing that is not a inline blue square button in the stock
XXE.
I can't migrate to the new version without this functionality.
I'm sorry but we cannot help you migrate your customization from XXE
v5.1 to v5.5. This is out of the scope of the support we provide to our
customers. Please ask the person who implemented the customization in
v5.1 to do exactly the same thing in v5.5.
Can you tell me how you changed the customization mechanism so I can get it to
work with the new version? This functionality was user-visible to me, because I
was using it. If it isn't in your changes file, then it's an oversight.
We have not changed the customization mechanism in any way. If you find
that we have changed the customization mechanism in v5.5, then please
report this as a bug.
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
