James Harkins <jamshar...@gmail.com> writes:
> At Wed, 25 Apr 2012 18:09:18 +0800,
> James Harkins wrote:
>> > Whether it should be a feature request or not is debatable. The syntax
>> > is, at present, fairly straightforward in that the headline text becomes
>
>> > the argument to the environment defined.
>>
>> I think "the headline text becomes the argument..." is the opposite of
>> straightforward. :-)
>
> OK, wait, I get it:
>
> \begin{alertblock}{HEADLINE TEXT HERE}
>
> \begin{beamercolorbox}{HEADLINE TEXT HERE}
>
> OK, it's a consistent translation.
Yes.
> 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.
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.
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!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)
