Slashdot Mirror


Open Office 2.0 Beta Candidate Released

JPyObjC Dude writes "The OpenOffice.org 2.0 beta candidate has been released. You can find the feature guide that covers the wide array of improvements over the current 1.1 release. There are a bunch of problematic UI quirks in 1.1 that have been fixed in 2.0." Feature categories include increased interoperability with Microsoft Office, Asian Language Features, Developer-Specific Features, and new Internet based features. Commentary and an interview with Colm Smyth available at NewsForge.com.

28 of 415 comments (clear)

  1. One day it'll be as good as MS Office! by bburton · · Score: 5, Funny
    Feature categories include increased interoperability with Microsoft Office...
    Hopefully the OpenOffice team has incorperated support for Clippy (finally!!). It's the one thing that's been keeping me from leaving MS Office. I just love that little guy. He's so helpful.

    I just don't know what I would do without all the incredibly useful toolbars in MS Office! Publishing my documents to the web, imbedding oh-so useful macros into all my documents. I like to turn them all on at the same time. I think there might even be an FTP client in there somewhere. You know what else I like about MS Office? I totally love th

    NO CARRIER
    NO CARRIER
    --
    Slashdot = ((Technology + Politics) / Trolls) % Grammar Nazis
    1. Re:One day it'll be as good as MS Office! by Gadgetfreak · · Score: 5, Interesting

      Our company just upgraded (I use the term loosely) to MS Office 2003, which got rid of the standard Office Toolbar. I thought it was rubbish anyways, and didn't use it. Programs are easy enough to find on the start menu, IMO.

      But you would not believe how many people came to me asking how to get their Office Toolbar to show up again. They just piled everything into it, and ignored the start menu altogether.

      I was so disappointed to find out just how many people really like those toolbars...

      --
      "No fair, you changed the outcome by measuring it!" - Professor Hubert J. Farnsworth
  2. Native Widgets! by Mr.+Sketch · · Score: 4, Interesting

    It's about time!
    (From TFA)

    Native system theme integration (native widget rendering)

    To enhance integration of OpenOffice.org with the underlying operating system, all user interface elements (such as buttons and scrollbars) will have the same look as those used in most other 'native' applications for that platform. OpenOffice.org will react on-the-fly to changes of the desktop theme, so when the user changes the desktop colors or theme, OpenOffice.org will adjust its own appearance to match.

    Native system theme integration will be available for Gnome (version 2.4 or higher), Microsoft (R) Windows (including XP and future versions), and KDE (version 3.2 and higher) desktop environments. On Windows XP the 'Windows XP Style' must be chosen under Settings - Control Panel - Display - Appearance to achieve the correct look.

    Theme integration will be the default for desktop environments that support it (listed above). Systems (for example, Windows 98/ME/2000, CDE) that do not support it will see no visual change in OpenOffice.org. On supported systems OpenOffice.org will always adopt the theme of the system and cannot choose not to do so.

    1. Re:Native Widgets! by moonbender · · Score: 4, Informative

      No.

      No engineering work has been performed on Quartz or Aqua development within the OpenOffice.org project since mid 2003. For the last year and a half all engineering work focusing on a native Mac OS X OpenOffice.org version has been concentrated in the NeoOffice/J project, using a combination of Java and Carbon technologies to replace X11.

      Due to various licensing, political, and fundamental engineering difficulties it is likely, for the near future, that native Aqua porting work will be based off of the NeoOffice.org project and not under the direct aegis of OpenOffice.org.
      (from http://porting.openoffice.org/mac/timeline.html)

      This was reported on Slashdot a couple of weeks ago.

      --
      Switch back to Slashdot's D1 system.
    2. Re:Native Widgets! by Qwavel · · Score: 4, Insightful


      My understanding is that it is NOT native widgets.

      Instead OOo did a lot of work to upgrade their own unique GUI framework to look and behave LIKE native widgets. This should guarantee longer load times, some unusual behaviors, and difficult integration. Most importantly though, this guarantees a duplication of effort as they maintain a completely seperate code base rather than contributing to one of the alternatives (eg. GTK+, wxWindows, SWT).

      As a C++ developer, I'm not going to work with the OOo code until they get their act together and start sharing code and work. Until then their code base is innaccesible to me.

      Please correct me if I'm wrong about what OOo is doing (I hope I am).

    3. Re:Native Widgets! by cozziewozzie · · Score: 4, Interesting

      Actually, I do think you are wrong.

      My understanding of their Native Widget Framework is that the VCL (the toolkit used by OO.o), in addition to drawing the widgets itself, can be used as a wrapper for Qt, GTK, MFC, or whatever else you are using on your system. So a little bit of overhead is there, but OpenOffice 2 should bring trully native look and feel.

  3. How's the database? by RazorJ_2000 · · Score: 5, Interesting

    I'm more interested in how the database is looking to be.

    --
    pi=sigma{n:0-infinity}[(1/16)^n][(4/(8n+1))-(2/(8n +4))-(1/ (8n+5))-(1/(8n+6))]
    1. Re:How's the database? by hey! · · Score: 5, Insightful

      Well, yeah. The open source databases are way beyond Access in robustness and performance and compare favorably with commercial offerings for non-enterprise level stuff. As a database professional, I would never willingly target Access as a delivery platform.

      But what is missing is the ability to give a normal person the capacity to muck around. That means spreadsheet entry view, a form entry view, forms design and report design components. Are you going to run a fortune 500 MRP system on Access? No. Are you going to run your office supply inventory on it? Sure. Even I use Access some times to do one shot projects like data conversions.

      What gets people into trouble with Access is when a small, ad hoc project gets not-so-small and not-so-ad-hoc anymore. We call it "hitting the Access wall". The world would benefit greatly from giving a system like mysql, postgres, maxdb, for firebird (preferably your choice!) the kind of front end convenience Access does.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  4. Re:WP? by Marthisdil · · Score: 5, Informative

    WriterPerfect filter spec link Writer The WordPerfect import filter is supported. You can now open a WordPerfect document in OpenOffice.org. http://specs.openoffice.org/writer/fileIO/writerpe rfect.sxw Seems so.

  5. Corel Suite by DeathFlame · · Score: 4, Insightful

    The only thing keeping my small office from switching over to OpenOffice is compatability with the Corel Suite, specifically Word Perfect and Quattro Pro.

    It used to be what our officed used exclusivley, but several people have been having issues with them. I've slowly started a switch to Open Office, but opening old documents and spreadsheet is impossible with Open Office, if they are any of the Corel Formats.

    1. Re:Corel Suite by wes33 · · Score: 5, Informative

      wordperfect import is supported via the libwpd project. This evidently still needs some work (although wpd2sxw does a good job for me). As the OO people acknowledge (in a linked document):

      "the filter needs continuous development to arrest bit-rot, and to improve it's capabilities. Many such developments have already taken place, but are not merged/proposed due to the voracious demands of bureaucratic process, and the commensurate stifling of the will-to-live."

      I know the feeling ...

    2. Re:Corel Suite by arivanov · · Score: 5, Informative

      Well, you simply have not run into the other big OO gremlin yet.

      Not a single vector graphics import format works properly.

      The ones that barely work (Autocad for example) lose colors and most of the formatting. So if you want to draw a half decent diagram using DIA and import it into an OO presentation you might as well forget it. Your only chance is to export it as a raster image and import it in OO. The result is horrible by all means. Horrible size, horrible visually, horrible in a print form and horrible to edit.

      And OO 2.0 does not fix a single one of this issues. Instead of that we get visual candy - KDE widget support. Excuse me, but can we actually get the basic functionality fixed first before we get into Clippy land.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
  6. Maximum row number by camcorder · · Score: 5, Funny

    At last 65536 rows as Microsoft Excell. Now lots of people will be able to use their xls files on OpenOffice.org as that's the major blocker for those people I know.

    1. Re:Maximum row number by RealAlaskan · · Score: 4, Funny
      At last 65536 rows as Microsoft Excell.

      Unfortunately, my boss uses spreadsheets (for populatoin models) with way more than 65k rows. He's stuck with Corel's spreadsheet, because it will do 1M by 1M spreadsheets.

      Obviously, we shouldn't be doing that sort of thing is a spreadsheet, but that's another story.

  7. Re:OO.o for OS X? by Noksagt · · Score: 4, Informative

    The most native that I have seen is NeoOffice. Native look & feel through carbon and java.

  8. Torrent link here! by Anonymous Coward · · Score: 5, Informative

    http://borft.student.utwente.nl:6969/ is the tracker

    OOo_2.0bc_Win32Intel_install.zip
    OOo_2.0bc_LinuxIntel_install.tar.gz
    these are direct links to the windows and linux installers.

  9. I can't wait by Schlemphfer · · Score: 4, Interesting
    I suspect I'm always going to be a WordPerfect fan, at least when I'm trying to do real writing instead of just get business done. But I'm nevertheless so grateful that OpenOffice.org exists.

    Just today, I got a friggin' Excel spreadsheet from my distributor. They wanted me to complete it and send it back to them. It would kill me to fork over my hard-earned dough for Microsoft Office, but thanks to OpenOffice.org I never have to. I just fired up the OpenOffice spreadsheet, inserted the data, saved it as an .xls file, and my distributor won't have any idea I don't even own Microsoft Office.

    This wasn't the time and place, but whenever I get a chance I tell people they can probably get by with OpenOffice.org instead of purchasing Microsoft Office. OpenOffice 1.1 is more than good enough for most tasks, so I can't wait to see how good 2.0 is. It's always nice to use a fantastic product that also just happens to keep me from having to pay the Microsoft tax.

    --
    I'm generally "Interesting," "Insightful," and even "Funny" here. What the hell happens to me at parties?
  10. Re:just curious by niki9 · · Score: 5, Interesting

    Plenty of small businesses, I'm sure. Mine is one of them, I work for a small design studio in NYC, 5 permanent employees on multiple OS's, all using OO, and most of our consultants do as well.

    --
    "Someone's gotta have some damn perspective around here!" -- Commander Susan Ivonova, Babylon 5
  11. Now smaller! by Anonymous Coward · · Score: 5, Interesting

    Anyone noticed that it is about 30megs smaller than the previous verison.

    Wonder why...

    1. Re:Now smaller! by narcc · · Score: 4, Funny

      Reminds me of a technical support story where a user called to complain that the new version of the software he purchased came on fewer disks than the previous version -- and wanted to know if they were shorting him on features.

  12. Beta Candidate?? by chris09876 · · Score: 4, Funny

    Is this a beta candidate? The only thing worse than google having betas for years is a company releasing a beta candidate.

  13. Impress Templates by dduardo · · Score: 4, Interesting

    When is OOo going to include more standard templates. To most people, Impress is useless because it doesn't come with a sufficient amount of bundled templates. Sure you can find more online, but people used to MS Office are not going to deal with that.

    1. Re:Impress Templates by dduardo · · Score: 4, Interesting

      That's exactly the problem. Many people, including myself don't have any artistic skill. That's why we need the bundled tmeplates.

  14. What Open Office Really Needs... by osewa77 · · Score: 4, Insightful

    is to work exactly like MS Office. Let's learn from the success of Firefox (vs Mozilla). Shortcuts, Menus, should be similar even if functionality is different. So people can migrate from Word without noticing the difference.

    1. Re:What Open Office Really Needs... by wildwood · · Score: 4, Funny

      is to work exactly like MS Office.

      Which version?

      --
      normal(adj)- people who don't sit on slashdot all day wondering why everyone else isn't building robots [DECS]
  15. A step forward by water-and-sewer · · Score: 5, Interesting

    I'm discouraged by the tremendous amount of comments here by people who have obviously not read the article but rather rushed to post "I hope it imports WP files" and the like. Holy schmoly.

    I think it's a great step forward. I signed up to be a beta tester for Star Office 8 and while I have only downloaded it this afternoon and won't get to install and play until tonight, I'm looking forward to the new features:

    Word Perfect import, a cleaned up user interface, better PDF export, better input filters for crapomatic Microsoft documents, and a database front end that can interface with MySQL? Who's yo daddy? Those are features that mean a lot to me.

    I'm a writer and I'm picky about my tools. And I take a Mac to school with me but run SUSE 9.1 and Xandros XD3 at home. Openoffice is the only software that really allows me to bridge the gap between those two platforms. On the Mac I run NeoOffice/J - a tremendous piece of software that's far more robust than people make it out to be. It doesn't load quickly, but once it does it gives me all the goodness of Openoffice.org with all the power of Mac OS X, and the interface is nice and clean, including native Mac print dialogues, and the like. I don't know what kind of alchemy went into marrying OO.o to Java to Mac OS X but I'm grateful someone went ahead and did it.

    Look closely at OpenOffice 2.0r1 and what you see is an attempt to steal marketshare away from existing MS Office users. That means cleaner widgets, better import/export capacity, and a look and feel that isn't too foreign. It's not breaking any barriers in the document-writing paradigm here (check out Mellel for Mac OS X for that), but it is making it easier for existing Office users to jump ship. And jump they will.

    There are several things I like about OO.o, including the stylist and navigator, the export to PDF functionality, and the way the interface meets my needs. At work I use MS Word 2003, and I swear to God I hate it, not because of who produces it but because it's the most awkward, confusing, automatic-in-unnecessary-ways piece of crap I've come across. And all that additional complexity has done little to make the secretaries I work with write good documents. I'm talking about borked-up formatting, inconsistent styles, and so on. OO.o deals specifically with those issues in a way I really appreciate.

    The new database component is a huge addition. To all you pinheads pontificating about how important an Access-like program is for the future of OO.o, shame on you for not having RTFA. This could very well be a killer app when all is said and done (the Star Office 8 beta forums make it look like it's still a bit buggy). That is: a front end that "looks like" Access, tied into a MySQL back end. That's fantastic! I currently use Rekall for my database front end, but I can't get a version for Debian, which is a major pain in the butt.

    In sum, ease up on all the "they better have included feature X." This is a major but manageable step forward, and while it doesn't solve all our problems, I think it's a big step forward to improving upon the success of previous editions of OO.o, and a big step forward to convincing potential MS Office refugees to give something new a shot. As for myself, I've decided compatability with MS Office users is no longer a concern to me. I'd rather just work alone with my grumpy ol' self. :)

    --
    If this were Usenet, I'd killfile the lot of you.
  16. Re:OO.o for OS X? by aldoman · · Score: 4, Interesting

    The trouble is that porting GUI software to OSX is very hard. This is due to Apple/anyone not caring about porting GTK to OSX, to run outside of X. Why Apple doesn't fix this is beyond me, as they could enjoy a wealth of nearly native software. It would also finally give some sort of cross platform GUI development platform that the Mac can be part of.

    I think OSX is getting very marginilised, which is a real shame since it's a very nice OS. When Linux supports my _printer_ and I can set it up in 1 minute using the GNOME printer configurationg tools, but I can't do it whatsoever on a much more expensive Mac, I think there is a problem.

    This is only going to happen more often as Linux starts to become the de-facto OS for 'simple' tasks - a hell of a lot of businesses only need an OS which can run a web browser (Firefox), do email and print, thanks to the huge amount of web-based applications which are coming on board. I still think it's got a way to go before businesses will completely migrate to it (even though Novell Linux Desktop makes it so much easier than any other distro I have used), but I think we'll certainly see more and more hardware/software being supported first on Linux, then Mac, if at all.

  17. On Moving NeoOffice to 2.0 by soullessbastard · · Score: 4, Informative
    Disclaimer: I am a developer of OpenOffice.org for Mac OS X and a founder of the NeoOffice project.

    I don't mean to be a curmudgeon, but NeoOffice/J won't be available in a 2.0 beta anytime soon. There are a number of reasons:
    • 2.0 isn't finished yet on any platform! We've already got so much on our plate that we simply can't spend our time working on such a large codebase that hasn't even yet reached code-freeze.
    • Mac OS X (X11) build support and testing for 2.0 isn't finished yet! In fact, it's only just begun. Because NeoOffice/J is built on top of the X11 base, we need to have a solid X11 version running and compiling before we can isolate whether bugs are inherent to Mac OS X or whether they are unique to the GUI replacement layer.
    • We haven't even finished NeoOffice/J 1.1! We're still working on trying to iron out all the bugs in the 1.1 based product. Moving to 2.0 is obviously going to introduce new bugs, and we can't consciously shoot ourselves in the foot right before a final release.
    • Translation of 2.0 isn't complete. NeoOffice/J supports localizations in over 40 languages, and we definitely don't want to leave any languages behind. We won't be considering moving until all of our supported languages are available.
    • 2.0 is not the final 2.0.x release. This is just a matter of fact...2.0 will probably have bugs after it is introduced and will have another 2.0.1 release, a 2.0.2 release, etc. It's easy to get caught up in the hamster wheel of keeping up with the torrent of patches and point releases from Hamburg and we can't afford to lose focus and let native porting suffer.
    • Moving to 2.0 is going to be a lot of work. Definitely months worth of dedicated work, actually, perhaps even more than a year. Just going from 1.0 to 1.1 took Patrick over a year easy and we're still not finished with that jump yet.
    • There are higher priorites than moving to 2.0. While folks love to clamor for "feature parity", we have different priorities (well, I do, perhaps Patrick disagrees). I am more than happy to trade 2.0 features in exchange for working on and completing the equally complex Mac OS X specific tasks, including:
      • getting the first "Final" release of NeoOffice/J!
      • moving to Java 1.4/1.5...crucial for the long-term viability of Neo/J on Tiger and future operating system revisions. There's no sense in spending a year perfecting 2.0 only to find it won't run on the latest and greatest. We already have to work around crashing bugs in the 1.3.1 VM every time there's just a minor update (e.g. 10.3.7 -> 10.3.8), and there's gotta be only so many more updates for which we can find workarounds until the VM just plain no longer works.
      • implementing the NWF and other Aqua widgets
      • using native file dialogs
      • beginning to redesign the interface to adhere to Aqua HIG
    • We only have so much time available! Although Patrick is truly astounding, there really is only so much time available as we need to feed our families and pay the rent from time to time. With limited resources available and several large and very technical projects looming on the horizon, they need to get prioritized.

    We're intending to backport the major feature of 2.0 that is required...OpenDocument format support. There are plans for an OpenOffice.org 1.1.5 release on other platforms that provides OpenDocument support which we hope to incorporate.

    What's most likely going to happen is that we'll try doing a NeoOffice/J 1.5 release with Aqua widgets and other Mac-specific features and technical enhancements. Our #1 goal isn't to keep up with the most up to date OOo release, but rather, to make a great Mac OS X office suite. NeoOffice/J 1.1 is the most solid foundation upon which to build it since it's the most bug free.

    Without substantial assistance (e.g. perfecting