emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [beamer] When are :BEAMER_envargs: used or ignored?
Date: Thu, 26 Apr 2012 17:51:42 +0800	[thread overview]
Message-ID: <87397q3jo1.wl%jamshark70@dewdrop-world.net> (raw)
In-Reply-To: <87ehranc3j.fsf@ucl.ac.uk>

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. 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 would guess that if you could suggest a consistent and more elegant
> solution, it would be considered favourably and maybe somebody would
> take it up and implement it.  No promises, however!

... but the elegance of that approach would be debatable, I suppose.

James


--
James Harkins /// dewdrop world
jamshark70@dewdrop-world.net
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal."  -- Whitman

blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks

  reply	other threads:[~2012-04-26  9:52 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 [this message]
2012-04-26 11:15           ` Sebastien Vauban
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87397q3jo1.wl%jamshark70@dewdrop-world.net \
    --to=jamshark70@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).