![]() Registered Member ![]()
|
I know it is not kde related, but it is FOSS related so here is the question: what do you think of the recent OOo fork?
There are two things that bothers me: 1- Their declared beta release delete any stable OOo you have on your system. BAD. 2- They included all the "nice to have but completely broken and unstable" patches from go-oo project, which includes the utterly broken kde4 integration, the "enhancements" to pdf export that makes exported links unusable, the great "use hardware acceleration" options that makes Impress to crawl when not to crash... BAD. I mean, I understand and even share the need to divorce from Oracle... but they are not doing it well, IMHO.
RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2 |
![]() Manager ![]()
|
1) too soon to criticize
2) my understanding is the go-go project brought good stuff/enhancements (and used by many distro's?) 3) Sun's ownership created some issues over their tight control which is why go-go created 4) hopefully the new structure will bring more developers (Sun control known issue in contributions) 5) hopefully the new structure will bring faster development 6) am worried that the Oracle/Sun developers will be no more and thus decrease development 7) hope go-go merges note: per your #1 concern appears temporary and Windows only "The current LibreOffice beta replaces any existing OpenOffice.org installation, on Windows. Installations should co-exist in the future." |
![]() Registered Member ![]()
|
I would first point out that this is the beta release and not the stable release, so they are more than welcome to include all of the "nice to have but completely broken and unstable" patches, etc. So long as they make sure that the patches and features that are included in the final stable release are stable and work as expected (or remove them from the release branch if they don't make the cut).
As for your first item - deleting (uninstalling) any stable OOo, I would much prefer this to the current - we'll just install the new versions beside the old versions and you have to do your own due diligence to remove the old versions. Of course, I can only assume that this refers to installation on Windows since the package manager should have already been doing the proper upgrade on any Linux distribution. OTOH, I do agree that the beta shouldn't remove stable versions as you are installing the beta to test the new features, not to be a permanent replacement (and besides that, LibreOffice is a fork of OpenOffice and should be treated as completely separate).
airdrik, proud to be a member of KDE forums since 2008-Dec.
|
![]() Administrator ![]()
|
FYI: almost all distros use Go-Oo, Ubuntu included.
"Violence is the last refuge of the incompetent."
![]() Plasma FAQ maintainer - Plasma programming with Python |
![]() Registered Member ![]()
|
How is it broken? Granted, the only things in ways of KDE-integration I've noticed are the icon-theme and the file-selector but those seems to work as intended.
OpenSUSE 11.4, 64-bit with KDE 4.6.4
Proud to be a member of KDE forums since 2008-Oct. |
![]() Registered Member ![]()
|
The status bar is not properly repainted.
Randomly, the load/save dialog freeze for long times. Many extensions (OOoLatex, for instance) make OOo to crash if kde4 integration is installed... There were more problems, but I do not remember which ones. I remember many reports (several filled by me) on Novell's bugzilla about their OOo build with "using kde4? Try uninstalling kde4 integration" and "thanks, that fixed the problem". Last time I tried novell's build was less than a month ago to end a complex 300 page document with more than 60 figures, several pages/paragraph and character styles and several Math objects. Novell's build messed up everything (disappearing or moving images, images that suddenly covered their captions, broken pdfs on which links did not work...) so I returned to vanilla build and ended the work without a single problem... I don't know how anyone else use OOo, but with heavy use go-oo always gave me problems while vanilla build did not. Another problem with this fork is "rebranding": it took several years to make people know about OOo, but now everything must be started again, so there will be lot of confusion... Time to push koffice, maybe? ![]()
RGB, proud to be a member of KDE forums since 2008-Nov.
And proud to be a kde user since 1.1.2 |
![]() Registered Member ![]()
|
Hm, maybe I've just been lucky then because I've never run into any of those problems. No, not quite. I ran into the file-selector freeze at one time. Don't remember the exact circumstances though, and I run OOo (mostly Writer) on an almost constant basis and quite complex documents.
OOo certainly isn't perfect, but I haven't run into more problems with the Novell build as compared to the vanilla one. But as always: YMMV. But yeah, I would love to be able to switch completely to KOffice if nothing else for it being better integrated with KDE. But far too many of my documents are, as yet, rendered incorrectly. Or maybe I should say: sufficiently different for it to be a real problem.
OpenSUSE 11.4, 64-bit with KDE 4.6.4
Proud to be a member of KDE forums since 2008-Oct. |
![]() Registered Member ![]()
|
Since the version is still beta, I think it is too early criticism
It is natural that there will be many errors , and I believe will solve all of these things in final version stable, because sun will (mostly) to bring many of the developers, and will speed up the process of stable version |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar