Will OpenOffice.org 3.0 be better?

Following on from my piece on whether OpenOffice.org can do the job I have remembered that OpenOffice.org 3.0 is due for release in September. So—with my comments on 2.3 in mind—let’s see whether the new version will address my needs.
Features
I’ll look at the features given by Sun in a presentation at last years OOoCon and examine whether they’ll be useful for my users. Of course, I’m judging this on a promised feature list rather than an actual product so I won’t be able to judge how well they work.
Personal Information Manager
Sun call this an “Outlook replacement” and it addresses one of the main excuses reasons for not migrating away from MS Office to OOo. Although we use Outlook here it may not be for much longer anyway as I am getting fed up with those oversized .pst files. I am instead looking at some web-based collaboration tools (a topic for a future column me-thinks).
OOXML import
This will come in handy because—even if we migrate to OOo—there are plenty who will continue to use MS Office and we will no longer need to ask them to send it in .doc format. I note it says import and not “import/export” but that’s not a big issue for us.
-
- Login or register to post comments
Printer-friendly version
- 1543 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
GitLab Web IDE
| Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
|
Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
| Security: Updates, Trustjacking, Breach Detection
|
Recent comments
2 hours 5 min ago
2 hours 6 min ago
2 hours 7 min ago
5 hours 13 min ago
5 hours 25 min ago
12 hours 18 min ago
1 day 14 hours ago
1 day 15 hours ago
1 day 21 hours ago
2 days 22 hours ago