Re: Docbook framework extension in Oxygen - css styling only partially implemented

Radu Coravu <[email protected]>
Newsgroups gmane.text.docbook.apps
Message-ID <[email protected]>
Hi Brendan,

Maybe you can try to behave more like the client, change computers, get 
a computer with the same operating system as the client's (because maybe 
you used Windows to create the framework and they are using Mac), try to 
do exactly the same steps the client does to install Oxygen on their 
side, take the zipped framework from the email you sent and try to 
install it.
If the problem can be reproduced, then possibly your ".framework" 
configuration file contains some absolute file references which only 
work on your side. Or maybe you have absolute references in your CSSs. 
Or you have Windows-style path separators "\" in certain path references 
and these should all be replaced with "/" which works on all operating 
systems.
If the problem still cannot be reproduced on your side, give the client 
exactly the steps you took on your side and maybe ask for sample XML 
files to test on your side.
If all else fails, you can send to the Oxygen support email address 
([email protected]) the zipped framework and maybe we can take a 
look at it.

Regards,
Radu

Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

On 10/11/2019 7:56 PM, Brendan Martin wrote:
> Hi,
>
>
>
> I developed a DocBook framework extension in Oxygen and had it uploaded
> to our client in a framework archive. The css styling is present, but
> not complete (for example) the font is not what I styled. The customized
> toolbar appears, but buttons ore inactive. They are also not
> context-sensitive (e.g., when you place the cursor in the table).
>
>
>
> I am only the desktop developer (the “content engineerâ€) and I can’t
> debug the client – I will relay any suggestions to them. Any help is
> appreciated.
>
>
>
> Regards,
>
> Brendan
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.