corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (COR-11) Make interface between docformat and webkit (prepare for e.g. Qt).
Date Sat, 17 Jan 2015 00:17:34 GMT

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

Dennis E. Hamilton edited comment on COR-11 at 1/17/15 12:17 AM:
-----------------------------------------------------------------

Qt recently came up on the Apache OpenOffice dev list.  I.e., at this thread: http://mail-archives.apache.org/mod_mbox/openoffice-dev/201501.mbox/browser

I suspect that Qt is not usable (directly bolted onto something that is part of Corinthia)
because of an important constraint with regard to Apache Projects (see https://wiki.apache.org/incubator/ApacheProjectMaturityModel
and LC20 there).  Qt is under what is called a Category X license and having a dependency
on it is tricky business.  It can work sometimes, but using the Qt API everywhere is likely
to cross the line into no-no territory.

I am assuming that this issue is not about any use in DocFormat itself, but it concerns an
edifice atop DocFormat that wants to fit in some GUI framework for surfacing an User Interface.

Are these meant to be nearly-orthogonal considerations (or, in the Model-View-Controller sense,
DocFormat is the layer at which the Model subsists, with View-Controller above)?


was (Author: orcmid):
Qt recently came up on the Apache OpenOffice dev list.  I.e., at this thread: http://mail-archives.apache.org/mod_mbox/openoffice-dev/201501.mbox/browser

I suspect that Qt is not usable because of an important constraint with regard to Apache Projects
(see https://wiki.apache.org/incubator/ApacheProjectMaturityModel and LC20 there).  Qt is
under what is called a Category X license and having a dependency on it is tricky business.
 It can work sometimes, but using the Qt API everywhere is likely to cross the line into no-no
territory.

I am assuming that this issue is not about any use in DocFormat itself, but it concerns an
edifice atop DocFormat that wants to fit in some GUI framework for surfacing an User Interface.

Are these meant to be nearly-orthogonal considerations (or, in the Model-View-Controller sense,
DocFormat is the layer at which the Model subsists, with View-Controller above)?

> 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
>         Environment: source
>            Reporter: jan iversen
>            Priority: Blocker
>
> We need a API to the library



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message