From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scot Becker Subject: Re: Beamer support in Org-mode Date: Thu, 10 Dec 2009 21:05:29 +0000 Message-ID: References: <6A790953-D036-4BAE-8833-E5B343A15331@gmail.com> <23189.1259253052@gamaville.dokosmarshall.org> <8F9C582F-F254-4FF7-A22B-E3D90081D380@gmail.com> <4b0ec920.0407c00a.1a73.1d20@mx.google.com> <4b2126f1.1408c00a.0695.3065@mx.google.com> <18166.1260466122@gamaville.dokosmarshall.org> <4B215ECD.3070703@comcast.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1558201348==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NIqCz-0001sl-K4 for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 16:05:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NIqCu-0001kD-Hb for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 16:05:57 -0500 Received: from [199.232.76.173] (port=46718 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NIqCu-0001k2-Cw for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 16:05:52 -0500 Received: from mail-ew0-f224.google.com ([209.85.219.224]:61615) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NIqCt-0004J0-HY for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 16:05:51 -0500 Received: by ewy24 with SMTP id 24so312673ewy.26 for ; Thu, 10 Dec 2009 13:05:50 -0800 (PST) In-Reply-To: <4B215ECD.3070703@comcast.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Mark Elston Cc: Org Mode , Carsten Dominik --===============1558201348== Content-Type: multipart/alternative; boundary=0015174bdc8cfe38e4047a662b82 --0015174bdc8cfe38e4047a662b82 Content-Type: text/plain; charset=ISO-8859-1 For what it's worth, my preparation style would follow Mark's. Chart the flow of what I want to say in org, ideally using whatever hierarchy I need to do it, then export the outline and essential detail for beamer-and/or-handouts. I'd keep the teaching notes to myself (and keep them part of the same outline) if there was a way to do it. I'm happy to use the \notes{} proposal until the org-hive figures out if something more elegant can be done. Scot On Thu, Dec 10, 2009 at 8:49 PM, Mark Elston wrote: > I have been following this discussion with some interest as it may > provide the basis for something I am interested in doing as well. > I hope my discussion doesn't muddy the waters too much... > > Nick Dokos wrote: > >> Darlan Cavalcante Moreira wrote: >> >> At Thu, 10 Dec 2009 17:09:33 +0100, >>> Carsten Dominik wrote: >>> >>>> ... >>>>> >>>> I still don't have any better ideas than this to represent notes >>>> in Org for beamer presentations. Just writing \noe{...} as you >>>> suggest will certainly work - the disadvantage is that this does >>>> not make a lot of sense when exporting to other formats. >>>> >>>> One option would be to turn all those notes into footnotes >>>> for other export..... >>>> >>>> I'd really be interested to get more input on this issue. >>>> >>>> - Carsten >>>> >>>> Maybe it is better to simple ignore notes when exporting to other >>> formats. >>> >>> For me notes in beamer are useful only to give me an idea of what I >>> intend to >>> talk about in the presentation and help me training for the presentation. >>> They >>> are not really "part of the final exported document" and sometimes I put >>> a lot >>> of information in them (possible in a different language from the >>> presentation). >>> >>> Also, the contents in notes can be anything such as a table or a figure. >>> This >>> obviously would result in an error if or if org tried to put them into a >>> footnote when exporting to other formats. >>> >>> Therefore, the question is has anyone here any interest in notes when >>> exporting >>> to other formats or do they only make sense when exporting to beamer? >>> >>> > My case is similar. I teach a class each week and, so far, have created > two documents; a set of handouts and my notes for teaching. Generally > these documents start from the same original and I modify and expand the > notes I use for teaching while leaving the handouts a smaller doc for > those in the class to take their own notes from. > > I don't use beamer as the handouts tend to be 6-8 pages of 'normal' text > as it is and my teaching notes are usually far larger. I don't want to > manipulate a stack of paper while teaching. > > > >> For me, notes are rather important: in addition to reminding me what to >> say, they are essentially a second level to the presentation (and I >> always include them in any handouts). Somebody who has a vague interest >> in the subject can look at the slides. If they want to go into it a bit >> deeper, they can look at the notes. >> > > My case is similar but I don't 'expose' my teaching notes to the > students for a variety of reasons. > > >> ... >> >> So unless somebody comes up with a really good idea, delaying any >> org-specific implementation might be the best way forward: it would save >> wear-and-tear on Carsten, allow the rest of us to catch up and gather >> some experience and perhaps come up with better ideas on how to handle >> this. >> >> Nick >> >> > I guess my request is similar to what has been discussed above in that I > would *very* much like to maintain handouts and teaching material in the > same file and then export it to two different files as necessary. This > would make my job a lot easier to manage. I could decide which tables, > figures, text, etc are common to both docs and which are just for me and > everything happens automatically behind the scenes. > > Beamer output is not critical for me (or even necessarily desired) right > now but I would like a way of marking some text for 'limited' export. > Using a special notation is not a problem if it gives me the ability to > maintain a single document that I can export to two different LaTeX/PDF > docs. > > Mark > > > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > --0015174bdc8cfe38e4047a662b82 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable For what it's worth, my preparation style would follow Mark's.=A0 C= hart the flow of what I want to say in org, ideally using whatever hierarch= y I need to do it, then export the outline and essential detail for beamer-= and/or-handouts.=A0 I'd keep the teaching notes to myself (and keep the= m part of the same outline) if there was a way to do it.=A0 I'm happy t= o use the \notes{} proposal until the org-hive figures out if something mor= e elegant can be done.

Scot
=A0

On Thu, Dec 10, 2009 at = 8:49 PM, Mark Elston <m_elston@comcast.net> wrote:
I have been following this discussion with some interest as it may
provide the basis for something I am interested in doing as well.
I hope my discussion doesn't muddy the waters too much...

Nick Dokos wrote:
Darlan Cavalcante Moreira <darcamo@gmail.com> wrote:

At Thu, 10 Dec 2009 17:09:33 +0100,
Carsten Dominik <carsten.dominik@gmail.com> wrote:
...
I still don't have any better ideas than this to represent notes
in Org for beamer presentations. =A0Just writing \noe{...} as you
suggest will certainly work - the disadvantage is that this does
not make a lot of sense when exporting to other formats.

One option would be to turn all those notes into footnotes
for other export.....

I'd really be interested to get more input on this issue.

- Carsten

Maybe it is better to simple ignore notes when exporting to other formats.<= br>
For me notes in beamer are useful only to give me an idea of what I intend = to
talk about in the presentation and help me training for the presentation. T= hey
are not really "part of the final exported document" and sometime= s I put a lot
of information in them (possible in a different language from the
presentation).

Also, the contents in notes can be anything such as a table or a figure. Th= is
obviously would result in an error if or if org tried to put them into a footnote when exporting to other formats.

Therefore, the question is has anyone here any interest in notes when expor= ting
to other formats or do they only make sense when exporting to beamer?


My case is similar. =A0I teach a class each week and, so far, have created<= br> two documents; a set of handouts and my notes for teaching. =A0Generally these documents start from the same original and I modify and expand the notes I use for teaching while leaving the handouts a smaller doc for
those in the class to take their own notes from.

I don't use beamer as the handouts tend to be 6-8 pages of 'normal&= #39; text
as it is and my teaching notes are usually far larger. =A0I don't want = to
manipulate a stack of paper while teaching.



For me, notes are rather important: in addition to reminding me what to
say, they are essentially a second level to the presentation (and I
always include them in any handouts). Somebody who has a vague interest
in the subject can look at the slides. If they want to go into it a bit
deeper, they can look at the notes.

My case is similar but I don't 'expose' my teaching notes to th= e
students for a variety of reasons.


...

So unless somebody comes up with a really good idea, delaying any
org-specific implementation might be the best way forward: it would save wear-and-tear on Carsten, allow the rest of us to catch up and gather
some experience and perhaps come up with better ideas on how to handle
this.

Nick


I guess my request is similar to what has been discussed above in that I would *very* much like to maintain handouts and teaching material in the same file and then export it to two different files as necessary. =A0This would make my job a lot easier to manage. =A0I could decide which tables, figures, text, etc are common to both docs and which are just for me and everything happens automatically behind the scenes.

Beamer output is not critical for me (or even necessarily desired) right now but I would like a way of marking some text for 'limited' expor= t.
Using a special notation is not a problem if it gives me the ability to
maintain a single document that I can export to two different LaTeX/PDF
docs.

Mark




_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

--0015174bdc8cfe38e4047a662b82-- --===============1558201348== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1558201348==--