New: Blender LTS (Nov 14, 2023), Platform 27.0 (Nov 30, 2023)
450+ real apps (49GB), 1.1 billion downloads, Please donate.
Now Accepting Wire Transfers, Testing Ad Placements
Better than open office... Plz!
Go-oo has built in OpenXML import filters and it will import your Microsoft Works files. Compared with up-stream OO.o, it has better Microsoft binary file support (with eg. fields support), and it will import WordPerfect graphics beautifully. If you are reliant on Excel VBA macros - then Go-oo offers the best macro fidelity too. If you expect your spreadsheets to calculate compatibly, or you get embedded Visio diagrams in your documents, you'll want Go-oo.
Go-oo's user interface is more familiar, with lots of small pieces of polish. We have built-in (working) multimedia integration on Linux, a beautiful solver component, and yourChinese should look sane. We also integrate with your system better by default: eg. enabling native file-selectors on Linux.
From first-time startup, where we sort I/O to reduce seek cost, to a highly optimised second start application and a systray quick-starter on Linux we are faster. We use less memory than up-stream, we link faster, use better system allocators, and don't waste so much time & memory in the registry. Go-oo performance is hard to beat.
Contributing code to go-oo is simple, and fast, following the traditional hackers' process of peer code review: just mail patches to the mailing list, or when we get used to your code - commit your patch immediately to HEAD ooo-build: no CWS, no hours of tagging, paperwork, no specification, no hassle. Of course - if your patch sucks - expect to hear how it can be improved.
For the code to live, grow and improve, to encourage participation and compete with the other office suite - we need sensible licensing: ie. weak copy-left. While in general we think LGPLv3 is a great & sufficient license for our code, others eg. Sun & IBM appear reluctant to include LGPL code into their products, and prefer other licenses such as the CDDL (a weak copy-left derived from Mozilla's MPL). Luckily dual licensing under the LGPLv3 / CDDL can help here - and we recommend this for the majority of our code.
We believe that copyright assignment to a single corporate entity opens the door for substantial abuse of the best-interests of the codebase and developer community. As such, we prefer either eclectic ownership (cf. Mozilla, GNOME, KDE, Linux), or an independent, meritocratic foundation (cf. Eclipse, Apache) to own the rights. Having said that we recognise and applaud Sun's technical contribution to OpenOffice and recommend that small patches & fixes to existing Sun code should be assigned to them under the SCA, and up-streamed.
Go-oo is a developer run meritocracy. If you want to contribute something concrete: code, bug fixes, bug triage, significant translation, build-bot maintainance etc. then there is a place for you as a key part of the team. If instead, you want to market Go-oo, install it, talk about it - that's really excellent, but this is not our focus: there are no formal roles in development to reflect this valuable work.
This is just another variant of OpenOffice.org that doesn't really add anything you can't add yourself as freely available open source plugins if you'd like it. The only really big thing is OpenXML support which is coming in a more solid and stable form in OpenOffice.org 3.0... we have a portable version of the beta available here:
OpenOffice.org is one of our biggest apps and takes the longest to build and package. We won't be working on any of the various OpenOffice.org variants floating around. We don't have the time and there's honestly not enough interest to make it worth our while. That said, if you genuinely like one of these variants yourself, you can simply download OpenOffice.org Portable and replace the files in App\openoffice with the OpenOffice.org variant of your choice.
Sometimes, the impossible can become possible, if you're awesome!
I would like there to be a portable version of Go-OO. I am begineing to like it mutch better then openoffice.org or it's beta 3 version because of the many things it can do.
...but aparently, it duzn't incl00d a spelcheker, eh?...
"I don't hate cats...as long as they stay on the freeway, where they belong."
- Brad Stine
Dose have everything Openoffice.org dose and more. I am at work so no Firefox spell checker.
...have an MDI (Multi Document Interface)?...
That's my biggest beef about OO - I'm so used to using MDI interface to view numerous documents at the same time (Opera, Firefox, most text editors, Foxit PDF, etc.), I'm surprized that no 1 haz built an Xtension/Plugg-inn 4 it as yet.
Firefox plug in for openoffice.org is part of OO. It's under the internet section of openoffice.org settings/options.
I am still wateing for a portable version of Go-oo as it supports more file format's then openoffice.org.
[Duplicate comment in other thread removed by moderator JTH]
As discussed, we don't plan to do GO-OO due to time and resource constraints and the fact that the useful features of GO-OO are coming in OOo itself. Plus, GO-OO is a "development" build (read: not final/stable).
GO-OO is mostly the result of a Novell developer's disagreement with the OpenOffice.org team. Here is some more background from Sun on it.
For the most part, there is no difference between GO-OO and OOo for nearly all users. The few that need MS Office 2007 support (like folks with offices who force them to use the format) can find it in the OpenOffice.org Portable 3.0 Beta. It's definitely not ready for primetime, though... neither in the OOo beta nor in GO-OO.
Openoffice.org 3 beta 2 spellchecker isn't working correctly. It has everything as beeing misspelled I can't wate till the final is out then.
... what's an issue for the original version but not for the comming portable Beta2.
The portable Beta2 comes with dics an 'side by side installed' c## runtime (another issue with the original beta on some systems without installed c## runtimes).
But if John said, if You can't wait, make Your own Go OOo Portable
Paid for Software more or less?
What You need is OSS!
is that C++ or C# ?
The developer formerly known as ZGitRDun8705
OpenOffice.org needs C# now? Boo-hiss....can't be portable anymore then C#=.NET
Good bye OpenOffice updates, I'll stick with the last 2.x then.
Thanks for the info, I wonder what is John going to do about it.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
You sure you don't just mean the latest visual studio runtime and not actually .NET? If it's .NET we may not be able to redistribute it. You can't redistribute the .NET runtime environment on SourceForge, Google Code, etc since it's a big closed source mess. And that would essentially mean that OpenOffice.org packages aren't open source anymore.
What do you mean by "big closed source mess"?
What unorganized do you find about .NET?
no version is compatible with other .NET releases. 3.0 was backwards compatible with 2.0 at first, but then 3.0 service pack 1 removed that compatibility.
It is the latest MS visual studio runtime (msvc*90.dll).
Back Your pardon, but the last MS runtime I've used in programming was vb6 ;-).
How could it be based on.net and be used in Linux? As the.net is not fully supported in linux except experamentaly. As I am still waiting for paint.net in linux.
It's not based on .NET...the windows version just needs the latest msvc runtimes.