doxygen-users

[Doxygen-users] xml

[Hunter M. <hma...@vi...>]

I know there has been on-going work toward xml output, but I have been
too busy to dig into it. I could have some time on my hands and would
like to see what I can do with the xml aspect of doxygen. I'm not sure
I have the skills but maybe I could somehow help out, if only in
trying to use what's there (if useable).

Could someone give some hints or references? Thanks for any info. 

	hunter

Re: [Doxygen-users] xml

[Hunter M. <hma...@vi...>]

Ok, I found the "XML" option in the config file. It successfully ran
against a codebase that produces about 230 pages of LaTeX output
producing a 1.8 MB xml file.

I will begin working with a smaller case. Is the doxygen.dtd file in
doxygen-1.2.11.1/addon/xmlparse the associated DTD? I'm not an XML
expert, what would be a useful next step? XSLT experiments?

	hunter



On Wed, Oct 17, 2001 at 03:37:25PM -0700, Hunter Marshall wrote:
> I know there has been on-going work toward xml output, but I have been
> too busy to dig into it. I could have some time on my hands and would
> like to see what I can do with the xml aspect of doxygen. I'm not sure
> I have the skills but maybe I could somehow help out, if only in
> trying to use what's there (if useable).
> 
> Could someone give some hints or references? Thanks for any info. 
> 
> 	hunter
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
> 

Re: [Doxygen-users] xml

[Dimitri v. H. <di...@st...>]

On Thu, Oct 18, 2001 at 10:26:00AM -0700, Hunter Marshall wrote:
> Ok, I found the "XML" option in the config file. It successfully ran
> against a codebase that produces about 230 pages of LaTeX output
> producing a 1.8 MB xml file.
> 
> I will begin working with a smaller case. Is the doxygen.dtd file in
> doxygen-1.2.11.1/addon/xmlparse the associated DTD? 

No, it is just something that could be used as a starting point ;-)
Any help on writing a proper DTD is highly welcomed.

> I'm not an XML
> expert, what would be a useful next step? XSLT experiments?

You could try that, I would be interested in the results. 

My priorities w.r.t. XML are:
1) get all the information collected by doxygen in the XML output.
2) write a parser library (xmlparse) that could be used by other 
   C++ programmers as a convenient API for writing new front-ends for 
   doxygen.

Regards,
  Dimitri

Re: [Doxygen-users] xml

[Christian H. <ch...@po...>]

On Thu, Oct 18, 2001 at 09:51:04PM +0200, Dimitri van Heesch wrote:
> My priorities w.r.t. XML are:
> 1) get all the information collected by doxygen in the XML output.

Though I haven't had time lately, I've been planning on writing
another patch to get more info generated in the XML, and also to
provide a config option for generating multiple XML files, just like
with HTML files.

I'll send it when I get a chance to finish it.

Christian

-- 
Christian Hammond         <>  The GNUpdate Project
ch...@po...  <>  http://www.gnupdate.org/
   Save the whales. Feed the hungry. Free the mallocs.

Re: [Doxygen-users] xml

[Hunter M. <hma...@vi...>]

On Thu, Oct 18, 2001 at 09:51:04PM +0200, Dimitri van Heesch wrote:
> On Thu, Oct 18, 2001 at 10:26:00AM -0700, Hunter Marshall wrote:
> > I will begin working with a smaller case. Is the doxygen.dtd file in
> > doxygen-1.2.11.1/addon/xmlparse the associated DTD? 
> 
> No, it is just something that could be used as a starting point ;-)
> Any help on writing a proper DTD is highly welcomed.

After playing with xsl/fop, I think that maybe the DTD structure might
be an area for experimentation. For example, I am finding that the
numbering control in XSLT (<xsl:number>) does not go outside a
sequence of sibling nodes. I suppose some cool XSL hacker could do
it. It's not like LaTeX where you can tap your own custom counter when
you want the next number value in a sequence.

What I mean is that the numbering works well for something like

chap
 sec
  subsec
  subsec
 sec
  subsec
chap
 sec
  subsec

Whereas the doxygen DTD (at a highlevel) looks like

compounddef
 compoundname
 sectiondef
  memberdef (the dtd and the output differ on this)
  memberdef
  memberdef
 sectiondef
  memberdef
 detaileddescriptio

I don't have any suggestions yet. I am just now realizing the impact
of DTD design on the ease of processing. 

	hunter

PS Should this go to doxygen-develop? Or to a smaller group than
doxygen-users?