[sphinx-dev] Re: FYI: different layout example

2010-02-09 Thread Felix Hummel
I like yours alot, Florian. What exactly did you modify and would you
be so kind to share?

  Felix

On 8 Feb., 13:25, Florian Diesch die...@spamfence.net wrote:
 Schollii oliver.schoenb...@gmail.com writes:
  For those interested in a somewhat different layout than one of the
  two default ones, I have played around with the layout.html and CSS
  and the result can be seen athttp://pubsub.sourceforge.net.

 http://www.florian-diesch.de/doc/python-und-glade/online uses a slightly
 modified version of the agogo theme included with the Sphinx 1.0
 development version.

    Florian
 --
 http://www.florian-diesch.de/software/xxgamma/

-- 
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.



[sphinx-dev] Re: customizing data member rendering

2010-02-09 Thread Václav Šmilauer
I got to some solution today, although it is a hack:

1. A function connected to autodoc-process-signature asks for __doc__
of the object it receives; __doc__ is scanned for the :ydefault:`(.?
*)` role. If it is found, it's added to the signature of that
attribute.

2. The :ydefault: role itself is defined to expand to nothing, so that
it doesn't end in both signature and docstring.

It looks like this: 
https://www.yade-dem.org/sphinx/yade.wrapper.html#yade.wrapper.CpmMat
. Sweet.

Cheers, Vaclav

 The classes are exposed from c++ via boost::python. Attribute's
 docstrings are supplied by me. I suppose the help(..) function returns
 raw docstrings, so below is parts of output from help(CpmPhys).
 The :ydefault: roles specifies default value, [m²] is units obviously
 (that could be changed to :yunit:`m²`, if necessary).

-- 
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.



Re: [sphinx-dev] Non-trivial conditional include with ifconfig?

2010-02-09 Thread Fernando Perez
Hi Kevin,

On Fri, Feb 5, 2010 at 11:58 AM, Kevin Dunn kgd...@gmail.com wrote:
 That could be it.  I use the 1.00 version from hg because of a bug in
 prior versions with  and  symbols that appear in source code
 with LaTeX output.

Did you actually build these and got the expected output?  I updated
sphinx to hg trunk, and even though now your approach doesn't give me
any errors, it simply won't produce any output for that section.

For now I've settled instead on using:

.. only:: instructor

   .. toctree::

  bessel_sol

where the _sol file can then contain normal markup.  It's a bit silly
as those _sol files end up sometimes being two-liners, so it would be
nice to have a fully clean solution to this.

In any case, many thanks for your help.

 By the way, thanks for IPython.

My pleasure!

Cheers,

f

-- 
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.



Re: [sphinx-dev] Non-trivial conditional include with ifconfig?

2010-02-09 Thread Fernando Perez
On Tue, Feb 9, 2010 at 10:52 PM, Fernando Perez fperez@gmail.com wrote:
 Did you actually build these and got the expected output?  I updated
 sphinx to hg trunk, and even though now your approach doesn't give me
 any errors, it simply won't produce any output for that section.

Scratch that! Your solution does work, thanks!  As I went back to
update sphinx and try again, I forgot about the small limitation of
only being allowed to start a new section level, not continuing with
another section header at the same level as the text before.

So in summary, with that minor limitation, your approach does work,
sorry for the noise.  If one truly needs the conditional text to
include more sections as the same level as the text before, I guess
the toctree call is the only one I can think of for now, but it does
the job.

Regards,

f

-- 
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.