Re: [sphinx-dev] New theme

2010-04-09 Thread Florian Diesch
Georg Brandl  writes:

> Am 16.03.2010 01:01, schrieb Florian Diesch:
>> 
>> Hi!
>> 
>> I'm creating a new theme called "freiburg". You can get it at
>> , a small example is
>> at 
>> 
>> Any feedback is welcome.
>
> Thanks for sharing, looks nice!  If at any time you feel like it's ready
> for merging into trunk, let me know.  You can get writer access then.

Thanks :-) I think it needs some more testing and clean up. Didn't had
much time to spend on it recently...



   Florian
-- 
Any sufficiently advanced bug is indistinguishable from a feature. 
   -- Rich Kulawiec 

-- 
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] Multiple stylings of preformatted text

2010-04-09 Thread Max Battcher

On 4/9/2010 2:34, malthe wrote:

In my document I have two types of text blocks corresponding to user's
text input and output. How do I tell Sphinx to assign a particular
HTML-class to each of them (e.g. "input", "output") such that I may
assign different colors in a CSS stylesheet?


As someone already mentioned, using the .. cssclass:: yourclass before 
the block will work.


Also, if your input/output formats follow an expected, parse-able 
format, you may want to consider writing a Pygments (pygments.org) lexer 
for the format, if one doesn't already exist. Writing a lexer is 
actually reasonably easy and there are plenty of examples to draw from 
in Pygments' source code. That can give you nice syntax highlighting of 
your input/output formats using the .. code-block:: yourlanguage directive.


--
--Max Battcher--
http://worldmaker.net

--
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] Multiple stylings of preformatted text

2010-04-09 Thread TP
On Fri, Apr 9, 2010 at 12:17 AM, TP  wrote:
> On Thu, Apr 8, 2010 at 11:34 PM, malthe  wrote:
>> In my document I have two types of text blocks corresponding to user's
>> text input and output. How do I tell Sphinx to assign a particular
>> HTML-class to each of them (e.g. "input", "output") such that I may
>> assign different colors in a CSS stylesheet?
>>
>> Any hints appreciated!
>>
>> \malthe
>>
>> --
>> 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.
>>
>>
>
> Take a look at the docutils class directive:
> http://docutils.sourceforge.net/docs/ref/rst/directives.html#class.
>

Ooops. I should also have mentioned this:

http://sphinx.pocoo.org/markup/desc.html#dir-class

"New in version 0.4: The standard reST directive class  is now
provided by Sphinx under the name cssclass."

-- 
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: Documenting functions declared with lambda or returned from higher order functions

2010-04-09 Thread Michael Rule
I would be happy even with a variety of hacks : most of these
functions are one-liners. Is there some way to just post the function
definition in the documentation ? Either in the object title or in the
documentation below ? I can do this by hand but then the documentation
does not automatically track changes in the code. Any ideas ?

--mrule

On Thu, Apr 8, 2010 at 9:17 PM, Michael Rule  wrote:
> Something like 80% of this library I am trying to document isn't
> declared with the traditional "def" syntax. I've figured out that
> Sphinx can produce reasonable documentation if I include a
> triple-quote string after the function declaration, but its not
> picking up arguments properly. Is there some way to the nice foo(a,b)
> format you get with def for functions declared as lambda functions ?
> You could even guess curried functions, if foo = lambda x:lambday:x+y
> then you could output foo(x)(y) in the documentation. Anyway, does
> anyone have any good ideas besides re-writing the entire library with
> "def" notation ?
>
> --mrule
>

-- 
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: Problem while generating the latex output

2010-04-09 Thread Guenter Milde
On 2010-04-07, g.bra...@gmx.net wrote:
> Guenter Milde  wrote:
>> On 2010-04-07, Kevin Horn wrote:
>> > On Tue, Apr 6, 2010 at 3:23 AM, Guenter Milde

>> >> Sphinx does not depend on Docutils but forked from it.

> Günter, I'm surprised that you're making such uninformed statements.

I have to realize that I did only look at the surface with Sphinx adding
many elements to the rst syntax, sometimes even incompatible (the ..
class:: directive) and with code duplication (I have to admit that I only
looked at my special field, the LaTeX writer).

> Sphinx is not intended as a replacement for docutils, and it does not
> try to make docutils obsolete.  You should know that by now.  

I accnowledge this with pleasure. I hope that there will remain a
"peacefull coexistence" of these tools, developing into a closer
co-operation or at least coordination.

> Otherwise, don't you think I wouldn't have bothered porting docutils to
> Python 3

I assumed this was just to give Sphinx a clean start,

> or contributing back speedup patches?

while this should have me told otherwise.
...

> Correct.  Sphinx builds upon docutils, and uses as much of docutils as 
> possible, with the LaTeX writer being the only exception ...

Does this mean that I can, e.g. use SVG and SWF vector images in HTML
after installing the Docutils development version without change to
Sphinx? This would be good news indeed.

Thanks for your clarification, 

Günter

-- 
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] Multiple stylings of preformatted text

2010-04-09 Thread TP
On Thu, Apr 8, 2010 at 11:34 PM, malthe  wrote:
> In my document I have two types of text blocks corresponding to user's
> text input and output. How do I tell Sphinx to assign a particular
> HTML-class to each of them (e.g. "input", "output") such that I may
> assign different colors in a CSS stylesheet?
>
> Any hints appreciated!
>
> \malthe
>
> --
> 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.
>
>

Take a look at the docutils class directive:
http://docutils.sourceforge.net/docs/ref/rst/directives.html#class.

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