openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <orc...@apache.org>
Subject RE: [QUESTION] Getting to AOO for Java (AOO4J)?
Date Sat, 07 Nov 2015 21:08:10 GMT
+1

> -----Original Message-----
> From: Marcus [mailto:marcus.mail@wtnet.de]
> Sent: Saturday, November 7, 2015 11:57
> To: dev@openoffice.apache.org
> Subject: Re: [QUESTION] Getting to AOO for Java (AOO4J)?
> 
> All nice, but with a short of developers that could do any of the points
> you listed below, it's just a theoretical idea what could be done. ;-)
> 
> My 2 ct.
> 
> Marcus

[orcmid] 
I agree completely, Marcus.  The whole idea is to get the idea of an AOO4J
off the critical-path of AOO work/speculation and let those who are inclined
to attempt an AOO4J do their proof-of-concept elsewhere.  

> 
> 
> 
> Am 11/07/2015 08:41 PM, schrieb Dennis E. Hamilton:
> > There has been suggestion, and some expressed support, for AOO
> becoming a
> > Java application.
> >
> > I don't want to discuss the merits of this, but how it might be
> undertaken.
[ ... ]
> >   3. EXPANDING THE ODF TOOLKIT PROJECT.  This is my favorite.  The
> Apache ODF
> > Toolkit (incubating) project is Java-based already.  It deals with
> some
> > fundamentals about supporting the OpenDocument Format (ODF).  One
> could
> > imagine building up the modularization to the point where one could
> achieve
> > Writer, Calc, ... etc., workalikes.  There, AOO4J could be a
> demonstration
> > of composition of a suite (or even standalone components with shared
> > libraries).  There are also available related applications for
> > interoperability testing of the level of ODF support: Apache
> OpenOffice
> > itself, LibreOffice, and Microsoft Office.  The support for Microsoft
> Office
> > native formats could come from the POI projects and other open-source
> > resources.
> >
> > The test of capacity is then one of how (2) or (3) manages to grow
> into a
> > thriving project.  Meanwhile, AOO is sustained and there are no
> diversions
> > until a natural migration occurs.
> >
> > How does any of that sound.  It means that there would be no
> revolutionary
> > disruption of the Apache OpenOffice project itself.
> >
> >   - Dennis
> >
> >> -----Original Message-----
> >> From: Dennis E. Hamilton [mailto:orcmid@apache.org]
> >> Sent: Tuesday, October 20, 2015 15:36
> >> To: dev@openoffice.apache.org
> >> Subject: RE: [QUESTION] Optional Java Use for Essential Functionality
> >>
> >> Summary of what this thread revealed, in-line.
> >>
> > [ ... ]
> >> [orcmid] There were some unexpected responses to these questions.
> >>
> >>   2. One suggestion was to remove the dependencies on Java.
> >>
> >>   3. Other suggestions included increasing the dependencies on Java,
> >> perhaps
> >> going so far as to make AOO a Java application.
> >>
> > [ ... ]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> 
> 
> 
> --
> 
> Ciao
> 
> Marcus
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message