Thanks for taking the time to check it out, sorry I didn't leave it in
a working state. I've not worked on it for a bit as I was taking time
out to work on another extension and get used to the rst/Sphinx setup.

It is next on my list so I'll get back to it next week. The first
thing I'll do is get it in a state where it actually runs!

>From what I remember it currently reads in the information from the
index.xml file of the doxygen xml output and displays that in a very
basic format but does not yet move on to extracting the details from
the other referenced xml files.

For more direct answers to your questions:
- The project is in early development stage.
- I think it will be a viable option but some issues need to be
overcome like how to easily generating multiple pages without having
to be too explicit in the mark up.
- There is no example of the final expected output, I'm not sure
enough of the systems involved to know fully what to expect.

Cheers,
Michael

On Tue, Mar 17, 2009 at 11:49 AM, rodrigob <[email protected]> wrote:
>
> I'm currently working on the documentation of a large C++ project
> using Sphinx (Doxygen is just not readable enough...).
>
> I was initially planning to do a trick like
> http://www.vlfeat.org/api/index.html
>
> where they split a generated page to use a header and footer for the
> generated doxygen html pages.
>
> However the 'breathe' extensions seems to be a better way of doing
> things.
>
> Could you explain the status of the project ?
> Do you think it is a viable option ?
> Is it somewhere a sample of the expected output ?
>
> Retrieving the current git branch and running the testsuite today
> provides an
>
>>>>>
> breathe/testsuite$ make html
> mkdir -p build/html build/doctrees
> sphinx-build -b html -a -N -d build/doctrees   source build/html
> Extension error:
> Could not import extension breathe (exception: No module named
> indexsuper)
> <<<<
>
> And it seems that indexsuper
> http://google.com/codesearch?hl=en&sa=N&q=indexsuper++lang:python&ct=rr&cs_r=lang:python
>
> is supposed to be provided by your code ?
>
>
> Thanks for your answer.
> Regards,
> rodrigob.
>
> On Feb 8, 1:09 pm, Michael Jones <[email protected]> wrote:
>> For those interested, I've not made much progress, what I have done is
>> summarised by the following two repositories:
>>
>> Sphinx extension:http://github.com/michaeljones/breathe/tree/master
>>
>> Output processing:http://github.com/michaeljones/doxml/tree/master
>>
>> I'm getting into a rhythm of working on it, but it might still be
>> several weeks before something basic is in place.
>>
>> Michael
>>
>> On Mon, Dec 15, 2008 at 11:02 PM, Michael Jones <[email protected]> 
>> wrote:
>> > I'm giving this a whirl, I'll keep this thread updated with progress.
>> > Might not be anything of interest before the new year though. Give us
>> > a shout if you'd like to help out,
>>
>> > Michael
>>
>> > On Sat, Dec 13, 2008 at 11:47 AM, Michael Jones <[email protected]> 
>> > wrote:
>> >> I've not tried, though I believe Dan's suggestion to be the best
>> >> direction to go in, with the one problem that the Doxygen XML output
>> >> is still in development so might well be subject to change.
>>
>> >> I'm still not finding the time I'm afraid.
>>
>> >> Michael
>>
>> >> On Tue, Dec 9, 2008 at 6:10 AM, Dmitriy <[email protected]> wrote:
>>
>> >>> Hi, Michael (and the rest of the Sphinx mailing list),
>>
>> >>> Have you had any luck with this? I would be very interested in using
>> >>> Sphinx to document C++ code.
>>
>> >>> Thanks.
>> >>> Dmitriy
>>
>> >>> On Oct 22, 1:49 am, mpj <[email protected]> wrote:
>> >>>> Hi,
>>
>> >>>> I was wondering if anyone has done any work on some kind of autoclass
>> >>>> equivalent for c++? I thought that using gccxml and pygccxml might be
>> >>>> an avenue worth exploring but I thought I'd check if anyone had put
>> >>>> some more thought into it.
>>
>> >>>> Sphinx is ace, thank you for all the hard work.
>>
>> >>>> Regards,
>> >>>> Michael
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to