From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Re: Beamer export: How to handle overlayarea Date: Thu, 24 Oct 2013 08:43:59 +0800 Message-ID: References: <87eh7f3pb8.fsf@gmail.com> <87bo2fudnn.fsf@gmail.com> Reply-To: jamshark70@dewdrop-world.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e012281fef0294304e971edc9 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49604) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZ91u-0000v3-Ov for Emacs-orgmode@gnu.org; Wed, 23 Oct 2013 20:44:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZ91s-0005vc-GQ for Emacs-orgmode@gnu.org; Wed, 23 Oct 2013 20:44:02 -0400 Received: from mail-ob0-x236.google.com ([2607:f8b0:4003:c01::236]:49713) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZ91s-0005vU-9e for Emacs-orgmode@gnu.org; Wed, 23 Oct 2013 20:44:00 -0400 Received: by mail-ob0-f182.google.com with SMTP id wn1so42054obc.41 for ; Wed, 23 Oct 2013 17:43:59 -0700 (PDT) In-Reply-To: <87bo2fudnn.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 , Emacs-orgmode@gnu.org --089e012281fef0294304e971edc9 Content-Type: text/plain; charset=ISO-8859-1 On Oct 24, 2013 12:58 AM, "Nicolas Goaziou" wrote: > There are two things to consider: what belongs to the manual, and what > belongs to `org-beamer-environments-extra' docstring. > > I think it is reasonable for the manual not to talk about %o, %r... but, > instead, simply point to the variable name. OK. > Headlines also support 'BEAMER_ACT' and 'BEAMER_OPT' properties. The > former is translated as an overlay/action specification, or a default > overlay specification when enclosed within square brackets. The latter > specifies options for the current frame or block, and will automatically > be enclosed within square brackets. That would help. I'd still like to see something more like a "for-dummies" explanation of passing options and arguments to LaTeX entities. I'm not saying the documentation is woefully inadequate (hardly that -- Suvayu's page got me rather far, and I got stuck on a couple of details). My experience was: it never would have occurred to me on my own to use the headline text for LaTeX code, and if there was a hint anywhere in the docs to suggest that this would be the way to go, I didn't find it. That's a conceptual leap that passed me by. FWIW, I often raise a similar point among SuperCollider devs, noting that we generally do a decent job of documenting class interfaces, but not such a great job of explaining to people who don't eat, breathe and sleep SC how to put the pieces together. That leads to questions such as [1] on the mailing list. Really basic use case, but this competent user is confused... meaning, the collective docs aren't doing a thorough job. This sort of doc would be appropriate for worg, but probably not the manual. If I have time while traveling, I'll draft up a few paragraphs -- but I don't know all the implementation details so I'd certainly need another pair of eyes. hjh [1] http://article.gmane.org/gmane.comp.audio.supercollider.user/102850 --089e012281fef0294304e971edc9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Oct 24, 2013 12:58 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> There are two things to consider: what belongs to the manual, and what=
> belongs to `org-beamer-environments-extra' docstring.
>
> I think it is reasonable for the manual not to talk about %o, %r... bu= t,
> instead, simply point to the variable name.

OK.

> =A0 =A0Headlines also support 'BEAMER_ACT' and = 'BEAMER_OPT' properties. The
> former is translated as an overlay/action specification, or a default<= br> > overlay specification when enclosed within square brackets. =A0The lat= ter
> specifies options for the current frame or block, and will automatical= ly
> be enclosed within square brackets.

That would help.

I'd still like to see something more like a "for-du= mmies" explanation of passing options and arguments to LaTeX entities.= I'm not saying the documentation is woefully inadequate (hardly that -= - Suvayu's page got me rather far, and I got stuck on a couple of detai= ls). My experience was: it never would have occurred to me on my own to use= the headline text for LaTeX code, and if there was a hint anywhere in the = docs to suggest that this would be the way to go, I didn't find it. Tha= t's a conceptual leap that passed me by.

FWIW, I often raise a similar point among SuperCollider devs= , noting that we generally do a decent job of documenting class interfaces,= but not such a great job of explaining to people who don't eat, breath= e and sleep SC how to put the pieces together. That leads to questions such= as [1] on the mailing list. Really basic use case, but this competent user= is confused... meaning, the collective docs aren't doing a thorough jo= b.

This sort of doc would be appropriate for worg, but probably= not the manual. If I have time while traveling, I'll draft up a few pa= ragraphs -- but I don't know all the implementation details so I'd = certainly need another pair of eyes.

hjh

[1] http://article.gmane.org/gmane.comp.audio.supercoll= ider.user/102850

--089e012281fef0294304e971edc9--