emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: flammable project <flammable.project@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to easily create a new export engine...
Date: Tue, 3 Sep 2013 22:14:33 +0200	[thread overview]
Message-ID: <CAJzEwi8duy2gb5eLyR0sMu9u6CgpEHB7s_weCJjYmavphaoE8A@mail.gmail.com> (raw)
In-Reply-To: <87mwnu2ecd.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

Thanks Nocolas and Suvayu,


I will spend some time on ox-md.el and the section listed by Nicolas.

One last question:
If I choose to extend the existing back-end, would I be able to put all the
code into a external file and allow the user to load it through it emacs
config file?
I mean, I would like to add a support of Twitter Bootstrap trough the
ox-html.el export engine. If the user add "(require 'ox-html-bootstrap)"
into its ".emacs" file, it will allow the user to extend the ox-html export
engine.
Does it seems possible?

Thanks






2013/9/3 Nicolas Goaziou <n.goaziou@gmail.com>

> Hello,
>
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> > On Tue, Sep 03, 2013 at 03:37:05PM +0200, flammable project wrote:
> >> Hi all,
> >>
> >> I'm looking for informations on how to create a new exporter based on
> the
> >> new export engine.
> >>
> >> I want to convert org files into HTML files in which some "functions"
> from
> >> Twitter Bootstrap framework will be instantiated via Emacs and Org-Mode.
> >>
> >> I'm quite fustrated because the org-export_generic.el file is obsolete
> and
> >> I tried to use ox.el ox-ascii.el files but I was discouraged by their
> heavy
> >> contents.
> >>
> >> Could you please tell how to easily find a good starting "point" ?
> >
> > You could take a look at ox-md.el; it derives from ox-html.el.  Since
> > you want to add to ox-html.el, that might be a nice starting point.
> >
> > Needless to say, you should probably wait for Nicolas's comment.  He is
> > the expert, I'm just a user who looks at the source from time to time
> > ;).
>
> The OP could also look at "12.13 Advanced configuration" from Org
> manual. There's an example on how to extend an existing back-end.
>
> There's also `org-export-define-derived-backend' docstring.
>
> If the new exporter is not meant for public consumption and would always
> be used instead of regular html back-end, defadvices are also fine.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
>

[-- Attachment #2: Type: text/html, Size: 4000 bytes --]

  reply	other threads:[~2013-09-03 20:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 13:37 How to easily create a new export engine flammable project
2013-09-03 13:51 ` Suvayu Ali
2013-09-03 14:02   ` Nicolas Goaziou
2013-09-03 20:14     ` flammable project [this message]
2013-09-04 10:15       ` Rasmus
2013-09-04 11:37       ` Eric Abrahamsen

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=CAJzEwi8duy2gb5eLyR0sMu9u6CgpEHB7s_weCJjYmavphaoE8A@mail.gmail.com \
    --to=flammable.project@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --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).