[
https://issues.apache.org/jira/browse/COR-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282070#comment-14282070
]
Peter Kelly commented on COR-11:
--------------------------------
The idea is that HTML is the API, and the API is HTML.
This enables a complete decoupling between components. The editor knows nothing
about the conversion library, and the conversion library knows nothing about
the editor. There a circumstances in which you might want to use one but not
the other.
If we want to provide an abstraction over various document formats that hides
the underlying representation, what we're effectively doing is designing a new
document format (not necessarily a serialisation format, but at least an
in-memory data model - once you have the latter, the former is easy). By
picking an existing standard format (HTML) for document representation, we can
thus focus on providing conversion facilities, rather than creating a new
format/data model.
> 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)
