Re: [ANN] Editable HTML export of Org-mode files

[Eric Schulte <schulte.eric@gmail.com>]

Simon Thum <simon.thum@gmx.de> writes:

> On 10/22/2012 10:38 PM, Eric Schulte wrote:
>> Simon Thum<simon.thum@gmx.de>  writes:
>> --8<---------------cut here---------------start------------->8---
>> foo bar
>>
>>
>>
>>
>>
>> --8<---------------cut here---------------end--------------->8---
>>
>> all of the spaces and newlines are inserted into the Org-mode file.
>> However, when that Org-mode file is re-exported, it uses the normal html
>> exporter (which *does* ignore whitespace by default).
>>
>> So, if you are not having the spaces inserted into your Org-mode file
>> that is a problem with org-ehtml, but if you *are* having the spaces
>> appear in your .org file (server-side), but they are not appearing in
>> the exported HTML, that is expected behavior.
>
> I meant when editing in the HTML page via the server
> call-back. Changing the WS means all lines change, regardless of
> whether I edited them. From your description I assume the edit box
> content comes out of the export, too? I guess that needs to change for
> this to work reliably.
>

Yes, the content of the edit boxes does come from the exported html.
For each portion of the Org-mode document (as delimited by
org-elements), both the raw Org-mode text and the HTML are exported
side-by-side, then the raw Org-mode text is hidden and the HTML is
displayed, until the [edit] button is pushed at which point JavaScript
is used to hide the HTML and to expose the raw Org-mode text in an edit
box.  When edits are committed they are committed one portion (edit-box)
at a time.

Does this make sense?

Why would something need to change for "this" to be reliable?

Thanks,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte