RE: DBus XML Documentation Parser

"Gary Partis" <[email protected]>
Newsgroups gmane.comp.freedesktop.dbus
Message-ID <[email protected]>
Hi all

As no one had answered my original query; I had a dig around the Python
scripts for dbus codegen.

I'd like to do the following to allow for text macros in dbus XML files
:

1. within the Dbus XML, have a   <macro name="foo" value="bah bah black
sheep"/>   type settings for at the beginning of the <node> section.

2. specify the macro name within annotation sections as &foo; but the
"&" will need to be &amp; for general XML compatability.

3. the resultant docbook output will need the <macro> sections output as
ENTITY sections. This requires a change to Python scripts.

4. using a tool such as docbook2pdf will generate a file with the macro
expansion complete.

It will not affect any existing Dbus XML files?

Does anyone have a problem with this?

Cheers

Gary
 

________________________________

From: dbus [mailto:[email protected]] On Behalf Of Gary
Partis
Sent: 09 December 2016 13:39
To: [email protected]
Subject: DBus XML Documentation Parser


Hi all
 
I am annotating my XML dbus definition files and have many
methods/properties/signals using the same parameter names (for example
"outputstate"). Instead of copy-n-pasting every instance of the
descriptive text for a method parameter, I would like to use some form
of macro/substitution system.
 
I have seen some more generic examples of this on the web for XML; but
nothing specifically for dbus definitions. Indeed, the examples I have
tried do not appear to work.
 
Does the gdbus-codegen application understand any particular form of
macro/substitution?
 
Many thanks in advance,
 
Gary
_______________________________________________
dbus mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dbus
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.