From: Nick Dokos <nicholas.dokos@hp.com>
To: jamshark70@dewdrop-world.net
Cc: Nicolas Goaziou <n.goaziou@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: New exporter, beamer confusion
Date: Tue, 05 Feb 2013 08:55:43 -0500 [thread overview]
Message-ID: <9669.1360072543@alphaville> (raw)
In-Reply-To: Message from James Harkins <jamshark70@gmail.com> of "Tue, 05 Feb 2013 17:01:30 +0800." <CAFniQ7VRbOppQd3As9UEV+81ksY5b4dNBKVb_jLmUUxkyHa7gg@mail.gmail.com>
James Harkins <jamshark70@gmail.com> wrote:
> ...
>
> I get the feeling here that the new beamer exporter was written
> without a lot of real-world user requirements. Certainly, it's
> understandable that HTML, LaTeX article-style and ODT exporters would
> be more widely used and more important to get right first. For beamer,
> though, I can't reconcile the announcement ("Even though the internals
> are completely different, the new exporter mostly behaves like its
> predecessor. There are only a few noticeable changes") with the fact
> that the new beamer exporter is a rather different animal that
> completely breaks compatibility with org files written for the old
> exporter, and may actually require a complete redo of the org markup
> for each file.
>
> I know my emacs-lisp chops are not up to the task of fixing what is
> broken in the new beamer exporter. I can supply a couple dozen source
> files, to help decide what level of backward compatibility is
> feasible. I'm not sure how else I can help.
>
> At least, it would be good to clarify, with respect to the
> announcement, if the new beamer exporter is intended to be reasonably
> backward-compatible with the old (with not-too-intrusive tweaks). If
> that was the intent, then it's not ready for release. Otherwise, I'd
> be happy to help draw up an upgrade path for people like myself who
> have developed workflows for the old exporter that will eventually not
> be supported anymore.
>
> In the meantime, I must stick with the old exporter, though I'll keep
> the discussion alive to hash out on the mailing list what needs to be
> done to make the new one production-ready for me.
>
I'm sure Nicolas is up to his ears in prep work, but eventually I'm sure
he or somebody else who knows more about it than I do, will comment.
Just as a general precaution, I wouldn't rush to judgement based on
my fumbling attempts: these were small experiments done without knowing
anything about the new exporter to begin with. I hope that they did more
good than harm, but it *is* just a hope on my part. Don't mistake them
for authoritative information.
Nick
next prev parent reply other threads:[~2013-02-05 13:55 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 16:37 org-url-hexify-p is not respected James Harkins
2012-09-10 1:50 ` James Harkins
2012-09-10 4:58 ` Nick Dokos
2012-09-10 6:16 ` James Harkins
2012-09-10 6:37 ` Jambunathan K
2012-09-10 6:48 ` James Harkins
2012-09-10 7:12 ` Jambunathan K
[not found] ` <CAFniQ7W_5QMUawD2NObyhy2_Y647as-NthobZ9OgAX4NLcVJBw@mail.gmail.com>
2012-09-11 10:22 ` James Harkins
2012-09-11 13:10 ` Activating modules before org-install (was: org-url-hexify-p is not respected) Memnon Anon
2012-09-11 13:56 ` Jonathan Leech-Pepin
2012-09-11 17:06 ` org-url-hexify-p is not respected Charles Philip Chan
2012-09-23 10:05 ` Bastien
2012-09-26 17:59 ` Michael Brand
2012-09-26 21:50 ` Bastien
2012-09-27 6:18 ` Michael Brand
[not found] ` <jamshark70@gmail.com>
2012-08-12 2:55 ` MobileOrg, webdav, correct use of org-mobile-directory? James Harkins
2012-08-12 4:29 ` Nick Dokos
2012-08-12 7:12 ` James Harkins
2012-08-12 8:43 ` Bastien
2012-08-12 8:50 ` James Harkins
2012-08-12 13:11 ` Nick Dokos
2012-08-18 23:25 ` Adam Spiers
2012-08-19 1:35 ` Adam Spiers
2012-08-19 5:49 ` James Harkins
2012-08-20 20:03 ` Rémi Vanicat
2012-08-19 2:41 ` Nick Dokos
2012-08-12 11:38 ` James Harkins
2012-08-12 12:40 ` Nick Dokos
2012-08-12 13:12 ` Nick Dokos
2012-09-29 16:34 ` LaTeX beamer export: relative file links? Nick Dokos
2012-09-30 2:04 ` James Harkins
2013-01-10 3:40 ` <M-S-left/right> changed? Nick Dokos
2013-01-10 9:17 ` James Harkins
2013-02-05 7:21 ` New exporter, beamer confusion Nick Dokos
2013-02-05 9:01 ` James Harkins
2013-02-05 13:20 ` Sebastien Vauban
2013-02-05 13:55 ` Nick Dokos [this message]
2013-02-05 19:03 ` Nicolas Goaziou
2013-02-06 0:11 ` Eric S Fraga
2013-02-06 18:55 ` Nicolas Goaziou
2013-02-06 22:39 ` Eric S Fraga
2013-02-07 12:31 ` Nicolas Goaziou
[not found] ` <37646106030B4CA98C6A7717FBD89D50@gmail.com>
[not found] ` <87vca4jigj.fsf@gmail.com>
2013-02-07 14:49 ` Vincent Beffara
2013-02-07 14:58 ` Nicolas Goaziou
2013-02-07 17:08 ` Rasmus
2013-02-07 21:48 ` Nicolas Goaziou
2013-02-07 23:38 ` Rasmus
2013-02-08 21:41 ` Nicolas Goaziou
2013-02-08 13:40 ` Eric S Fraga
2013-02-06 2:12 ` James Harkins
2013-02-06 4:35 ` Eric S Fraga
2013-02-06 12:32 ` Rasmus
2013-02-06 13:12 ` Suvayu Ali
2013-02-06 13:45 ` Sebastien Vauban
2013-02-06 19:57 ` Nicolas Goaziou
2013-02-07 1:32 ` James Harkins
2013-02-05 9:36 ` Eric S Fraga
2013-02-25 6:25 ` How to make the new exporter open PDF using evince? James Harkins
2013-02-25 7:01 ` Mike Gauland
2013-02-25 6:52 ` Nick Dokos
2013-02-25 13:06 ` James Harkins
2013-02-26 2:40 ` Martin Marier
2013-02-27 9:51 ` James Harkins
[not found] <CAFniQ7UgwaQ5jO2r7iJ7PbakWfpvsJGZw2FNNf+sawwvKqSUqQ@mail.gmail.com>
2012-09-29 5:55 ` LaTeX beamer export: relative file links? James Harkins
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 2:38 <M-S-left/right> changed? James Harkins
2013-02-04 4:00 New exporter, beamer confusion James Harkins
2013-02-04 6:39 ` Suvayu Ali
2013-02-04 8:55 ` James Harkins
2013-02-04 19:51 ` Nicolas Goaziou
2013-02-05 0:09 ` James Harkins
2013-02-05 12:32 ` Eric S Fraga
2013-02-05 18:06 ` Nicolas Goaziou
2013-02-05 23:49 ` Eric S 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=9669.1360072543@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@gmail.com \
/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).