From: Austin Frank <austin.frank@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [org-beamer] inline slides?
Date: Fri, 29 Jan 2010 12:13:51 -0500 [thread overview]
Message-ID: <m01vh84ywg.fsf@gmail.com> (raw)
In-Reply-To: 87wrz3jzqe.wl%ucecesf@ucl.ac.uk
[-- Attachment #1.1: Type: text/plain, Size: 2203 bytes --]
On Wed, Jan 27 2010, Eric S Fraga wrote:
> I could see it being useful, along the lines of all the tangling
> examples in org-babel.
Yes! Tangling of embedded code is a good comparison.
> more importantly, I often will prepare more than one presentation
> based on a given project and each presentation will be substantially
> different enough to make it difficult to embed slides.
> Yes, this I can see. However, the type of different content you may
> wish to attach/embed will depend on its final purpose. That is, in
> terms of presentations, who will be in the audience?
These are good points. My inclination would be to handle variations on
the same talk using git. For projects where this workflow makes sense,
I would write the initial paper and presentation together. Upon
completion, I would make a git tag marking the finished state for that
version of the talk. Subsequent talks could be created by creating a
branch. In most cases, I would probably edit the slides-only version of
the file directly (rather than in the context of the original paper).
>> Since slides are mostly just headlines with special tags and properties,
>> at the end of the process I could easily selectively export just the
>> text of the dissertation or just the embedded slides.
>
> This begs the question: maybe an "export to org based on tags"
> function is all that is required? And this is probably already
> implemented; I hesitate to suggest how or where, given my lack of
> awareness of all the various multitude of features of org-mode, but I
> can imagine that sparse trees could be part of any solution?
Yes, I think that the basis of the export function will be building a sparse
tree and then exporting the visible buffer. I wouldn't say this is all that
is required, though. I'd really like to have the
*************** embedded slide
*************** END
style of inline definition. Again, this allows slides to be embedded
without changing the surrounding outline context.
> Just some thoughts...
Thanks!
/au
--
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc
[-- Attachment #1.2: Type: application/pgp-signature, Size: 194 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-01-29 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 21:38 [org-beamer] inline slides? Austin Frank
2010-01-27 16:10 ` Eric S Fraga
2010-01-28 10:41 ` Darlan Cavalcante Moreira
2010-01-29 17:17 ` Austin Frank
2010-01-29 17:13 ` Austin Frank [this message]
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=m01vh84ywg.fsf@gmail.com \
--to=austin.frank@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).