You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@corinthia.apache.org by "Peter Kelly (JIRA)" <ji...@apache.org> on 2015/02/10 19:43:11 UTC

[jira] [Commented] (COR-11) Make interface between docformat and webkit (prepare for e.g. Qt).

    [ https://issues.apache.org/jira/browse/COR-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314623#comment-14314623 ] 

Peter Kelly commented on COR-11:
--------------------------------

Just coming back to this - I think a good step forward first would be for us to focus on getting the editor working in-browser, with a server-side component handling file format conversion. This will be usable both for local editing (run the web server locally, and bring up a browser to localhost), or could be deployed on a web server.

The latter would also give us a nice way of showcasing the project, by providing a demo site where people can come and try out the editor, and see how well it works with their existing word docs (where and how to host this is an issue; but that's a separate discussion).

I think the title of this JIRA issue would should really be "design and implement a user interface" - the interfacing between WebKit and DocFormats is simply a matter of linking a given app against both libraries and using DocFormats when loading/saving documents. The *real* challenge is the bigger picture of where this fits in, and I think this latter is something we need to decide before we can know what to do with the bits that we currently have.

I don't have any specific preferences regarding the server-side technology; it could be done in Python (I'm doing some REST API implementation in Python right now in some other work and I quite like it); it could be an Apache module, a java servlet, a node.js app, or something else. It really depends on the skillset of whoever is willing to implement the server. I think it would be nice to have it done in a way that's easy for people to integrate into their websites/intranets etc. so that they can add editing and conversion functionality without having to radically change the rest of their site.

And then there's the desktop - that's another question. I'm very much inclined towards Qt on technical grounds. I'm not sure about whether the license would prevent development on a Qt frontend to occur within the context of an Apache project (this would be a real shame IMHO); I guess GTK is another alternative but I haven't been very impressed by GTK apps I've seen on non-Linux platforms.

I've been extremely busy of late but am hoping to come back to the editor and tidy up some unfinished work on some features and document it more thoroughly.

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