[
https://issues.apache.org/jira/browse/COR-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282074#comment-14282074
]
Peter Kelly commented on COR-11:
--------------------------------
Incidentally, as an example of where the separation between DocFormats and the
editor would be relevant - picture a web-based editor based on Corinthia. This
would have both a server-side component and a client-side component.
The server-side component would utilise DocFormats to convert files to HTML and
send them to the client over HTTP (and the inverse on save). DocFormats needs
to run on the server, as its native code, and cannot run in the browser
(ignoring emscripten/asm.js for the purpose of this discussion).
The client-side component would utilise the built-in support for parsing and
rendering HTML already provided by the browser, and use the editor library to
provide the ability for the user to modify the document. The client does not
need to know anything about docx, odt, and other formats, which keeps things
simple on the client. In fact the built-in support for HTML that browser
engines provide was the reason this was chosen as the common intermediate
format for DocFormats over another format like odt.
> Make interface between docformat and webkit (prepare for e.g. Qt).
> ------------------------------------------------------------------
>
> Key: COR-11
> URL: https://issues.apache.org/jira/browse/COR-11
> Project: Corinthia
> Issue Type: New Feature
> Components: DocFormats - API
> Environment: source
> Reporter: jan iversen
> Priority: Blocker
> Fix For: 0.5
>
>
> We need a API to the library
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
