From mboxrd@z Thu Jan 1 00:00:00 1970 From: suvayu ali Subject: Re: [dev] About a beamer back-end Date: Thu, 21 Jun 2012 18:49:33 +0200 Message-ID: References: <87ehpg8vfo.fsf@gmail.com> <87ipep83ds.fsf@ucl.ac.uk> <87ehpbphcz.fsf@gmail.com> <87k3z32eug.fsf@ucl.ac.uk> <87wr30ohn1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59172) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Shka3-0008R0-8M for emacs-orgmode@gnu.org; Thu, 21 Jun 2012 12:50:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ShkZw-00014E-Mn for emacs-orgmode@gnu.org; Thu, 21 Jun 2012 12:50:02 -0400 Received: from mail-bk0-f41.google.com ([209.85.214.41]:57692) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ShkZw-0000wd-Bb for emacs-orgmode@gnu.org; Thu, 21 Jun 2012 12:49:56 -0400 Received: by bkcjm19 with SMTP id jm19so903937bkc.0 for ; Thu, 21 Jun 2012 09:49:54 -0700 (PDT) In-Reply-To: <87wr30ohn1.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Org Mode List Hi Nicolas, On Thu, Jun 21, 2012 at 4:37 PM, Nicolas Goaziou wrot= e: > > If you want to try them out (there has been no serious debugging for > them), you can > > =C2=A0(defalias 'org-metaup 'org-element-drag-backward) > > `org-element-drag-backward' is a strict super-set for `org-metaup'. > I will try this out today. > I'll keep headlines for blocks. =C2=A0But I think I'll introduce a couple= of > small changes. > > - Sectioning and packages are extracted from `org-e-latex-classes'. > =C2=A0Since calling Beamer back-end is explicit, it can be applied on any > =C2=A0tex file, not only when that file starts with > =C2=A0"\documentclass{beamer}". =C2=A0Additionally, an equivalent to > =C2=A0`org-beamer-use-parts' is unnecessary. > This would be a welcome addition in line with the org philosophy of org documents being backend agnostic. > - An headline at `org-e-beamer-frame-level' level becomes a frame, > =C2=A0unless it has the "noframe" tag. =C2=A0In that case, its contents a= re > =C2=A0inserted between surrounding frames. > In one of your follow-up replies you mention you are not sure what could be the use case. The beamer package has the option handout, that allows one to produce handouts for your slides with text in between frames included in the final pdf. This addition would make that process as simple as adding the handout option to beamer and recompiling the latex source! > - Any headline above that level has a block type (depending on the > =C2=A0BEAMER_env property). =C2=A0Without that property, the headline is = still > =C2=A0a block ("\begin{block}{title}...\end{block}"). > This is also a very nice addition. > - Since above some level, everything is a block, there is no "low level > =C2=A0headline" anymore. =C2=A0Thus, the H:num OPTION item sets > =C2=A0`org-e-beamer-frame-level'. =C2=A0There's no use for BEAMER_FRAME_L= EVEL > =C2=A0keyword. =C2=A0It also means you can't make lists out of headlines. > This will again cleanup the syntax and make it more uniform across backends. :) > - An headline below `org-e-beamer-frame-level' with an "appendix" tag > =C2=A0becomes an appendix part. > I would appreciate this feature a lot! > - An headline with a "note" tag becomes a note between frames if at > =C2=A0`org-e-beamer-frame-level', within current frame otherwise. > > - There is no separate syntax for \alert{} command: it is the default > =C2=A0output for bold objects (i.e. *text* becomes \alert{text}). > I am a little apprehensive about this. Bold is something I use (and see others use) frequently in presentations. I would suggest changing the choice to something that is less used in presentations. The `_' markup could be a good candidate or one of the two `=3D' or `~' could be used (since they render to something very similar in the pdf). But this is not an important point; as long as this is configurable, I'm happy. :) > - Obviously, all special tags specified in this list are customizable. > A huge thank you for all the wonderful and hard work you have put in. :) --=20 Suvayu Open source is the future. It sets us free.