There is feature that I think is useful : the export of the rst file
to an html file which contains the speech transcript interspersed with
pictures of the slides. I am thinking at the presentation kind where
the slides are really light in terms of content and really a visual
support to a speaker. The layout for this presentation:
http://www.kroah.com/log/linux/ols_2006_keynote.html is a good example
of what I describe.
Is this layout "supported" or deemed useful in the target rst ->
Please, where are the sources of the rst -> slides converter that is
being discussed if it already exists?
On Mon, Sep 13, 2010 at 11:03 PM, Guenter Milde <milde@...> wrote:
> On 2010-09-13, Stefan Merten wrote:
>> 2 days ago Alan G Isaac wrote:
>>> On 9/10/2010 3:11 PM, Stefan Merten wrote:
>>>> The problem with this approach for me is: It introduces a lot of
>>>> degrees of freedom which is useful re flexibility but not useful re
>>>> easyness and compatibility. The lots of degrees of freedom end up in
>>>> difficult problems you already discussed in this thread.
>>> I think at the most basic level, there is not a conflict.
>> True. But there are different opinions about the right default.
> Which, IMO, speaks for making this a configurable option. The author of
> the writer can then decide on the default for this option.
>>> 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.
> After skimming the prosper, seminar, and beamer manuals and examples,
> the "natural" choice seems a "topic" directive.
>>> For this, we just need to be able to specify as an option
>>> what level of sectioning determines slides. This can be
>>> implemented by decorating every section at the appropriate
>>> header level. (I.e., with a user option.)
>> Well, if you think it is naturally to use sections then why force
>> people to specify an option?
> Only people that do not like the default setting of this option are
> forced to specify it.
>> Convention over configuration would make the natural thing the default
>> and the alternative, often more powerful approach an option.
> Relying on convention without an option would mean that the alternative
> needs a different writer (or at least a different front-end).
>>> Then only additional objects for which slides are wanted
>>> need be decorated by hand. If there are none, then nothing need
>>> be added by hand.
>> Still the option needs to be given by hand.
>> Yesterday Guenter Milde wrote:
>>> On 2010-09-10, Stefan Merten wrote:
>>>> 3 days ago Guenter Milde wrote:
>>> IMO, there are use cases for:
>>> a) slides without heading/title
>> Could be managed by using transitions.
> Then you still need to "style away" the transition in the "printout"
>>> b) more than one (sub) sections on one slide
>> I hardly can imagine slides where you want to have *sections* on a
>> slide but ok.
> c) A document (article/report/script/speakers notes) containing the
> slides very much like graphics or tables -- optionally printed
> or skipped in the "printout" version.
> Seminar, prosper, and beamer all have separate environments for slides
> and separate slide-titling commands.
> The "slides" version, only prints the content of these "slide"/"frame"
> So the question is not only "when to start a new slide" but also
> "what should be on the slide and what not".
>>> which cannot be achieved with Alans: "use the lowest section level"
>> True. I'd even add the use case that not all parts of a slide set have
>> the leaf nodes at the same height. Thus I'd suggest a default rule
>> like "every section containing content beyond comments and nested
> Actually, if going this way (section titles == slide titles, everything
> not explicitely marked "notesonly" goes on a slide), I'd suggest "every
> section (including the title) starts a new slide" as default.
>>>>> and compatibility with other writers,
>> But sections have the right meaning everywhere.
> Not in a document that contains slides (in contrast to a document that
> consists of slides). Otherwise, there would not be any need for a
> distinct "frame" environment, nor for the \frametitle and \framesubtitle
> commands in beamer.
>>>> In my previous mail I proposed a syntax for a pause. My main point is
>>>> that such a syntax must be tiny and inline so it doesn't disturb you
>>>> when you are reading the source.
>>> Are "pauses" really used in-line (inside paragraphs, say)?
>> I don't know whether you ever cared to read the beamer manual but IIRC
>> it is even mentioned there.
> I have to admit that I did not read all 240 pages.
> So let me explain a bit more: my question is not whether it is possible
> to use ``\pause`` in-line, but whether it is widely used in an inline
> context (so that it makes sense to invent an rst inline syntax).
> The line
> LyX: Use the “Pause” style with an empty line to insert a pause.
> on page 80 of the beameruserguide suggests the answer is "no"
> (a LyX style is a block-level element).
>>>> Classes do not have these features. Roles may but roles are for
>>>> regions whereas here you have a point.
>>> The role content (say :pause:`*`) can be ignored by the writer/style.=20
>>> You can define a substitution in your document if this is still too much
>>> "visual clutter".
>> I can't. The problem with a substitution is that I can not substitute
>> an empty string - at least I found no solution for this. But that is
>> what would be needed: A markup recognized by the writer which can be
>> defined as a substitution ending up as an empty string. Any ideas?
>>> With the latex2e writer, you can already convert a :pause: role into a
>>> ``\pause`` command (ignoring the content) by defining a \DUrolepause
>>> macro in the preamble or style sheet.
>> This breaks compatibility with other writers since even if they are
>> able to handle the :pause: role they should not ignore the content.
> IMO, they should. The "dummy" pause role should simply be ignored.
> 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.
> The effort to do this is similar to the effort needed to hide the
> transition element.
> However, I would prefer an "incremental" class argument for lists (and
> maybe also complete slides -- meaning to pause between every paragraph).
>>>> *If* we really need the flexibility here then I'd prefer a convention
>>>> over configuration approach. By default the sectioning is the lead but
>>>> you may use special classes like you suggested to ignore the section
>>> Than make your favourite setting the default.
>> Which would be a configuration over convention approach. So far I
>> don't need to tweak the defaults in reStructuredText
> You will not need to tweak the defauls as long as you code the writer
> (or backend) with your preferences as default or convince the author to
> do so.
>> which also makes documents unportable.
> This is why I propose a "settings" directive, but this is a different
> BTW: did you try whether a re-definition of \section commands or the the
> \AtBegin... commands provided by beamer could be used to make slides with
> the standard latex2e writer and a custom preamble/style-sheet?
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing
> Docutils-users mailing list
> Please use "Reply All" to reply to the list.