5 ms·
Anyone know if this would impact on NeoOffice, the Mac native port? They seem to draw code from both LibreOffice and OpenOffice. [Side note: the way NeoOffice
by SyneRyder 10y ago
Anyone know if this would impact on NeoOffice, the Mac native port? They seem to draw code from both LibreOffice and OpenOffice.
[Side note: the way NeoOffice asks for yearly donations in order to access binary updates is very smart. Synergy also uses this method, and NeoOffice & Synergy are the first GPL projects I've regularly contributed to as a result.]
- davidgerard 10y agoNot at all. As I understand it (I looked into this when I was doing a big fix-up on the OpenOffice cluster of articles on Wikipedia), NeoOffice tracked OOo (and then ooo-build/Go-oo) until 3.1.1, when it stopped doing that and just maintained that codebase. Though they pull in fixes from LO and AOO, but I don't know how substantial that is - NeoOffice is only two guys.
- bsharitt 10y agoI used NeoOffice a long time ago when OpenOffice required X11 on OS X. Now that LibreOffice works natively on OS X, what does NeoOffice offer now? Is it like Camino was to Firefox?
- SyneRyder 10y agoWhile I've not tried LibreOffice (downloading now!), I think the Camino / Firefox comparison is a good one. My reason for choosing NeoOffice was because I wanted the most Mac-like experience and without a dependency on Java. It looks like the main difference/advantage right now is integration with the native Mac font rendering & grammar/spellcheck engines, according to the front page of the NeoOffice website.