From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Beamer support in Org-mode Date: Thu, 10 Dec 2009 12:28:42 -0500 Message-ID: <18166.1260466122@gamaville.dokosmarshall.org> 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> Reply-To: nicholas.dokos@hp.com Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NImpn-0004XE-NC for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 12:29:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NImpi-0004RU-I2 for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 12:29:46 -0500 Received: from [199.232.76.173] (port=43355 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NImpi-0004RD-7k for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 12:29:42 -0500 Received: from vms173001pub.verizon.net ([206.46.173.1]:53910) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NImpi-0006vK-JA for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 12:29:42 -0500 Received: from gamaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KUG009865R3EKB0@vms173001.mailsrvcs.net> for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 11:25:52 -0600 (CST) In-reply-to: Message from Darlan Cavalcante Moreira of "Thu, 10 Dec 2009 13:50:52 -0300." <4b2126f1.1408c00a.0695.3065@mx.google.com> 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: Darlan Cavalcante Moreira Cc: Org Mode , Carsten Dominik Darlan Cavalcante Moreira wrote: > At Thu, 10 Dec 2009 17:09:33 +0100, > Carsten Dominik wrote: > > > > > > On Nov 26, 2009, at 7:29 PM, Darlan Cavalcante Moreira wrote: > > > > > > > > > > > I usually make my presentations in beamer as below. > > > ,---- > > > | \begin{frame} > > > | \frametitle{This is the frametitle} > > > | \begin{itemize} > > > | \item Some information > > > | \begin{itemize} > > > | \item Some information in a subitem > > > | \end{itemize} > > > | \item more information > > > | \item more information \note[item]{This is a note about this > > > item} > > > | \end{itemize} > > > | \end{frame} > > > `---- > > > > > > Therefore, I think a simple solution is just writing the \note > > > command directly > > > in org that would then be passed to beamer. In org-mode the same > > > slide would be > > > > > > ,---- > > > | * This is the frametitle > > > | - Some information > > > | - Some information in a subitem > > > | - more information > > > | - more information \note[item]{This is a note about this item} > > > `---- > > > > > > This avoids cluttering the org file and since the item (including > > > the note) will > > > probably span more then one line, then just leaving notes like this > > > will allow > > > hiding everything with the outline capabilities of org-mode. If a > > > subtree is > > > used this would probably not be possible. > > > > > > The "item" option in the note command is used in beamer to number > > > the notes (I > > > myself always want this). > > > > > > Of course that if everyone else like to put the notes at the end of > > > the frame > > > then a subtree with all the notes makes sense. Beamer does not > > > impose where the > > > notes should be inside the frame and I can reeducate myself to put > > > them inside a > > > subtree, but I'd like to leave the notes near the items they are > > > related to, if > > > possible. > > > > 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? > 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. I've done a handful of presentations using org/beamer and they have all been written specifically for exporting to beamer. In most cases, I've had to manipulate the LaTeX output to get what I want (but at least part of that was because of my own stupidity: my mapping from org to beamer was much more limited than it had to be - unfortunately, I've not had the time to go back and rework a presentation in light of what I now know, so I still can't be much help to say what works and what doesn't). Given that I only export the presentation to beamer, I'm actually happy with Darlan's solution. I hope to try it over the Christmas break and report back. 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