Distributing custom framework with certain alternative CSS styles turned on by default?
Posted: Fri Nov 16, 2018 12:08 am
Hello,
I have a question regarding this page:
https://www.oxygenxml.com/doc/versions/ ... css-styles
The figure "Styles Drop-down Menu in a DITA Document" at the bottom of the page shows that a few alternative CSS styles each has a check mark in front of it, e.g. + Full width, +Hints, etc. That's how the CSS styles in my custom framework looks too.
However, after I distribute this custom framework to others, they don't seem to find the alternative CSS turned on by default, i.e. when they click the +Styles drop-down menu, none of the alternative CSS style shows a check mark in front of it.
Is there something that I can do when sharing the custom framework, to allow others have exactly the same alternative CSS styles "checkmarked", under the +Styles drop-down menu?
Thanks,
Charles
P.S. I did some search and found this thread, which might be somewhat related: topic10621.html However, my use case seems to be a bit different as it is more about how to control the default behavior of the shared framework.
I have a question regarding this page:
https://www.oxygenxml.com/doc/versions/ ... css-styles
The figure "Styles Drop-down Menu in a DITA Document" at the bottom of the page shows that a few alternative CSS styles each has a check mark in front of it, e.g. + Full width, +Hints, etc. That's how the CSS styles in my custom framework looks too.
However, after I distribute this custom framework to others, they don't seem to find the alternative CSS turned on by default, i.e. when they click the +Styles drop-down menu, none of the alternative CSS style shows a check mark in front of it.
Is there something that I can do when sharing the custom framework, to allow others have exactly the same alternative CSS styles "checkmarked", under the +Styles drop-down menu?
Thanks,
Charles
P.S. I did some search and found this thread, which might be somewhat related: topic10621.html However, my use case seems to be a bit different as it is more about how to control the default behavior of the shared framework.