From: Stefan M. <sm...@oe...> - 2010-09-20 17:09:35
|
Hi Guenter! 2 days ago Guenter Milde wrote: > On 2010-09-16, Stefan Merten wrote: >>>>> On 9/10/2010 3:11 PM, Stefan Merten wrote: >>>>> The idea was that objects that should generate a slide should >>>>> be decorated with a ``slide`` class. >>>>> Naturally we want to be able to write documents for slides >>>> ^^^^^^^^^ >>>>> where sub(sub)sections are automatically used as slides. >>> =20 >>> After skimming the prosper, seminar, and beamer manuals and examples, >>> the "natural" choice seems a "topic" directive. > >> Fair enough. But for reST users this is probably not very "natural". >> Also topic directives imply no navigation as section headers do. > > I just want to point out that it depends on the context what some-one > considers "natural". I see. Well, I'm doing this effort to make reST even more useful than it is. Insofar my effort addresses users already familiar with reST and thus what is "natural" to them should be the guiding line. >> I'd say that these are very special cases. I agree that it would be >> nice to have solutions for this but IMHO that would be in the 20% >> region of the 80:20 rule. > > Currently, I see it rather as 2:1 .... Well, AFAICS all slide writers so far followed the approach that no special adornment is necessary and sections are fine to delimit slides. This means a lot to me. >>>> .... Thus I'd suggest a default rule >>>> like "every section containing content beyond comments and nested >>>> sections". >>> =20 >>> Actually, if going this way (section titles =3D=3D slide titles, everythi= >> ng >>> not explicitely marked "notesonly" goes on a slide), I'd suggest "every >>> section (including the title) starts a new slide" as default. > >> But then you have empty slides for top level sections. This is >> probably not what you want. > > No, I have a big title on the slide. Keeping my suggestions about navigation slides in mind that would be another type of navigation slide. I could imagine an option like --navigation=<type> where <type> gives the type of navigation you want with the default of ``none``. >>> I don't know about rst2pdf and the odtwriter, but both the html4css1 and >>> the latex2e writer enable you to style a custom role in a way that its >>> content is ignored. This can be done either in a style-sheet or (with the >>> "raw" directive) in the document or an included file. > >> One of my main use cases for reST is to use it in things like Plone or >> MoinMoin. In such environments you don't have the option to do such >> things. Please take this into account. > > Is the "raw" role blocked there? This is typically the case. Indeed I need to change my |p| substitution for these environments whereas (my) `rst2beamer` worked fine with it :-( . Well, if David accepts my patch then this can be solved differently. Grüße Stefan |