Slashdot Mirror

colaboy writes "As of today, the folks at OpenOffice.org have successfully built OpenOffice.org 638c for Mac OS X using the X11 windowing system from XFree86.org. It works. They need, more than ever, help to finish it, so that it uses OpenOffice.org 1.0 and Aqua, and is bug-free. Download it now, and join the project and mailing list. Hunt for bugs; test features; make suggestions. They have proven the concept: OpenOffice.org can run--and it looks beautiful--on Mac OS X."

colaboy writes "As of today, the folks at OpenOffice.org have successfully built OpenOffice.org 638c for Mac OS X using the X11 windowing system from XFree86.org. It works. They need, more than ever, help to finish it, so that it uses OpenOffice.org 1.0 and Aqua, and is bug-free. Download it now, and join the project and mailing list. Hunt for bugs; test features; make suggestions. They have proven the concept: OpenOffice.org can run--and it looks beautiful--on Mac OS X."

DenialS writes: "Congratulations to the OpenOffice.org team! Version 1.0 of the open office suite has been released. I'm downloading it now; I've had good luck with the previous stable builds. Release notes haven't been posted yet, so I can't say what the major differences are between 1.0 and the previous stable build, 641d, but I'm looking forware to finding out!"

Damek writes "In the spirit of the proliferating news about Office alternatives and 1.0 versions this week, OpenOffice.org has released a new version of OpenOffice, 641d, the last planned release before 1.0. They're calling for help in pinning down and eradicating final bugs before they hit the big milestone: "...we would like you to download it, test it, and finally vote on the feature set.""

Damek writes "In the spirit of the proliferating news about Office alternatives and 1.0 versions this week, OpenOffice.org has released a new version of OpenOffice, 641d, the last planned release before 1.0. They're calling for help in pinning down and eradicating final bugs before they hit the big milestone: "...we would like you to download it, test it, and finally vote on the feature set.""

Over on NewsForge, Roblimo has taken a look at Sun's new StarOffice 6.0 (due out in April for retail purchase), and comparing it to OpenOffice build 641C. I installed StarOffice on a new Toshiba laptop, and since my Mandrake 8.2 ISOs are still trickling in, have StarOffice 6.0 running instead under Windows XP. (I have just a few additional notes on this, below.)

The installation was dead simple, and therefore better than most software: I popped in the CD, and with about 10 minutes of point-click-whirrring, the software was installed. The only notable aspect of this process is that the CD included (and popped onto my hard drive, with prompting) a new Java runtime environment (Sun's standard JRE, version 1.3.1). The helpful timer that accompanies the install is conservative, which is nice -- it started out estimating 14 minutes for the "transferring files" portion, but quickly dropped down to less than five.

Having not touched StarOffice for a while, it's nice to see the features in OpenOffice trickle in -- most importantly, getting rid of the monolithic desktop makes it actually usable to those of us who hate screen-hijacking software. And at least on this 1 GHz, 256MB laptop, even "bloatware" features like auto-correction are snappy enough not to be bothersome.

Two small notes on Roblimo's review for anyone curious about using SO under Windows: The Windows version does claim to open "WordPerfect (Win) 6.0-7.0" documents, which is at least a start toward WordPerfect compatibility. And under Windows, the nice X-Window style one-click text transfer isn't an option. One more note for 6.0 Beta testers: you can download a patch from Sun to extend the life of the beta from March 31 to June 3 2002.

nickbrown writes: "In this interview with the KOffice development team it is revealed that only about 4-6 people are working on the suite of applications. It would appear they lack the resources to keep up with the likes of openoffice. Worth a read as it highlights the troubles they are having trying to produce a truly productive office suite for KDE."

no parity writes "Last year on October 13, much of the source to Sun's StarOffice was released as the OpenOffice project. They have set up a birthday page to celebrate what they have achieved in that one year - yes, it prints, spellchecks and has online help. Keep up the good work, guys!" Yep - and my installation still spits up, too. *grin*

no parity writes "Last year on October 13, much of the source to Sun's StarOffice was released as the OpenOffice project. They have set up a birthday page to celebrate what they have achieved in that one year - yes, it prints, spellchecks and has online help. Keep up the good work, guys!" Yep - and my installation still spits up, too. *grin*

kevin@ank.com was there last night when "Max Lanfranconi of the OpenOffice project spoke to the Silicon Valley Linux User Group on Wednesday morning's release 6.0 of the LGPL'd office suite. When the project was opened two years ago, it was missing online help, spell-checking, and printing which had been based on proprietary commercial libraries. With release 6 the open source community has replaced these missing features." Read on for some more information on the new release, courtesy of Kevin.Update: 10/04 22:11 GMT by T : Several readers have pointed out that the 6.0 release is actually the beta of StarOffice 6.0. Though StarOffice is based on OpenOffice code, there's not actually a new build of OpenOffice yet. OpenOffice's is currently at build 638.

"Release 6 also gets rid of the old Star Office desktop of version 5 which was generally disliked for its annoying tendency to cover up all of the other windows you were working with and make it difficult to interact with your X Window Manager.

The application suite has programable APIs for each of the applications, exposed through a custom object request broker named UNO. In an impressive demonstration, Max showed live update of a spreadsheet with real-time stock data, all under the control of a small Java application. Changed data were reflected throughout the spreadsheet table with each update as the sheet recalculated each cell based on the new input.

Max freely admits that there are still weaknesses in the code. He pointed to the ten year lifespan of the mostly C++ code base, and hopes to see the code improved with the use of more modern C++ features. In browsing through the source tree I don't find that the code is in nearly as bad shape as Max portrayed it. Admittedly I've only seen a tiny fraction of the code (at 3.7 million lines, OpenOffice is by far the largest open source project in the world), but my random sampling showed very good coding practises, like preprocessor guards around each header include to reduce compile time due to reopening headers that have already been processed. Even with these measures in place however, the full system takes upwards of 15 hours and 1.5GB of disk to build on currently available hardware.

System load time for the office suite has been significantly reduced (about 20s on Max's 500MHz laptop with 128MB memory) by removing several libraries from the link process and instead loading them on demand. Over the next year or more Max hopes to see more modularization of the code base with the eventual goal of seperating the monolithic program into seperate applications linked together through an object request broker.

Q&A went on until we got kicked out of our room, so there is a lot more that is new about OpenOffice than I've described here. If you are interested you can pick up a copy at OpenOffice.org, or at one of its mirrors around the world."

kevin@ank.com was there last night when "Max Lanfranconi of the OpenOffice project spoke to the Silicon Valley Linux User Group on Wednesday morning's release 6.0 of the LGPL'd office suite. When the project was opened two years ago, it was missing online help, spell-checking, and printing which had been based on proprietary commercial libraries. With release 6 the open source community has replaced these missing features." Read on for some more information on the new release, courtesy of Kevin.Update: 10/04 22:11 GMT by T : Several readers have pointed out that the 6.0 release is actually the beta of StarOffice 6.0. Though StarOffice is based on OpenOffice code, there's not actually a new build of OpenOffice yet. OpenOffice's is currently at build 638.

"Release 6 also gets rid of the old Star Office desktop of version 5 which was generally disliked for its annoying tendency to cover up all of the other windows you were working with and make it difficult to interact with your X Window Manager.

The application suite has programable APIs for each of the applications, exposed through a custom object request broker named UNO. In an impressive demonstration, Max showed live update of a spreadsheet with real-time stock data, all under the control of a small Java application. Changed data were reflected throughout the spreadsheet table with each update as the sheet recalculated each cell based on the new input.

Max freely admits that there are still weaknesses in the code. He pointed to the ten year lifespan of the mostly C++ code base, and hopes to see the code improved with the use of more modern C++ features. In browsing through the source tree I don't find that the code is in nearly as bad shape as Max portrayed it. Admittedly I've only seen a tiny fraction of the code (at 3.7 million lines, OpenOffice is by far the largest open source project in the world), but my random sampling showed very good coding practises, like preprocessor guards around each header include to reduce compile time due to reopening headers that have already been processed. Even with these measures in place however, the full system takes upwards of 15 hours and 1.5GB of disk to build on currently available hardware.

System load time for the office suite has been significantly reduced (about 20s on Max's 500MHz laptop with 128MB memory) by removing several libraries from the link process and instead loading them on demand. Over the next year or more Max hopes to see more modularization of the code base with the eventual goal of seperating the monolithic program into seperate applications linked together through an object request broker.

Q&A went on until we got kicked out of our room, so there is a lot more that is new about OpenOffice than I've described here. If you are interested you can pick up a copy at OpenOffice.org, or at one of its mirrors around the world."

kevin@ank.com was there last night when "Max Lanfranconi of the OpenOffice project spoke to the Silicon Valley Linux User Group on Wednesday morning's release 6.0 of the LGPL'd office suite. When the project was opened two years ago, it was missing online help, spell-checking, and printing which had been based on proprietary commercial libraries. With release 6 the open source community has replaced these missing features." Read on for some more information on the new release, courtesy of Kevin.Update: 10/04 22:11 GMT by T : Several readers have pointed out that the 6.0 release is actually the beta of StarOffice 6.0. Though StarOffice is based on OpenOffice code, there's not actually a new build of OpenOffice yet. OpenOffice's is currently at build 638.

"Release 6 also gets rid of the old Star Office desktop of version 5 which was generally disliked for its annoying tendency to cover up all of the other windows you were working with and make it difficult to interact with your X Window Manager.

The application suite has programable APIs for each of the applications, exposed through a custom object request broker named UNO. In an impressive demonstration, Max showed live update of a spreadsheet with real-time stock data, all under the control of a small Java application. Changed data were reflected throughout the spreadsheet table with each update as the sheet recalculated each cell based on the new input.

Max freely admits that there are still weaknesses in the code. He pointed to the ten year lifespan of the mostly C++ code base, and hopes to see the code improved with the use of more modern C++ features. In browsing through the source tree I don't find that the code is in nearly as bad shape as Max portrayed it. Admittedly I've only seen a tiny fraction of the code (at 3.7 million lines, OpenOffice is by far the largest open source project in the world), but my random sampling showed very good coding practises, like preprocessor guards around each header include to reduce compile time due to reopening headers that have already been processed. Even with these measures in place however, the full system takes upwards of 15 hours and 1.5GB of disk to build on currently available hardware.

System load time for the office suite has been significantly reduced (about 20s on Max's 500MHz laptop with 128MB memory) by removing several libraries from the link process and instead loading them on demand. Over the next year or more Max hopes to see more modularization of the code base with the eventual goal of seperating the monolithic program into seperate applications linked together through an object request broker.

Q&A went on until we got kicked out of our room, so there is a lot more that is new about OpenOffice than I've described here. If you are interested you can pick up a copy at OpenOffice.org, or at one of its mirrors around the world."

jeffy124 writes "ZDnet has an interesting article on how OpenOffice, Sun's Open-Source version of StarOffice, needs some serious help in being ported to the Macintosh OS-X. With Microsoft about to release Office 2001 for OS-X and demo it at next week's MacWorld Expo, support in getting a Mac OS-X port out for OpenOffice is critical to keeping a Microsoft dominance of yet another operating system's office suite to a minimum. The project is need of someone to step up to the plate as a project lead."

jeffy124 writes "ZDnet has an interesting article on how OpenOffice, Sun's Open-Source version of StarOffice, needs some serious help in being ported to the Macintosh OS-X. With Microsoft about to release Office 2001 for OS-X and demo it at next week's MacWorld Expo, support in getting a Mac OS-X port out for OpenOffice is critical to keeping a Microsoft dominance of yet another operating system's office suite to a minimum. The project is need of someone to step up to the plate as a project lead."

OldBen writes: "This arose out of a thread that bounced between the OpenOffice and Evolution mailing lists. Looks like the folks that brought us phpGroupWare are looking to establish an open standard for communication between groupware components. A site has been established at http://www.ogsproject.org. Right now it looks like it's nothing more than a mailing list, but this is a critical step in the development of products that can once and for all replace Exchange/Outlook/Project, and therefore MS Office." Maybe I'm boring and have accountant-style glasses, but OpenOffice and phpGroupWare are two of my favorite projects, because I can taunt the very nice IT guy at the Microsoft-heavy office I used to work in with some tempting, flexible answers to the "what about Outlook?" question.

mprudhom writes: "According to Yahoo!, Sun has today released the source to StarOffice, as promised. Go to www.openoffice.org and download it, or just grab it with:
cvs -d:pserver:anoncvs@anoncvs.openoffice.org:/cvs login
cvs -d:pserver:anoncvs@anoncvs.openoffice.org:/cvs co OpenOffice ". Okay, people can stop submitting this now.

MEconomy asks: "I'm the CTO of a commercial entity developing a technology that we plan to 100% open source. I'm looking for other options, opinions, and bulletproof arguments to take to Open Source-leery business types to convince them to release earlier (my preference) rather than later." While releasing the source early is a good thing, it can be released too early. I would never release the code to a project that wasn't in a runnable state, and would honestly consider holding off source releases until the project was at least in the "beta" stage. What do you think?

"I am very curious what peoples' thoughts are on the tradeoffs (business risks, community reputation, etc...) between:

1. immediate release of the source code at product launch,
2. waiting until the technology has acquired a large enough user base to insure a competitor won't just 'take the code and run',
3. commit to full source code release and release piecemeal (ala ZeroKnowledge),
4. a short-term (~1yr) closed-release to mutually trusted third parties (e.g. EFF),
5. placing the code in a provable timed-release escrow."

   [Update by nik]: Accepted practice seems to be to wait until about a year after you're bought by Sun. . .

jjr writes "An article over at TechWeb states the date for the release of the source code Star Office 6.0 is on Oct. 13 and it will be released at openoffice.org." We've been hearing rumors of this for some time now, but I'm still looking for confirmation of the license, but the rumor is that it will be Open Source compliant, and hopefully GPL (especially considering the (well deserved) heat they took over their previous license). Rumors about the license in German. I've also heard that the among the major goals is a GTK port of the suite. Update: 07/19 01:31 PM by CT : It's apparently official: Finally a story in English proclaiming that it will be released under the GPL!