SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
BTW this is answered in Document Foundation's FAQ as well:
Q: What does this announcement mean to other derivatives of OpenOffice.org?
A: We want The Document Foundation to be open to code contributions from as many people as possible. We are delighted to announce that the enhancements produced by the Go-OOo team will be merged into LibreOffice, effective immediately. We hope that others will follow suit.
Its the channel topic for the go-oo IRC channel in the freenode network.
It says that go-oo is deprecated and development switched to LibreOffice now.
Michael Meeks is a Novell employer, previously responsible for go-oo.
Today he is part of the leading team of developers working in LibreOffice.
You can read a very interesting interview of his about LibreOffice at LWN
The packages on my site are the result of the SlackBuild that is available on SlackBuilds.org This script does not really "build" LibreOffice as Eric does, it just repackages the binaries from The Document Foundation the "Slackware way".
It is marked as being for beta1, but the script works just as well with the second beta.
The packages have been downloaded over a hundred times from my site, that's over 17GB of data. Until now my provider has not complained
The other thing I wonder about is where things are going with the OO.org user interface update project. There was a lively debate around that project on how to update the user interface to make things better and whether or not to mimic Microsoft Office's new UI.
With all of that as background, and with LibreOffice being a fork, I have to wonder just how much of Open Office's code they're going to use in the future.
IMHO, it's much more important is document format compatibility. ODF development goes on, and I'd not be surprised, if Oracle would try sooner or later to "accelerate" this development to a pace that competitors just can't keep. It's a real good thing, that Novell and Red Hat and Google support LibreOffice, therefore!
Regarding the UI, LibreOffice means a new chance. The best UI was the one of StarOffice 5.2. It was intuitive for new users and highly efficient for experienced ones. It was fresh and fast. Totally different from MS Office. But all following releases tried to clone MS Office more and more, to a degree that you can look into the OOo help, if you want to find out how to do something in MS Excel. IMHO, this is the *wrong* way to go. It made OOo more powerful, and makes the switch for long-yeared MS Office users a bit easier. But in the end, they won't like their new environment more than their previous one, as it is equally bloated and much less responsive.
LibreOffice (and Go-OO) are faster, and better examples of what can be done. But regarding the UI, I hope that the developers take a break and then restart with fresh and new ideas, setting the pace themselves, instead of just thinking, how the UI of MS Office could be cloned without violating patents and copyright.
Compatibility is required on the backend, but productivity and user-friendliness should drive the UI development. LibreOffice means a new chance for that.
And, BTW, while KOffice is not even close to a point where it could be used for daily work, it has some good ideas implemented in its UI. For a new user, not spoiled by MS Office, it's probably much easier to start working with KOffice than with OOo.