> On 15 Feb 2015, at 2:50 am, Dave Fisher <[email protected]> wrote: > > Very true. Some time ago you answered my questions about the architecture. > Although I am very busy, sooner or later I will engage the build and then I > can see where to apply my programming or architecture skills. > > Let's test my memory - the underlying architecture conceptually simple enough > in no particular order. > > HTML editing - HTML editing with JS
Yes. Specifically, we have an editing *library* upon which one can build editing applications. One of the project goal is to build on or more such applications; two ideas that have been discussed are a Qt-based native app, and a web app which can run in a browser. > HTML presentation / common layer - HTML rendering with CSS Yes, although the actual rendering is handled by the browser’s rendering engine (e.g. WebKit/Gecko), not Corinthia itself. > DocFormats structure core library > input document in a particular mime-type > output document in a particular mime-type > update document in a particular mime-type Correct. > filters to support mime-type selection. Not sure what you mean by “selection” here - there’s no *detection* of file types, though it would be correct to say that there are filters for different mime types (file formats). The filter invoked for a conversion is determined by the file extension. — Dr Peter M. Kelly [email protected] PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
