From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: Beamer support in Org-mode Date: Mon, 21 Dec 2009 05:50:26 -1000 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> <78CCC120-4A39-4A85-A659-CCDC71EF5CEA@tsdye.com> <4B216FF8.3090101@comcast.net> <20270.1260487865@gamaville.dokosmarshall.org> <4B2188F1.8020307@comcast.net> <90577D02-ACC2-4149-9E38-93FC66FFD403@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMkWv-0002O4-Oq for emacs-orgmode@gnu.org; Mon, 21 Dec 2009 10:50:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMkWq-0002E2-Co for emacs-orgmode@gnu.org; Mon, 21 Dec 2009 10:50:41 -0500 Received: from [199.232.76.173] (port=48154 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMkWp-0002Dg-Tv for emacs-orgmode@gnu.org; Mon, 21 Dec 2009 10:50:35 -0500 Received: from outbound-mail-15.bluehost.com ([69.89.18.115]:58075) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1NMkWo-0004Ar-Pa for emacs-orgmode@gnu.org; Mon, 21 Dec 2009 10:50:35 -0500 In-Reply-To: <90577D02-ACC2-4149-9E38-93FC66FFD403@gmail.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: Carsten Dominik Cc: Org Mode Aloha Carsten, I've had a chance to look at your first draft of beamer support. You've done a terrific job. So much of the draft is right that it helps to focus thoughts on the parts that are candidates for discussion and possible change. Along those lines, I don't think using headlines for \begin{columns} ... \end{columns} works very well. I think headlines should be reserved for sectioning, frames, elements of frames (blocks and friends), and notes. Once a headline level has been designated for frames (n), then headline n+1 becomes an element of the frame, and headline n+2 becomes notes for the frame (following Daniel Martins' lead). To my mind, columns are attributes of a frame, so they might better be handled as a property of the frame. Frame elements are specifically assigned to a column, or not, using a property. Roughly, this would yield the following syntax, which ought to export fairly cleanly with the HTML and LaTeX exporters. #+BEAMER_FRAME_LEVEL 2 * Section 1 ** Frame 1 :PROPERTIES: :FRAME_COLS: 2 :END: *** Element 1 :block: :PROPERTIES: :IN_COL: 1 :END: - Item 1 - Item 2 **** Notes about Element 1 block - Keyed to Item 1 - Keyed to Item 2 *** Element 2 :block: :PROPERTIES: :IN_COL: 2 :END: - Item 3 - Item 4 *** Element 3 This element spans two columns. The headline doesn't appear on the slide. *** Element 4 (headline doesn't appear on the slide because not a block or friend) :PROPERTIES: :IN_COL: 1 :END: - Item 5 - Item 6 ** Frame 2 *** Element 1 - Item 1 - Item 2 **** Notes - Note for item 1 - Note for item 2 Thanks again for drafting what should be a very useful addition to the already insanely useful org-mode. HTH, Tom On Dec 10, 2009, at 10:05 PM, Carsten Dominik wrote: > Hi everyone, > > the current state of affairs in beamer support is now in > the master branch of the git repo. > > My little draft documentation is now at > > http://orgmode.org/worg/org-tutorials/org-beamer.php > > But it is really limited and I am hoping very much that someone > will turn this into something useful! > > - Carsten > > > On Dec 11, 2009, at 12:49 AM, Mark Elston wrote: > >> Nick Dokos wrote: >>> IIUC, another way to go (possibly much simpler than org-babel[1]) >>> is to use >>> selective export: >>> #+EXPORT_SELECT_TAGS: Tags that select a tree for export >>> #+EXPORT_EXCLUDE_TAGS: Tags that exclude a tree from export >>> Mark the handout and notes sections with different tags and export >>> the document twice, once with the handout tag selected and once >>> with the notes tag selected. >> >> This sounds like it would work as well, though it probably results >> in a very different org-file organization to make it work. I will >> have to play around with the various options to see what works best >> for me. >> >> Thanks. >> >>> HTH, >>> Nick >>> [1] NB: org-babel is another area that I know very little about, but >>> hope to learn more about during vacation (although by this time, the >>> todo list for vacation has expanded sufficiently to occupy several >>> lifetimes...) >> >> Hah! I know exactly what you mean... >> >> 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 > > - Carsten > > > > > > _______________________________________________ > 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