emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [beamer] When are :BEAMER_envargs: used or ignored?
Date: Thu, 26 Apr 2012 13:15:23 +0200	[thread overview]
Message-ID: <80d36ulp6c.fsf@somewhere.org> (raw)
In-Reply-To: 87397q3jo1.wl%jamshark70@dewdrop-world.net

Hi James,

James Harkins wrote:
> At Thu, 26 Apr 2012 17:44:56 +0930,
> Eric Fraga wrote:
>> > But I still have the issue with it
>> > that the user has to adapt the org-file structure to suit beamer's
>> > requirements. Org-mode is all about reflecting the content in a way
>> > that makes sense FIRST to humans, and only secondarily to exporting
>> > engines.
>> I agree.  However, the problems arise when exporting because of
>> fundamentally different structures between org and the export
>> target.  This is why we have the various kludges (if people can forgive
>> me for calling them this) like ATTR_HTML and ATTR_LATEX.  There is no
>> easy or elegant mechanism in org for satisfying all the different export
>> target requirements that are fundamentally inconsistent with org's
>> outline heritage.
> I understand. An elegant solution would take some mulling over (especially
> considering that I've only recently started using the export features, and my
> knowledge of LaTeX is superficial at best). In the meantime, I can live with
> the current situation.
> That the headline title is used for the color specification is probably not
> such an unbearable thing in practice. How many color boxes are there likely to
> be on one slide? (Meaning, if you're tempted to load up a slide with so many
> color boxes that you get confused about the content, maybe the content needs
> to be restructured.) If it's the only color box on the slide, quite likely you
> can infer its content from the frame title or other headings nearby.
> It just struck me as a loose end, and I'm glad I asked about it, because I
> have a better understanding of the issues now.
>> For this particular case, it could be that the beamercolorbox
>> environment could be made to expect a specific PROPERTY, much like the
>> column environment does.  The question would then be: what should the
>> headline be used for as beamercolorbox has no real text content
>> argument.
> There are other beamer tags that don't use the headline text, namely quote and
> quotation. According to the beamer user guide, there's no place for the
> headline:
> \begin{quote}<action specification>
> environment contents
> \end{quote}
> Compared to
> \begin{block}<action specification>{block title}<action specification>
> environment contents
> \end{block}
> So, there is already a situation where you have to put some dummy text into
> the headline that won't appear.

And, in Org-Beamer, you have the explicit tag `b_ignore' as well, to ignore
the entry title, using the contents only.

> Maybe there could be special handling for title-less environments, so that
> the headline would become the environment contents and colorbox could take
> its color from a property...

I don't find that a particularly attractive option, since you would end up
with very long headlines (often more than 80 characters) and you would not be
able to have multiline (or multiparagraph) contents.

Best regards,

Sebastien Vauban

  reply	other threads:[~2012-04-26 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  7:07 [beamer] When are :BEAMER_envargs: used or ignored? James Harkins
2012-04-25  4:41 ` Eric Fraga
2012-04-25 10:09   ` James Harkins
2012-04-25 12:49     ` James Harkins
2012-04-26  8:14       ` Eric Fraga
2012-04-26  9:51         ` James Harkins
2012-04-26 11:15           ` Sebastien Vauban [this message]
2012-04-25 13:15     ` Eric Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80d36ulp6c.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).