From: Guenter M. <mi...@us...> - 2010-09-07 20:53:21
|
On 2010-09-07, Alan G Isaac wrote: > On 9/7/2010 6:19 AM, Guenter Milde wrote: >> class argument based approach to slides with reStructuredText >> ------------------------------------------------------------- >> Objects can be "decorated" with special class arguments: >> newslide >> place this object on a new slide >> newoverlay >> place this object on a new "overlay" (which gives the appearance of >> incremental exposure of a given slide). >> notesonly >> do not place this object on a slide (i.e. ignore when producing slides) >> (Can be achieved without changes to Docutils via the >> strip-elements-with-class setting). >> slidesonly >> do not place this object in the notes (i.e. when generating >> standard HTML/LaTeX/PDF output for the handout or notes). >> (Can be achieved without changes to Docutils via the >> strip-elements-with-class setting). >> --slide-section-level=N >> Add "newslide" to all section headings of level N. >> which, with N==1, would result in the current rst2s5 behaviour. ... > I propose as a slide-writer default ``--slide-section-level=0`` > to mean that the last subsection level present in the document > is the slides level. Actually, I would rather use the special string "last" in this case. To me, ``slide-section-level: 0`` would mean no automatic adding of the "slide" class argument to any section level. And I would use this as default (but we don't need to argue about defaults, as these can be easily changed in the config file). > Why not just use 'slide' and 'overlay' > (instead of 'newslide' and 'newoverlay') > unless those are likely name conflicts? I do not insist (but see below). > I'm not sure how 'overlay' would work. In the good old times, an 'overlay' would be a slide that is layed on top of the last slide on the overhead projector, so both contents are visible. In a video-presentation, the PDF of the next slide should show the content of the last slide + the content of the overlay(s). In beamer this is implemented by the macro \pause. > An addition: > I think it is important to be able to tag lists (at least) > as say 'incremental', to signal to the writer to generate > a sequence of overlays. You are right, it might be necessary/sensible to have an additional class argument "incremental", so that :: .. class:: overlay #. first #. last would be added in one step, while :: .. class:: incremental #. first #. last would be added item-wise. > A problem (?): > What happens if a container is labeled a slide and so is one of its > contained objects? (E.g., a section and a subsection?) * A new slide will start and its content is the contained object (this is the reason I called the class argument "newslide"). However, decided yet what should happen if the next contained object does not have the "slide" (or "newslide") class. Possible procedures: a) put on another slide (thought as continuation of the slide of the containing object), b) just continue the current slide, c) ignore (as the slides of both the containing object and the preceding object are closed). Or have both, "slide" and "newslide": slide: Place the content of the labeled object on a slide or (if it does not fit or there is a "manual slide-break") a set of slides. newslide/nextslide/break-slide/slide-break: "manual slide-break", start a new slide, ignored if there is no slide to split. In order to find an optimal set of class arguments and rules, one would have to survey existing slide-making applications (beamer, prosper, powerdot, S5, ..., powerpoint) and map the available "knobs" and macros to a consistent rst syntax. > The ``--slide-section-level=N`` option is the most pressing change. > If this just decorates with say 'slide', which makes recognition > of this class the most pressing change for slide writers. > It would be great if all slide writers handled at least this. > I believe this would be trivial for rst2pdf and rst2beamer (pypi). I will stay with Beamer in LyX. Günter |