Return-Path: X-Original-To: apmail-corinthia-dev-archive@minotaur.apache.org Delivered-To: apmail-corinthia-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D51E179E5 for ; Thu, 8 Jan 2015 11:27:47 +0000 (UTC) Received: (qmail 35911 invoked by uid 500); 8 Jan 2015 11:27:48 -0000 Delivered-To: apmail-corinthia-dev-archive@corinthia.apache.org Received: (qmail 35887 invoked by uid 500); 8 Jan 2015 11:27:48 -0000 Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@corinthia.incubator.apache.org Delivered-To: mailing list dev@corinthia.incubator.apache.org Received: (qmail 35876 invoked by uid 99); 8 Jan 2015 11:27:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jan 2015 11:27:48 +0000 X-ASF-Spam-Status: No, hits=-1997.8 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 08 Jan 2015 11:27:46 +0000 Received: (qmail 34715 invoked by uid 99); 8 Jan 2015 11:27:26 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jan 2015 11:27:26 +0000 Received: from mail-la0-f45.google.com (mail-la0-f45.google.com [209.85.215.45]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 99B1C1A0041 for ; Thu, 8 Jan 2015 11:27:25 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id gq15so8628151lab.4 for ; Thu, 08 Jan 2015 03:27:24 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.54.167 with SMTP id k7mr12475322lbp.72.1420716444317; Thu, 08 Jan 2015 03:27:24 -0800 (PST) Received: by 10.112.10.16 with HTTP; Thu, 8 Jan 2015 03:27:24 -0800 (PST) In-Reply-To: <4B5466FE-B97B-4971-8868-2E42ED2DAC0E@comcast.net> References: <011901d02a21$d7db3860$8791a920$@acm.org> <4B5466FE-B97B-4971-8868-2E42ED2DAC0E@comcast.net> Date: Thu, 8 Jan 2015 12:27:24 +0100 Message-ID: Subject: Re: Corinthia web and social media From: jan i To: "dev@corinthia.incubator.apache.org" Content-Type: multipart/alternative; boundary=001a11c3fb30fd7ffb050c22525f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3fb30fd7ffb050c22525f Content-Type: text/plain; charset=UTF-8 On 8 January 2015 at 00:29, Dave Fisher wrote: > > On Jan 7, 2015, at 1:36 AM, jan i wrote: > > > On 7 January 2015 at 04:25, Dave Fisher wrote: > > > >> Hi Dennis, > >> > >> I like your style. I'll introduce myself to those who don't know me in > the > >> near future. > >> > >> What I am grasping for is documentation on the architecture and how Java > >> based libraries like Apache POI and PDFBox would fit with Corinthia. > Once I > >> can understand this then I might be able to lean in with help with > Office > >> and PDF. > >> > > Hi Dave > > > > Welcome aboard. Looking forward to work together with you on this > project. > > > > When Peter and I meet, I looked into especially POI because I think there > > is a lot we can use there. Peter taught me the benefit of having pure C > > code due to the different platforms. Without it being written in stone, I > > as developer, would find it very difficult accepting a second programming > > language, or the requirement of needing a java runtime. Having said > that, I > > have been thinking about if there are java->C converters we could use. > > I can see a benefit to one language, but that may really be about how > tightly coupled the architecture really is and if it is modular enough to > allow for different languages in the conversion tool chain. > > In my case I am thinking about (PDF,PPTX) -> HTML5(SVG) -> Corinthia > enabled edits -> Responsive and/or Collaborative Presentation. > this could be a use case for only using the editor, which uses HTML5. > > I have various tools to do conversions I guess I want to do my own convert > to HTML5 and then have Corinthia help with editing and then handle the > conversion out. > That sounds like a good idea. And then of course we can do something so you can start the editor (javascript + docformats library) embedded. > > I know that a C port of POI is not to interesting to me. There is a .NET > port - https://npoi.codeplex.com/ > > If Java will work for at least some conversions then I have an argument > for my work about open sourcing my Osmosis tool that converts PDF into > HTML5. The cool part is the way shapes and text is regrouped into layout.If > it had to be in C then I won't get much traction. > Just a few words to describe the complications. DocFormats is today a static linked C library, it consist of 3 layered parts (without going into all details): - At the bottom we have platform/core, that takes care of the data model (HTML5) and platform dependencies. - Above that we have the filters, each filter has its own implementation, so all filters are in parallel - At the top we the API, the outward facing part of the library (this is by far not completed). If you wanted to make a java based filter. You would need to write a skeleton C filter that can be linked into docformats. The skeleton, would then need to communicate with the java implementation. Peter and I discussed making plugable filters a while ago, but decided against it (for now), because we dont see a lot of different filters. However now that we are more people working the world might change. rgds jan i > > Regards, > Dave > > > > > rgds > > jan I. > > > > > >> > >> Regards, > >> Dave > >> > >> > >> > >> Sent from my iPhone > >> > >>> On Jan 6, 2015, at 6:30 PM, Dennis E. Hamilton < > dennis.hamilton@acm.org> > >> wrote: > >>> > >>> Dorte, > >>> > >>> Thank you for the introduction. So you and Jan talk every day! That > >>> is valuable context! > >>> > >>> I don't think we have a shared understanding of how the web can > >>> work for Corinthia. > >>> > >>> I appreciate your effort and your skill with the web pages. > >>> > >>> Because the web site is responsive, and the Wiki is not, it may be that > >>> the web site is a better place to gather information. It might be a > >>> better place to arrive at with searches on the Internet also. > >>> > >>> If the goal is to attract committers on existing Apache projects, it > >>> is perhaps unclear what questions such persons have about Corinthia > >>> and the best way to answer them. It is also not clear what is the > >>> best way to have their attention and awareness on Corinthia. > >>> > >>> Those are all good questions. Thank you for pointing out that these > >>> need to be considered. > >>> > >>> It is my misunderstanding about the web pages. I did not understand > >>> them to be drafts or proposals. I took them as steps in a desired > >>> direction. I did not want to "churn" the pages, and I did not know > >>> where to start. I confused myself about passing changes through Jan > >>> to you. > >>> > >>> - Dennis > >>> > >>> -----Original Message----- > >>> From: Dorte Fjalland [mailto:dortecasacondor@gmail.com] > >>> Sent: Tuesday, January 6, 2015 15:36 > >>> To: dev@corinthia.incubator.apache.org > >>> Subject: Corinthia web and social media > >>> > >>> Hi all, Happy New Year. I can see that there has been some > >>> correspondence now re. the Corinthia web/social media strategies and > the > >>> content so far proposed. I prefer to comment in a new post as I would > not > >>> know where else to reply. > >>> > >>> I made the current web proposal based on my understanding that the > >> project > >>> needed like a kind of "sales brochure" aimed at getting committers from > >>> other Apache projects involved in Corinthia and therefore a site that > >> would > >>> be easy to overview and containing basic/essential information and with > >>> links to all the serious and detailed stuff to be found in wikis etc. > >>> > >>> Reading the various mail threads i get the impression that maybe the > >>> community should find out who they want to reach and then decide the > >> tools. > >>> Re the fb page and the Twitter the members who are active on those > medias > >>> can be editors/admins and provide content, but again, you can do this > >> with > >>> the intention of attracting new people and or a way of communicating ( > in > >>> public and with the purpose of attracting attention/new people). > >>> > >>> I am sorry to read that the web site proposal has been seen as a > private > >>> and already agreed on job. This was not the intention. Anyhow, if some > of > >>> you don't know it, then Jan is my husband and we do talk ... also about > >>> Corinthia. Before I retired to Southern Spain together with Jan I used > to > >>> work with web journalism and information strategies. > >>> > >>> All for now, looking forward to hearing your comments. > >>> Dorte > >>> > >> > > --001a11c3fb30fd7ffb050c22525f--