emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* New exporter: where are the back-end functions called?
@ 2012-06-11 21:17 Thorsten Jolitz
  2012-06-12 12:53 ` Nicolas Goaziou
  0 siblings, 1 reply; 2+ messages in thread
From: Thorsten Jolitz @ 2012-06-11 21:17 UTC (permalink / raw)
  To: emacs-orgmode


Hi Nicolas, Hi List, 

when trying to enhance the HTML back-end of the new exporter with
interactive HTML elements, one possibility (probably the easiest and
best) is to write variants for the export functions for some Org
elements that insert different HTML in the output string (HTML form
fields instead of static HTML).

By far the most interesting Org element for me is the 'headline'
element, that is transcoded by the following function from
'org-e-html.el': 

,--------------------------------------------------------------
| (defun org-e-html-headline (headline contents info)
|   "Transcode an HEADLINE element from Org to HTML.
| CONTENTS holds the contents of the headline.  INFO is a plist
| holding contextual information."
`--------------------------------------------------------------

Now I don't want to mess around in the original exporter code, but
rather would like to rename this function and all the helper functions
it calls with the 'iorg'-prefix and then experiment with changing the
function bodies.

Unfortunately, I cannot figure out where 'org-e-html-headline' is called
in the export process, searching for the function name gave no result. 

Can anybody give me a hint how to find the caller(s) of this function?
Is there Emacs functionality that finds all the callers of a function? I
suspect the call is somewhere concatenated out of different pieces in
the source code, so a simple search won't help probably.

-- 
cheers,
Thorsten

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: New exporter: where are the back-end functions called?
  2012-06-11 21:17 New exporter: where are the back-end functions called? Thorsten Jolitz
@ 2012-06-12 12:53 ` Nicolas Goaziou
  0 siblings, 0 replies; 2+ messages in thread
From: Nicolas Goaziou @ 2012-06-12 12:53 UTC (permalink / raw)
  To: Thorsten Jolitz; +Cc: emacs-orgmode

Hello,

Thorsten Jolitz <tjolitz@googlemail.com> writes:

> when trying to enhance the HTML back-end of the new exporter with
> interactive HTML elements, one possibility (probably the easiest and
> best) is to write variants for the export functions for some Org
> elements that insert different HTML in the output string (HTML form
> fields instead of static HTML).
>
> By far the most interesting Org element for me is the 'headline'
> element, that is transcoded by the following function from
> 'org-e-html.el': 
>
> ,--------------------------------------------------------------
> | (defun org-e-html-headline (headline contents info)
> |   "Transcode an HEADLINE element from Org to HTML.
> | CONTENTS holds the contents of the headline.  INFO is a plist
> | holding contextual information."
> `--------------------------------------------------------------
>
> Now I don't want to mess around in the original exporter code, but
> rather would like to rename this function and all the helper functions
> it calls with the 'iorg'-prefix and then experiment with changing the
> function bodies.

You may have a look at `org-export-define-derived-backend' macro and
"Defining a Back-End" in Org export documentation[1].


Regards,

[1] http://orgmode.org/worg/dev/org-export-reference.html

-- 
Nicolas Goaziou

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-06-12 12:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-11 21:17 New exporter: where are the back-end functions called? Thorsten Jolitz
2012-06-12 12:53 ` Nicolas Goaziou

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