An Early Look at OpenOffice.org 3.0
ahziem writes "With the final release 167 days away and an alpha version available, it's time to look at OpenOffice.org 3.0's new features: view multiple pages in Writer, notes in the margin, Microsoft Office 2007 file format support, Solver in Calc, new visual theme in Calc, native tables in Impress, more columns in Calc, error bars in charts, performance improvements, real native Aqua Mac support, and more."
and there will be plenty of folk who can be pessimistic about this, but I'm having trouble with doing that. It's free, being improved, and already works as good or better than MS office for more than 99.9% of the needs of myself and my family as well as most people I know. Those are not empirical numbers (just a good guess) but I remain impressed. What are the downsides to this? I'm not trolling, just wanting to know what they are.
Support NYCountryLawyer RIAA vs People
Finally us mac weirdos will be able to move away from NeoOffice and get to the sweet sweet sensation that is OOO. It was just way way too slow on Mac before because the support was fake.
Features are nice, of course, but how does it perform? How much memory does it take to run? Will it work well on relatively slow hardware, or do I need the latest and greatest to run it? Is it significantly slower than the last version, significantly faster, or about the same?
Everything is subjective.
I guess I'm one of the few that really really likes the office 2007 interface and really wish OO would adopt something similar. That's not enough to get me to switch (not an option anyway, running linux fulltime now). It's a little frustrating to see MS continually evolving their product in very visible ways, while OO has looked pretty much the same for 3 years now. If we want people to switch to OSS, we need to be visually superior to MS. All the back end superiorities of OO are not immediately obvious to many (free file format, multiplatform, powerful editable style system, etc), aside from the cost.
Whether your like or hate the office 2007 interface, at least MS is out there rethinking how people use applications, which tasks they need to access the quickest, etc. OO is sticking to the same old massive row of buttons. Koffice is doing more thinking along these lines, but personally I don't really like where they're going. But at least they're rethinking things.
I am happy that after something like 5 years of suffering, the scientists finally get what they really need - definable range for error bars. Cause really, having to use Gnumeric for analyzing data, because OO 2.X was missing such a vital function was pretty sad.
Kudos to the development team for implementing these changes, and allowing me to further propagate open source software within the academic community.
??? It already exists? OpenOffice Base has a dependency on Java, but otherwise it's available for all platforms. (The core database is HSQLDB.) As I recall, you can use either JDBC or ODBC drivers to connect to a remote database.
The data sources configured in OpenOffice Base can then be used in programs like Calc.
So... I'm not really sure what the issue is?
Javascript + Nintendo DSi = DSiCade
You're a little confused.
Aqua is the set of widgets and such that make up the MacOS X user interface. It has evolved over the various versions of the OS, but it's still Aqua.
Quartz is the underlying PDF-based drawing technology that MacOS X uses to draw everything to the screen- including the Aqua UI widgets.
Referring to native Aqua is quite correct.
The ringing of the division bell has begun... -PF
This does not affect the users directly, but it is a major pain for integrators/porters. OO.o has a terrible habit of bundling all of the 3rd-party software packages, that it uses, into its own source tree. I'm talking about (probably missed some):
If they could, I'm certain, they would've bundled Java too, but — fortunately — Sun's license prohibits that... Now I realize, that this is done to offer "a single package" to those, who build it on their own, but nobody does. Everybody gets these from their OS' integrators. And the pain for us is enormous, because to force OO.o build to stop its silly ways is a serious undertaking. For some of the above packages there is --with-system-foo configure-flag, but not for all, and the default is to always use the bundled one, so support for the external ones bitrots quickly...
Most of the local builds don't bother and so end up wasting disk space and CPU-time rebuilding packages, which are external to OO.o. The end results are also bloated, duplicating stuff, that's already installed on the users' systems and without bug-fixes, which have already gone into each of the respective package since its most recent "bundling" into OO.o tarballs.
Download a source tarball and see for yourself... Something like: tar tjf OOo_OOG680_m9_source.tar.bz2 | grep 'z$'. No other software project does this on this scale and for good reasons — it is Just Wrong[TM]. OO.o better clean up their act in this respect...
In Soviet Washington the swamp drains you.