Yes. Separating the Javadocs from the source code is definitely not the way I wanted to go. But Sphinx remains my best possible solution for formatting the document I am working on so I will try to make the best of it at this point.
Indeed, I'm not sure now if I should use the autodoc command at all for this - perhaps I will simply format the Javadocs using traditional list and table markup in the RST. Would there be any advantage in using autodoc in this situation if the corresponding Java source code is not readable by Sphinx? On Wed, Feb 24, 2010 at 5:29 PM, Janet Swisher <jmswis...@gmail.com> wrote: > Ouf! That defeats the idea of keeping code and doc comments in the same > place. You'll need to be vigilant to be sure the docs are kept up to date. > > --Janet > > > On Wed, Feb 24, 2010 at 11:40 AM, Chris Collins <xop...@gmail.com> wrote: > >> That confirms my suspicion that I just need to bite the bullet and copy >> and paste my JavaDocs into some rst files. >> >> Thankfully there will be an easier way in the future. Thanks for the >> links, Kevin. >> >> -- > You received this message because you are subscribed to the Google Groups > "sphinx-dev" group. > To post to this group, send email to sphinx-...@googlegroups.com. > To unsubscribe from this group, send email to > sphinx-dev+unsubscr...@googlegroups.com<sphinx-dev%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/sphinx-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-...@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
