Slashdot Mirror


Aqua OpenOffice.org v2.0 Cancelled

Ant writes "According to MacSlash's story, a recent post on OpenOffice.org said no Mac OS X work has been done since 2003 and that there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :("

689 comments

  1. Oh noes! by Luke727 · · Score: 2, Funny

    Open Source fail it? That's unpossible?!

    --
    If you find this post offensive, don't read it! THINK ABOUT YOUR BREATHING! I am what I am because of how apes behave.
    1. Re:Oh noes! by Rosco+P.+Coltrane · · Score: 4, Informative
      Not at all. It's a strategic choice. Look at the reasons given in the text:

      Regardless of the progress on native porting (or lack thereof), continued X11 development is crucial for the ongoing viability of OpenOffice.org on Mac OS X. There are a number of critical factors that make X11 more relevant then native porting:

      X11 Will Always be Faster to Market.....

      X11 Will Always be More Stable.....

      X11 Will Always Look like Other Platforms.....

      X11 is the Ultimate Testing Tool.....

      So essentially, what they're saying is, X is their basic graphical platform, they want it to stay that way, and they don't want to divert efforts to do a native port for a machine that they consider a niche market.

      They're just focusing on what they think will make the most users happy. Simple as that.

      --
      "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    2. Re:Oh noes! by bob+beta · · Score: 1

      In terms of Install Base, it would be suspicious to call X their 'basic graphical platform,' since I just installed and am using OpenOffice 1.1.4 on a Windows 2000 system. I didn't have to bring up eXceed to use it. . .

      In terms of X11, I guess Windows is a 'nichey port' but one with a lot bigger base than the Macintosh 'nichey port' would have.

    3. Re:Oh noes! by Anonymous Coward · · Score: 3, Insightful

      Yeah but openoffice on X11 basically sucks for an OSX desktop user familiar with the Macintosh interface.

      On a 1.2 GHz G4 with plenty of RAM, it's noticeably slower to start than any other app, including the dominant commercial office suite, and things like cutting and pasting between applications don't work. Add to that, unfamiliarity of the interface and poor interoperability with the file formats your clients and partners are using (can you say microsoft monopoly?) and it's not worth the trouble.

      Unfortunate, because, like it or not, OSX is a significant unix desktop userbase. I tried and failed to migrate a mac-centric client to open office, so I know from experience that users mostly just want to meet their deadlines. They don't care what the boss is spending for software, they don't care about vendor lockin, they don't care about philosophy, they don't even care much about stability. They care about ease-of-use (usually meaning familiarity) and interoperability.

    4. Re:Oh noes! by Bulln-Bulln · · Score: 2, Insightful

      They're just focusing on what they think will make the most users happy. Simple as that.

      That's just a lame excuse for "We are the mighty Sun, but we don't help those Mac faggots, because Apple is now competing with us in servers. We neither helped those OS/2 idiots when we released the StarOffice 5.2 source. We had the OS/2 sources of StarOffice 5.1, but OS/2 is from IBM and they are competing with us either. We didn't want to release the source of Win32 StarOffice, too, but Windows is too big to ignore."

      PS: No, I don't think that Mac or OS/2 user are fags or idiots, but it's my impression that Sun thinks that way.

    5. Re:Oh noes! by Tim+C · · Score: 2, Insightful

      X11 Will Always Look like Other Platforms

      But how many users are going to hop from platform to platform using OO, compared to the number who are going to stick to one platform (OS X) and hop from app to app?

    6. Re:Oh noes! by jcr · · Score: 1

      I suspect that it's more a matter of keeping X11 viable.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    7. Re:Oh noes! by ElGuapoGolf · · Score: 2, Interesting

      That's just a lame excuse for "We are the mighty Sun, but we don't help those Mac faggots, because Apple is now competing with us in servers. We neither helped those OS/2 idiots when we released the StarOffice 5.2 source. We had the OS/2 sources of StarOffice 5.1, but OS/2 is from IBM and they are competing with us either. We didn't want to release the source of Win32 StarOffice, too, but Windows is too big to ignore."

      Yeah, it couldn't possibly be that porting from X11 on Linux/Solaris to X11 on Mac is much much easier than actually creating an Aqua port.

    8. Re:Oh noes! by Anonymous Coward · · Score: 0

      Well, Sun doesn't exactly do much for the Apple platform in general. Apple provides the JVM, because Sun refuses to. Sun has allowed Apple access to needed code to provide functionality like the Hotspot compiler, but refuses to provide any work towards the platform themselves.

      This is another reason why the Aqua port is getting no love, because Sun doesn't like bending over for companies unless they are being lubricated with the green.

    9. Re:Oh noes! by tverbeek · · Score: 1
      PS: No, I don't think that Mac or OS/2 user are fags or idiots,

      Well, some of us are!
      PS: No, I've never used OS/2.

      --
      http://alternatives.rzero.com/
    10. Re:Oh noes! by MikeFM · · Score: 3, Insightful

      They'd do good to do a port to the gecko engine used by Firefox and other Mozilla apps. That way the two projects could share resources for making the apps friendly for a wide-selection of platforms.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
    11. Re:Oh noes! by tverbeek · · Score: 1
      But how many users are going to hop from platform to platform using OO, compared to the number who are going to stick to one platform (OS X) and hop from app to app?

      I'm actually a pretty frequent platform-hopper, using Linux, OS X, and Windows to some extent just about every day. It's one of the reasons I've standardised on OOo: the availability of the same feature set and file formats on all three. (For example, I can pull up the script for my graphic novel and work on it no matter where I am and what I'm supposed to be doing.)

      Although my platform hopping does gets me a little mixed up sometimes regarding the placement/function of the Alt/Ctrl/Command/Windows/Option keys, I generally don't find the UI differences problematic; I expect them. The only situation in which I'd see the different "look" as a serious concern is for the *n*x- or Windows-only user who finds himself sitting at someone's Mac, wondering why there's no menu along the top of his OOo window. This point was a nice try at justification for the decision, but it's really a very minor factor, and not worthy of being placed alongside the other more compelling reasons.

      --
      http://alternatives.rzero.com/
    12. Re:Oh noes! by Warhaven · · Score: 1

      Buggers. I want the $10.00 back that I donated.

    13. Re:Oh noes! by Bulln-Bulln · · Score: 1

      Of course it's easier. I never said anything else.
      But as you can also see, Sun doesn't have a lot interest in helping other plattforms. Sun had the OS/2 sources for StarOffice. They didn't release it. Why not?
      Sun also had older Mac sources for StarOffice. While not the latest code, it may could have served to help create a Carbon version of OpenOffice.

    14. Re:Oh noes! by ElGuapoGolf · · Score: 1

      But as you can also see, Sun doesn't have a lot interest in helping other plattforms. Sun had the OS/2 sources for StarOffice. They didn't release it. Why not?

      Because there were exactly 47 users of OS/2 left once Sun bought the Staroffice product. Mind you, as one of the 47 I was pretty crushed, but I do understand sometimes people make those decisions that make business sense.

    15. Re:Oh noes! by tverbeek · · Score: 1
      They'd do good to do a port to the gecko engine used by Firefox and other Mozilla apps.

      How would an HTML-rendering engine help them with UI APIs?

      --
      http://alternatives.rzero.com/
    16. Re:Oh noes! by MikeFM · · Score: 1, Informative

      Uhh Firefox, Thunderbird, etc is written using that engine. It isn't just an HTML engine. It's a general UI API that portable apps can be written in using common tools like HTML, CSS, Javascript, XML, etc. Why not port OpenOffice to that platform.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
    17. Re:Oh noes! by Anonymous Coward · · Score: 0

      You're thinking of XUL idiot
      XUL is the cross-platform XML-gui lib.

      Moz/FF/etc are XUL apps using the gecko renderer for html.

    18. Re:Oh noes! by sander · · Score: 1

      This is total bullshit. The OS/2 part of the sources were released together with the others and even more were *NOT* thrown out even after nobody had shown any interest in them for more than 3 years. It doesn't mean the sources would build out of the box - they won't as there has been no maintenance on those platform specific parts - it just means that they are / were there to be picked up by interested parties. Except that there is no evidence therea re any.

    19. Re:Oh noes! by arivanov · · Score: 1

      No, This is Sun marketing and project management choice. They are looking at OO as a part of their desktop solution. A different OO will increase their training costs, muddy the overall message and most importantly increase the sales of a CPU that is in the servers of their main competitor.

      When Sun is making a decision you can always count on the following: they will make the decision regardless of technical or financial merit if the words IBM are involved anywhere. In that case it will be whatever the anti-IBM decision will be. It is part of the company culture (just ask any old time Sun staffer anything about IBM and watch).

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    20. Re:Oh noes! by MysteriousPreacher · · Score: 1

      I'm sure I've used an OS/2 powered ATM at least once over the years so you'd better make that 48 users.

      --
      -- Using the preview button since 2005
    21. Re:Oh noes! by AaronLawrence · · Score: 0

      That would be pretty much a rewrite. Just as easy to say, "port it to Visual Basic"

      --
      For every expert, there is an equal and opposite expert. - Arthur C. Clarke
    22. Re:Oh noes! by the+angry+liberal · · Score: 1

      Add to that, unfamiliarity of the interface and poor interoperability with the file formats your clients and partners are using (can you say microsoft monopoly?) and it's not worth the trouble.

      So, you think the reason why OO on OSX sucks at handling common business file formats is because Microsoft has a monopoly? The next time I write bad code, I'll be sure to blame Microsoft too. Then, at least, I'll fit in with special people like yourself.

    23. Re:Oh noes! by Anonymous Coward · · Score: 0

      Hey idiot,
      XUL is rendered using Gecko.

    24. Re:Oh noes! by jedidiah · · Score: 1

      Size of the userbase is NEVER a valid excuse not to release source. So the source languishes, big deal. If no one "picks up the ball", then Sun is no worse off for it.

      Not releasing the source to a particular sub-project when you are releasing the rest of it is just childish and petty.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    25. Re:Oh noes! by 4of12 · · Score: 1

      So the obvious question is why can the MS Office development team straddle the Mac OS X and the Windows platforms while the OpenOffice development team deems it too difficult?

      Is it

      1. they can't afford to pay as many professional developers?
      2. they have higher standards about messy codebases where MS marketing gets to run over the Office development team and tells 'em to lump it?
      3. there are smaller technical differences between the low level display technologies of Mac and Windows than between Mac and X11?
      4. there isn't enough flexibility in the personalities of the different OOo developers (wouldn't be the first time that programming talent was bundled with prickly personalities)?

      While they may have a point about the stability of X11, I can't believe everyone is happy about its technical features - hopefully X.org will improve things for all of us.

      --
      "Provided by the management for your protection."
    26. Re:Oh noes! by Paladin128 · · Score: 1

      I think you're talking about the XUL platform. It's a toolkit/platform, not an engine -- there's a BIG difference.

      --
      Lex orandi, lex credendi.
    27. Re:Oh noes! by MikeFM · · Score: 1

      It still takes a layout engine to do something for the toolkit/platform. It's all one ball of wax. Regardless, my point is that OpenOffice should be ported to that toolkit/platform/engine/thingamabob.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
    28. Re:Oh noes! by JohnFluxx · · Score: 1

      Just because they are common it doesn't mean they are easily read. They are fantastically complicated to get right. Even Office corrupts them from time to time (Ever had word put big X's where your pictures should be? Ever had Access corrupt your database?)

      So yes, OO's problem with handling Microsoft documents is because, gasp, of Microsoft.

    29. Re:Oh noes! by LPetrazickis · · Score: 1

      The Mac and Windows Office are based off two different codebases.

      Microsoft tried to unify the codebase with Word 6.0 for Mac, but it was such a disaster that they ended up selling downgrades back to Word 5.1 for Mac.

      --
      Is this a sigs-optional kind of place? 'Cause I am totally down with that if you know what I mean.
    30. Re:Oh noes! by Paladin128 · · Score: 1

      1) The XUL toolkit isn't rich enough to build all of OpenOffice.

      2) Other cross-platform toolkits that do the job better are already available. Qt, WxWindows, etc.

      3) Are you willing to foot the bill for 10,000+ man-hours? Porting OpenOffice.org to a new toolkit is NOT a trivial task.

      What really needs to be done is the VCL needs to be re-implemented for Carbon/Cocoa. This is NOT an easy task. It's unfortunately not a priority for Sun, or most of the OO.o volunteers. Honestly, there needs to be a whole crapload more programmers that switch to a Mac (possible, with the new Mac Mini), or some company has to get behind it -- and there's no company with anything to gain by doing so.

      --
      Lex orandi, lex credendi.
    31. Re:Oh noes! by aztracker1 · · Score: 1

      "there's no company with anything to gain by doing so"

      Hmm... what about Apple? I know they have their own iWorks, but it just seems to me that a "Apple Office" based on Ooo wouldn't be a bad idea at all.

      --
      Michael J. Ryan - tracker1.info
    32. Re:Oh noes! by Paladin128 · · Score: 1

      OO.o is functional, but not NEARLY smooth and slick enough. Look at OpenOffice Writer and put it next to the screenshots of Pages...

      Besides, for the Apple name to be on it, they'd want it to be an Apple exclusive product. Like the rest of iLife.

      --
      Lex orandi, lex credendi.
    33. Re:Oh noes! by aztracker1 · · Score: 1

      Probably so, been looking at pages, and with the price point for the mac mini, may just put one of these on my kvm.. :)

      --
      Michael J. Ryan - tracker1.info
    34. Re:Oh noes! by MikeFM · · Score: 1

      Which part of OpenOffice is XUL not rich enough for? It works for all the UI elements of Firefox, Thunderbird, Classic Mozilla Suite, and several other apps. Web page content can be positioned very precisely and supports fully animated content, alpha transparency, etc. I'm sure improvements could be made but I don't see any reason it couldn't handle the job.

      Other cross-platform toolkits are not as flexible as XUL. You can't use use CSS and Javascript to easily tweak Qt, Wx, etc apps. I personally like Wx a lot but I don't think OpenOffice, Firefox, etc would be better than XUL.

      Porting to XUL would be profitable since future toolkit work could be shared between multiple projects. As opposed to using Aqua, etc which is basicly a wasted effort of a port. I thought OpenOffice should have worked with the Mozilla project on a common toolkit from the beginning but I guess they didn't see the benefits.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
    35. Re:Oh noes! by arkanes · · Score: 1

      There was some talk about porting OOo to either XUL or to wxWidgets (Qt isn't practical because of the license restrictions on Windows). What I got from the discussion is that a) porting to a new toolkit would be a boatload of work, b) it's boring work that nobody wants to do. and c) writing your own toolkit is intersting and fun. Simply porting VCL to the Mac turned out to be impractical because of basic structural differences (the wxWidgets Mac port runs into many of the same problems). The OOo project suffers from a pretty hardcore case of NIH, in my experience. It's possible that the writing off of a Mac port will spark more interest in a port to a new toolkit, though.

    36. Re:Oh noes! by Anonymous Coward · · Score: 0

      I sure hope the independent XUL implementations like the one the KDE team is developing know that.

      Wow! that's a load off my shoulders.

      XUL is a language like HTML and was intened to be platform-independent just like it.

  2. What's the downside to using X11? by Eric+Smith · · Score: 5, Interesting

    Forgive my ignorance, but doesn't OS X include an X11 server? Is there any major drawback to running OpenOffice as an X11 application rather than a native one?

    1. Re:What's the downside to using X11? by Mathiasdm · · Score: 3, Informative

      I think it's not all that easy to install OpenOffice.org as X11 application.

      It requires some work (according to what I heard).
      In other words: it won't be popular for 'Joe Average'.

      --
      Join the anonymous, help develop the network: http://www.i2p2.de
    2. Re:What's the downside to using X11? by Zelet · · Score: 5, Informative

      Yeah, I run OO under X11 on OS X - but it is as ugly as it is on Linux. Which is pretty damned ugly and slow.

      --
      ...And when they came for me, there was no one left to speak out for me." - Martin Niemoeller (1892-1984)
    3. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      While X11 can be considered native, (no slowdowns) the UI isn't totally native and it still doesn't look or behave like an OS X application

    4. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Is there any major drawback to running OpenOffice as an X11 application rather than a native one?

      It doesn't look native. Every program looks different in Windows, the odd program looks different on UNIX/X11, but such actions are not tolerated on the Mac.

    5. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Yes. No. respectively

    6. Re:What's the downside to using X11? by Anonymous Coward · · Score: 1, Insightful


      Other than it's slower and looks like total crap?

      Sorry, but X11 is something which should have died a quiet death circa 1994. Even with the newer WMs you can still spot an X11 app a mile away (although to be fair, that has a lot to do with all the crap GUIs designed for unix apps...I'm looking at you, Gimp.)

    7. Re:What's the downside to using X11? by NSash · · Score: 2, Insightful

      It's slow and ugly, at least in comparison to native apps.

      This news is really a pity.

    8. Re:What's the downside to using X11? by mr100percent · · Score: 4, Informative

      The non-aqua version which uses the X server works fine... if your objective is to have something that works similar to Linux.
      It works fine until you actually want to use the wealth of rich, high-quality fonts that comes with OS X. So I guess that makes the NeoOffice/J project ever more important.

      The NeoOffice/J team has done a fantastic job of gradually Aquafying OpenOffice without anywhere near the same resources.

    9. Re:What's the downside to using X11? by JayDiggity · · Score: 5, Informative

      Functionally, there is little difference except that is certainly slower than running it natively. Where the big problem lies is that Mac users (and I'm one of them) expect coherence and integration in their UI. A Mac version of OpenOffice that runs using X11 will not provide this.
      Also, think of anyone who's switched over from Windows with a sour taste in their mouth - they want to avoid Microsoft at all costs, including MS Office. They've heard great things about OpenOffice, but when they go to try it, it's slow and kludgy. Not a very good impression at all.

    10. Re:What's the downside to using X11? by dn15 · · Score: 4, Insightful

      OOo works fine under X11, but...
      - Most people don't have X11 installed - it's optional.
      - It doesn't have the key combos people are used to.
      - It may never be made to *look* native if it remains X11-only.
      - Menubar is in the "wrong" place for a Mac app.
      - It doesn't have a standard Dock icon of its own.

      Those are the primary issues, and none of them are necessarily deal-breakers for you or me. But they they severely hamper usability for inexperienced users who don't know what X11 is and won't understand why the app looks and behaves the way it does.

    11. Re:What's the downside to using X11? by lakeland · · Score: 4, Insightful

      Yes, it is ugly. It integrates very badly into the rest of the system (e.g. you can't alt-tab to it properly). Copy-Paste doesn't work between other apps well. The whole UI feels like a unix application.

      I guess it would be like running a windows app on linux and having the whole thing feel like a windows app. Sure, it runs and it is better than nothing, but compared to a true linux app it is awful.

      A native (carbonised) OOo would be suitable for giving to people running OSX that ask for a word processor. An X11 OOo is suitable for linux users who also have a mac.

    12. Re:What's the downside to using X11? by Goalie_Ca · · Score: 4, Interesting

      As a linux user before i got my mac i was wondering the same damn thing... but then i got my mac. First of all, the X11 applications don't conform to apple's UI guidelines. It just doesn't fit in at all. It's goofy and awkward. Secondly, you gotta load up an x11 environment and then the application. You thought it took long enough to load up already? Luckily X11 doesn't take up too much memory though x11 applications feel less responsive for stuff like menu systems. It draws really fast, but doesn't respond too quickly.

      --

      ----
      Go canucks, habs, and sens!
    13. Re:What's the downside to using X11? by Dr_LHA · · Score: 5, Informative

      It just doesn't work very well. It's interface runs slowly (on my 1Ghz G4 Powerbook) and it doesn't fit in well with the rest of the operating system. Also the Powerpoint clone doesn't actually work properly as I was unable to get it to run the slideshow full screen, which makes it effectively useless for anything other than composing presentations.

      I use OpenOffice all the time on Linux, but for my Mac I went out and bought MS Office as I needed Office software. OpenOffice on X11 just doesn't work well enough for it to be any use.

    14. Re:What's the downside to using X11? by J.+J.+Ramsey · · Score: 2, Informative

      "Is there any major drawback to running OpenOffice as an X11 application rather than a native one?"

      IMHO, the biggest drawback is that the fonts are awful. The antialiasing in OpenOffice X11 isn't too wonderful.

      Pity Apple didn't compile in the TrueType bytecode interpreter into the FreeType library bundled with X11. Then OpenOffice could leave the antialiasing turned off, and the fonts would be readily readable.

    15. Re:What's the downside to using X11? by Anonymous Coward · · Score: 3, Insightful

      If you are talking about "functionally", things like a working clipboard are essential. Especially for Mac users which historically have had nearly no integration problems (drag-n-drop and rich clipboard always Just Worked unless you still X11 into the mix)

    16. Re:What's the downside to using X11? by Grey+Ninja · · Score: 0

      Personally, I am inclined to blame Apple for the lack of integration with X11. They try to give X11 just enough support to be functional, but they still want to be different enough to warrant a complete rewrite of code for their platform to be fully useful.

    17. Re:What's the downside to using X11? by Yaztromo · · Score: 5, Informative
      Forgive my ignorance, but doesn't OS X include an X11 server?

      Ignorance forgiven :).

      Mac OS X Panther (10.3) does indeed come with an X11 server. However, there are two caveats to this:

      • It isn't installed by default, so if the user didn't select it for installation, it won't be on their system,
      • Apple doesn't include the X11 server on systems with OS X preloaded (which is all of them). (It is included on the CDs/DVDs you get with the system, however),
      • Installation of X11 after OS X is installed typically requires the user to reboot their system with their OS X install disc, and then install the X11 support atop their existing OS X installation.

      Not a major problem for power users who need X11 support (this was virtually the first thing I did when I took posession of my first PowerBook last year), but hardly something you can expect your average user to do.

      Is there any major drawback to running OpenOffice as an X11 application rather than a native one?

      Yes, there are multitudes of such problems, including:

      • Unlike every other OS X application, OOo has an in-frame menu bar, and doesn't use the system menu bar (perhaps worse, as X11 does provide a menu bar, you wind up with two menu bars that have some duplication -- for example, both the X11 server and OOo's frame have an "Edit" menu, which can be confusing to a user),
      • The installation and program launching routine isn't terribly user friendly,
      • Apple's excellent font subsystem isn't integrated into OOo, thus you don't get good anti-aliases text,
      • No Aqua look and feel -- everything in it looks quite a bit different from every other application. No nice Aqua scroll bars, for example. Or list boxes. Or other standard controls.
      • No desktop integration. The icon in the title bar can't be dragged (in most OS X apps, the icon in the title bar actually represents the document or data being worked on, and you can drag and drop it as if it were the applications icon in the finder, allowing you to do stuff such as e-mail a document by dragging it's title bar icon and droppinng it into the Mail applications icon in the Dock), no text drag-and-drop with the rest of the system, can't use any of the Mac OS X services (like summarization, or text-to-speech), etc.
      • Doesn't even use the standard OS X mouse pointers. Even the plain old black arrow pointer is different as soon as you mouse over OOo,
      • Doesn't use the standard OS X printing subsystem controls (which is too bad, as the standard OS X print dialog makes it easy to print, fax, or save to PDF all within a single dialog),
      • In fact, all of the dialogs are non-standard. File load/save dialogs are another area where this is readily apparant.

      That's just a sampling of issues off the top of my head.

      The one thing they did at least do was to integrate OOo with OS X's clipboard support directly, making cut and paste between applications work as expected. But that appears to be the extent of OS X support.

      I'm rather disappointed in the attitude of OOo in this regard, because OS X really should have a native port of OpenOffice. The only way OpenOffice can take on Microsoft is to not only build a better office suite, but to make sure it's available virtually everywhere in versions that integrate well with whatever operating system it's being used on.

      Anyone other than me remember when StarOffice's target operating system was IBM's OS/2?

      Yaz.

    18. Re:What's the downside to using X11? by Durandal64 · · Score: 1

      Oh give me a fucking break. Aqua is one window server; X11 is another. When developers write for either, they use different APIs. If you can think of an easy way to bridge the two completely toll-free so that no code modification is required, I'd love to hear it.

    19. Re:What's the downside to using X11? by Megane · · Score: 1, Flamebait
      Installation of X11 after OS X is installed typically requires the user to reboot their system with their OS X install disc, and then install the X11 support atop their existing OS X installation.

      Wrong. You should be able to just insert the install disc, find the appropriate .PKG files, and double-click on them to run the installer.

      I guess everybody's just too busy constantly recompiling their Linux packages from source to mess with an OS X port. Must be the same problem with the MESS emulator, which hasn't been upgraded since 2003 either.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    20. Re:What's the downside to using X11? by Grant_Watson · · Score: 1

      It doesn't look native. ...such actions are not tolerated on the Mac.

      This is very true.

      ... Every program looks different in Windows, the odd program looks different on UNIX/X11....

      Um... you must have a different standard for "different" on Unix. Programs all look different on Unix, unless you are in a Mac-user mood and confine yourself to programs that follow the Gnome HIG or something. By comparison with Unix, Windows interfaces are pretty standardized.

    21. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      It's X, therefore it looks like shit.

    22. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      He's referring to the fact that OpenOffice wouldn't match the look and feel of native applications. Most applications on Mac follow the same conventions but OpenOffice would stick out like a sore thumb.

    23. Re:What's the downside to using X11? by d00ber · · Score: 1

      The fonts and menus look absolutely horrible - worse than Linux in fact.

      One solution is to use a PPC Linux distro. OOo looks pretty good on Yellow Dog last time I checked. I don't do much wordsmithing at home.

      I know this last solution is not for a user who just wants the Mac to work though.

      Perhaps the best solution is to give some attention to getting the X version on Mac too look good.

      I think it is a bad idea to abandon the MacOS X version just whan Apple comes out with iWork.

    24. Re:What's the downside to using X11? by bob+beta · · Score: 1


      I guess it would be like running a windows app on linux and having the whole thing feel like a windows app. Sure, it runs and it is better than nothing, but compared to a true linux app it is awful.


      It must be a truly weird alternative universe that you're dwelling in.

    25. Re:What's the downside to using X11? by GuidoW · · Score: 2, Interesting

      I guess it would be like running a windows app on linux and having the whole thing feel like a windows app. Sure, it runs and it is better than nothing, but compared to a true linux app it is awful.

      Funny, this is a perfect description of what it's like to run OOo on Linux - The installation looks and handles like a Windows app's, the way it integrates into the system is Windows school of thinking and it shows, the installed application looks and feels like a Windows app and finally you can, by default, not use all of the fonts available to all the other X-apps you're usually using....

      --
      If it's so secret, then how come I've never heard of it?
    26. Re:What's the downside to using X11? by Quino · · Score: 1

      It's not too bad, you can get X11 for Mac OS X from apple:

      http://www.apple.com/macosx/features/x11/download/

      It doesn't come preinstalled, but I remember it was about as easy as anything else that you need to do on a Mac (that is, pretty straighforward). Just reading the link above, apparently it comes bundled:

      Optional install from the third Mac OS X v10.3 Panther CD.

      I installed it on my woman's laptop so that she could try out OpenOffice before forking cash over for MS Office. Sadly, it didn't handle the extremely complicated spreadsheets she uses at work (I realize she's somewhat of an exception, she does use/create very complicated spreadsheets and little inconsistencies made the graphs not always work out. Oh well, she had to feed the beast.)

      I had no idea of a native OpenOffice.

    27. Re:What's the downside to using X11? by Grant_Watson · · Score: 2, Informative

      Sorry, but X11 is something which should have died a quiet death circa 1994. Even with the newer WMs you can still spot an X11 app a mile away (although to be fair, that has a lot to do with all the crap GUIs designed for unix apps...I'm looking at you, Gimp.)

      Um... X11 is the underlying technology. I don't have any real Unix GUI experience, so somebody correct me if/when I'm wrong: X11 has no concept of a button. Buttons, text boxes, list boxes and other "widgets" are drawn by a toolkit. GTK is used for Gnome and its stuff; Qt is used for KDE and its stuff.

      The programs you are talking about just use old-fashioned toolkits. For a better explanation, look at the above link by a guy with a really spiffy first name.

    28. Re:What's the downside to using X11? by GFLPraxis · · Score: 2, Insightful

      1) Difficult to install.
      2) Slow as heck.
      3) Ugly as heck.

    29. Re:What's the downside to using X11? by bob+beta · · Score: 1

      Anyone other than me remember when StarOffice's target operating system was IBM's OS/2?

      So you're saying MacOS X has a similar future ahead?

    30. Re:What's the downside to using X11? by gallir · · Score: 1, Informative

      OOo ugly in Linux?

      It's as "ugly" as in windows. And much faster.

      --
      sgis ddo ekil t'nod i
    31. Re:What's the downside to using X11? by bob+beta · · Score: 3, Informative

      I guess everybody's just too busy constantly recompiling their Linux packages from source to mess with an OS X port.

      Why would Linux users care one iota about an OS they don't use??? Do you contribute time and effort into Linux projects?

    32. Re:What's the downside to using X11? by Anonymous Coward · · Score: 1, Insightful
      OOo ugly in Linux?

      It's as "ugly" as in windows.

      I think that was his point.
    33. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      The point is that even if you could fake the look-n-feel and keyboard shortcuts, there still would be numerous issues that Mac apps simply do not have.

    34. Re:What's the downside to using X11? by CrackedButter · · Score: 1

      So step 4 is profit then?

    35. Re:What's the downside to using X11? by Anonymous Coward · · Score: 1, Interesting

      OS/2 was just one othe target operating systems. StarDivision had ports for different UNIX systems like Solaris, HP/UX, SCO UNIX or AIX and they had a native port to Mac OS. StarOffice ran on Windows 16 bit, 32 bit and on Linux. They even had a port for IBM mainframe. Most of the development effort has been done by StarDivision engineers. The OpenOffice.org community has got a lot of volunteers who use Mac OS/X but there are just a few developers who port the core libraries to Mac OS/X. It wouold be helpful if some highly skilled developers could join the porting team. Apple doesn't seem to have an interest into this.

    36. Re:What's the downside to using X11? by AddressException · · Score: 1

      It's as "ugly" as in windows

      Exactly.

    37. Re:What's the downside to using X11? by Taladar · · Score: 1
      - they want to avoid Microsoft at all costs, including MS Office. They've heard great things about OpenOffice, but when they go to try it, it's slow and kludgy. Not a very good impression at all.
      If you copy a bloated piece of crap like MS Office basically 1:1 you must end up with something like Open Office.
    38. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      then ask Apple to allow the usage of byte hinting technology within open source programs like the freetype library

    39. Re:What's the downside to using X11? by nuggetman · · Score: 1

      Installation of X11 after OS X is installed typically requires the user to reboot their system with their OS X install disc, and then install the X11 support atop their existing OS X installation.

      Orrrrr you can just download it from http://www.apple.com/macosx/features/x11/

      --
      ...and that's all there is to it.
    40. Re:What's the downside to using X11? by andreyw · · Score: 1

      "enough support"? No, its a full blown X Server based of XFree86. Heck, the even provided a window manager that makes the window decorations fit in with the rest of OS X. As the other poster said, gimme a break - they designed their own windowing system AND they provided an X11 server that fits in well into their environment. What more do you want? The API is different so porting an application from X11 to Aqua acutally takes effort? Boo hoo. What, pray tell me, did you expect? Did you know that porting a win32 app to Xlib, GTK, QT, Aqua, Carbon OR ncurses actually takes effort? LOL!

    41. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      As soon as you try to make the app consistent, some apps like winamp, xmms, etc come along with skins and themes. There is no point in trying to force consistency with a proprietary toolkit.

      X11 does it the correct way. It's up to the developer to choose the toolkit consistent for the app. If you use the right toolkit (qt/wxwindows) your app is portible, while if you use the wrong toolkit (mac/aqua) your app is not portible.

      If anything, apple should open up aqua, instead of the open app being ported to the closed toolkit.

    42. Re:What's the downside to using X11? by Eravnrekaree · · Score: 5, Insightful

      I really dont see what the problem is with using the X11 version of OpenOffice on Mac OS X. Maintaining a seperate version of Open Office for another proprietary API would have consumed more precious developer resources which could instead be used to add new features to Open Office rather than endlessly reinventing the wheel to port old features to a million different OS dependant APIs. X11 is the most widely avialable GUI system and is available on most OSs, and works perfectly fine.

      Some have said that the X11 version is "ugly", but the Open Office developers have only themselves to blame for that, there are numerous beautiful graphics toolkits avialable on X11 which wonderful and georgeous user interfaces can be created with. Its not like X11 actually restricts user interface design, in fact, X11 provides a stable, time tested and refined platform which doesnt limit the beautiful user interfaces that you can implement on top of it.

      As far as performance, I get excellant performance from X11 on my systems, ussually better than Windows on the same hardware. X11 itself actually does not consume much memory or resources at all on your system. The X Server core consumes under 3 MB (this is around the executable size of the Xnest server which includes just the Xserver core, no hardware drivers).

      In fact, It wouldnt bother me at all if Open Office was run on Windows using the cygwin X11 servers rather than have a native windows port. And, i do use Windows and Cygwin all the time, I would much rather see developer resources go to adding new features to one X11 open API based port rather than maintaining a bunch of native ports for proprietary closed OS dependant APIs like Windows and Mac. The overall result would be a much better quality product on all operating systems. Such is part of the beauty of the standardised, OS indepedant X11 API, it allows the same GUI work to be used across many platforms.

    43. Re:What's the downside to using X11? by peterb · · Score: 1, Insightful

      The downside is that then you're running X11. And X11 sucks

    44. Re:What's the downside to using X11? by Alrescha · · Score: 2, Informative

      "Installation of X11 after OS X is installed typically requires the user to reboot their system with their OS X install disc, and then install the X11 support atop their existing OS X installation."

      It's a nit, but I think that 'typically', installing X11 involves putting in CD 3 and double-clicking on the X11 package. You make it sound pretty ugly when it isn't.

      A.

      --
      ...bringing you cynical quips since 1998
    45. Re:What's the downside to using X11? by tverbeek · · Score: 4, Insightful
      The NeoOffice/J team has done a fantastic job of gradually Aquafying OpenOffice without anywhere near the same resources.

      For better or worse, the success of NeoOffice/J in this regard has to be considered as a factor in the abandonment of OOo/Aqua. In other words, Neo has rendered a native Aqua port unnecessary. That's really what the OOo folks are saying.

      Any Mac user who considers the OSX11 version ugly and hard to install (and it is) should download the current Neo 1.1beta and give it a look. It's easy to install, and while still not as pretty as one expects to find in a Mac app, it integrates well enough into the OS X environment (e.g. native pull-down menu, keyboard shortcuts, printing, fonts) that it could "pass" as a native app. It's no Office X, but it's good enough to give to Regular People as a free substitute. I think the only thing it's missing that it really needs is a "look and feel" theme that mimics Aqua instead of MacOS 9, and (like all versions of OOo) more speed.

      So now we have two clear choices:

      If consistency with the current Win and Lin versions is important to you, use the OSX11 version.

      If consistency with other OSX apps and ease of installation is important to you, use NeoOffice/J.

      --
      http://alternatives.rzero.com/
    46. Re:What's the downside to using X11? by Bluetick · · Score: 1

      It's not as bad as everyone makes it out to be. X11 is a 16 meg download from Apple's site, or you can just install it off one of the Panther install discs I believe. How difficult is it to install? Well it's a .pkg file. Mount it, run it, put in your password and it's installed. I don't know why people say it's hard to install, maybe they're thinking of another X11 implementation (there's quite a few). It integrates with OSX pretty well actually. You can tab between X11 and other apps, and they also can be used with Expose and minimized to the taskbar. The titlebars and stuff are all OSX looking and you can use the same cut and copy shortcuts between them.

      Anyway if you want some info on it
      This one goes to 11

    47. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Down, Zoidberg !

    48. Re:What's the downside to using X11? by Angostura · · Score: 4, Informative

      Moreover X11 is an optional item (default=no) when you initially install the OS. My guess would be that the large majority of Mac users don't have it installed.

    49. Re:What's the downside to using X11? by Yaztromo · · Score: 1
      It's a nit, but I think that 'typically', installing X11 involves putting in CD 3 and double-clicking on the X11 package. You make it sound pretty ugly when it isn't.

      Depends on your source media. The Panther DVD that came with my PowerBook has multiple partitions on it, and the OS install partition isn't the default one. Instead, when you insert it you get one with some directions to reboot the system with the disc inserted. There is no "CD 3" in this case (as everything is on a single DVD).

      The end result remains the same, however -- it isn't something you can reasonably assume all end-users can easily achieve.

      Yaz.

    50. Re:What's the downside to using X11? by pixelgeek · · Score: 4, Interesting

      -- The only way OpenOffice can take on Microsoft is to not only build a better office suite

      Actually I think that path will fail miserably. The path to take is the one I think that Apple is taking. Make sucecssful and compelling apps that provide people with the features they want and make them easy to use and interoperable.

      Office apps are typically bloated and infuriating to use. The main reason I don't use OO on any platform is that it tries to mimic the same horrible user experience that Office has.

      Why duplicate crappy applications? People aren't that stupid and if you give them useful, functional applications that still do things like read Office files then I am sure they will use them.

      No-one likes Office so what is there to lose in trying to duplicate Office formats but with a better app?

      I'll be checking out Pages when it comes out but if Keynote is any indication I am sure it will be yet one more reason not to use Office or OO

    51. Re:What's the downside to using X11? by poemofatic · · Score: 2, Informative

      --Open Office uses a FIPS approved RNG to model their font kerning code. Seriously, though, t he f ont l oo ks l i keth is

      (well only a little better.) Certainly unusable for any professional settting.

      --There is no cut and paste. Well, there is *some* cutandpa
      ste of plaint ext char act
      tht suffers fr
      om the problms shown her e

      --No native font support. Fine, I guess until you
      *end up with a thousand useless .ttf and type 1 fonts on your system
      *cannot use the corporate fonts provided by your employer.

      --unstable. And yes, I mean it crashes spontaneously, and yes I've filed bugs, and yes nothing was done about any of them. For example, if you delete a data source (even a text data source) it will crash openoffice and this has been true since version 1.0.2 and no one gives a shit.

      --a big mess. By, "a big mess" I mean the code base is shit ugly, with windows and solaris PPC specific magic constants everywhere throughout the code. The code just isn't portable, and getting it to even compile on a mac is an achievement requiring hundreds of hours of developer time. At that point, the OOo team says "done!" and ships the code. This is relevant because porting resources are siphonned off to fighting with the developer practices, and this will cause the mac code to suck for a long long time to come. By far the number 1 thing SUN can do is to enforce some clean portable developer practices. This will shave years off of the mac (and freebsd, and Linux PPC, and IRIX) ports.

      --Printing support doesn't work. There are some hacks for a generic (not type 42) printer, but the functionality is mostly broken. Apple has an excellent Gimp-print subsystem that these guys can't wrap their solaris specific magic constants around.

      --Pdf generation is ugly and slow, producing poorly kerned, misaligned, sometimes incorrectly rendered text (attempting to pdf custom RGB colors often results in the colors randomly appearing and not appearing in the text.)

      --You need to be a font/Gimp print expert to customize the thing to work at all. Not very mac friendly.

      --ODBC and JDBC are both painfully broken. It seems that the crashes occur in the display code somewhere, although no one has bothered to debug any of this.

      This is not true of the excellent windows port, which Just Works and can be installed by, uh, normal office users.

      --

      When in doubt, have a man come through a door with a gun in his hand.

    52. Re:What's the downside to using X11? by CastrTroy · · Score: 1

      I'd much rather use an ugly office suite then one like MS word which doesn't have open formats and costs $150 for something that continually gets slower and more bloated as time goes on, without giving any new features that are actually useful in the last 10 years. I think WordPerfect 5.1 had everything that 99.9% of people need in a word processor.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    53. Re:What's the downside to using X11? by skinfitz · · Score: 0, Troll


      Silly! It's not pretty enough!

      Everyone knows Mac users would burst into flame if they used software that looked like one of those common computers. They would much rather pay Microsoft hundreds of dollars for something that looks prettier.

    54. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      As others already pointed out it is apple's fault that X11 doesn't work correctly on their system (no hardware acceleration, no GUI integration, ...)

      Other operating systems like QNX, Linux, BSD integrate X11 very well into their operating system environment.

    55. Re:What's the downside to using X11? by Bulln-Bulln · · Score: 1, Informative

      Other than it's slower and looks like total crap?

      I those were the only problems, I would be glad.
      Unforunately the are bigger problems. I can't paste text from Firefox into OpenOffice, because there's no common clipboard between X11 and Aqua. May it would work if I used the X11 version from Firefox...
      I also can't drop a text file onto OO's icon to open the file, because OO has no icon! There's just the X11 icon from the X-Server.
      OO's shortcuts use the Ctrl key instead of the Cmd key.

      At least NeoOffice/J supports the clipboard, Cmd shortcuts, and D&D on the icon. With customized toolbar icons, Neo/J also looks OK (it's not a nice fully Aqua look, but better than that ugly Win95 look).

    56. Re:What's the downside to using X11? by timmyf2371 · · Score: 1

      The only problem with this statement being that in my experience I've always found MS Office a very able set of programs, whereas it's "clone" OpenOffice is the office suite which tries so hard to be MS Office but fails in most respects.

      --

      Backup not found: (A)bort (R)etry (P)anic
    57. Re:What's the downside to using X11? by Yaztromo · · Score: 4, Insightful
      No-one likes Office so what is there to lose in trying to duplicate Office formats but with a better app?

      I disagree with the hypothesis that "No-one likes Office". I can agree that most people here on /. (myself included) don't like Office, but we're in a minority situation.

      I imagine there are lots of people in clerical professions who have gone on two-day courses to get a certificate saying they know how to use Office who rather like it, because they're experts in it. Much like there are people out there who really like Windows because they make a lot of money working in it (regardless of how truly crappy it is).

      I can understand why OOo is targeting the Office crowd -- they don't need to target those people who have a need for a word processor every third Sunday -- they're going after those people who are currently using MS Office day-in and day-out, and who expect a competing suite to offer similar features and a similar experience.

      I'll be checking out Pages when it comes out but if Keynote is any indication I am sure it will be yet one more reason not to use Office or OO

      My copy of iWork is already on order. I've been wanting to get Keynote for some time now, and getting it bundled with what looks to be a high-quality word processing/page layout solution for less money equals me pre-ordering a copy from Apple's website the same day it was announced :).

      Yaz.

    58. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0
      The problems you mention are not the fault of Open Office. Apple provided an inadequate X11. Most of the problems you mention could be fixed by Apple providing a better X11 which would make it easier for application maintainers to provide a better Mac "look and feel".

      For example, The Open Office folks shouldn't have to worry about Apple's version of anti-aliased fonts. Apple's X11 should be designed so that it "just works". An intelligent X11 from Apple would allow a plethora of X11 apps to become better integrated with the Mac.

      Face the truth. X11 exists on Mac, but it is only a half-hearted effort. It needs more more work. It's up to Apple. Let Apple provide the best tools, and the applications will follow.

    59. Re:What's the downside to using X11? by BubbleDragon · · Score: 1

      $150?! Try $499 for Office Pro 2003. You're right about the features that no-one needs, though. If Word 'corrects' my numbering one more time when I'm doing problems 10, 12, 23, and 35 for homework, I'll scream.

    60. Re:What's the downside to using X11? by SillyNickName4me · · Score: 1

      Uhm, yeah.. ask Apple to give itself a license to enable bytecode in the freetype library they distribute...

      This simply has nothing to do with them not allowing OSS to use their patents, Freetype includes the code, but you have to obtain the license when turning it on.

      Of course the above is a problem, just a different oen from Apple not grantng itself a license obviously.

    61. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Thank you mister quoter

    62. Re:What's the downside to using X11? by CastrTroy · · Score: 1

      Yeah, my solution. I've turned off everything that it does automatically. There's about 30 checkboxes required to do this. The price I was referring to was the cheap home version, which offers nothing less than the professional version, at least as far as I can tell.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    63. Re:What's the downside to using X11? by big+tex · · Score: 1

      Silly! It's not functional enough!

      If it can't get copy and paste right, it's no good. That's so basic I don't even know where to begin.

      The thing that bothers me the most is that I can't remap copy from CRTL-C to APPLE-C like every other application.

      I ran linux for the last five years, and recently bought a powerbook. For me, it's definitely not the 'pretty' thing.
      OOo sucked on linux as well.

      --
      I think I need a new sig here.
    64. Re:What's the downside to using X11? by eyeball · · Score: 5, Insightful

      I'm sure a million other osx folks will flame about this, but it's really difficult to use X11 when you're used to the consistency of native OSX (Cocoa or Carbon to a certain extent) applications. i.e.: All OSX apps have similar places to go for preferences, to open/save files, edit, help, etc. Plus keybindings and mouse behavior are all similar. Compared to that, running an X11 application is like being thrown back to 1990. Menu's are attached to the window, keybindings are messed up, and you're lucky if copy/paste works.

      I don't see what the problem is with integrating native GUI libs with an OSS project. Firefox does this with extreme success on multiple platforms. This should've been OpenOffice's strategy from day 1.

      --

      _______
      2B1ASK1
    65. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Don't like it? Feel free to pay hundreds of dollars for a proprietary office suite.

      OOo is not consistent with the OSX menu scheme? You must remind yourself of one fact: OpenOffice is not an OSX suite, it is not written or published by Apple in any way. If they want to be a true multi-platform office solution, then it is lunacy to adopt a Mac-specific UI.

      If the good people at OOo have bothered to make their app run at all under OSX, then that is "Free As In Beer". Given how much Mac users are forced to pay for pretty much everything, they should be grateful that free software is availble.

      Besides which, OOo works splendidly under Linux. Free seeds grow best in free soil....

    66. Re:What's the downside to using X11? by mattkinabrewmindspri · · Score: 5, Interesting
      I can't convey this easily without sounding like a huge asshole, but I'll try.

      Mac people don't want what open-source people think is a good interface. They want consistency and an easy learning curve. This means having all of your programs look and act basically the same. Menus, widgets, the whole shebang. X11 programs on the Mac feel very foreign and difficult by comparison, like they don't belong. Sure, they run just as well as they do on other operating systems, but they are missing a certain je ne sais quoi, which even the best X11 program is not going to have.

      An aqua port of OO.o would be very worthwhile. In fact, I think it could be *huge*. Mac users are some of the most anti-Microsoft people around, and don't want to shell out money for Microsoft Office. Having a good open-source office program like OO.o on the Mac would be good for Mac users, OO.o users, and anyone who isn't a fan of Microsoft.

    67. Re:What's the downside to using X11? by Fnkmaster · · Score: 3, Insightful

      Nobody really cares what goes on underneath the hood. The real issues are 1) ease of installation on an unmodified OS 2) aesthetic quality and performance of GUI. If you can get both of these with some embedded implementation of X11 based on the Cygwin stuff, then more power to you. But don't expect anybody to take an office suite seriously that requires you to install a complete windowing system on top of your native OS just to make it work. Installing Cygwin isn't terribly hard or anything, but unless the whole process is completely seamless from a user perspective, people just won't do it. And companies will drop it like a hot potato.

      So in short, there's nothing fundamentally wrong with using the X11 version of OOo on Mac OS X, except that it doesn't mesh with the native look and feel, subjectively feels slower than any native Aqua app does, and requires (or at least it used to - it may be integrated into the install process now, haven't checked the OS X builds in ages) separate installation of an X11 server before it will work. These are all completely unacceptable in a mass market office suite.

    68. Re:What's the downside to using X11? by tfoss · · Score: 1
      I really dont see what the problem is with using the X11 version of OpenOffice on Mac OS X.

      Well, as long as you don't mind limiting the audience for OO.o to a rather small subset of OSX users.

      X11 is the most widely avialable GUI system and is available on most OSs, and works perfectly fine.

      Again, this is true only for a *very* small population of computer users.

      The overall result would be a much better quality product on all operating systems.

      Which pretty much no one would use.

      Seriously, how many percent of windows users 1. have cygwin & X installed, or 2. would be willing to install them to use an office suite that is, at best, comparable to microsoft office? If the point is to make a good product that many people will use, you need to have either a native port, or else some feature that is just orders of magnitude better than microsoft office.

      -Ted

      --
      -=-=- Quantum physics - the dreams stuff are made of.
    69. Re:What's the downside to using X11? by master0ne · · Score: 1

      i was just about to say the same thing when i read the parents post, openoffices target audiance are ms office users who when migrating to linux dont want to have to relearn the whole UI, rather just pick up where they left off. Big buisness support this modle so they dont have to retrain alot of their employee's when migrating they simply pick openoffice which is so simmilar to MS office it requires almost no retraning!

      --
      Noone writes jokes in base 13!
    70. Re:What's the downside to using X11? by pixelgeek · · Score: 1

      -- I can agree that most people here on /. (myself included) don't like Office, but we're in a minority situation.

      Are we?

      Do you know people that are happy with Office? I don't know any.

      I don't know any people that use Office apps on a regular basis that don't have very negative opinions of the applications. Most people I know use Office by default or because it is assumed that you need to use it to be able to share documents with other people.

      -- they're going after those people who are currently using MS Office day-in and day-out, and who expect a competing suite to offer similar features and a similar experience.

      Which may be the point but that doesn't mean you have to make the same sort of application as Office. Why does an Office-suite have to look, feel and act like Office?

      And of this group of people how many of them use more than 10% of the Office features? Heck, I still run into people that don't even know that Word does change tracking.

    71. Re:What's the downside to using X11? by pixelgeek · · Score: 1

      How much of the UI do you need to relearn in actuallity?

      Office is notorious for its utterly complicated menus and buried features.

      Surely a simpler application with a better UI and better user experience would be a better alternative

      I think that the idea that people won't accept an "Office" suite unless it looks like and acts like Office is one of those old chestnuts that haven't actually been tested.

    72. Re:What's the downside to using X11? by simcop2387 · · Score: 1

      it leaves out frontpage and access IIRC

    73. Re:What's the downside to using X11? by sabNetwork · · Score: 0, Flamebait

      Yeah man. It's pretty damned ugly in Windows, too.

      Not to criticize your GUI fashion sense.
      --

    74. Re:What's the downside to using X11? by KAMiKAZOW · · Score: 1

      Just FYI: There isn't even a X11 version of current OO 2.0 pre-releases.
      So it's not the question "Aqua or X11?"

    75. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Hark! I've been caught. Yeah, I quoted.

    76. Re:What's the downside to using X11? by BishopBerkeley · · Score: 2, Insightful

      Yes, that's the main reason. However, the introduction of iWork cannot be ignored. Why deal with the hassle of making a native version of ooo when neooffice is just about there AND Apple is introducing its own fairly (MS) compliant office suite?

      --
      "...who search the reason of things
      Are those who bring the most sorrow on themselves." --Euripides, The Medea
    77. Re:What's the downside to using X11? by Slack3r78 · · Score: 2, Interesting
      As soon as you try to make the app consistent, some apps like winamp, xmms, etc come along with skins and themes. There is no point in trying to force consistency with a proprietary toolkit.

      To borrow a phrase from the English, "Bollocks."

      This is precisely one of the things that makes the Macintosh such a great platform. Apple developed UI guidelines, and, for the most part, developers stick to them. I might agree with you if OOo was the norm in Mac applications, but in reality it's a huge exception.

      Simply put, OOo will not succeed on the Mac platform if it appears "broken" to the users, which is where things sit with the X11 port.
    78. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      "In other words, Neo has rendered a native Aqua port unnecessary. That's really what the OOo folks are saying."
      Strange, I thought they were saying that there were licensing, political, and engineering difficulties. As in the groups that fund ooo aren't interested in helping out Mac users.

    79. Re:What's the downside to using X11? by Yaztromo · · Score: 2, Informative
      Which may be the point but that doesn't mean you have to make the same sort of application as Office. Why does an Office-suite have to look, feel and act like Office?

      When I worked for IBM I, as a developer, got to sit on the other side of the one-way mirror during end-user UI/HCI testing from time to time. And believe me when I tell you that people want products to work and act like what they're already used to, regardless of whether or not what they're used to is completely optimal.

      This is the same reason why Gnome and KDE are often chasing a Windows-like design philosophy. They want to give people something they'll feel comfortable switching to.

      Is this ideal? Certainly not. But HCI R&D is rife with products that tried to create an easier way to accomplish something, succeeded, and bombed in the industry because it wasn't what people were used to (I'd personally hold up OS/2's WorkPlace Shell as such a product -- IMO the WPS is one of the biggest successes of HCI research in the last 20 years, and we all know how much good that did OS/2 in the long run).

      I don't like it one bit -- I prefer software that doesn't just try to emulate the market leader, but which actually tries to innovate in UI and HCI design (one of the reasons why I switched from OS/2 to OS X for my primary desktop system). But I'm unfortunately in the minority.

      Do you know people that are happy with Office? I don't know any.

      Yes, I'm sorry to say that I do. I know people who absolutely swear by it, and think that trying to compete against it is pointless. If you go outside technical circles, there are a LOT of these people out there. Are they right? Of course not -- but that doesn't mean we can deny that they exist :).

      Yaz.

    80. Re:What's the downside to using X11? by linders · · Score: 1

      blasphemy, are you saying no one likes chippy?

    81. Re:What's the downside to using X11? by pixelgeek · · Score: 1

      Interesting comments. Thanks

      Which makes one wonder why people would continue to use products and interfaces that are so poor?

      Is it that the first experience of having to learn the application or product was so negative that they are now afraid of learning a new application because they think it will be as arduous?

      Or are people just lazy?

    82. Re:What's the downside to using X11? by Grey+Ninja · · Score: 1

      I still can't think of any valid reason why you wouldn't be able to put a shortcut to an X11 app on the dock.

    83. Re:What's the downside to using X11? by Anonymous Coward · · Score: 2, Insightful

      If they want to be a true multi-platform office solution, then it is lunacy to adopt a Mac-specific UI.

      Ahhh, but that's the question. If they really want to be truely multi-platform, then either A: they need to have a UI that is flexible enough to "theme" for different operating systems, B: they need to create GUI shells for different operating systems. What you're talking about right now is having a uni-platform office solution based on X11, which may or may not fulfill either A: or B:.

      Given how much Mac users are forced to pay for pretty much everything, they should be grateful that free software is availble.

      In some cases, you get what you pay for (great shareware, for example.) In other cases you get great stuff for free (lots of freeware, OS/FS software like Firefox, bundled apps from Apple like Safari.) I don't think Mac users are really hurting for good software, although having a fast, fully-compatible version OO would be great.

      Consider that the Windows version of OO is integrated quite well, while the current X11 version of OO for MacOS X isn't that great.

    84. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Have you ever used OSX? How about having to use cygwin on windows for OO. Sounds pretty gay don't it.

    85. Re:What's the downside to using X11? by Yaztromo · · Score: 1
      Which makes one wonder why people would continue to use products and interfaces that are so poor?

      Because the more involved a thing is, the more chance you can label yourself as an "expert" and not get laughed at.

      MS Office is hardly the first product in the world with an unwieldly interface to it. There are lots of products in the world that require an expert to use -- some of which require a license to use because of their unweildliness. Can you fly a helicopter? I know I can't. People who can get a certain amount of prestege for their ability to use a product. It's the cult of the arcana.

      Ever meet the secretary who thinks they know about computers because they can use a word processor? I once worked for a company where the secretary thought she knew everything about PCs because she had a certificate for WordPerfect.

      Then again, I know a few people who make their living solely off the MS economy. People who are MCSE's, and recommend and service only Microsoft products. These people also love MS Office, because it's another revenue source for them. They are MS's "true believers", and are fanatics in the truest sense.

      Or are people just lazy?

      You can never over-estimate the power of laziness :).

      Yaz.

    86. Re:What's the downside to using X11? by gravytas · · Score: 1
      I can't paste text from Firefox into OpenOffice, because there's no common clipboard between X11 and Aqua. May it would work if I used the X11 version from Firefox...

      On my Mac I just use [command]-c to copy and either [command]-v or Middle-Button-Click to paste, depending on whether the target is Aqua or X, respectively. If you don't have a 3-button mouse, you can use a combination of [control]-[option]-click to paste in X.

    87. Re:What's the downside to using X11? by nathanh · · Score: 1
      I disagree with the hypothesis that "No-one likes Office". I can agree that most people here on /. (myself included) don't like Office, but we're in a minority situation.

      I disagree with your claim that "most people here on /. don't like Office". I don't think you have evidence either way. I think you're just stating your dislikes as if you're representative of the entire group.

      I like OO.org. I only use a word processor and OOWriter is significantly better than either Kword or Abiword. The latest versions (1.1.3) even look good under GNOME due to decent theme support. The display fonts are anti-aliased and it finds all the fonts on my system. The export to PDF feature is perfect. The interface responds quickly on my 1GHz laptop w/ 384MB RAM. I really couldn't expect it to be much better.

      I don't think I'm alone in liking OO.org. I won't make the mistake of claiming that "most people here on /. do like OO.org" but I will make the claim that you're making shit up.

      My copy of iWork is already on order. I've been wanting to get Keynote for some time now, and getting it bundled with what looks to be a high-quality word processing/page layout solution for less money equals me pre-ordering a copy from Apple's website the same day it was announced :).

      You're buying proprietary applications to run on a proprietary operating system. That's fine. Your decision to make. But you're the Wordperfect running on PC-DOS user of the future. I hope the immediate gratification of shiny buttons and translucent windows makes up for the inevitable redundancy.

    88. Re:What's the downside to using X11? by NardofDoom · · Score: 1
      An X11 OOo is suitable for linux users who also have a mac.

      And how many people is that? 2,000? 3,000? Maybe? What about the millions of Mac users who need a carbonized - or even better, a cocoaized - office suite.

      NeoOffice/J is almost there. Good enough that I use it every day. But Mac users need more.

      Really, making an open source application popular with Mac users is perhaps the greatest challenge for the OSS community. We don't mind paying or good software, but we demand a fantastic UI and experience.

      --
      You have two hands and one brain, so always code twice as much as you think!
    89. Re:What's the downside to using X11? by jez9999 · · Score: 2, Funny

      Surely you mean the other way round? That would be an upgrade.

    90. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      "This means having all of your programs look and act basically the same."

      This is a serious question: Why is this important? I've been using computers from twenty years and have never used an interface which is consistent across all applications. What am I missing?

      My only contact with Mac users is via Slashdot so maybe I'm off base but judging by the comments that are posted here, the only difference between me and the Apple fans is a permanent hard-on.

    91. Re:What's the downside to using X11? by killjoe · · Score: 3, Insightful

      I can't say this without being a huge asshole but i'll try.

      If the mac users are really that picky about the UI why don't they pay for the development of a mac version of OO or lobby apple for a real office suite or just say fuck it and buy msoffice?

      If not openoffice then maybe koffice or abiword/gnumeric or something.

      It just strikes me as being totally arrogant to say "what you gave me for free isn't good enough for me, go back make it so that I am happy and don't expect me to lift a finger or spend a dime either."

      Maybe it's time to scratch off the mac as a supported platform for OO.

      --
      evil is as evil does
    92. Re:What's the downside to using X11? by killjoe · · Score: 3, Insightful

      "These are all completely unacceptable in a mass market office suite."

      I think this is exactly why OO will never be ported to macosx. The developers know that the mac crowd will not accept OO unless it's better then MS office. The windows and linux oo users are more tolerant and flexible in their expectations. They are willing to use something for free even if it does not work as well as something that costs 400 dollars. Mac users would rather pay the 400 dollars then to use anything that would spoil their mac experience.

      I think this is a good decision by the OO guys. It would be really hard to support or live up to the expectations of the typical mac user. It would be a thankless job and it would be very painful.

      --
      evil is as evil does
    93. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      By all means, go right ahead. Mac users aren't interested in your idea of what a decent interface is. Don't let the door hit you on the ass on your way out.

    94. Re:What's the downside to using X11? by SpiceWare · · Score: 1

      1) Printing doesn't work. When I tried using OpenOffice I had to create a PDF, then print the PDF using an OS X application.

      2) Fonts don't work well. Either I could see the font onscreen, but not on the paper; or I could see the font on the print out, but not on screen. A few fonts worked in both places, but it was a major hassle trying to figure out which ones.

      Due to those issues I opted to use NeoOffice/J.

    95. Re:What's the downside to using X11? by Yaztromo · · Score: 1
      You're buying proprietary applications to run on a proprietary operating system. That's fine. Your decision to make. But you're the Wordperfect running on PC-DOS user of the future. I hope the immediate gratification of shiny buttons and translucent windows makes up for the inevitable redundancy.

      Here's a newsflash for you: all software is eventually redundant. You think Open Office is still going to be around 20, 30, or 40 years from now? Sure the formats may be open, but what good is that if you can no longer run the software, and have no ability or intention to write your own viewer?

      My word processing needs are minimal. I'm a software developer, not a clerical worker. I don't generate documents for printing terribly often, and when I do it is usually for immediate consumption (ie: stuff that gets printed to paper immediately).

      And personally, I'm not concerned about running a proprietary application in this case, as there is every indication that Pages' native file format will be XML based, with a publically available XSLT, making it very easy to transform into other XML formats. However, for my minimal needs, I'm not particularily concerned, and have no problems changing applications and file formats in the future if necessary.

      Sorry, but your attempt at FUD doesn't fly here.

      Yaz.

    96. Re:What's the downside to using X11? by Shockmaster · · Score: 1

      Actually, "complicated spreadsheets" are not somewhat of an exception for many business users of Office software. While OO.o is perfect for many (and on this front, not even all) students and people that are using primarily Word/Powerpoint without many bells and whistles, for a whole lot of users out there Excel is the engine that drives their use of office software. I don't however thing that is insurmountable for the OO.o dev team, but MS has a lot more experience when it comes to these formulas. What everyone needs to hope for is that they don't keep crating increasingly complicated formulas in Excel while OO.o plays catchup.

      --

      ---
      Take it sleazy,
      -The Shockmaster

    97. Re:What's the downside to using X11? by tverbeek · · Score: 2, Informative
      This should've been OpenOffice's strategy from day 1.

      The problem is that "day 1" for OpenOffice was the day Sun handed them a huge codebase specifically written for X11 and Win32. No Mac API support included.

      By contrast, Mozilla was given an app that had already been coded for Mac, so on "day 1" the porting project was already complete. Then with Firefox, they started pretty much from scratch, so on "day 1" they were actually at square 1, and had the liberty of taking cross-platform support into account.

      --
      http://alternatives.rzero.com/
    98. Re:What's the downside to using X11? by Eravnrekaree · · Score: 2

      I haven't used many Mac programs, lately, however on Windows, X11, and most other platforms, there ussually does seem to be some variation on where a certian menu item or button is between programs. But the concept of the menu bar, buttons, and standard UI elements tends to be similar and although the user may have to browse a few menus to see where everything is, often the same features are there but they might be in a different place. This is what users always seem to have to do when using a new program, like switching from IE to Firefox.

      We also could say that one of the advantages of Open Office is it has the same layout on multiple OSs so no matter what OS you happen to be using at a certian time it works the same. I am sure there are other applications that run on say both Windows and Mac that do the same thing.

      I do agree that installation needs to be seamless on every platform, and this means seamless installation of X11 if it is not already there without the user having to do that seperately. This could be done in various ways, such as including X11 on the CD or having the installer download and install it automatically if its not already installed. It would be less work to do this than try to deal with porting the same program to multiple incompatible APIs. The development costs of doing this can be intense and drain resources from improving the software.

    99. Re:What's the downside to using X11? by Anonymous Coward · · Score: 4, Insightful

      >I really dont see what the problem is with using the X11 version of OpenOffice on Mac OS X.

      You probably haven't used the Mac much. Probably the BEST thing about the Mac is the consistency of the UI (enforced by published Human Interface Guidelines) - this has been an advantage since the original 128K machine.

      OO.o on OS X stinks- the menus are attached to windows instead of the standard Mac menu bar, Mac fonts aren't available, dialogs don't match the Aqua standard, aliases aren't supported in File Open/Save dialogs, cut and paste are broken, there is no QuickTime or iPhoto or Services or Dock or Keychain or AppleScript support, and the damn thing is S-L-O-W.

      For users who came over from Windows/Linux (i.e. the ones who bitch the most about well-established Mac UI conventions) OO.o might be acceptable. For anyone who is used to the Mac's capabilities, it's a POS.

      There's a profound lesson which many a developer from Apple and Microsoft on down has discovered vis the Mac market- crap won't fly. Period. Crippling your app so it is limited to "common denominator" features found on other platforms is a sure path to failure.

      If the OO.o developers had REALLY been interested in the Mac, they would have supported the above Mac technologies plus new stuff like Spotlight and Automator. This announcement is no real shock nor is it much of a loss for the platform.

    100. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Why would you pay for something when some sucker will do it for free? And if we end up having to pay for it, it is more worthwhile to just buy MSOffice. Our only interest in OO is the fact that it is free (as in BEER).

    101. Re:What's the downside to using X11? by Anonymous+Brave+Guy · · Score: 1
      If the mac users are really that picky about the UI why don't they pay for the development of a mac version of OO or lobby apple for a real office suite or just say fuck it and buy msoffice?

      Mac users already seem to have a very nice office apps suite available from Apple: iWork. I haven't used it myself, but from the publicity and screenshots, it looks like what Mac users have been crying out for for some time: a polished, powerful, professional office suite that isn't just Office for Windows but a version behind.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    102. Re:What's the downside to using X11? by Anonymous+Brave+Guy · · Score: 2, Informative
      This is a serious question: Why is [having all of your programs look and act basically the same] important? I've been using computers from twenty years and have never used an interface which is consistent across all applications. What am I missing?

      You're missing the fact that most users aren't as familiar with their computers as you or I might be. To a more casual user, the more consistent the interface, the easier the learning curve and the more productive the tool.

      One big reason that Windows took off in mainstream PC use was that it provided standard UI conventions: loading and saving files were done with the same commands on the same menus; clipboard use was consistent across applications (and later even between them); there were common ideas for menus, icons, toolbars, status bars, use of the mouse, keyboard shortcuts, etc.

      The Mac is the same, with its own conventions, except that Apple have always had better UI people than Microsoft. Throwing in an OSS app that (like most OSS apps) is rather deficient in the usability stakes just isn't going to win users over when they've got much more polished products available to use instead, no matter how little it costs to buy or how community-centric the attached philosophy may be.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    103. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      If there wasn't a native Windows port, there's no way in hell that OpenOffice could even begin to think about displacing MS Office. That is the grand goal, isn't it?

    104. Re:What's the downside to using X11? by sg_oneill · · Score: 1

      And not being there extremely fucks my seriously high expectations of being able stop blowing my IT budget in the work place out.

      Half out techies cant seem to figure out how to get mac X windows to work, so how the heck are our users supposed to?

      Oo is dead on the mac it seems. Its a shame, cos it could of been the platform where it finally got its hold. Apple people , like linux people seem hate microsoft softare almost on principle. A ripe market, alas one thats been thrown away.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    105. Re:What's the downside to using X11? by Anonymous+Brave+Guy · · Score: 1

      Sadly, I can confirm that several of the problems you mentioned actually are problems in the Windows port as well. The PDF output, for example, has terrible font problems on a bad day, and it seems to have all sorts of problems with mail merge and data sources in Writer. OpenOffice just isn't that polished a product yet, which is presumably why the dev team are more inclined to focus on core functionality than on porting to yet another platform.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    106. Re:What's the downside to using X11? by seann · · Score: 1

      i agree

      previous poster sucks

      you are correct

      --
      I'm a big retard who forgot to log out of Slashdot on Mike's computer! LOOK AT ME.
    107. Re:What's the downside to using X11? by orin · · Score: 2, Interesting

      I use office every day and I'm happy with it. My primary income is as a textbook author. There are features in Office 2003, especially the revisions and comments stuff that no other package comes close to providing. These features have streamlined the editing and revision process by a significant amount compared to how it was done even a few years ago.

      Believe it or not, there are people out there that do use some of those funky little features that no other package supports. Don't assume that everyone can get by with an office suite that has a less extensive feature set than the MS product.

    108. Re:What's the downside to using X11? by WGR · · Score: 1
      Microsoft Office was originally developed for the Macintosh (Before it was ported to Windows) so Mac users have been used to the MS Office interface for quite along time (20+ years). Without a Macintosh version using Macintosh interface conventions, Open Office will never be able to replace MS Office in the corporate world.

      Yes, most corporate desktops run Windows, but a significant number, mostly in creative areas like advertising and design, use Macs. Engineering might have Solaris/HP Unix workstations, but these groups also have Windows machines for personal use Since both Mac and Windows machines run MS Office, corporations recommend MS Office for cross platform compatibility in any purchase RFP. Without a native Mac version of Open Office, Open Office will be ineligible for use by any corporation that uses Macs.

    109. Re:What's the downside to using X11? by killjoe · · Score: 1

      "Mac users already seem to have a very nice office apps suite available from Apple: iWork."

      First of all iWork does not have a spreadsheet as far as I can see. Secondly so what? There are dozens of office software you can buy. Just buy them and leave the OO guys alone.

      --
      evil is as evil does
    110. Re:What's the downside to using X11? by killjoe · · Score: 3, Insightful

      "Without a Macintosh version using Macintosh interface conventions, Open Office will never be able to replace MS Office in the corporate world."

      That's just pure bullshit. OO will do just fine in the corporate market without mac support. Mac support never has been and never will be an obstacle. Like you said it's like 1% of the corporate desktops.

      --
      evil is as evil does
    111. Re:What's the downside to using X11? by Guy+Harris · · Score: 1
      OOo is not consistent with the OSX menu scheme? You must remind yourself of one fact: OpenOffice is not an OSX suite, it is not written or published by Apple in any way. If they want to be a true multi-platform office solution, then it is lunacy to adopt a Mac-specific UI.

      A certain multi-platform Web browser and a certain multi-platform mail reader have UIs that are at least somewhat more Mac OS X-like on OS X than OOo's UI is, so it's not as if multi-platform apps can't look at all like native apps. Firefox/Thunderbird are, admittedly, not as native in look and feel as other apps, but I have the impression that's considered by the developers as a deficiency that should eventually be fixed.

    112. Re:What's the downside to using X11? by bruthasj · · Score: 1

      You willing to step up and make the contribution? Cause if you're not, it's not going to happen. Contrary to popular belief, arm-chair analysis and feedback isn't what makes the world turn--Opensource or otherwise. It's those that take action which cause things to spin, whether through donations, code, bug reports, *using it anyway, though it sucks*, documentation, irc support, etc. etc.

      Whining about aesthetics never got anyone anywhere. Even Jobs knows about that.

    113. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      I really dont see what the problem is with using the X11 version of OpenOffice on Mac OS X.

      You are not a typical Mac user, then.

      I assure you, I have tried to get typical Mac users to consider OOo. Generally they are quite receptive to the idea. They see it on my PC, and they see something that looks like MS Word, acts like MS Word, and does not cost a penny (unlike MS Word).

      Then they see it on their Mac. And unlike MS Word, it is not a Mac application. When they try to open a file in it, they get a file open dialog they do not understand. When they try to configure it, they get a preferences dialog they do not understand. When they try to integrate it with other programs, they fail. When they try to print from it, they fail.

      And they go out and buy MS Word instead.

    114. Re:What's the downside to using X11? by Blakey+Rat · · Score: 1

      Bingo!

      There was a revealing quote on the Slashdot article where Pages was announced. (Apologies, I'm not going to spend the time to look it up.) One of the posters asked, "so Apple has a replacement for Word and Powerpoint, but where's the replacement for Excel?" And somebody replied, "they haven't figured out how to make a better spreadsheet than Excel yet."

      Apple isn't trying to beat Office at its own game or anything like that. All they're doing is identifying ways the office suite can be improved, and making those improvements... that's why Excel, the most perfected of the Office apps, has no replacement yet. And for good reason... how do you beat Excel for spreadsheets?

    115. Re:What's the downside to using X11? by Jason+Earl · · Score: 1

      HCI really only comes into play when you have two competing products that have the same cost of acquisition. That means that the two competing products must either deal with precisely the same formats and protocols, or they must have essentially the same market share.

      Designers and programmers think that HCI is important, and they are often willing to pay extra for a more consistent interface. Normal people, on the other hand, won't. That's why IBM PCs running DOS crushed the early Macs. There was no question that the Macintoshes where nicer systems, but the IBM PCs were "good enough" at a lower price. That is also why Windows beat out OS/2. OS/2 was a superious system, but consumers didn't care. Windows was good enough, and it was cheaper. If IBM had flooded the market with inexpensive OS/2 development tools, and priced OS/2 so that PCs with OS/2 had a competitive advantage over PCs with Windows then the computer world would be a different place now.

      OpenOffice.org doesn't need to be the functional equivalent of MS Office to achieve total world domination. It simply has to be good enough at a lower price. Unfortunately, Microsoft's current market share means that "good enough" for many people has to include nearly seamless sharing of documents with MS Office users. On the bright side Microsoft has to keep forcing its users to upgrade in order to stay in business. For example, Microsoft is getting ready to push all of its existing MS Office users to an incompatible new set of XML-based formats. When this happens millions and millions of MS Office users with older versions of MS Office are going to find out that they are out in the cold unless they are willing to pay hundreds of dollars to update their software. Many of these folks are likely to find that OpenOffice.org is "good enough."

    116. Re:What's the downside to using X11? by DMJC-L · · Score: 0

      I can see this in a similar way to my own plight with gnome and kde, now I'm a gnome user, I'm not going to flame over which is better, I like to have my entire desktop look and work the same way, only gnome apps do that for me. I'm sure there are kde users who feel the same and who only run kde apps. Now that's not to say that running both is a bad thing, but some of us like having our cake and eating it to. So I can sympathize with mac people. The only real solution to this I guess is to let the guys writing the apps split the apsp into frontend/backend and get mac users/gnome users/kde users/windows users to write the frontends themselves.

    117. Re:What's the downside to using X11? by pjbass · · Score: 1

      For the most part you're correct. In the old days, people used Xlib. There was no true concept of widgets, but if you wanted something bad enough, you made it work. In some sick sense there was/is a widget library, but it pales in comparison for ease of use alongside GTK+/Gnome and KDE these days.

      I've not written anything meaningful using Xlib directly, but I work with people who have and who do; it is an exercise in extreme pain and love at the same time, and I'd strongly recommend using one of said toolkits for any/all GUI development.

    118. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      So the OO guys should be beyond criticism? Jesus-- get over yourselves...

      Like it or not, the grandparent (and the great great grandparent) have pretty good points. Not only do Mac users have to put up with the shit that is OO.o, but they (we) are completely within their rights to voice complaints about OO.o.

    119. Re:What's the downside to using X11? by strider44 · · Score: 1

      OO.Org doesn't try to be a clone of MS Office, it tries hard to be an office suite. Sorry if it's not exactly the same to what you're used to, because that's not what they're going for.

      Saying OO.Org is a failure at being a MS Office clone is exactly like saying Firefox is a failure at being an Internet Explorer clone, because, after all, it doesn't have the same GUI and doesn't even include ActiveX.

    120. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      You willing to step up and make the contribution? Cause if you're not, it's not going to happen.

      In that case, OO is pretty much doomed on the mac. If only people who are willing to get their hands dirty with development are allowed to criticise the software, then you're going to have a very limited pool of criticism. That's stupidly self limiting, IMHO. Someone who doesn't want to aid in development may have a valuable opinion... don't dismiss it out of hand.

      Whining about aesthetics never got anyone anywhere. Even Jobs knows about that.

      It's not about aesthetics... it's about interface consistency. A program running on a mac which is designed for another platform is definitely going to have an interface which is different from what most Mac users are used to. That's a bad thing, and will limit OO adoption a great deal.

    121. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      It really doesn't work very well - almost to the point of being unusable.

      Maybe there's a workaround I don't know about, but I find that switching from OpenOffice to an Aqua app and back agian seems to invoke one of the Exposé functions.

      It is very frustrating.

    122. Re:What's the downside to using X11? by OrangeTide · · Score: 1

      Actually Lotus 1-2-3 is better than Excel, if you ignore that it's for DOS and no longer being produced. Personally I use sc, but mainly because it comes with psc. Which lets me prepare data from various sources and run sc equations on it. sc is public domain, but it's probably not appropriate to bundle with iWork. :)

      The point is interesting though, if you allow me to expand on it a bit. All spreadsheet programs are basically "perfect". Lotus 1-2-3, Excel, gnumeric, and sc are all pretty much the same thing. What sort of innovation can be done in the world of spreadsheets?

      uses scheme for it's equations, that might be an innovation. But it's probably a step in the opposite direction for Apple.

      --
      “Common sense is not so common.” — Voltaire
    123. Re:What's the downside to using X11? by snilloc · · Score: 2, Informative
      macros too.

      In addition to the work of getting OOo installed, I would need to re-record all my macros. I'm not about to do that when they work just fine on Excel97, which I have no forseeable plans to upgrade.

      For me, it's a lot of work just for "philosophy".

    124. Re:What's the downside to using X11? by SteveM · · Score: 0

      I can't say this without being a huge asshole but i'll try.

      You'll have to try harder.

      It just strikes me as being totally arrogant to say "what you gave me for free isn't good enough for me, go back make it so that I am happy and don't expect me to lift a finger or spend a dime either."

      We're not. We're saying, "This isn't good enough, so I'm not gonna use." That's all. If the OO folks want us to use OO then they, like you, will have to try harder. If not, so be it.

      It just strikes me as totally arrogant to think that the user's expections are irrelevent.

      By all means the OO folks should code to whatever standard they want. They're doing it because they want to. Scratching that itch. Not because anyone is paying them for a product. But if you are writing something for yourself, don't be surprised if nobody else wants it.

      SteveM

    125. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      I think he meant that it will not replace MS Office on the Mac in the corporate world. And you are pure bull shit.

    126. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Who is giving +Insightful to this dolt? Mac users, like Windows users, would be happy to use a free office suite if it was 1/2 as good as MS office, but was 100% compatable with MS office. I have tried using OO at work, but I usually spend more time fixing the document so looks correctly then I do making the changes that I needed to. People who make money using tools like MS office are going to spend the money to buy the software then looking for free alternatives because the price of the software is always less then employee time used to fix everything. Mac users don't have higher expectations then Windows users. Linux users are forced to use OO and other MS office clones because MS office won't run on Linux (with out WINE or something simular)

    127. Re:What's the downside to using X11? by whorfin · · Score: 2, Informative

      If the mac users are really that picky about the UI why don't they pay for the development of a mac version of OO or lobby apple for a real office suite or just say fuck it and buy msoffice?

      They are doing exactly what you're so eloquently suggesting.

      MS Office is a top selling OSX application (likely *the* top selling app), and Apple has just announced their iWork suite.

      --
      Laugh while you can, monkey-boy!
    128. Re:What's the downside to using X11? by idlerich · · Score: 2, Informative

      Actually Abiword does have a Mac OS X version, and it's very nice. You can also get TeXShop for the Mac, which is great for those of us who prefer to use LaTeX rather than word processor. So frankly who needs OO.

    129. Re:What's the downside to using X11? by AndyElf · · Score: 1

      iWork (at least now) lacks a spreadsheet (if Apple makes one, will they call it `Grid?' :)). Not to mention a light-weight database (but I guess this maybe unnecessary, since FileMaker has been there for ages).

      I thought for a while that Apple should have put some effort behind supporting Aqua port of OOo, but this may not really fit all that well with their strategy. It may still make sense for them to work with either Gnumeric or Kspread team to get at least the engine (the way KHTML become a part of WebKit).

      --

      --AP
    130. Re:What's the downside to using X11? by the_rev_matt · · Score: 4, Insightful

      That's not what they're saying at all. What they are saying is "If you want us to use what you make, make something we would want to use."

      Most Mac users do exactly as you suggest, which is use MS Office or some other native Mac alternative.

      Saying "I'm giving you this for free, so you better use it even though it doesn't suit your needs." is just as arrogant.

      And I say this as someone who is perfectly happy running the X11 version of OO.o on my Macs.

      --
      this is getting old and so are you

      blog

    131. Re:What's the downside to using X11? by AndyElf · · Score: 1

      I'll second that -- having a *theme* at least that makes a little *effort* to make it less of an alien on Mac desktop -- that would be very good and much appreciated by Mac crowd, I'd gather.

      --

      --AP
    132. Re:What's the downside to using X11? by Durandal64 · · Score: 0, Flamebait

      Because the everyday person doesn't need it, and it's fucking confusing for anyone but a geek. If geeks want it, they can install it. Why don't you just tell Microsoft that they need to include their POSIX layer with every Windows install and smack a "Getting Started With Windows Unix Services" tutorial on the screen during initial setup?

    133. Re:What's the downside to using X11? by mrchaotica · · Score: 3, Interesting
      Maintaining a seperate version of Open Office for another proprietary API
      Who said the Mac OS API was proprietary? It's not. In fact, you can even use it both on *nix/X11 and The OS Which Shall Not Be Named. There's only one difference with the version for other platforms:

      It's called GNUStep.

      Porting OpenOffice to Aqua/GNUStep would actually be useful. GNUStep is similar to Java or .NET/Mono; it's just as cross-platform and just as native, and unlike .NET it's native on the Mac as well (does Mono work on the Mac yet?).
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    134. Re:What's the downside to using X11? by luvirini · · Score: 3, Insightful
      Actually excel was the original engine that got microsoft office to it's dominant position. It was (and probably is) the best spreadsheet around.

      I remeber back when people still bought their office apps separately and Excel was the superior thing.

      It was then that microsoft started pushing the office concept with the pricing where you could get the whole office package for about one and half times the excel price, thus people started going for it, though usually word was seen as not so good solution, but a "good enough" one.

    135. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0
      "If the mac users are really that picky about the UI why don't they pay for the development of a mac version of OO or lobby apple for a real office suite or just say fuck it and buy msoffice?""


      Which is exactly what we're doing. Apple has so far built an excellent presentation program and a new word processor. The spreadsheet will certainly follow in a year or two. And MS Office 2004 is a popular package, and a pretty good one, if you're willing to pony up.

      As for funding a Mac port of open office...why, excatly, should we pay for supposedly Free-with-a-capital-F package? OO.o isn't up to par on the Mac. Not because it's bad software, but because it's badly integrated to the point where most users, having a good feel for how a Mac program should act, would be hopelessly confused and frustrated. Effectively, OO.o is already "unsupported" on the Mac. Mac users aren't interested in living off the crumbs of OO.o, and OO.o's maintainers aren't interested in supporting the Mac, so we have an impasse.

    136. Re:What's the downside to using X11? by sander · · Score: 1

      So what you are basicly saying is that Mac users are happy to get 10% of the functionality everybody else has as long as that functionality comes packaged in Jobs-blessed UI?

    137. Re:What's the downside to using X11? by NordicMan · · Score: 1

      I think you would find that Mac users would pay for another office suite, if it properly communicated with the existing dominant suite. I don't need that right now. However, I am going to get hold of the OOo, and I think you should not generalise about Mac users. For one thing, it certainly is appreciated, the work that has gone in to making the OOo work on OS X. By the way, we do spend a dime or more on products. So I hope that the Mac is not 'scratched off'.

    138. Re:What's the downside to using X11? by sander · · Score: 1

      What you seem to have forgotten to do is compare the functionality offered by OOo and iWorks. iWorks is not even really an office suite, never mind powerful - its a pretty basic word processor with inline drawing capability.

    139. Re:What's the downside to using X11? by pixelgeek · · Score: 1

      -- And somebody replied, "they haven't figured out how to make a better spreadsheet than Excel yet."

      I can't imagine that it would take more than a two hour brainstorming session to come up with a list of compelling ways that Excel could be improved.

      Lets start with data entry and formatting.

    140. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      The developers know that the mac crowd will not accept OO unless it's better then MS office.

      Umm perhaps I am nutty, but isn't this the whole point of competition? Nobody should use it unless it provides something better than other competing applications.

    141. Re:What's the downside to using X11? by mrchaotica · · Score: 5, Insightful
      Aside: This isn't really a reply to you, matt-whatever, but instead a reply to the community at large who think OS X is just for traditional "Mac people" -- so when I say "you," don't take it personally.
      Mac people don't want what open-source people think is a good interface. They want consistency and an easy learning curve.
      As an "open-source [person]," I think Mac OS has a very good interface. In fact it's so good that I don't use my Linux computers all that much any more. I admit that it's got consistency and an easy learning curve, but it's powerful too. That learning curve isn't steep, but it doesn't stop climbing!

      So, what are these powerful features I'm talking about?
      • AppleScript. Do all YOUR [assume you're a Linux user for a minute, please] graphical applications support scripting -- and more importantly, cross-application scripting? Mine do! And I can mix Applescript and Bash script in the same file.
      • Services. I can select text in any application and have it spell-checked, read to me, inserted into an email, auto-summarized, etc. I can even apply an Applescript to it.
      • The Terminal. I get a pretty GUI, but I get all the UNIXy commmand-line goodness, too.
      • Mac apps. I can run *nix and X11 apps just like you can, but I can run Mac apps too, and you can't. There are lots of Mac apps with no real (decent and complete) equivalent on Linux: iTunes, Keynote, commercial games, that bookshelf thingy that there was an article about yesterday, etc. And they've got the je ne sais quoi too. ; )
      Oh, and in a few months when Tiger comes out we'll get two biggies:
      • Spotlight. Not only does it search, but it enables Smart Folders -- now I can set it up so that all my data gets organizes itself, instead of me having to do it manually!
      • Automator. I'll be able to create scripts graphically (no worrying about syntax and no having to look up the API).
      If all you Linux or Windows people see when you look at OS X is the eye candy, you're missing the point.
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    142. Re:What's the downside to using X11? by sander · · Score: 1

      Sorry, but - why the heck should the majority of OOo developers care even one bit what the mac users want? Sooner or later they will most probably die out anyways - the more they want everything to be delivered on a silver plate to them, the faster it will happen.

    143. Re:What's the downside to using X11? by Trelane · · Score: 1
      here was no true concept of widgets, but if you wanted something bad enough, you made it work. In some sick sense there was/is a widget library,
      There was Xlib, and Xtk (the X Toolkit) and the Athena widgets. Both Xtk and Athena provided widgets, iirc. They weren't nearly as pretty as modern graphics, but they were quite functional (for a look at such an app, try xman); not at all "sick" imho.
      --

      --
      Given enough personal experience, all stereotypes are shallow.
    144. Re:What's the downside to using X11? by Karma+Farmer · · Score: 1

      Mac users, like Windows users, would be happy to use a free office suite if it was 1/2 as good as MS office, but was 100% compatable with MS office.

      First, no I wouldn't. I'd pay good, solid cash for an office suit as good as MS Office, and it doesn't even have to be compatible. I won't use a shitty office suite, even if it's free.

      And second, the only people who say "100% MS Office Compatible" are the ones who have absolutely never used office in a business environment. The COM interfaces and VBA support aren't heavily used, but ever office I've ever been in depends on them for at least one application.

    145. Re:What's the downside to using X11? by sander · · Score: 1

      If your techies can't figuire it out then with 99.99% of probability either they really have no clue and you are better off with firing them or you are just a troll.

    146. Re:What's the downside to using X11? by Tsiangkun · · Score: 1

      OO kicks ass on linux. It just doesn't fit in with the OS X interface. Even basic functions like copy and paste doesn't work smoothly with native apps. Apple charges a premium for a consistent friendly interface, and all the X11 applications don't really fit in, it's nothign against OO.org in particular.

    147. Re:What's the downside to using X11? by mrchaotica · · Score: 2, Informative

      Yeah, right.

      If that's the case, then how is it that I'm reading this on a Mac with ZERO non-free applications, aside from the ones that came with the computer (iLife '04, AppleWorks, etc)? (Oh, and zero "pirated" applications" too.)

      On my Mac, I've got AbiWord, America's Army, BitTorrent, Blender, Butler, Camino, Cenon, Desktop Manager, DivX, Fire, Firefox, Frozen Bubble, Gimp, Handbrake, Limewire, LyX, MPlayer, Nethack, Nvu, OpenOffice (yes, the X11 version -- I don't like using it, though), OSXPlanet, Quinn, Seti@Home, StepMania, TexShop, Thunderbird, VLC, and Waste. And I also use Fink. Is that enough tolerance and flexibility for you?!

      Except for Gimp and OpenOffice (Fink doesn't count), all of these programs are native Aqua apps. If it's worth it to them -- even Nethack, for crying out loud! -- to make native Aqua ports, shouldn't it be worth it for OpenOffice?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    148. Re:What's the downside to using X11? by mrchaotica · · Score: 2, Insightful

      I hate to tell you, but the Mac isn't dying out. At my school, I see lots of students switching to the Mac, in fact.

      And the really significant part? I don't go to an art school. I go to an engineering school, and it's the Computer Science majors (including me) who are switching!

      OpenOffice would do well to cater to the Mac people as well as the Free Software people, because more and more, it's the same group!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    149. Re:What's the downside to using X11? by nathanh · · Score: 1
      Here's a newsflash for you: all software is eventually redundant. You think Open Office is still going to be around 20, 30, or 40 years from now?

      20? 30? 40? I'm talking 2, 3, or 4 years. But I'm glad you're bringing us newsflashes. Where would I be without your wisdom.

      And personally, I'm not concerned about running a proprietary application in this case, as there is every indication that Pages' native file format will be XML based, with a publically available XSLT, making it very easy to transform into other XML formats.

      I've been burnt before by proprietary applications even when the "format" was open. I'm talking about UNIX. I have no desire to tread that path again. One day you'll be burnt as well, if you haven't been already.

      Sorry, but your attempt at FUD doesn't fly here.

      Rolls eyes. Whatever. You're a terrorist. And probably a communist too.

    150. Re:What's the downside to using X11? by Herr_Nightingale · · Score: 1

      "It would be a thankless job and it would be very painful."

      Not to mention there aren't very many Mac users anyways. How many OO.o developers for Mac are there now, just the two of 'em?

    151. Re:What's the downside to using X11? by gaspyy · · Score: 1

      I can't say this without being a huge asshole but i'll try.

      Maybe the mac users don't care about paying now for the development of an office suite that will be ready and polished sometimes in the future, when they have ready alternatives. It's not like Mac doesn't have a decent office suite.

    152. Re:What's the downside to using X11? by diamondsw · · Score: 1

      If you haven't noticed, they DO say "fuck it" and use Microsoft Office, that is, if they notice you exist at all. I thought this was about providing a usable free alternative to Office? If you want to scrap a platform, go right ahead - you just ceded that to Microsoft.

      In the greatest of ironies, Microsoft's Mac business unit has been well known for many years for putting a huge amount of Mac-specific polish and features into their apps, frequently adding features not found in the Windows version. And the Open Source's answer to this is "you don't like it, fuck off"? Gee, I wonder who people will support.

      Firefox is a great example of polishing a port to be "native enough" - it uses proper keybindings, menu structure, and integrates with key OS features. It *feels* like a Mac application, although it shows its heritage at a few minor seams. Meanwhile, OpenOffice requires running in a completely foreign environment with a relatively bizarre interface. Yeah, you're going to convert a lot of people with that...

      --
      I don't know what kind of crack I was on, but I suspect it was decaf.
    153. Re:What's the downside to using X11? by killjoe · · Score: 1

      " So the OO guys should be beyond criticism? Jesus-- get over yourselves..."

      If you don't like it get your money back.

      "Not only do Mac users have to put up with the shit that is OO.o, but they (we) are completely within their rights to voice complaints about OO.o."

      You don't have to put up with it. Nobod is forcing you to use it. If you don't like it use something else.

      --
      evil is as evil does
    154. Re:What's the downside to using X11? by Seeker5528 · · Score: 1

      "The problem is that "day 1" for OpenOffice was the day Sun handed them a huge codebase specifically written for X11 and Win32. No Mac API support included."

      The source handed out by Sun on day 1 was a functional product.

      "By contrast, Mozilla was given an app that had already been coded for Mac, so on "day 1" the porting project was already complete."

      By contrast the code netscape released was incomplete, then scrapped after several months, so what there was and was not code for really makes no difference. It seems to me there were several issues with aqua based Mac ports of Mozilla. Is there on that is kept in sync with the main tree?

      If there are developers that are willing to step in and do the work, then the work will continue.

      Later, Seeker

    155. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Yes they do include a custom X 11 in OS X. And it is possible to have it hook into the core of the OS, things like carbon, aqua and core foundation.

      All the X11 application developer has to do is include some header files that are freely downloadable from Apples developer site and compile the application with them.

      Doing so in effect makes X11 nothing more than another framework to the OS much like Java is. It will still LOOK like an X11 appy, still use the X11 dialogs etc, but it will allow it to interface with the OS like an aqua app.

      But do they do it? NOOOOOOOoooo...

    156. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      you know all those brain cells you currently have tasked remembering how XYZ app is laid out and where all the menu items are?

      They could be used for something else.

      And when you buy a new app you don't have to devote anymore of your brain to remembering that this app has CDE function in this location as opposed to in that location in XYZ app.

      Easier navigation for basic functionality means you are using the app more quickly for productivity.

      And once more leaves you with brain cells that you could be using to store memories of more pleasant things then the layout of a particular application...

    157. Re:What's the downside to using X11? by artoffacts · · Score: 1

      Three words (two of which are possibly spelt wrong): Sveinbjorn Thordarson's Platypus. Wrap a sh script that starts OpenOffice in an .app wrapper and then treat it like you would any other .app, problem solved.

    158. Re:What's the downside to using X11? by HuguesT · · Score: 1

      GNUstep has made huge strides in the last couple of years but it is not what I would call a bulletproof development environment, it has compatibility problems with what Interface Builder generates on the Macs (and old NeXTStep workstations) and it only implements a subset of the Mac Toolkit anyway.

      On the other hand Sun has access to the old OpenStep implementation since they co-developed it with NeXT.. IIRC it is more complete and more stable than GNUStep, although it relies on PS rather than PDF for drawing. It would be interesting if it could be open-sourced and like you suggest made the basis of their suite.

      Unfortunately I don't think this will happen. Sun has a huge vested interest in X.

    159. Re:What's the downside to using X11? by PHPfanboy · · Score: 1

      Yeah I love this attitude!
      You cater to my needs and I give you $0.
      Based on this philosophy I have been developing an Open Source Business Plan for ya:
      1) You work
      2) I use
      3) Profit! (not yours though)

      --
      29 mpg. YMMV.
    160. Re:What's the downside to using X11? by paretooptimum · · Score: 1

      One potential model is Firefox. We need a core group to take the open office applications, which are suffering from bloat, and strip them down, making unnecessary functioality return as plug-ins. Any takers?

    161. Re:What's the downside to using X11? by HuguesT · · Score: 1

      Hi,

      No other word processor, perhaps, but there are excellent open-source solutions for writing material.

      I'm not a textbook author but I'm a researcher, I write stuff every day as well, from course notes to articles via presentations.

      Honest question: What do you think your chances are to be able to re-read and re-edit your current work in 15 years time?

      AFAIK no current version of Word can correctly read 1990 word-4.0 files. I've had that problem not long ago.

      I a previous job I was handling word files regularly. It was pretty common to see one colleague print the very same version of the file you have, with the same version of the software on the same printer and have it still look different. Sometimes dramatically so, like uncorrectly labelled lists.

      My experience with revision notes in Word (2001, not 2003) is that they don't compare with a revision control system. Word revisions do work between 2 people but not more, and it quickly becomes very hard to track who's done what in heavily edited areas. In case of disagreement they can become a liability. Hopefully the 2003 version are better.

      OTOH since I moved from Word to TeX 14 years ago, I've had zero problem of that nature since it only uses ASCII (or Unicode these days). Revisions between multiple people are handled with CVS (or subversion these days), so you know exactly who did what when and why (thanks to comments), and you can revert easily.

      I've edited two books of proceedings. The first was done using only TeX, and it was essentially a matter of deciding how the book would look in the end. It was possible to produce a single PDF document of the whole book with a consistent look without too many problems. We got a refund from the publisher because they assumed that we would deliver them a PDF document with too many mistakes in them that they would spend days to correct, but it simply didn't happen. It was basically right the first time.

      For the second we accepted Word documents, and it was a nightmare to make all of them look even remotely alike, and we didn't succeed in producing a single PDF of all of them. It remained a collection of disparate individual articles, and we did spend about a week with the publisher fixing all manners of mistakes (like missing figures, page numbers, etc...)

      To me Word has a long way to go still.

    162. Re:What's the downside to using X11? by HuguesT · · Score: 1

      Yes, for example why is it that if you want to edit a cell in Excel, you need to click on it, then move your cursor to the editor field in the toolbar?

      This is terribly inefficient, yet Gnumeric and OOo do the same thing.

    163. Re:What's the downside to using X11? by quarkscat · · Score: 2, Interesting

      I don't want to give the appearance of being
      a troll here, but WTF? The only downside to
      using X11 is that the development team isn't
      in a toe-to-toe slugfest with whatever the
      platform dependent GUI-of-the-day is.

      OOo long ago (3+ years) decided that they would
      fork OO between platforms instead of using a
      common source tree with #IFDEFs to handle
      platform dependencies. The argument promulgated
      was that separate source trees would make use of
      platform dependent GUI standards better. My
      argument (at the time) was that a common source
      tree would be easier to maintain, and so what if
      the application did not look like other apps on
      the same platform -- a common look-and-feel
      across platforms would establish some measure
      of "branding". Well, okay -- so why now drop
      the differentiation between platforms that OOo
      thought was so necessary (and break the common
      source tree maintenence relief)? And especially
      only for the Max OSX platform?

      What I see is 3+ years of wasting time on
      platform differentiation (to compete head-to-head
      with MS Office), instead of making the entire
      suite slicker and more feature-rich. As it
      turns out, anyone trying to stay current with
      constantly evolving GUI standards from either
      Microsoft or Apple is "chasing their tails".
      IMHO, "look-and-feel" can easily be trumped by
      top quality rock solid code, and a feature-rich
      environment.

      Abandoning the platform-dependent GUI on one
      platform (OSX), while dancing toe-to-toe with
      Microsoft's GUI on the another is the worst of
      both worlds. Chasing ghosts does not get the
      job done. A feature-rich office apps replacement
      that can go anywhere with a simple "./configure"
      and "make" has intrinsic value, even if it is
      reliant upon X11.

      Just my rapidly depreciating $00.02 worth.

    164. Re:What's the downside to using X11? by omarin · · Score: 1

      Well, I just tried using Open Office on my Mac yesterday, and aside from OO being ugly, I was not able to cut and paste text from a native Mac OS X app to OO. I tried from several native OS X apps to Open Office, but no luck. And then there's the fact that having to use X11 on a Mac just feels like a kludge when TWO apps open (Open Office and X11) when you just wanna type but don't wanna use M$ Word.

    165. Re:What's the downside to using X11? by Bulln-Bulln · · Score: 1

      Huh? I copied random text from Firefox can't paste it into OpenOffice (X11).
      I tried Ctrl-V and your [Ctrl]-[Option]-click technique. Are you sure it works for you? I doesn't work for me.

    166. Re:What's the downside to using X11? by Squozen · · Score: 1

      Yes. Compared to a native Aqua app, X11 bites.

    167. Re:What's the downside to using X11? by Squozen · · Score: 1

      Actually Office on the Mac is a version ahead of Windows.

    168. Re:What's the downside to using X11? by orin · · Score: 1

      Word 2003's revisioning system is far superior to that of other versions of Microsoft Office. It is very clear which editor made particular alterations. It also distinguishes on the basis of pass, so the changes made by an editor on the first pass are represented differently by those made by an editor on their second pass. I usually have about 3 different other people go over my chapters once I submit them and even when it has gone through the cycle twice, it is clear who has changed what.

      My answer to your question is I don't know. I suspect the answer is yes I would be able to, if only because the newer revisions of office haven't broken the Office 97 format. Other authors I know who have been writing since the early 80's regularly update their stuff if they've kept them (that is, they regularly save the file in a new format every 5 years or so).

      Textbooks also tend to update almost as often as word processors ;-).

      As you know, when a book is ready for publication, the final versions are delivered in PDF (as you pointed out). Each one of my books (and even a few magazine articles) have required a final review of a PDF rather than a word document. That's generally where you have to find out if there are figures that are missing and so on. 99% of the time though there isn't any problems at this stage.

      I've looked at other word processors. I've read /. for years, so I'm very aware of the alternate options out there. I've tried everything, from AbiWord, through WP for Linux, StarOffice, OO.o and a slew of others. I use a lot of Word's features and I'm fully cognisant that most other people do not. For many people, other solutions are applicable - but as Bruce Schinder recently noted in his Cryptogram, for some of us, there are certain features in Word that are completely necessary which simply aren't replicated anywhere else. They are unlikely to be replicated within an Open Source application any time soon because to few people have the same itch.

    169. Re:What's the downside to using X11? by Simon+Brooke · · Score: 1
      Some have said that the X11 version is "ugly", but the Open Office developers have only themselves to blame for that, there are numerous beautiful graphics toolkits avialable on X11 which wonderful and georgeous user interfaces can be created with. Its not like X11 actually restricts user interface design, in fact, X11 provides a stable, time tested and refined platform which doesnt limit the beautiful user interfaces that you can implement on top of it.

      You're missing the point (yes, there is one).

      Graphical user interfaces work and leverage user experience by being consistent. Inconsistent user interfaces are a bad thing. Conequently, taking an application with one style of user interaction and dropping it onto a screen where every other application has a different style of user interaction is going to make things more difficult for users.

      This has nothing to do with whether or not you use X11 as your basic underlying windowing layer. As you say, there are lots of nice GUI toolkits for X. But it has a lot to do with how you abstract your user interface controls. Sun has a lot of experience of doing this, and, frankly, a lot of experience of getting it wrong.

      Look at Java. Originally it came with the Abstract Window Toolkit, which was the right idea if not brilliantly executed. Whatever platform you used, an AWT application had menus which looked like and worked like the menus of the platform - because they _were_ the menus of the platform, mapping Java methods onto the windowing API of the platform; and similarly for all other UI widgets. It was lightweight, looked consistent and, to a considerable extent, worked consistently. But because Sun wanted AWT apps to work exactly alike on all platforms, AWT had to be the lowest common denominator of the GUI features of those platforms: if you had two, or three, or more buttons on your mouse you could still only use one. There's no mechanism in AWT to allow you to specify how to react to a second mouse button, or a scroll-wheel, if it happens to be present... but it would have been so easy to do.

      So next Sun brough out Swing, which is a mighty piece of bloat and a heroic processor hog, which ignores all the high level GUI API of the host operating system and instead provides its own GUI components, guaranteed to be inconsistent with the user interaction style of every platform. Cle-ver.

      If Open Office had adopted an AWT-like approach to interacting with the GUI components of the host platform (but extended to make use of extra features when present), the problem of supporting Aqua would cease to be a problem.

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    170. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      But we are within our rights to complain about it.

    171. Re:What's the downside to using X11? by mennucc1 · · Score: 1

      > it's really difficult to use X11 when you're
      > used to the consistency of native OSX (Cocoa or
      > Carbon to a certain extent) applications. i.e.:
      > All OSX apps have similar places to go for
      > preferences, to open/save files, edit, help,
      > etc. Plus keybindings and mouse behavior
      > are all similar.

      Those people who find it "really difficult" to
      find a menu item probably have so many problems
      using their PC that they will not even be able
      to start OpenOffice, let alone notice that it
      is X11 and not native.

    172. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Quite the opposite. As a Mac user, I'm not happy with even 100% of the functionality without the UI consistency.

      I would argue, though, that an inconsistent UI with the same features is at best 10% as functional.

    173. Re:What's the downside to using X11? by rhodes777 · · Score: 1
      "running an X11 application is like being thrown back to 1990. Menu's are attached to the window, keybindings are messed up, and you're lucky if copy/paste works."

      FWIW: KDE offers OSX-style application menu bars.

    174. Re:What's the downside to using X11? by roard · · Score: 1

      GNUstep has compatibility problems with what InterfaceBuilder generates on the Macs ? well, yes, sortof.

      What IB and GORM (the GNUstep equivalent to IB) do, is to *serialize* a bunch of objects. GNUstep does that in a cross-platform way (if I create a .gorm on linux/ppc it will work on windows/x86), but of course it's not byte-by-byte compatible with what IB does -- it's impossible, as the serialisation depends directly on the platform/runtime.

      BUT. InterfaceBuilder can now generates XML files instead of the previous binaries, and there are some efforts to make GNUstep read them. So we'll probably have the hability to read directly InterfaceBuilder files (nibs) in the coming year. If you want to help :-)

      Additionally, you could also use Renaissance, an XML framework to generate interfaces on GNUstep and on OSX (so, just one file for both platforms).

      it only implements a subset of the Mac Toolkit anyway.

      Er, well, it's technically true -- GNUstep only implements the Cocoa part, not Quicktime, for example. But frankly, GNUstep cover nearly everything in Cocoa that you don't have too much difficulties to port a Cocoa program to GNUstep in general (and vice-versa).

      On the other hand Sun has access to the old OpenStep implementation since they co-developed it with NeXT.. IIRC it is more complete and more stable than GNUStep, although it relies on PS rather than PDF for drawing. It would be interesting if it could be open-sourced and like you suggest made the basis of their suite.

      Well, I'm not so sure that OPENSTEP/Solaris is "more complete" than GNUstep, as we have nearly everything implemented (the missing things are classes barely used). What GNUstep miss is some new classes added by Apple recently, that's all. And GNUstep implements partly theses new classes, while OPENSTEP/Solaris doesn't. On the other hand, yes, OPENSTEP/Solaris is probably more stable than GNUstep/Solaris ;-) (although GNUstep/linux works quite well now).

      Anyway, as you say, it won't happen. Sun is a strange company -- having OPENSTEP available (and moreover, the fantastic development tools !) and a bunch of OPENSTEP applications (they bought LighthouseDesign!!), ... they choose to can the project and burry thoses apps, and go along with Java to bring an "Object Oriented Desktop". We still wait for it with Java..
      Talk about a heavy Not Invented Here syndrom... (it's even worse as they participated in the API creation..)

    175. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      But only for KDE apps, so not for OOo (not even if you run it under KDE).

    176. Re:What's the downside to using X11? by zotz · · Score: 1

      " you know all those brain cells you currently have tasked remembering how XYZ app is laid out and where all the menu items are?

      They could be used for something else."

      How does this match with the "more hooks thinking" wrt the more you learn/know the easier it is to learn/know more?

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    177. Re:What's the downside to using X11? by divec · · Score: 1
      The non-aqua version [...] works fine until you actually want to use the wealth of rich, high-quality fonts that comes with OS X.


      I've not tried OOo on OS X, so I'm not in a position to comment on the font quality. However, assuming it's using FreeType like the Linux version does, it's Apple's own patents which cause rendering quality problems.

      --

      perl -e 'fork||print for split//,"hahahaha"'

    178. Re:What's the downside to using X11? by daviddennis · · Score: 1

      You are making a product.

      We (Mac users) are your customers.

      We can choose to take your product for free, or we can pay $150-odd for the Student/Teacher edition of Microsoft Office, which only requires that you're not the owner of a large business.

      You should consider an alliance with Mac users because they have already decided to "think different". They just want a product worthy of different thinking.

      Using a Windows-style GUI isn't going to cut it. After all, we didn't choose Windows, so the odds are pretty good that we don't want a me-too imitation. That's why the Microsoft Mac Business Unit creates a program that looks nothing like Windows.

      Ironically enough, we'd rather have that product than yours, which, if my memory serves, has all the gray depressive feel of Windows 98.

      (When I was IT manager (among other hats) at a mid-sized 200-employee company, I tried introducing OpenOffice and it bombed since it messed up the reading of even simple Office documents. It was a gigantic embarassment to me. All the hard work in the world doesn't pay off if it doesn't show in the product. Sorry, guys).

      D

    179. Re:What's the downside to using X11? by leandrod · · Score: 1
      > No Mac API support included.

      This is not true. StarOffice did have a Mac OS port until at least v4.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    180. Re:What's the downside to using X11? by UnxMully · · Score: 0

      Well then you clearly don't remember that before Excel became dominant, Lotus 123 was the spreadsheet of choice for the discerning user. Far better than Excel.

      The reason Excel became the dominant spreadsheet was because Lotus sunk all of their development resource into Improv which then died on it's arse leaving them nowhere to go with SmartSuite.

      A summary of the history appears here http://en.wikipedia.org/wiki/Lotus_Improv/

    181. Re:What's the downside to using X11? by SteveM · · Score: 1

      I know your post is flamebait but ...

      Sorry, but - why the heck should the majority of OOo developers care even one bit what the mac users want?

      They shouldn't. That's my point. They should code whatever they want for themselves. End of story.

      But then they shouldn't be surprised if the users, in this case OS X users, don't flock to their product.

      You can't completely ignore the user's expectations and wants and then complain when the same users reject your product.

      The OO folks have decided that they do not want me, as an OS X user, to be an OO user. Fine. I won't be.

      SteveM

    182. Re:What's the downside to using X11? by SteveM · · Score: 1

      But that is the open source "business" plan.

      How much have you paid for your copy of Linux?

      How much direct profit has Linus made from Linux?

      And yet Linux sems to cater to a lot of people's needs.

      SteveM

    183. Re:What's the downside to using X11? by jedidiah · · Score: 1

      No, Windows took off in mainstream PC's because it was what was already being bundled with everyone's hardware. The fact that it wasn't quite as arcane as DOS might have helped. However, enforcement of arbitrary limitations on user interfaces really had nothing to do with it.

      If anything, it was the web browser that drove adoption of WinDOS based PC's. It finally presented a killer application that the general public could buy into.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    184. Re:What's the downside to using X11? by jedidiah · · Score: 1

      What are we using, Wordstar?

      Isn't the whole point of a GUI the fact that you don't have to remember the details of every little application you use? HELL, if you imposed arbitrary limits on what can be done with user interfaces you could just go back to DOS5.

      You're taking the biggest advantage of GUI's and just flushing it down the toilet.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    185. Re:What's the downside to using X11? by jedidiah · · Score: 1

      If Mac users want a proper Mac version of OpenOffice, they have the capacity to code it themselves. If they don't want to do this (for whatever reason), such a version won't exist.

      At this point, it's really no one else's fault if there's no real Mac version of OO.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    186. Re:What's the downside to using X11? by luvirini · · Score: 1

      oh, I do remeber lotus 1-2-3 But in order to ot make my post too long, I left out things that happened before that. By the time lotus had stopped developping (for all practical purposes) and then excel was in strong shape, that is when this thing happened. ofcourse we could go back to times before lotus too.. (uuh digging memory.. memory recall failied.. page lost... multiplan?) :)

    187. Re:What's the downside to using X11? by jedidiah · · Score: 1

      >You are making a product.
      >
      >We (Mac users) are your customers.

      Not at all.

      WE all are making the product.

      If you collectively choose not to participate then that's ultimately your own problem. You have no need to "depend on the kindness of others".

      --
      A Pirate and a Puritan look the same on a balance sheet.
    188. Re:What's the downside to using X11? by TheRaven64 · · Score: 1
      GNUStep is similar to Java or .NET/Mono; it's just as cross-platform and just as native, and unlike .NET it's native on the Mac as well (does Mono work on the Mac yet?).

      Unlike .NET and Java, GNUstep apps are native code, not bytecode. I am not going to get into the argument of whether this is a good thing or not - there are some interesting things that could be done to optimise Objective-C in a JIT environment, but the runtime does something similar. This does, however, mean that GNUstep apps need to be recompiled for each target platform (not a huge problem, since it only needs to be done once.

      Also, GNUstep and OS X interface builder files are not the same. Until 10.3, OS X interface builder produced binary files. Now they are XML, which means that it should be possible to translate them easily to GNUstep compatible ones (Nicolas gives some more detail in another reply to the parent post). The opposite ought to be possible as well - providing a mechanism for loading GNUstep interface builder (GORM - Graphical Object Relationship Monitor) files in OS X, since they are both simply collections of serialised objects.

      One of the huge advantages of GNUstep as a development environment is that it is very easy to customise the final result with the addition of bundles. One particular example is the menu bar. On NeXT platforms and GNUstep the menu `bar' is a vertical stack, which is usually at the top left of the screen but can also be moved around. With the addition of a bundle this can be changed to put it at the top of the screen (if you want a Mac feel), or tied to each window (if you are using a Windows-derived GUI).

      --
      I am TheRaven on Soylent News
    189. Re:What's the downside to using X11? by TheRaven64 · · Score: 1
      A native (carbonised) OOo would be suitable for giving to people running OSX that ask for a word processor.

      It's been mentioned a few times in this thread, but I would recommend AbiWord for these people. I haven't used the latest builds, but the beta I looked at a while back was very close to HIG compliance, and the developer was specifically asking people to file UI bugs.

      --
      I am TheRaven on Soylent News
    190. Re:What's the downside to using X11? by UnxMully · · Score: 0
      Point taken. Visicalc I think was the original but that's well before my time.

      When I started with Windows PCs we had the choice between Smart Suite and Office, though there were others none were quite so well packaged it seems. Technically Smart Suite was well ahead of Office and, IMHO, in some areas - the use of style sheets in Ami/Word Pro for example - Office is still behind.

    191. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Does anyone seriously use a wordprocessor for typesetting? HAH HAH HAH!

    192. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      How about: It's next to impossible to get OO to print! Things like that are always a problem when you're an appendage of the main operating system.

    193. Re:What's the downside to using X11? by JohnFluxx · · Score: 1

      I thought OO.org didn't use configure and make?
      Doesn't it have its own complex build system?

    194. Re:What's the downside to using X11? by Blakey+Rat · · Score: 1

      Uh. Yeah, but if you click a cell and just start typing, the input automatically goes into the editor field... so I don't really see this as a valid complaint. You make it sound like a three-step "click, click, type" process when it's really a two-stop process "click, type."

    195. Re:What's the downside to using X11? by WGR · · Score: 1
      Corporate users want a product that is the same across platform, that follow well defined and uniform GUI conventions for the platform on which it is installed and that can be easily supported by their helpdesk/technical staff.

      Without a Macintosh GUI version, Open Office fails this and would not be eligible for many companies purchasing requirements. I like Open Office and I have installed it on a number of friends systems, but it needs to have a corporate reputation, not just a geek reputation. As long as Sun/OpenOffice.org does not take the coprorate market seriously, they will lose out to Microsoft, which does.

    196. Re:What's the downside to using X11? by renoX · · Score: 1

      OK, I'm curious: do Word, Excel, IE support AppleScript?

      You know, KDE applications are scriptable too, but it' true that very few Linux users use only KDE or only Gnome apps usually it is a mix of toolkit (bleah)..

    197. Re:What's the downside to using X11? by Ginnungagap42 · · Score: 1

      According to the Word:Mac help file:

      "Microsoft Office 2004 features native AppleScript dictionaries for Microsoft Word, Excel, PowerPoint, Entourage and Graph."

    198. Re:What's the downside to using X11? by KlomDark · · Score: 1

      Menus attached to the window are a throwback to WHEN? I'd call that a throw forward compared to the corny Mac menu interface.

      I take it you are saying the non-intuitive interface of having the menu for the current window at the top of the screen a good thing? Intuitive only to long time Mac users. Always throws me off completely - Is this the system menu or the application menu? Drag the floppy to the trash can to erase it or eject it?

    199. Re:What's the downside to using X11? by Anonymous+Brave+Guy · · Score: 2, Insightful

      I'm sorry, but what you wrote is nonsense, pure and simple. The combination of Windows, Word and Excel was what put Microsoft where they are today. Back then those tools were so far ahead of the DOS-based word processing and spreadsheet market in usability that almost everyone jumped to Windows to use them. The interoperability of Word and Excel, and the standard user interface of all Windows applications, were two of the major selling points in the promotional material. The fact that Windows made it relatively straightforward for new players to offer their products with similar GUI look and feel helped a lot, too.

      The web browser is almost irrelevant to Microsoft's current position. They hardly even noticed the web until the 95 generation, by which time the Windows product line had long since estabished itself as the dominant PC platform.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    200. Re:What's the downside to using X11? by mrchaotica · · Score: 1

      Oh, well, I assumed that the people making OpenOffice want their program to be more widely used. If that's not the case, then that's fine too...

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    201. Re:What's the downside to using X11? by mrchaotica · · Score: 1
      Unlike .NET and Java, GNUstep apps are native code, not bytecode... This does, however, mean that GNUstep apps need to be recompiled for each target platform (not a huge problem, since it only needs to be done once.
      And it's even less of a problem since you can distribute "fat binaries" that include code for several platforms. That means that even though it's native code, you can just distribute Foo.app instead of Foo(PPC).app, Foo(x86).app, Foo(Sparc).app, etc.
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    202. Re:What's the downside to using X11? by Brandybuck · · Score: 1

      With the exception of the pretentious Mac twits, what the user wants more than anything is software with *functionality*. All the slick user interfaces in the world don't mean shit if they don't do anything. You certainly want a good user interface, but it's priority number two. Substance over style. Features over flair.

      --
      Don't blame me, I didn't vote for either of them!
    203. Re:What's the downside to using X11? by BeepBeepBiloobop · · Score: 1

      The comment about functioning clipboard and cut-and-paste is the biggest thing to consider, IMHO. I have installed X11 (the one from Apple - too lazy to look up what the official name is...) and I installed OO.o. Everything went fine as far as the installation was concerned. It acts (as far as I can tell so far) just like the Windows version (and this is a good thing - I have that version on my PC).

      It acts ok until you try to move information out of the X11 area. At that point you might just as well be writing everything longhand. I understand that I have gotten my moneys' (smirk) worth from the application and I will use this for now because I don't really want to go to MS for the light amount of work that these applications would see on my home machine. The issue is that this application acts as if it is in a vacuum as far as communication goes. Who wants to save a separate file every time you want to move something from one (OO.o) window to another (OSX)? Given that, I can't use it as a default office application, so I will be looking elsewhere (including the full MS version).

      --
      I think so, Brain; but where are we going to get a duck and a hose at this hour?
    204. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      you don't get it, do you.. a real shame closed-minded fucks like you have to keep running your mouth time and time again..

      You know a consistent menu bar is good UI design. right? ...aaaand you know that something that throws you off.. means nothing to the rest of the world. Everyone but you, it seems, knows to just look at the upper-left, next to the apple, and see what program they're in if they happen to get confused.

      Consistency is a good thing. Repeat after me, dumbass.

    205. Re:What's the downside to using X11? by Grey+Ninja · · Score: 1

      No, it would be more like Microsoft not allowing an MS-DOS application to have a shortcut on the desktop, or to be used as the default application for certain file types.

      There's just no reason for not including support for such a thing. You forget that Mac OS X is built upon a UNIX distro.

    206. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      floppy? what floppy? there hasn't been a floppy in any mac since '98. You're definitely living in the last century.

    207. Re:What's the downside to using X11? by jbolden · · Score: 1

      For an end user what is a distinction between an application menu and a system menu? For that matter isn't the system GUI really just another application? That's the way most developers look at GUIs. Apple is right in having "finder is just another app".

    208. Re:What's the downside to using X11? by jbolden · · Score: 1

      What do you think the iApps are? That are highly low functional applications with very easy to use interfaces. The vast majority of applications on your system will be ones which you are a beginning user on. For those apps ease of use for the 10% functionality trumps having the full 100%. The goal is to be able to to quickly and easily do 3% of the things the app does.

    209. Re:What's the downside to using X11? by KlomDark · · Score: 1

      Yah yah, and the same fucking idiots that think the menu should be at the top of the screen, rather than attached to the app window, are the same fucking idiots that you have to remind that the underwear goes on the inside of your pants.

    210. Re:What's the downside to using X11? by KlomDark · · Score: 1

      > You know a consistent menu bar is good UI design. right? ...

      Yes, a consistent menu-bar at the top of the window I'm working is, is good UI design. Having to leave my application to drag my cursor half-way across the desktop just to access a menu command seems like it would also make some kind of sense, to the heavily medicated.

      > aaaand you know that something that throws you off.. means nothing to the rest of the world.

      7% of the entire user-base (being generous I know) is "the rest of the world"?

      > Everyone but you, it seems, knows to just look at the upper-left, next to the apple, and see what program they're in if they happen to get confused.

      It's nice to know that all the work done by Skinner and Pavlov has paid off for an infinitesimal segment of our society. Enjoy the "Mac Experience" you happy little Rhesus monkey.

    211. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      I'm detecting a lot of Mac Envy in your posts, joe. Maybe it's time to get a Mac Mini and get over it?

      I'm sure that being a hobbyist tinkering with semi-functional crap is very rewarding, spiritually if not economically. However, I'm sensing a lot of frustration from you, probably because, even after all efforts, it still doesn't work quite right. You tell yourself, "Well, it's good enough for gubmint work", but then when a smugly satisfied Mac user points out your method's shortcomings, it really sticks in the craw, doesn't it?

      It's past time to switch, joe. The rage you feel towards Mac users is displaced rage. You are unable to place the rage on the appropriate target because that would threaten your already weakened self image that is so heavily invested in that appropriate target. Yes, I'm speaking of Linux.

      The funny thing is, is that if you made the switch, it would probably make you into a decent linux developer once you've seen how things work when they are done right.

    212. Re:What's the downside to using X11? by benhaha · · Score: 1

      It matches perfectly. You know where a menu is in Word. You have a connection -- hook -- in that you know that menus are consistent between Word and Excel. This makes it easier for you to learn/know where menus are in Excel.

      It only works if there are relationships between the things you know. There are no hooks to help you learn lists of random numbers, hooks exist where there is commonality, and the more commonality, the more hooks there are.

      Cheers.

      --
      NO ID: BEING FREE MEANS NOT HAVING TO PROVE IT
    213. Re:What's the downside to using X11? by Zelet · · Score: 1

      I'm going to reply to my own post cause there are too many replies to mine.

      1. OOo is VERY ugly.
      2. Linux desktops are generally ugly.
      3. Each new KDE/Gnome release it gets less ugly.
      4. I like and use Linux for desktop and server systems. I also use Windows and Mac. They each have their place. Linux's is just in the closet :)

      --
      ...And when they came for me, there was no one left to speak out for me." - Martin Niemoeller (1892-1984)
    214. Re:What's the downside to using X11? by Anonymous Coward · · Score: 0

      Actually, having the menu at an edge of the screen makes it much easier to use quickly (at least with a standard mouse, not so much with some of the laptop built in mouse types).

      "How?", you say? It effectively makes the menu bar infinitely tall, because you can get to it by flicking the mouse all the way up. Large objects (even if they're just effectively large) are quicker to hit than small objects.

      To test it yourself, open an application and try to quickly hit a menu item without overshooting it. Now try the same thing with (for example) the windows task bar, which is at the bottom of the screen for the same reason Apple puts the menu at the top of the screen ('infinitely' tall screen objects).

    215. Re:What's the downside to using X11? by iroll · · Score: 1

      Open OO.o for Macintosh (X11).

      Create a presentation with the Powerpoint clone (can't remember the name).

      Try to go full-screen.

      If your idea of 'full-screen' includes a bar across the top, then you'll be fine. However, this little annoyance makes it infuriating for me to use OO.o for presentations.

      And by the way, the Mac user community is well-known for happily purchasing shareware--who says they wouldn't buy a boxed opensource product? If I saw a boxed, Cocoa-ed version of OO.o for a reasonable price, I'd snap it up. OO.o for windows is a pleasure to use. Remember we aren't all surfing /. and sourceforge for all of our application needs; put it in a box, slap a $30 pricetag on it, and stick it in the campus bookstores next to that $200 (academic price!) copy of Office, and with a little word-of-mouth it'll fly off the shelves. If it's impossible to sell boxed open-source software, Redhat and Suse must be run by friggin' idiots.

      --
      Repetition does not transform a lie into the truth. - FDR
    216. Re:What's the downside to using X11? by brienc · · Score: 1

      I installed it no problems on my PowerBook G4 on 10.3, I had to d/l X11 from Apple's web site, but it was cake after that. There is excelent documentation. Here is a link to the dmg.bz2.
      I use it everyday, although not macros.

    217. Re:What's the downside to using X11? by janeil · · Score: 1
      Hey, now, who's a monkey? (Correct answer: All of us!) But gosh, maybe any UI is no more than a personal preference? Or maybe even what one learned and became used to first? Intense diatribes about menu position preferences are very juvenile, kids.

      Personally, I notice that between linux, mac, and windows, the mac allows the least adjustment of the interface to suit one's preferences. Tho' xp seems headed towards less user control.

      For my part, whenever I install windows, the first thing I do is drag the taskbar to the top of the screen where it belongs. So the first menu choices are programs to be run, for example, as opposed to shutting down the machine. But, I don't have any interest at all in anyone else's preferences, nor should anyone really care about mine.

      For what it's worth, attaching or not attaching a menu to the app's window was always more of a resource saver question, just tracking one menu is simpler. Plus the simple matter of available pixels.

      What I would prefer is the ability to set these menu positions and locations as I choose, without a shareware add-on.

    218. Re:What's the downside to using X11? by bsartist · · Score: 1

      Hey, now, who's a monkey? (Correct answer: All of us!)

      Actually, no... We're apes. Monkeys have tails. :-)

      --
      Lost: Sig, white with black letters. No collar. Reward if found!
    219. Re:What's the downside to using X11? by master0ne · · Score: 1

      yes, but you try telling big buisness that. all phb's think change = bad! and if they can get sompthing free that doesnt change a whole lot thats what they want. because it wasnt broken before, so why fix it. (i know it was / is broken but it worked so they done see it as broken)

      --
      Noone writes jokes in base 13!
  3. Comment removed by account_deleted · · Score: 0, Flamebait

    Comment removed based on user account deletion

  4. So? Use Neooffice by mr100percent · · Score: 5, Informative
    Neooffice is coming along nicely, it's finally in Beta. It's got an Aqua interface, Openoffice core, and doesn't require X11.

    1. Re:So? Use Neooffice by VAXGeek · · Score: 2, Interesting

      I second this, this is the project to watch for OpenOffice on MacOS. Everyone should donate to this project, they are really getting work done.

      --
      this sig limit is too small to put anything good h
    2. Re:So? Use Neooffice by patdabiker · · Score: 2, Interesting

      NeoOffice/J, the current version, is Java based (from the wiki. I'd like to see a version of OpenOffice using native Aqua and Quartz.

    3. Re:So? Use Neooffice by Goalie_Ca · · Score: 3, Interesting

      I haven't tried out neoffice but I must admit MS office for mac is damn impressive. When MS is forced to omit OS-level integration and install only 4 apps, none of that other crud, it works out quite nicely. In fact, the UI hit the sweet spot, it loads fast, it's very nice, and it's not bloated at all. The install is nice and snappy too because all you gotta do is copy a folder and stick the cd key in.

      I still prefer to use latex for writeups but when i need to use office, MS office for Mac is pretty damn good. There is a reason why office for mac consistently gets better reviews than its windows counterpart.

      --

      ----
      Go canucks, habs, and sens!
    4. Re:So? Use Neooffice by BobPaul · · Score: 1

      Well maybe that's why none of the apple developers were working on OO.o Aqua... They're all working on Neoofice!

    5. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      NeoOffice/J is a fork. Nothing else...

      Apple or the Apple community should support developers who are willed to contribute into an alternative on Mac OS/X and who like to spend time and work into developing a native Aqua port.
      There are just few developers who worked on the port to Mac OS/X and there were just a few developers who worked on porting the native widget set to look alike Aqua in NeoOffice/J but they did a failure when defining the port as fork by licensing NeoOffice/J differently than OpenOffice.org.

      Please support Ed and the others by helping them to port OpenOffice.org. Otherwise free software development on Mac OS/X won't be as complete as on Windows or on Linux and the other Unices.

      Apple could help by licensing byte hinting to all applications freely that run on Mac OS/X. Unfortunately this is Apple patented technology that allows Apple to have font rendering that looks different than within X11 when using the freetype library

    6. Re:So? Use Neooffice by despik · · Score: 1

      Object accepted! Temporal displacement IN PROCESS!!

      --
      "I seem to have mastered a certain amount of control over physical reality."
    7. Re:So? Use Neooffice by Doc+Ruby · · Score: 1

      Does it read/render MS-Word and MS-Excel files (>95% of all features)? Does it save NeoOffice docs in MS-Office data formats, so Windows readers won't even notice the NeoOffice origins (for >95% of the features)? Or at least, is that the plan, which looks like it's working?

      --

      --
      make install -not war

    8. Re:So? Use Neooffice by McDutchie · · Score: 1
      NeoOffice/J is a fork. Nothing else...

      So? The whole point of Free software is that it can be forked if the original developers mess up. They have messed up with the Mac port, so now a fork has come forward that provides the functionality instead. How is this bad?

    9. Re:So? Use Neooffice by Doomdark · · Score: 1
      I'd like to see a version of OpenOffice using native Aqua and Quartz.

      Why? Should it really matter what technology is used under the hood, if it works well? I'd think that it wouldn't matter much whether it was written in Lisp, Ruby, assembler or Java, as long as end result is good?

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
    10. Re:So? Use Neooffice by Halo1 · · Score: 1
      Does it read/render MS-Word and MS-Excel files (>95% of all features)? Does it save NeoOffice docs in MS-Office data formats, so Windows readers won't even notice the NeoOffice origins (for >95% of the features)?
      It does all of that just as well (or just as badly) as OpenOffice, since it's plain OpenOffice with a Java GUI on top (instead of an X11 GUI).
      --
      Donate free food here
    11. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      The answer is: developer resources

      The NeoOffice/J guys cannot compete against the development efforts done on the incompatible development CVS branch of the next version. If they do a fork then they allways have to do that development again because all new implementations are done on the development branch. And they cannot commit back because of the different licensing scheme of the OpenOffice.org project

    12. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      Look, the Mac guys doing OpenOffice obviously didn't know what they were doing. As a Mac developer, I see no reason why it couldn't have been done, unless OpenOffice is the biggest mess of spaghetti code since the first high school programming assignment in COBOL was handed in...

    13. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      I cannot accept this argument. Maybe you're right but:

      It would be time for you to contribute to the project by doing a source code review and to post this into the OOo development list. Maybe someone will change that code.

    14. Re:So? Use Neooffice by Anonymous Coward · · Score: 2, Informative

      I'd like to see a version of OpenOffice using native Aqua and Quartz.

      Uh, I think you mean "cocoa"? NeoOffice/J does use actual real-life Aqua (the apple blue-button interface) and runs using Quarts (the apple display compositing system).

      Java is only used to facilitate this. The program is not written in java. It's 99% C/C++.

    15. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      I thought the main issue was that there were no "mac guys doing open office" -- that is, OS X just does not have a large group of volunteer developers for such a project.

    16. Re:So? Use Neooffice by Billly+Gates · · Score: 1

      Well the fork is what caused Openoffice to stop Aqua development

    17. Re:So? Use Neooffice by qw(name) · · Score: 1


      I would have to agree with you on this one. I just received my Office:mac 2004 Professional this past week and have enjoyed the experience quite a bit. The only reason I bought it was because my employer has an MS Home Use Program agreement with MS. I paid $20 for my copy. ;-)

    18. Re:So? Use Neooffice by MattHaffner · · Score: 1

      I felt like Office X was fairly impressive compared to earlier versions. 2004 is a joke, from what I've seen so far. PP 2004 was less compatible with my PP X presentations than Keynote was: symbol font didn't convert (which is used everywhere for me and colleagues in science), text box placements were off, kerning looks bad sometimes... On top of that 11.1 won't install on my machine no matter what I do. I've tried full uninstall of Office X and 2004 and reinstall from scratch. Download from MS or the auto-updater. Did not matter. Finally, Word 2004 still takes up about 10% of the CPU on my 800 MHz machine in the background. With no document loaded. What the heck is a word processor doing in the background without words to chew on? Sheesh...

      I'm all over iWork. Bring it on.

    19. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      I just recently downloaded and installed Neooffice on a Mac for a client who's primarily doing graphics and Web design using Dreamweaver and the Adobe stuff. She does fiddle with the occasional simple spreadsheet, and often has to open a Word or Powerpoint file someone's sent her in an email. Someone else in the same office is successfully using OO on a PC to do the same things, and likes it better than MS Office.

      We'll see how it goes. So far it looks reasonably stable, and it's fast enough for the purpose at hand. At least we haven't yet seen any sign of that Goddamned paper clip.

    20. Re:So? Use Neooffice by Anonymous Coward · · Score: 0

      I'm amazed at people who hold this opinion. I cant imagine how people can like the cluttered and dumbed down, candy interface of MS office for mac. It seems like a piece of software written for primary school children who are just learning to use their first computer. Besides that i am completely mystified as to why people continue to not show any support for promising open source projects such as openOffice and neoOffice. Its so crucial that people step outside their comfort barrier to give these projects are real trial, and if its viable for you to use it all the time then certainly do so. For every mac user that makes the switch over to openOffice and abandons the MS suite it helps to justify further development of the project on our platform, and ultimately help to get the user base to justify more efforts to make a native port of the project for the mac. Even if the suite doesn't do everything you need, use it for every single thing that you can do with it, and then use whatever else for the few things that you possibly cant do with it. Taking these strides to help support the project means a lot, and will ultimately go a long way towards keeping this project alive on the mac.

  5. X11 Aqua? by ghettoboy22 · · Score: 4, Insightful

    FTA as a reason not to do Quartz or Aqua "X11 Will Always Look like Other Platforms: Many people deploying OpenOffice.org count the identical look and feel on all supported platforms as a major benefit. It helps them reduce training and, in many cases, implement a single multi-platform solution using OpenOffice.org as middleware (such as extendedPDF). Any native work that changes the interface would remove this as a critical selling point for OpenOffice.org for these users."

    Umm, I have yet to hear one negative comment regarding Aqua interfaces (done right). This comment appears to be nothing but pure FUD. If anything, an Aqua UI would make an OOo suite EASIER to use on an OS X system.

    But, again, whatever. I can't wait to get ahold of Pages. Apple seems to have finally woken up and realized they need their own (updated) office/productivity suite. OOo is great and all, but if their team seems to have the attitude "one platform, one UI" is better, I'll pass.

    Besides, there's always NeoOffice/J to root for! ;)

  6. At least there's still NeoOffice by dn15 · · Score: 4, Informative

    It's disappointing news, but at least there's still the NeoOffice project. Its was originally intended to be a place for experimenting with the issues involved in a native OS X port, but if the office OOo project won't be doing it hopefully NeoOffice will get more support as the primary (er, only) Aqua version.

    1. Re:At least there's still NeoOffice by dn15 · · Score: 1

      er, make that "the official OOo project"

    2. Re:At least there's still NeoOffice by Rares+Marian · · Score: 1

      They are using the NeoOffice port.

      --
      The message on the other side of this sig is false.
    3. Re:At least there's still NeoOffice by Anonymous Coward · · Score: 0

      I think we all need to show our support for the neoOffice project, and if at all possible to encourage a merger of the project with the main openOffice project to make everything more integrated and make it a more unified effort. I understand the guys working on neoOffice must be doing a lot of work, and may be a bit hesitant about joining the rank, but i think it really would be good to keep all the efforts surrounding the project and its various developments together, as one unified front. Instead of people saying they are using neoOffice, they could be using an openOffice.neo build or something similar, not this distinct separation which is present at the moment, i cant see anything positive in keeping this divide an longer.

  7. Re:My first first post.. by Anonymous Coward · · Score: 0

    neooffice does it very well

  8. Heh by pHatidic · · Score: 4, Informative

    Except for that in the first paragraph of the article it says that a port is being released by NeoOffice. Did anyone even rtfa?

    1. Re:Heh by Anonymous Coward · · Score: 0


      NeoOffice isn't part of the OpenOffice group. It's a fork, meaning it will not always been in line with the "main" OO.

      The more interesting part of this article is that the OO folks stopped development on an Aqua version 2 years ago, and for 2 years have been lying to everyone that it was still going to come out. How many people donated money to the cause hoping it would speed things along only to find out they got screwed?

    2. Re:Heh by advocate_one · · Score: 4, Insightful

      Looks like the NeoOffice guys got off their butts and decided to do it rather than stay put and wait for others to do it for them... Nice one guys... More power to your fingers. The others who were expecting it to be done for them by the OOo team should hang their heads in shame... First rule of Opensource... if you want it, then get on and do it... otherwise you could find yourself waiting forever...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    3. Re:Heh by spac3manspiff · · Score: 1

      No, remember it's slashdot

    4. Re:Heh by pHatidic · · Score: 0, Offtopic

      Yes, but it's also about the third time that Michael has done this in as many days. Now I think he is doing it on purpose out of bitterness after being called a hypocrite in the other thread.

    5. Re:Heh by .com+b4+.storm · · Score: 2, Informative

      Yes, but the disappointing thing here is that the primary OpenOffice developers have officially washed their hands of Aqua support, not that they ever cared much for it anyway. That's where most of the development muscle and money is, in the main OpenOffice project. NeoOffice is only being done by a couple of people, and because it is not really an official project, it is always a step behind. They will constantly have to pick up the pieces every time a new release comes out and breaks something in NeoOffice. It's like how Wine tries to make Windows apps fit into Linux - it'll never be perfect, because it's a moving target.

      Don't get me wrong, NeoOffice is an amazing project and it works extremely well, especially given the limited number of developers behind it. I remember one of the NeoOffice folks posted before that OpenOffice 2.0 was supposed to be a total redesign that would take into consideration the model of Aqua/Cocoa apps, to make porting easier. Apparently that idea was nixed, hence the official plans for support being dropped. Now the NeoOffice people will be stuck with trying to fit the square peg of OO2 into the round hole of Aqua, as they've been trying to do with the 1.x series. What was originally a temporary and experimental project has now become the only hope for decent OpenOffice on the Mac.

      Ah well... No offense to NeoOffice or OpenOffice, but I will be grabbing a copy of iWork soon, so I won't have to worry about it much except when I have one of those (very rare) needs for a spreadsheet. :)

      --
      "Wow, you're like some kind of superhero able to ward off happiness and success at every turn."
      -- Ryan Stiles
    6. Re:Heh by sugar+and+acid · · Score: 1

      Well they are kind of the same thing actually. NeoOffice was supposed to be a testing ground to work out how to port OOo to Aqua. Then they were then going to intergrate those changes back into the OOo.

      They have decided that maybe that isn't a practical way to do it after all, and instead maintaining a separate fork "NeoOffice" is a better way.

      The big problem eventually with this is that NeoOffice is forked off the OOo 1.x code base, and so will lack new features coming out for newer versions of OOo. How hard these features will be to backport, or alternatively how hard it is to fork off OOo again and do another port to aqua? I don't know but it isn't trivial.

  9. What is X11 vs. native vs. NeoOffice.org??? by solafide · · Score: 1
    Forgive my ignorance, but what is special about native? What is Aqua and Quartz? Why is x11 bad?

    Thank you. Billy

    1. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 0, Flamebait

      native is special because it runs faster and blends in with other native apps

      aqua and quartz are bad because they are made by apple

      x11 is good because it is produced by the good folks over at X.org

    2. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 0

      no dude, the idea is to troll the slashdroids :>

    3. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 1, Funny

      dude your homepage is scary

    4. Re:What is X11 vs. native vs. NeoOffice.org??? by crazney · · Score: 2, Interesting

      Also, he claims

      Large animals, such as sheep and cattle, are used to convert captured solar energy into a form that humans can use ... huh?

      That's what plants are for buddy.. Large animals then convert the hard earned energy of the plants into useless gasses, heat, sound and a tiny bit of food.

      If you want sustainability, get rid of the big animals. In fact get rid of the chickens, too.

      --
      stuff
    5. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 0

      Are they bad just because they are made by Apple? Or bad because they are proprietary. Honestly this whole thing is dumb. OOo runs native on win32, on X11 for *nix and should run native under OS X if it weren't for developers not feeling like doing it.

    6. Re:What is X11 vs. native vs. NeoOffice.org??? by rekenner · · Score: 0

      To briefly summarize... X11 allows certain Linux programs to be run on OSX. It has to be run and then programs are run in it. It feels alien compared to all the rest of OSX and has other problems with integrating into OSX. A version of OOo in Aqua/Quartz would be more integrated into OSX and look better.

    7. Re:What is X11 vs. native vs. NeoOffice.org??? by HeelToe · · Score: 4, Informative

      See some of the earlier posts, but in general:

      It's a hassle to use X11 under Mac because you must start up X11 and then OOo. Additionally, the menus do not behave as other Mac menus do, and the integration to the rest of the desktop isn't perfect.

      Aqua is the name for the most current display widgets for Mac OS X. Quartz is the video display technology they're built upon. A native Aqua/Quartz application uses the Mac OS X desktop natively, without going through an X11 server that sits as an intermediate.

    8. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 0

      This would be true, other than many of these large animals feed on plants that would not be suitable for human consumption. (And for that matter, are in areas that are not very suitable for farming plants humans would like).

    9. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 0

      >> Large animals, such as sheep and cattle, are used to convert captured solar energy into a form that humans can use
      > ... huh?

      I.E., the grass uses solar energy (via photosynthesis) to get usable food for itself, the animals eat the grass to get energy for themselves, and people eat the animals, just like God intended.

    10. Re:What is X11 vs. native vs. NeoOffice.org??? by curne · · Score: 2, Informative

      Everything parent says is absolutely correct, just apart from one little thing. MacOS X automatically starts X11 when you run an X application. The launcher does this by looking at the libraries that the app links to.

      I use several X11 app under OSX and it functions great. However, native Aqua apps are generally easier on the eye.

      --
      All interpreted languages are abstractions over Lisp
    11. Re:What is X11 vs. native vs. NeoOffice.org??? by HeelToe · · Score: 1

      Thanks for the correction - I did not know this.

    12. Re:What is X11 vs. native vs. NeoOffice.org??? by Anonymous Coward · · Score: 0

      bad because they are made by apple AND bad because they are proprietary. both are BAD things.

  10. WiApple now getting into the office suite arena... by Anonymous Coward · · Score: 2, Interesting

    With Apple now getting into the office suite arena, I'm far more inclined to buy it then get the free Open Office anyways.

    Yes, I'm willing to pay for superior alternatives.

  11. Qt version by rxmd · · Score: 4, Interesting

    It's possible to compile OpenOffice using Qt for the interface (e.g. in OpenOffice/KDE). Since Qt is available with an Aqua frontend, why not use that?

    It wouldn't provide overly tight integration with the MacOS X user interface, but it would be way better than today's X11-based OpenOffice.

    --
    As a state gets corrupt, its laws multiply; the most corrupt states have the most numerous laws. (Tacitus, Annales 3:27)
  12. Neo Officej by Cow007 · · Score: 1

    I like Neo Office just fine. All the grit and power of x11 with the nice aqua wrapper and menus.

    --
    411 Y0UR 8453 4R3 8310NG 70 U5!! -NSA
  13. Major setback? by saskboy · · Score: 1

    I'm not too familiar with the office products for a Mac, but doesn't Microsoft offer an Office product for it?

    If open source hopes to compete with Microsoft, they are going to just have to offer support for THE open office standard.

    --
    Saskboy's blog is good. 9 out of 10 dentists agree.
    1. Re:Major setback? by NemosomeN · · Score: 1

      Yes, because Mac users are Microsoft's biggest customer base. Face it, most Mac users are fervently anti-MS.

      --
      I hate grammar Nazi's.
    2. Re:Major setback? by Anonymous Coward · · Score: 0

      Hahaha..
      Really, here we got an advertising campaign from Apple who only shows an apple computer, and was written "use Word, Excel, Powerpoint".
      Really, looks at this thread: people are going to (or pretend to) pay for MSO just for the sake of not running AppleX11..

  14. iWork Killed It by the+pickle · · Score: 1, Insightful

    Honestly, how many Mac users would bother with the perpetually vapourware Aqua OOo when they could get iWork? Free software (both senses) is great, but there are some times when it's worth it to pay. Once iWork adds a spreadsheet component, there won't be much reason to think about using OpenOffice stuff on a Mac.

    p

    1. Re:iWork Killed It by peragrin · · Score: 1

      I am one. Pages won't access the hundreds of files I have stored in OO.o file format.

      Yep Apple could even bother to implenet import and export for an Open Document spec.

      --
      i thought once I was found, but it was only a dream.
    2. Re:iWork Killed It by scottking · · Score: 1

      You really think that Apple will make a Spreadsheet app for iWork?

      Seems unlikely to me. If there is one place Microsoft truly dominates it's in that market. Excel is a pretty decent tool, and I can't see a lot of users switching out of it considering how much time and effort most companies have put in learning it and building with it.

      But hey, I could be wrong... The "Distortion Field" is powerful. I was at Macworld, and I had to muster all my will to not run out of the Expo and buy an iPod shuffle I really have no use for.

      --
      scott king
    3. Re:iWork Killed It by ThousandStars · · Score: 1
      No, iWork didn't kill a native OOo Mac port. Primarily technical considerations killed it, as I mention in my post here. When I first looked at OOo last summer when I got my PowerBook and didn't know anything about Aqua I was quite idealistic and foolish in thinking that porting OOo can't *really* be that hard. But then I hadn't looked at the codebase, which is still enough to give me nightmares. Furthermore, most of the contributors, or at least those on the mailing list, don't give a damn about iWork. Some just moved to NeoOffice/J. Others were frustrated there was a schism at all.

      I think plenty of Mac users would "bother" with OOo if it was native, both for political and cost reasons. iWork has nothing to do with the cancellation, and if you think it does, remember that work does continue on NeoOffice/J.

    4. Re:iWork Killed It by Yaztromo · · Score: 1
      Yep Apple could even bother to implenet import and export for an Open Document spec.

      I'm going to assume you intended to type couldn't up above.

      A few issues with this. First off, OASIS isn't finalized yet, so you can hardly blame Apple for not supporting OASIS.

      Secondly, while Pages isn't available yet (I have my copy already pre-ordered), as it is partly based off the Keynote codebase, and Keynote uses XML for its data storage format, and as OASIS is likewise an XML format, and as Apple publishes the XSLT for its file formats, it shouldn't be difficult for anyone who really needs to to write an XSLT transformation between Pages native format and OASIS.

      As such, document interoperability shouldn't be a big problem. Apple's formats have tended as of late to be fairly open (with the notable exception of FairPlay), so Open Source developers should be able to quickly develop the necesary tools for these suites to interoperate.

      And who knows? Perhaps by the time OASIS is out of draft form and is an official specification there will be enough people out there using it that Apple would be happy to support it natively within iWork 06.

      Yaz.

    5. Re:iWork Killed It by 0racle · · Score: 1

      Unless the OO.org dev team are clairvoyant iWork did not kill a native Aqua OO.org. iWork was announced last week, and there was speculation for a few weeks before that, but the blurb says that there was no work being done on the Aqua port for over a year. It also remains to be seen if iWork is any good.

      --
      "I use a Mac because I'm just better than you are."
    6. Re:iWork Killed It by bcrowell · · Score: 1
      Yeah, I'm just baffled why anyone would care about having an Aqua-native OOo. My experience with OOo has been that it's just not a very good word-processor. Slow, bloated, and problematic in the open-source world because of Java's screwy licensing.

      • If my work requires me to exchange complex MS Word documents with other Word users, then I'm going to need Word, and my employer will presumably pay for it.
      • If I just want to be able to open the occasional simple .doc file that someone sends me as an email attachment, I can install X11 and the X11 version of OOo.
      • If I want a native word-processor that doesn't suck and that can read most Word files, I can buy iWork.
      • If I'm such a great believer in free information that I really feel I must run nothing but open-source software, I'm presumably not using MacOS X in the first place.
    7. Re:iWork Killed It by BasilBrush · · Score: 1
      You really think that Apple will make a Spreadsheet app for iWork?

      Absolutely. If they release a presentation package one year, then a word-processor the next, it's almost certain the following year is a speadsheet.

      Seems unlikely to me. If there is one place Microsoft truly dominates it's in that market. Excel is a pretty decent tool, and I can't see a lot of users switching out of it considering how much time and effort most companies have put in learning it and building with it.

      All of which you could also have said about PowerPoint and Word.

    8. Re:iWork Killed It by gl4ss · · Score: 1

      yeah.. iWork killed it two years before it came to life!

      neo killed it, to be serious.

      --
      world was created 5 seconds before this post as it is.
    9. Re:iWork Killed It by Rauser · · Score: 1
      If I just want to be able to open the occasional simple .doc file that someone sends me as an email attachment, I can install X11 and the X11 version of OOo.

      Not to nitpick, but the copy of TextEdit that is already on your OS X machine can open .doc files already. Thus, another reason Apple has reduced the need of OOo.

      --
      The white zone is for loading and unloading only. If you need to load or unload go to the white zone. It's a way of life
  15. Yes! by Anonymous Coward · · Score: 1, Interesting

    One more point to bring up when people ask my why on earth I'm running linux on my ibook. :-D

    Seriously, that's bad. I knew that there weren't many people involved in porting it and I expected it to take longer than planed, but I never imagined it would simply be canceled.
    Does somebody know what those political and licensing issues were in particultar?

    1. Re:Yes! by goMac2500 · · Score: 1

      I don't get your point. OpenOffice will run the exact same way it does under OS X as it does under Linux. The point of the article is that a version of OpenOffice that would act like an OS X application rather than a Linux application was canceled. Instead, the OpenOffice teams wants to keep all the platforms acting the same.

  16. Maybe cause of good work on Neooffice/J ? by markk · · Score: 2, Insightful

    The story isn't very informative, but since the Neooffice people seem to have a good port underway for OS/X, there isn't a lot of reason to go after pure aqua anyway. If this brings more resources to the Neooffice folks, then I don't see this as a bad thing at all.

    Just a happy Neo Office user who loaded in a bunch of Excel sheets annd got a lot of work done.

  17. And there was much... yawning by UTRules · · Score: 4, Informative

    Other than being free, I don't see what OpenOffice has to offer on the OS X platform. KeyNote works great, version 2.0 looks even better, and for those who care (and I'm one of them), the file format is xml-based and completely transparent. The OS X paradigm of encapsulating applications and documents in a directory instead of some gigantic kludgy single file means you can go into a .key file and see all the images and movies you've added to the presentation, as well as a single "presentation.apxl" file that contains the presentation itself in a completely obvious xml format.

    The new word processing program for the Mac announced at this year's MacWorld, called Pages, was written by the same team that wrote KeyNote and presumably uses the same open file formats.

    And these programs together are $79; even less if you can get the .edu discount.

    There's no Apple spreadsheet program (yet)...

    1. Re:And there was much... yawning by Chordonblue · · Score: 1

      Not here. This is important (although less so because of NeoOffice).

      My school switched over to using Star/OpenOffice three years ago. With more and more Macs (and with the Mac mini - even more so), appearing in dorm rooms, this is critical for us.

      --
      "...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
    2. Re:And there was much... yawning by Yaztromo · · Score: 3, Insightful
      Other than being free, I don't see what OpenOffice has to offer on the OS X platform.

      I know of one potentially big one, and that is platform independance.

      This may not be big on your list of needs if you're just running OS X at home, but in an enterprise setting where they've standardized on one office suite, but permit different OS's for different purposes, having one suite that can be run on all of them is important.

      Or what if you suddenly need to change OS or hardware platforms? It's generally nice to be able to be able to use the same applications, even on a different environment. I know this is why I have Firefox installed on all of my systems, be they Linux, Mac OS X, OS/2, or Windows.

      OOo could be a big deal on OS X if it were available in a pure Aqua version (NeoOffice/J notwithstanding). But it isn't, and now it looks like it won't be anytime in the near future.

      Yaz.

    3. Re:And there was much... yawning by UTRules · · Score: 1

      I do see what you're saying, but consider this: if all you want to do is be able to take your OOo documents from Linux to OS X and back, you can do this already with the X11 version. The only reasons for having an Aqua version is (1) easier to use for people used to OS X interfaces, and (2) better integration with other OS X applications. (1) isn't an issue if you already know OOo, which presumably you do. And if (2) is important to you, well, sorry, but you have to make a choice between being integrated with a particular OS environment and getting platform independence. It ought to be easy to convert a Pages or a KeyNote document to OOo format, which was one of the (implicit) points of my post.

    4. Re:And there was much... yawning by Guy+Harris · · Score: 1
      The only reasons for having an Aqua version is (1) easier to use for people used to OS X interfaces, and (2) better integration with other OS X applications. (1) isn't an issue if you already know OOo, which presumably you do.

      (1) might still be an issue if you already know a particular non-Aqua application. I know Ethereal rather well (:-)), but it's still a bit of a pain to have the menu bar in the wrong place - I sometimes catch myself moving to the top of the screen to, for example, start a capture.

      And if (2) is important to you, well, sorry, but you have to make a choice between being integrated with a particular OS environment and getting platform independence.

      Well, maybe. Sometimes Thunderbird manages, for example, to recognize non-standard URL schemas that are registered by applications, even though it runs on multiple platforms - or did you mean something by "platform independence" than "runs on multiple platforms with the GUI-independent code common"?

      I wish Thunderbird would also let selected text be processed by applications that have registered as services, and a lot would like it to integrate with Address Book; I think those are both at least being considered.

    5. Re:And there was much... yawning by magefile · · Score: 1

      Other than being free, I don't see what OpenOffice has to offer on the OS X platform.

      Is there any (major) word processor, for any platform that does word completion other than OOo? If it doesn't have that, I won't willingly use it, and that was the case even before I started experiencing joint problems.

    6. Re:And there was much... yawning by dustmite · · Score: 1

      The OS X paradigm of encapsulating applications and documents in a directory instead of some gigantic kludgy single file means you can go into a .key file and see all the images and movies you've added to the presentation, as well as a single "presentation.apxl" file that contains the presentation itself in a completely obvious xml format.

      You just roughly described the OpenOffice file format. An OO file is just a gzip containing an organized directory hierarchy that uses "completely obvious" XML files for the data and saves images separately and obviously under e.g. "Pictures" .. and with virtually any half-decent file manager (Windows Explorer is the worst file manager ever created so it doesn't count) you can simply browse right into a gzip file. This is one of the things I really like about the OpenOffice file format - a single, optimally compressed data file but still highly transparent and open. There is nothing kludgy about it, it's about as un-kludgy a file format as you can get on Windows and *nix platforms.

    7. Re:And there was much... yawning by bahamat · · Score: 1
      There's no Apple spreadsheet program (yet)...


      But can you guess which new app Jobs will announce at the WWDC '06? It's only a matter of time.
    8. Re:And there was much... yawning by Anonymous Coward · · Score: 0

      Well yes of course its free, and that is very important to a lot of people. Besides that it provides you with a choice, too many of the mac faithful are all to happy to sit down and be stupefied by the short comings of apple software that's nothing more than kiosk software!

    9. Re:And there was much... yawning by Anonymous Coward · · Score: 0

      I entirely agree with this, i myself use OS X and Windows at home, while at uni i also use Linux, so for me it is very important to be able to use the same office suite across all of these platforms for writing my assignments and anything else that i must do. I also entirely agree about there being a huge potential for openOffice on OS X, i think there are a lot of people like myself who are very unhappy about the current office applications available and would benefit very much a native OS X port of openOffice. The amount of new users that could be gained from a native OS X port of openOffice is horrendous, and the openOffice project maintainers would be silly to ignore such an opportunity as it presents itself now. If ignored such an opportunity may not arise again, and that would be a tragedy itself.

  18. AbiWord's new port by Anonymous Coward · · Score: 5, Interesting

    This makes AbiWord's introduction of a Cocoa port even more newsworthy, in my opinion. Yes, I know it's not as robust an offering (I'm not sure how it could be with drastically different methods of development), but being able to read documents across the three major platforms in the same native format is a huge plus for me. YMMV, though.

    1. Re:AbiWord's new port by TheRaven64 · · Score: 2, Insightful
      I tried AbiWord's OS X build a while back when it was still advertised as being beta in big letters and found a few things wrong with the UI. A very few things - things which would probably take a day or two of coding to fix in total. I haven't tried later versions (since I really don't use word processors for anything and hence have no real use for it), but I was very impressed by it. It looked and acted like an OS X app in a way that OpenOffice never did (even in the NeoOffice incarnation).

      AbiWord was developed with proper MCV abstraction, and has Windows, GTK, Photon (QNX), BeOS (no longer supported) and Aqua (OS X) user interfaces. Because it was sensibly designed, it can easily be ported to other GUI front-ends (I believe the Cocoa port was done by a single person). OpenOffice is a huge heap of crusty code, which needs a huge amount of re-factoring. Version 2 was supposed to provide this, making it easy to add new GUI layers, but this seems not to have happened.

      --
      I am TheRaven on Soylent News
    2. Re:AbiWord's new port by Anonymous Coward · · Score: 0

      >> I tried AbiWord's OS X build a while back when it was still advertised as being beta in big letters and found a few things wrong with the UI. A very few things - things which would probably take a day or two of coding to fix in total. I haven't tried later versions

      fjf has been working to fix things to make them more Mac user friendly. he seemed to appreciate all the feedback slashdot readers provided so I'd encourage you to try Abiword again and help suggest any more little details that might need tweaking.

    3. Re:AbiWord's new port by Anonymous Coward · · Score: 1, Informative

      Current Abiword on OS X 10.3 is excellent.

      Recommended
      http://prdownloads.sourceforge.net/ abiword/AbiWord -2.2.2.dmg?download

    4. Re:AbiWord's new port by fourfoot · · Score: 1

      Agreed. If you're looking for a decent open source word processing app for OS X, then AbiWord is really the only option. It completely blows OOo and even NeoOffice/J out of the water. Now, what I would really like to see is a nice aqua port a spreadsheet app like gnumeric. For me, nothing else would be necessary to entirely replace a full-blown office suite like OOo or MS office.

  19. WTF?! by Richard_at_work · · Score: 4, Informative

    Ant writes "According to MacSlash's story, a recent post on OpenOffice.org said no MacOS X work has been done since 2003 and that there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :("

    It says nothing of the kind. From the link:

    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.

    and

    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.

    What it looks like is that they have recognised that NEOoffice is a valid port, and any Aqua port by themselves would be a duplication of effort. The Slashdot story blurb makes it sound like they just gave up because it was too hard. They call this journalism now?

    1. Re:WTF?! by This+is+outrageous! · · Score: 1
      It says nothing of the kind.

      Actually yes, it does. Basically they have made clear that there are no plans to Aquafy 2.0. See:

      there won't be much Aqua work (if any) going into the main OOo code line because the main OOo code is so far out of sync with NeoOffice/J.

      What it looks like is that they have recognised that NEOoffice is a valid port

      Yes, but that forked from OOo 1.x.

      --
      This is...

      O
      U
      T
      R
      A
      G
      E
      O
      U
      S

      !

    2. Re:WTF?! by Anonymous Coward · · Score: 0
    3. Re:WTF?! by TSage · · Score: 1

      >>The Slashdot story blurb makes it sound like they just gave up because it was too hard. They call this journalism now?

      Sorry, this is Slashdot, definitely not journalism. This is where editors call "FUD" on other sites for drumming up press for other companies, all while delivering fresh FUD daily. I'm sure most of it is harmless and unintentional, but at least some of it is for their own ends, either by creating support for their overriding company (OSTG) or just creating a stir to generate page viewings.

      I wish this would change, but the way the editors react to such criticism, I wouldn't hold my breath.

      TSage

  20. Setback in Establishing PowerPC as Workstation by reporter · · Score: 1
    The continued development of OpenOffice on Macintosh would have helped to establish Macintosh as the premier engineering workstation. Macintosh already has 2 of the 3 key ingredients: awesome processor (PowerPC) and a variant of UNIX. The Mac still needs ECC memory.

    OpenOffice is one of those "business" applications that engineers need. Spreadsheets are used to draw graphs predicting the ascent of your own products and the demise of your competitor. Wordprocessors are needed to write engineering reports.

    IBM has exited the PowerPC workstation market. Apple could be the de factor manufacturer of PowerPC workstations. A tieup between IBM and Apple would be a formidable force.

    The workstation market is large enough for 2 major competing processors: AMD64 (and the Intel clone!) and PowerPC. (UltraSPARC is already dead.) Having two competitors is better than having monopoly (i.e. just AMD64), for competition spurs development and price reductions. The ultimate winner is the consumer.

    1. Re:Setback in Establishing PowerPC as Workstation by Anonymous Coward · · Score: 0

      Um, Microsoft Office? Also, the XServe has ECC memory. So apparently the Mac has everything it needs to be the premier engineering workstation... (personally I think it has a ways to go before it can claim that spot)

    2. Re:Setback in Establishing PowerPC as Workstation by Anonymous Coward · · Score: 0

      You seem to be unaware that the XServe is not a workstation.

    3. Re:Setback in Establishing PowerPC as Workstation by aristotle-dude · · Score: 1
      ECC memory? Do most PC's used as workstations in businesses have ECC memory? No, of course not. Most business takes place at sea level anyway where ECC memory is largely irrelevant given that the atmosphere has filtered out most of the cosmic radiation at that altitude.

      ECC memory is only a requirement for server clusters, not workstations. Stop spreading FUD.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    4. Re:Setback in Establishing PowerPC as Workstation by JeffTL · · Score: 1

      Well, if you're shopping for a workstation you can probably afford MS Office, or if you don't need a spreadsheet, iWork.

    5. Re:Setback in Establishing PowerPC as Workstation by SteeldrivingJon · · Score: 1

      "OpenOffice is one of those "business" applications that engineers need."

      Er, no. OpenOffice is a member of a class of business applications that engineers need. There's nothing special about OpenOffice that makes engineers "need" it, specifically. It is easily replaced with another office product, or separate applications that do the same thing.

      "IBM has exited the PowerPC workstation market. "

      Er, no they haven't. They exited the Intel PC market.

      They're still going to make POWER RISC-based workstations. It's kind of a natural, since they're going to be making POWER RISC computers in other segments, and making chips for Apple.

      --
      September 2011: Looking for Cocoa/iOS work in Boston area Cocoa Programmer Quincy, MA
    6. Re:Setback in Establishing PowerPC as Workstation by rco3 · · Score: 2, Insightful

      Engineers need spreadsheets to draw graphs? Custodial engineers, maybe. REAL engineers use things like MATLAB, MathCAD, etc. to draw graphs. If Excel lets you graph on log-log and semi-log scales, I haven't been able to find it - and, for that reason, I haven't tried to find it in a while. Got better things to do with my time than twist a spreadsheet into being an engineering application. REAL engineers don't predict the demise of any competitors, that's what marketing pricks do.

      Besides which, NOTHING about OpenOffice or MS Orifice requires ECC or a workstation.

      When it comes to engineering documents, a combination of LyX, XCircuit or XFig, and MATLAB beats the shit out of Excel and Word any day of the week. I think I'd quit my job before I tried to write a real, equation-heavy engineering document in Word. LyX just has a better EQ editor hands down. And there's a native OSX version of LyX.

      What's needed to establish Macintosh as "the premiere engineering workstation" platform is ENGINEERING APPLICATIONS. PSpice, MathCAD, a decent version of MATLAB, various FEA packages, etc. Vendor support in the form of OSX-native tools (Altera, Microchip, are you listening?). Obviously I'm EE-biased here (being an EE), but I'm sure that the ME, ChE, and CE guys can provide a similar wishlist. How about an OSX version of Autocad? THAT would sell some Dual G5 boxen.

      Processor architecture is really irrelevant here. It's the OS that matters. Autodesk, say, can easily recompile a Unix version of Autocad to run on SPARC, AMD64, Xeon, P4, MIPS, or PowerPC once they develop the Unix version . Now, it may not be completely straightforward to turn that into a native Aqua version, but it's gotta be easier than converting the Windows version to Aqua.

      --

      Ce n'est pas un vrai mouvement de robot!
    7. Re:Setback in Establishing PowerPC as Workstation by Anonymous Coward · · Score: 0

      I think if you click on "Workstations" at Dell.com or IBM.com, you'll find that vast majority of models have ECC.

      [Fact is the lack of ECC caused that vaulted VA Tech cluster to be dismantled and replaced.]

    8. Re:Setback in Establishing PowerPC as Workstation by Anonymous Coward · · Score: 0

      One of the reasons that I decided to completely stop using M$ "office" and learn OO in more detail was because of OO's equation editor which allows everything to be typed in, no need BS point click point click *BANG!!*

      after couple of days of heavily writing equations you just write formula from top of your head
      another caveat is you start thinking recursively in terms of placing lots of brackets and not getting confused in them.
      ~omi

    9. Re:Setback in Establishing PowerPC as Workstation by goMac2500 · · Score: 1

      Development of OpenOffice on Mac hasn't stopped. Rather they're opting to not use the native Aqua window server and use the X11 server instead.

    10. Re:Setback in Establishing PowerPC as Workstation by JadeNB · · Score: 1
      When it comes to engineering documents, a combination of LyX, XCircuit or XFig, and MATLAB beats the shit out of Excel and Word any day of the week. I think I'd quit my job before I tried to write a real, equation-heavy engineering document in Word. LyX just has a better EQ editor hands down. And there's a native OSX version of LyX.
      How about LaTeX? Why have a GUI frontend to insulate you from what you're really doing? Much better to dive right in and have all the power and flexibility right at your fingertips. Another advantage of this approach is that you don't need anything but a text editor (and, eventually, a LaTeX compiler) -- than which you can't get more portable.

      P.S. `It's hard to learn' is no justification at all. Sit down with a handwritten version of a document you want to produce, or a document somebody else produced, and a LaTeX reference book. You'll be TeXing within the hour.

    11. Re:Setback in Establishing PowerPC as Workstation by rco3 · · Score: 1

      I can do raw LaTeX, have done so. However, I find that most of what I need to do is easier in LyX. If I need to do raw LaTeX, I simply open an ERT (Evil Red Text) box with CTRL-I and put in whatever I want. Subfigures, e.g., are more easily formatted with ERT than using the built-in routines. However, inserting a citation is as easy as hitting Alt-I,C and selecting it from a list. I don't have to remember the tag I gave that citation, which I really appreciate when I'm writing a 187-page thesis and citing different 6 papers from the same guys (Was it Wang1999c or Wang1999d?). And, since LyX will happily output pure TeX, it's as portable as you want it.

      There are times when using a GUI is faster and easier, and my experience has been that LyX is one of them. You may operate better command-line only - that's cool. I suspect that if you spent an hour with LyX, you find yourself wondering why you ever thought it was more efficient to run LaTeX three times and then run a DVI viewer, all from the command line, than it is to simply press CTRL-D once. Another advantage that I find is that you can see the formatting in LyX as you type it - not WYSIWYG, no, byt WYSIWYMeant - which is insanely useful for things like equations, tables, etc. I don't have to worry about whether I got a typo in \uespackage{babel_touched_my_junk_liberally} or not. Oops - I did. Now I have to find it and recompile. Damn.

      The reason to have a GUI to insulate me from what I'm really doing is that the GUI accelerates what I'm doing. I don't have to know assembler to program in C, and I don't have to know the current equation for a MOSFET in saturation in order to use a 7404 hex inverter. More to the point, I don't have to find the W/L ratios of the P and N transistors in order to figure out the number of gates I can drive with it - even though that's what I'm really doing.

      For that matter, why learn LaTeX when I've already got a perfectly good typewriter? Oh, yeah - because it's easier and more flexible, making me more productive. And LyX is easier still, but just as flexible. That makes it more powerful for me. YMMV.

      --

      Ce n'est pas un vrai mouvement de robot!
  21. Re:X11 Aqua? by steve_l · · Score: 1


    remember, OOo is very much sun backed, the company who believe that a native java UI (Swing) is better than tight integration with the base OS.

    Its interesting that the windows version doesnt have a native X11 version (obviously) and the standalone download does look different from star office. So consistency in look and feel isnt that high.

  22. Wow, what sensationalism by daveschroeder · · Score: 4, Insightful

    First of all, this is NOT related to Apple announcing iWork. At all. No, there's no conspiracy.

    Second, this is OLD news. Anyone who's even remotely followed OpenOffice.org Mac OS X porting work knew any potential Aqua port was on the back burner. Way on the back burner. With the stove unplugged.

    Third, the X11 port will ALWAYS continue to exist.

    Fourth, there is a Mac OS X graphical port, albeit via Java, in the form of NeoOffice (1, 2). This project has come a LONG way since its relatively recent inception, and is an impressive work melding OpenOffice with the Mac OS X look and feel. There's more work to be done, but the latest 1.1 development release is impressive.

    Fifth, there are gargantuan technical hurdles to maintaining a full Aqua port of OpenOffice without greater engineering support (perhaps from the likes of Sun, who has shown zero interest in maintaining OpenOffice for Mac OS X, much less maintaining a commercial StarOffice for Mac OS X). These are all detailed here, incidentally by one of NeoOffice's chief representatives.

    So calm down. This isn't an Apple conspiracy, or the end of OpenOffice for Mac OS X. OpenOffice will continue, in X11 form AND in the likes of things such as NeoOffice. If anyone is to blame for the official OpenOffice.org Aqua port going by the wayside, frankly, it's a lot closer to Sun than anyone else.

    1. Re:Wow, what sensationalism by NutscrapeSucks · · Score: 0

      Are you an official Apple rep? You speak like it and perhaps you should identify yourself when astroturing.

      Also, please reply directly to people's posts rather than blatently attempting to karmawhore a root level early post to the top of the page.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    2. Re:Wow, what sensationalism by Anonymous Coward · · Score: 0

      Thanks mom for looking out for us...

    3. Re:Wow, what sensationalism by crazney · · Score: 1

      a) He was addressing lots of posts.. That'd be more karmawhoring.

      b) check his website, he's an academic.

      --
      stuff
    4. Re:Wow, what sensationalism by bhima · · Score: 1
      I don't see how you can say that this is not related to the announcement of new software from Apple. I'm sure the NeoOffice guys are clever (both of them) but they don't have enough manpower to make this happen. I have NeoOffice, put simply I don't like it (as much as I like OO.org on Wintel) I will not buy Microsoft products so the instant Pages is out I will buy it and i will use it.

      Sure I'm a technical user but I can't believe I'm alone in my feelings or with my purchase decisions.

      As far as the X11 port I honestly don't think it's relevant, I've tried out a couple of X11 reliant applications on my Mac and they fall into two categories 1, I'm glad it's available for free because I have not found an alternative and 2: I will not allow it on my system even if for some reason I was paid to do so.

      Currently I'm developing a small PC board using EAGLE (with in their free license) and I haven't quite decided where it falls but I'm glad I did not pay for it because the UI is really, really poor.

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    5. Re:Wow, what sensationalism by daveschroeder · · Score: 1

      I don't see how you can say that this is not related to the announcement of new software from Apple.

      The Aqua port has been dead for over a year and a half.

      How is this related to an Apple announcement last week?

      Regardless of your feelings about Pages, the same can be said about any open source competitor to any commercial product.

      If there were 100 reasons why the Aqua port of OpenOffice isn't going forward, about 98 other reasons would be ahead of "Apple releasing iWork".

    6. Re:Wow, what sensationalism by Anonymous Coward · · Score: 0

      I don't see how you can say that this is not related to the announcement of new software from Apple.

      I don't know... maybe because the OOo folks said that the haven't had anyone working the Aqua port since ummm... 2003...? Those folks back in 2003 must has seen the future.

      Pages may be on more nail in the coffin but the corpse has been dead and rotting for a while.

    7. Re:Wow, what sensationalism by ThousandStars · · Score: 1
      Are you an official Apple rep? You speak like it and perhaps you should identify yourself when astroturing.

      Nice combo troll/ad hominem attack. If you bother following the web link in the OP's profile, you'll see that it identifies him and his work. It's hardly astroturfing to point out what's already known. I also wrote a post de-bunking one of the iWork posts, because the cancellation of this particular aspect of OOo on the Mac has nothing to do with iWorks.

      Also, please reply directly to people's posts rather than blatently attempting to karmawhore a root level early post to the top of the page.

      Sometimes it's more efficient to reply to a recurring and incorrect theme in a number of posts than to reply to each post individually. How the OP is being a "karmawhore" is unclear, since he'd actually gain less karma by posting a single rebuttal than by posting ten different rebuttals in various threads? He posted a legitimate comment and you should respect it as such. The better question is how you got the +1 Insightful that drew my attention, particularly given your posting history.

    8. Re:Wow, what sensationalism by NutscrapeSucks · · Score: 1

      > Nice combo troll/ad hominem attack.

      Check daveschroeder's post history. You'll find an enormous number of root-level karmawhore posts which consist of 5 numbered points about why Apple Never Does Anything Wrong. The guy's MO is appleturfing instead of participating, and therefore he get's trolled/adhomed.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    9. Re:Wow, what sensationalism by This+is+outrageous! · · Score: 1
      So calm down. This isn't an Apple conspiracy

      Who on earth said that? You're not replying to anyone.

      If anyone is to blame for the official OpenOffice.org Aqua port going by the wayside, frankly, it's a lot closer to Sun than anyone else.

      Huh? Sun should be blamed for not porting OOo to the Mac?!?

      --
      This is...

      O
      U
      T
      R
      A
      G
      E
      O
      U
      S

      !

    10. Re:Wow, what sensationalism by daveschroeder · · Score: 1

      Who on earth said that? You're not replying to anyone.

      Numerous people said it in response to this story. Therefore, I'm not replying to anyone in particular. For many examples, view the main story with all comments, and search for "iWork".

      Huh? Sun should be blamed for not porting OOo to the Mac?!?

      Um, yes. In fact, PRECISELY Sun. Sun has provided massive engineering support and manhours to versions of OpenOffice for Solaris, Linux, and particularly Windows. They also offer full, commercial, supported versions of StarOffice for those platforms.

      They do nothing even close for Mac OS X. The Mac OpenOffice.org porting folks don't have a fraction of the resources the Solaris/Linux/Windows people do.

      And before you say "Well DUH, it's because there's no version of StarOffice for Mac OS X!!!!" I'd urge you to think a little bit harder about that statement. (I.e., why is there no version of StarOffice for Mac OS X, and the associated engineering and programming support for the associated OpenOffice.org project? Academic and institutional customers have been demanding it for more than three years.)

  23. no big loss by dankelley · · Score: 4, Interesting
    Even if there were an OO port to the standard OSX gui, would it matter?

    The x11 port works as well as it does on other platforms, i.e. it's great unless you want ms-office compatibilityl. The OSX port would add eye candy and a more conventional OSX "feel." I suppose it would also support fonts (which mac users have in massive numbers). But would these things be enough to make users switch? I think not.

    Folks who want full ms-office compatibility will use ms-office or, perhaps, the upcoming iWork. nd folks who can live with something that is not ms-office compatible (and I stipulate that OO is not) will probably be just as happy to use the existing x11 interface.

    Me? For committee work (which demands ms-office compatibility), I'll use ms-office. For presentations I'll use keynote, unless I'm sharing it and therefore using PowerPoint. For my research writing I'll use latex. For my friends I'll use a fountain pen. Hm... OO doesn't fit in anywhere :-(

    1. Re:no big loss by Anonymous Coward · · Score: 0

      Great comment - you tell people should just 'use as is' and then say you have no use for OO at all!

      This is exactly the point, if OO had Aqua support and intergration with OSX then maybe you would consider it a real alternative.

      Pretty useless comment.

    2. Re:no big loss by jonabbey · · Score: 1

      On what basis do you claim that OO is not compatible with MS-Office?

    3. Re:no big loss by dankelley · · Score: 1
      My basis is that word, excel, and powerpoint documents have not transferred correctly to OO, and vice versa.

      I lost quite a lot of time about 1.5 years ago, making lectures in OO that then transferred badly enough to PowerPoint that I had to edit every single item, replacing things and resizing boxes.

      I've also seen problems with tables in word.

      As for excel, I don't have much recent experience, so I can't comment.

      I suspect that, over time, OO will improve in its compatibility. So my statement was recounting experience, not predicting the future.

      I really dislike ms-word and ms-excel. But I have no choice. I collaborate with folks who assume 100% compatibility with these ms products. Whether OO can give me 95% or even 99.9% is irrelevant. Anything less than 100% is unacceptable. I know, there are difficulties from version to version of the ms products, and from PC to Mac ... but these are not an issue in collaboration; my collaborators accept that, but they will not accept wilful use of applications known to be incompatible. This sucks but it is reality. As I said, for my fun work -- my research -- I use open-source.

      PS. I've submitted some bug reports on OO, and eventually they got fixed. The future looks bright. I have no doubt that in an environment that does not require the use of ms products, OO will be a complete and wonderful solution.

    4. Re:no big loss by Anonymous Coward · · Score: 0

      "The x11 port works as well as it does on other platforms, i.e. it's great unless you want ms-office compatibilityl."

      Well, on the Mac, you get two menubars when you use OOO which uses X11. The cursors flip-flop, and Ctrl-X is the keyboard shortcut for cut when the standard on mac is Cmd-X. I would list more, but don't remember much since I've been staying away from it. These aren't problems for Linux which is more similar to Windows. I seriously wouldn't have minded if Apple dropped the command key in favor of the control key when they switched to OS X. OoO is aiming for 100% compatibility with MS Office, so it's supposed to be able to replace that in your pricture. Ahh, LaTeX... that's nice. :)

  24. Re:FREE MAC MINIS by Anonymous Coward · · Score: 0

    it's a scam
    it's a scam
    it's a scam

    The way such free offers work is, they recruit you to spam all your friends (or slashdot as the case may be) and in the process of collecting referrals, start selling off your contact info and email address to companies. Intelligent spammers at work.

  25. Re:X11 Aqua? by lederhosen · · Score: 1

    > Umm, I have yet to hear one negative comment
    > regarding Aqua interfaces (done right).

    Icons on the red, green and yellow buttons are first
    seen when you have the mouse pointer over them.

    I belive this is *negative*.

  26. I feel I just have to say it..... by iwadasn · · Score: 1, Insightful


    "But C is portable, why are they having portability problems when C is sooooooo portable? Thank god they didn't do it in Java, because java isn't really portable, not like C, and it'd be slow if it was in java, even slower than it's already glacial performance, and it might use lots of RAM, more than that 100 MB it uses now. It'd also slow downt he probject, because C is easier to write than Java, everybody knows C, but there aren't any CS departments that base their courses on Java, who cares about java...."

    Seriously, we really need a suite of JAVA tools, like word processors, spreadsheets, web browsers, etc... No more of this "well, it works on Windows, if you want it on Linux or Mac though we'll have to sit down and write it all over again, and probably introduce a ton of bugs....." stuff.

    What good is a program that depends on exact versions of 50 libraries (yeah, like I'll be able to reinstall that in 5 years and have even an outside shot at it working) and only works on a couple platforms, if you're lucky. Portability isn't an advantage, it's a requirement. If you're portable spatially (to different platforms) today, then you'll probably be portable temporally (to different time periods) tomorrow. If you can't even get it to run on most of the platforms that exist TODAY, then what makes you think it'll run on the newfangled computer that is going to come out 5 years from now? You've just given you work a lifespan of only a couple years, why would you do such a thing. I know I don't get up in the morning and say to myself "I think I'll do something excruciatingly difficult, and I'll do it in such a way that I'm guaranteed to have to come back and do it again in a couple of years".

    Let the C loving rants begin. I'm sure there will be several responders who say "But C is portable and fast" utterly ignoring the ponderous quantity (OOO, Mozilla, virtually every game ever made, etc..) of evidence indicating that the difficulty faced in porting is immense, and when you make your own custom hacked windowing system to speed the process (Mozilla), it ends up being a slow RAM hog, even more so than it would be if it was written in JAVA, or another portable language to begin with.

    I really just wish lots more programmers would grow up, then there'd be more good toys to play with.

    1. Re:I feel I just have to say it..... by Geoffreyerffoeg · · Score: 2, Interesting

      Not as a rebuttal, but as an inquiry:

      Is there a good compiler (open source or otherwise, but for the major platforms) that will turn Java into native code without requiring a virtual machine?

      I don't see why one shouldn't exist, but I haven't heard much about one.

    2. Re:I feel I just have to say it..... by n.wegner · · Score: 1

      GCJ? The Gnu Compiler Collection member that does exactly that?

    3. Re:I feel I just have to say it..... by tji · · Score: 2, Insightful

      WTF?

      Obviously, this is not a C portability issue. It's an issue with proprietary GUI APIs.

      If it used some standard GUI abstraction layer, it would have been a simple port (as seen with the X11 version, which was easily ported to MacOS+X11 -- how's that for C portability?). But, the port to a different GUI would take much more effort. Unfortunately, the developer resources just aren't there for a native UI port (most of the relevant developers gravitated over to the MacOS X only, Java based, NeoOfficeJ instead).

    4. Re:I feel I just have to say it..... by damiam · · Score: 1

      You're looking for gcj.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    5. Re:I feel I just have to say it..... by Anonymous Coward · · Score: 0

      I really just wish lots more programmers would grow up, then there'd be more good toys to play with.

      "Because growing up means using the same language I like to use".

      Sounds like other programmers aren't the only ones that need to grow up.

    6. Re:I feel I just have to say it..... by Osty · · Score: 1

      even slower than it's already glacial performance

      Drop the apostrophe in "it's", unless you meant "slower than it is already glacial performance". That doesn't make any sense to me, but perhaps it does to you.

      there aren't any CS departments that base their courses on Java, who cares about java

      As horrible as the idea may be, there are a number of CS departments that made the Java switch during the big Java boom of the late 90s. My alma mater did the switch, though luckily I was always at least a semester ahead of Java changes.

      Seriously, we really need a suite of JAVA tools, like word processors, spreadsheets, web browsers, etc... No more of this "well, it works on Windows, if you want it on Linux or Mac though we'll have to sit down and write it all over again, and probably introduce a ton of bugs....." stuff.

      Just as soon as Java gets a good, cross-platform widget set, this can start happening. AWT and Swing aren't it. SWT is the right way to go, IMHO, but since it's not built into Java, it'll never have as much acceptance as AWT or Swing, and Java on the client will continue to be judged by those crappier toolkits.

      What good is a program that depends on exact versions of 50 libraries (yeah, like I'll be able to reinstall that in 5 years and have even an outside shot at it working) and only works on a couple platforms, if you're lucky.

      Java has the same problem. The Java base librraries are good, but there will always be something you want or need to do that the default set of libraries doesn't supply. What do you do? Well, just like a C programmer, you find a library that has already done what you need, and you use that. As for portability across platforms, you still have to worry about differences in the JRE for each environment and if you make any assumptions about a particular platform (paths, for instance). Java gives you the possibility of being portable, but it doesn't guarantee it.

      when you make your own custom hacked windowing system to speed the process (Mozilla), it ends up being a slow RAM hog, even more so than it would be if it was written in JAVA, or another portable language to begin with.

      The problem is not writing your own custom hacked windowing system (which XUL isn't -- it's a custom hacked widget set; the difference being that a widget set is the stuff inside the window, while a windowing system handles the windows themselves and doesn't much care what's inside), but writing your own custom hacked system stupidly. Mozilla's XUL is written stupidly, because it doesn't use native widgets (hey, sounds like Swing!). If the Mozilla developers would lose the ego, they would find that there are a number of good cross-platform widget sets (Qt, wxWindows (or wxWidgets, I guess they're calling it now), or even GTK+, though that would be my very last choice for a cross-platform widget set). Instead, the Mozilla team created Firefox when people complained about the weight of the Mozilla suite, yet they left XUL in place. At least there's Galeon, K-Meleon, and even Konqueror (since it can use Gecko as a rendering engine) available as native-widget web browsers.

    7. Re:I feel I just have to say it..... by HeghmoH · · Score: 1

      Show me one program, just one program that was written in any kind of portable manner that looks and works nice on the Mac.

      OpenOffice is, of course, completely out, because the X11 port looks and acts like something from 1990.

      MS Office is also out, it has tons of Mac-specific code.

      FireFox is close, but it still looks and acts like a Windows/Linux app in many ways.

      I haven't seen anything written in Java that even vaguely approaches a decent Mac application. LimeWire and Azureus are jokes in this regard.

      What makes you think Java would be any better in this regard?

      --
      Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
    8. Re:I feel I just have to say it..... by iwadasn · · Score: 2, Insightful

      Not that I've ever heard of, but why do you want to turn something generic into something not generic? I guess I can see why someone might want to do that, but once you go that route you have the same "We depend on exacly these versions of these libraries, and woe betide the fool who attempts to use a newer or older one..." thing going on.

      I guess I"m a bit cynical, as I deal with vendors all day, and they give me the same BS that all the OSS zealots do about native code. I can't tell you how many times we've had a box go down only to find that the sort of hardware/software that can actually run this POS program just doesn't exist anymore. We must have 30 different system configurations at work, I know we've got a few one-offs just specifically to run some native program that a vendor gave us a couple years back.

      What happens if one of those one-of-a-kind boxes goes down? Can you get an old US-II running a 3 year old version of solaris with exactly these 50 libraries, and can you get it quickly enough that the company doesn't go out of business before you can bring that thing up? This is probably the single biggest problem with native code, it's HELL to support, but it's even worse if you have to try to integrate with it programatically.

      We never have exactly the same compilers/libraries as our stupid vendors, so we can never programatically integrate with thier software, it always gets reduced to passing around files and socket calls, I don't have to tell you what a hoot that is. It's actually possible (and not that hard) to integrate with these things through CORBA, but our sucky vendors usually make that impossible. Even then, it solves the second problem but not the first one.

      So, the choice is clear. If we let our vendors give us native code, then we need to plan on having 50 system configurations, and a couple of EXACT duplicate spares of each, as well as dozens of different development environments perfectly suited to each sucky program, or a horrible file based API.

      Alternatively we can just require that it's Java or it doesn't get in the door, and then all these problems are gone. If a box goes down, we just replace it with any equivalent hardware and are pretty confident that it'll work. We can also call the APIs directly, as we won't have compiler/library/calling convention mismatches. Even better, if it crashes, we might get a useful stack trace as opposed to merely a core dump and a dead program.

      I also must say that the shops that write in JAVA are hugely more cluefull than those that don't. I've worked with and worked at both types, you either understand the above situation, or you don't. You never want to work with or for anybody who can't understand the scenarios layed out above. At work, we are (fortunately) doing a good job of keeping native code out, though there's still a little bit here and there. We are going to add another piece of native code it looks like, but it's either that or buy something from Reuters, and in this case it appears that going native by not-reuters is better than getting anything from Reuters.

    9. Re:I feel I just have to say it..... by iwadasn · · Score: 1


      Partially true, but the X11 port is pretty sucky. It doesn't feel like an OSX application, and has verious other problems due to its alien nature. I don't think they get more than 1/2 credit for the X11 port.

      Compare this to something like Limewire that works beautifully on every platform, and integrates wonderfully into most of them. They surely wrote some native code, but I'm sure it wasn't much, and you can always download the jar if you want it clean of such things.

    10. Re:I feel I just have to say it..... by tijnbraun · · Score: 1

      There a few.
      One which is free sofware is GNU Compiler for the Java but I'm not sure if it works with swing.

      AWT is not supported so I suppose swing isn't either.

    11. Re:I feel I just have to say it..... by iwadasn · · Score: 1



      "As horrible as the idea may be, there are a number of CS departments that made the Java switch during the big Java boom of the late 90s. My alma mater did the switch, though luckily I was always at least a semester ahead of Java changes."

      You missed my sarcasm apparently.

      Also, what's wrong with swing? It seems to work fine on OS X, Windows, and Linux, as far as I can tell. Looking at JEdit, NetBeans, Limewire, some of our vendor apps, and our own internal apps at work, it seems fine to me.

      Perhaps you're a little more particular though. Pretty much all of those apps are snappeir than OOO and Mozilla/Firefox, as far as I can tell.

    12. Re:I feel I just have to say it..... by Geoffreyerffoeg · · Score: 1

      Not that I've ever heard of, but why do you want to turn something generic into something not generic? ... Can you get an old US-II running a 3 year old version of solaris with exactly these 50 libraries

      No, I can't, but I can recompile the same guaranteed-portable Java onto the new computer, or at worst run it under a virtual machine.

      Sorry if I wasn't clear in my original inquiry. By native code I mean machine language vs. bytecode, not platform-specific C vs. portable C or Java. I want something that will, e.g., run on Windows and turn a .java file into a .EXE instead of a .class. I'd still be coding in Java.

    13. Re:I feel I just have to say it..... by Anonymous Coward · · Score: 0

      You can make Java more Mac aware. It is just a pain.

      Azureus is SWT, not Swing.

    14. Re:I feel I just have to say it..... by mlk · · Score: 1

      You can get round the lack of swing, by using SWT (or other GCJ compatabile WT) and SwintWT (or equiverlent for your WT).

      --
      Wow, I should not post when knackered.
    15. Re:I feel I just have to say it..... by mlk · · Score: 1

      I use to maintain a
      list, but it is very out of date now.

      JET requires the JVM to be packeted to include Swing.

      --
      Wow, I should not post when knackered.
    16. Re:I feel I just have to say it..... by Anonymous Coward · · Score: 0

      Mozilla's XUL is written stupidly, because it doesn't use native widgets (hey, sounds like Swing!). If the Mozilla developers would lose the ego, they would find that there are a number of good cross-platform widget sets (Qt [trolltech.com]

      Except Qt widgets aren't native either..

    17. Re:I feel I just have to say it..... by Anonymous Coward · · Score: 0

      If the Mozilla developers would lose the ego, they would find that there are a number of good cross-platform widget sets (Qt, wxWindows (or wxWidgets, I guess they're calling it now), or even GTK+, though that would be my very last choice for a cross-platform widget set).

      You don't know what you're talking about.

      Qt and Gtk are much like Swing in that neither uses native widgets (it just so happens that on many *nixes that Qt and Gtk are essentially the "native" widgets). The biggest advantage of this is that the widget functionality is identical across platforms and a particular LnF is essentially cross platform. This last thing (that look and feel is cross platform) is actually a disadvantage for Mac users since the "native" style has to be simulated. Qt/Aqua is good, but it is not perfect (and there is a lag with newest Aqua changes), furthermore laying out a Qt design will not guarantee HIG conformance on Mac which seems to be a major issue in this whole debate. The other problem with Qt is that it requires a commercial license for Aqua and Windows, GTK+ doesn't. On Windows XP, GTK and Qt have the ability to use the native themeing, so they are native at lowest possible level of rendering. On XP, there really is no expectation of a HIG (even if there is one, the average Windows user has to put up with a complete mish mash of GUI looks (it is a myth that X11/*nix is any worse in this regard, I use a wide variety of apps on Windows and if you use more than just Office and IE you find there is very little UI stuff in common)).

      wxWidgets is much more like AWT/SWT, and so it isn't fair to compare to Gtk/Qt. wxWidgets is much closer to wrapping the native high level controls/widgets. It also has an API modelled after MFC (not generally a good thing, since that was just a light wrapper around Win32 API, which means alot of Win32 idiosyncracies punch through wxWidgets). Also, a major problem with these AWT type sets is again, that their layout managers are at too low a level to follow varying HIG and high level layout standards (like on Mac) and even worse they force the API to conform to the lowest common denominator. I have never seen a wxWindows app, that when compiled for Aqua actually follows the HIG or looks native (except superficially).

      If you talk to any commercial software developer you will learn that their is simply no way around these problems. The only way to handle this is with another level of indirection, that is, you layer a frontend independent layer between the GUI and the application logic. Your application logic cannot be intertwined with a particular GUI library, so that you can write a completely custom frontend that does whatever it needs to do to look native. Many free applications do this, for example Abiword, Freeciv.

      Another example to drive this home. GTK+ and wxWidgets are both great at geometry, but chances are they will do nothing for you when you want to get that great app of yours to work on a 240x320 (vertical) PocketPC or Palm because everything except the most trivial of apps has to have its GUI input methodology completely restructured for a smaller device like a PDA.
      For an app expected to have enduring cross platform value, abstracting the frontend from the application logic should not be drawn at the GTK or Qt or wxWidgets (or AWT/SWT) line no matter how pretty their style engines promise to be. They simply are too low level (desktop GUI centric) to contain all the necessary frontend abstractions.

    18. Re:I feel I just have to say it..... by Anonymous Coward · · Score: 0

      If you talk to any commercial software developer you will learn that their is simply no way around these problems.

      God damn it, yeah I should have proofread. After typing "commercial software developer" I must have just used "their" there because I thought I was going elsewhere with the sentence.

      Yes, I usually know the difference between "their" and "there". (And I know American quote punctuation rules to, but I renounce them).

    19. Re:I feel I just have to say it..... by SoupIsGood+Food · · Score: 1

      Yes. It's called GCC, which stands for "Gnu Compiler Collection." It can do C, C++, Objective C, Java, Fortran and Ada. Apple uses compiled native Java rather than VM Java as one of the programming languages officially supported by Xtools. You can use GCC to compile Java code into native binaries on just about every platform GCC runs on.

      ~ SoupIsGood Food

  27. This is why Open Source projects fail by sakusha · · Score: 5, Insightful

    You can't ignore the largest Unix vendor in the world: Apple. You're just cutting your own throat if you ignore a huge segment of the market for your software. Projects succeed when people USE the software.

    1. Re:This is why Open Source projects fail by Anonymous Coward · · Score: 0

      I think one of the (if not the) biggest unix vendor in the world is still IBM.
      IBM has lost money over the last decade with it's computer business than Apple has ever made profit.
      Disclaimer: Though I rather like the Apple's hardware, I don't like the software at all. The IPod not beeing able to play Ogg Vorbis, and OS X beeing closed sauce are just two examples.

    2. Re:This is why Open Source projects fail by Theolojin · · Score: 1

      You can't ignore the largest Unix vendor in the world: Apple. You're just cutting your own throat if you ignore a huge segment of the market for your software. Projects succeed when people USE the software.

      Let us be *very* generous and say that Apple accounts for 10% of the desktop market. Focusing on the remaining 90% (plus) of the desktop market is in *no* way "cutting [their] own throat." Projects do indeed succeed when folk use the software. At least nine times as many folk do not use Apple's Unix than do. OpenOffice.org is appealing the overwhelming portion of the "market."

      --
      Life is short; think quickly.
    3. Re:This is why Open Source projects fail by sakusha · · Score: 1

      You're not getting the point. Mac users have wanted to be free from Microsoft long before there ever was such a thing as Linux, or even Windows for that matter. This is the natural market for Open Office.
      Open Office is intended to make a cross-platform open format for documents. If you only support your primary market, you've just made it into a single-platform PC product again. So the project has failed its goal.

    4. Re:This is why Open Source projects fail by Anonymous Coward · · Score: 0

      Thank you.

      I very very much aggree with this outlook.

      If you want Open Source or Unix Projects to work, you have to make it avaliable to Mac Users who now make up a large portion of your market place.

    5. Re:This is why Open Source projects fail by aristotle-dude · · Score: 1
      Have a look around at versiontracker.com in the OS X section. There you will find many open source apps which make use of other open source projects. These projects help bring more public attention towards these very open source projects.

      Now look at the landscape of the PC market. The vast majority use Windows. Most of them have no interest in running any variety of *nix OS and they don't want to use Cygwin. How exactly are you supposed to easily port open source apps to windows?

      Look at all of the spyware on windows in the freeware apps. Look at all of the people developing closed source applications with stolen open source code on windows. CherryOS anyone?

      Now with this picture, which platform should you be focusing on outside of linux? Mac OS X or windows. Windows may have a lot of marketshare but your application is likely to be either copied quickly by a closed source developer or just lost in the sea of crapware with better marketing.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    6. Re:This is why Open Source projects fail by ratboy666 · · Score: 1

      "You can't ignore the largest Unix vendor in the world: Apple. You're just cutting your own throat if you ignore a huge segment of the market for your software. Projects succeed when people USE the software."

      I need to cut that out...

      Apple "ignored" UNIX and the idea of a cross-platform GUI. If Apple makes OS X GUI available, then, sure, OOo can use it.

      Until then? Nope, not happening. It's not open, it's not in MY Unix.

      Yep, call me a Zealot, whatever. I DEMAND cross platform compatibility (on my SUN kit, on my HP kit, my IBM kit -- and on my Intel kit). Apple sure is compatible -- that's why X Windows is supplied with the machine.

      That's because Apple wants to run with the big dogs. Where they have even LESS presence than Microsoft!

      Gotta figure that years of marketing to artists has taken a toll.

      Ratboy.

      PS. I am envious of 1 (one) feature of the Mac -- the abililty to have truly transparent terminals.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    7. Re:This is why Open Source projects fail by Anonymous Coward · · Score: 0

      Apple is not that big a market to ignore for OpenOffice.org. They've got a Windows version, after all.

      It would be different if it was a Unix-like OS product only, of course but it's not.

    8. Re:This is why Open Source projects fail by sakusha · · Score: 1
      Yep, call me a Zealot, whatever. I DEMAND cross platform compatibility (on my SUN kit, on my HP kit, my IBM kit -- and on my Intel kit). Apple sure is compatible -- that's why X Windows is supplied with the machine.

      Apparently Mr. Zealot doesn't recall his favorite SUN platform's proprietary GUI, Motif.
    9. Re:This is why Open Source projects fail by kiddygrinder · · Score: 1

      This is why open source projects succeed actually, if a great enough need arises, someone will do the port. Oh, it did. Oh, someone has.

      --
      This is a joke. I am joking. Joke joke joke.
    10. Re:This is why Open Source projects fail by thanasakis · · Score: 1

      Apparently Mr. Zealot doesn't recall his favorite SUN platform's proprietary GUI, Motif.

      Which is quite natural really, because:

      1)Motif is not a proprietary product of Sun. It is owned by the Open Software Foundation which was formed by IBM,DEC and HP.
      2)Sun stopped developing motif applications a long time ago. Last time I checked they were actually contributors to GNOME. Solaris has a gnome desktop available (for those who don't want to use CDE) for a couple of years.

    11. Re:This is why Open Source projects fail by goMac2500 · · Score: 1

      They aren't ignoring Apple... They're still making OpenOffice for Mac. They're just going to use X11 instead of Aqua for windowing.

    12. Re:This is why Open Source projects fail by gl4ss · · Score: 1

      not really, you're the one taking it wrong. apple users in general are NOT people who just want to be free from microsoft, they want to use apple because apple is apple and because apple makes the best software and hardware available(in their minds).

      apple is NOT the natural place for open source projects - as the users pay alreay premium to be with _APPLE_, to use _APPLE_ designed os, to use it on _APPLE_ hardware. they WANT a lock in, but they want it to be apple. they don't want faster machines, they want it to be apple. they don't care if they have to pay over four hundred bucks for gig of ddr333 - because they know it's apple and therefore it is better.

      as such, no matter how good your open source product and no matter how free it is it can never compete with anything apple. openoffice would never be able to be a iProduct, since it's not an apple product and as such it could never compete on it's terms.

      they would happily walk into a lock in(as it would make everything work 'perfectly'). after all, they don't care if their os comes with nagware.

      --
      world was created 5 seconds before this post as it is.
    13. Re:This is why Open Source projects fail by nathanh · · Score: 1
      Apparently Mr. Zealot doesn't recall his favorite SUN platform's proprietary GUI, Motif.

      Motif is a widget set, not a GUI. You're probably thinking of CDE.

      CDE was from IBM, Digital, Microsoft and HP, not Sun.

      Sun's proprietary GUI was OpenWindows. It was a heck of a lot better than CDE.

      Sun stopped building on CDE about 4 years ago and has been a GNOME supporter ever since.

    14. Re:This is why Open Source projects fail by ikekrull · · Score: 2, Interesting

      Well, yes they can ignore Apple, what has anybody in the OSS world got to lose by 'ignoring Apple'?

      Revenue? nope.

      Respect? not from tards like you, I guess

      If Apple doesn't want to support X11 properly, with a decent font server and a lack of high-performance extensions, thats their call.

      So tell me again what the motivation for volunteers to port to OS X native APIs (which are mostly closed and proprietary) are?

      Come on, You have a native MS Office port for your platform, a bunch of other shareware or commercial office suites and surprising as it may be for you, Linux/UNIX users are not all primarily motivated by this ridiculous 'BEAT MICROSOFT AT ALL COSTS' idea.

      Just pay for an office suite if you need one that fits criteria that the open alternatives don't meet.

      Thats the economic model that Apple's Carbon and Cocoa APIs encourage, so if you want to have a go at someone over it, take it up with Steve Jobs, not the people in the OSS community.

      Nobody owes it to you to slave away cutting code for an essentially closed platform that few developers have on their desktops, so you can type out your word processing documents. If it means so much to you, either do it yourself or organise a bunch of people to do it for you.

      Its not going to happen just because you post your whinings to Slashdot, thats for sure.

      --
      I gots ta ding a ding dang my dang a long ling long
    15. Re:This is why Open Source projects fail by Guy+Harris · · Score: 1
      Open Office is intended to make a cross-platform open format for documents. If you only support your primary market, you've just made it into a single-platform PC product again. So the project has failed its goal.

      So where was the announcement that they'd stopped supporting the UNIX+X11 platform? In order to "only support [their] primary market", they'd have to drop support for UNIX+X11 or for Windows, whichever is their "primary market", in order to "only support [their] primary market"; as UNIX+X11 isn't PC-only, presumably you're not talking about them dropping Windows support.

    16. Re:This is why Open Source projects fail by bob+beta · · Score: 1

      Apple isn't a UNIX vendor. They're not even licensed to call their patch-together OS a UNIX.

    17. Re:This is why Open Source projects fail by Blakey+Rat · · Score: 1

      At the risk of pissing off all of Slashdot, the reason that Apple didn't use X11 isn't for compatibility, but because X11 sucks ass. It's not even nearly as good as the window toolkit they were using in MacOS 8 and 9, and it certainly wouldn't have been a step forward if they moved from OS 9 to something based around X11.

      Apple wanted to off-load window code into the video card. You can't do that with X11. Apple wanted copy and paste to work as gracefully as it did in OS 9, X11 can't provide that. Apple wanted a 'services' feature, like OpenStep had, and to my knowledge there's no way X11 could do that. And forget the features they've added since, like Expose.

    18. Re:This is why Open Source projects fail by bnenning · · Score: 2, Insightful

      they WANT a lock in, but they want it to be apple. they don't want faster machines, they want it to be apple. they don't care if they have to pay over four hundred bucks for gig of ddr333 - because they know it's apple and therefore it is better.

      I'm sorry, that's just silly. Nearly all Mac users use Macs because they prefer them to Windows and Linux PCs. That's it. It has nothing to do with worshipping Apple. (Yes, there are the guys that paint Apple logos in their hair. They aren't exactly representative).

      as such, no matter how good your open source product and no matter how free it is it can never compete with anything apple.

      Counterexamples: Firefox and Camino.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    19. Re:This is why Open Source projects fail by gl4ss · · Score: 1

      but mac users prefer safari, as it's 'amazingly perfect', over those - they really aren't contenders against the apple solution(firefox on mac and camino are mainly used by geeks who use mozillas on other platforms too).

      typical mac user doesn't know enough of "linux" to be able to prefer anything. typical mac user isn't any more of a geek than a typical pc user is.

      or haven't you heard how great the built in stuff in tiger is going to be and blow everything out of water yet, and that other vendors have no idea how to do things?

      --
      world was created 5 seconds before this post as it is.
    20. Re:This is why Open Source projects fail by pete-classic · · Score: 1

      You fundamentally misunderstand Open Source (at least to the extent that it overlaps Free Software). A piece of proprietary software lives or dies on market share, be it share of a niche, or share of all PC deployments. Conversely, Free Software (read: "community" Open Source) lives and dies on developer interest. I will grant that the two are not strictly unrelated, but scrabbling for a relatively small group of expensive users (in terms of developer time) is not only not "cutting your own throat", it is good strategy.

      OO.o doesn't ignore OS X. Period. It does give Apple's proprietary display system the short shrift. For the reason cited above this is the right thing to do, at least until such time as a sufficient amount of non-transferable developer time materializes. (And I expect this will happen sooner than later.)

      -Peter

  28. Because QT looks like ass on Mac by melted · · Score: 4, Insightful

    That's why. It's not native to Aqua and it shows. Mac people like polished apps, and Qt apps simply look like they've been poorly ported from Windows.

    1. Re:Because QT looks like ass on Mac by Brandybuck · · Score: 3, Informative

      I've got a Qt app I distribute for Mac. It looks native because it *IS* native. It uses the native Qt/Aqua. The widgets are genuine Aqua widgets because Qt uses Aqua to draw them. The menu bar is placed at the top of the screen. The configuration menu was moved as appropriate. Etc, etc, etc. With a few carefully placed #ifdefs and a properly constructed icon and application bundle, no one can tell it's really developed under FreeBSD.

      --
      Don't blame me, I didn't vote for either of them!
    2. Re:Because QT looks like ass on Mac by Bulln-Bulln · · Score: 1

      Yeah, polished apps are nicer. But you forget one thing: Many Mac users hate MS. There is no big fully native office suite on Mac except MS Office. iWork '05 looks nice, but it's not a big office suite.
      NeoOffice still doesn't look too great, but it has so many fans, because it's the only big alternative. There is no WordPerfect and no SmartSuite. And NeoOffice also free (beer and speech).

      A well ported Office app (--> as in "not so buggy") written with Qt will have it's fans. I'm sure most users won't care if the menu layout is not so mac like, when the rest works well.

      (I know about about the smaller office programs on Mac, like AbiWord, Mellel, etc)

    3. Re:Because QT looks like ass on Mac by This+is+outrageous! · · Score: 1
      I've got a Qt app I distribute for Mac. It looks native

      I looked it up (QT screenshot, QT/Aqua screenshot).

      It looks impressive, compared to Neooffice/J.

      But does that QT OOo actually build? on the Mac?

      --
      This is...

      O
      U
      T
      R
      A
      G
      E
      O
      U
      S

      !

    4. Re:Because QT looks like ass on Mac by Anonymous Coward · · Score: 0
      I'm sure most users won't care if the menu layout is not so mac like, when the rest works well.
      You obviously don't know Mac users.
    5. Re:Because QT looks like ass on Mac by rxmd · · Score: 1
      Qt apps simply look like they've been poorly ported from Windows.
      Well, at present OOo on OS X looks like it's been poorly ported from Hell. It really doesn't get worse than that.

      NeoOffice is slightly better, but not a lot, and I have no clue why they chose Java for the implementation. Platform independence can't be the reason.

      At least a Qt version would provide native widgets, a native menubar and Dock integration as well as better copy/paste at all, as opposed to X11. You could still tell the difference (toolbars, no printing, probably some right mouse button quirks), but a Qt version would be way better than what we have now, including NeoOffice.
      --
      As a state gets corrupt, its laws multiply; the most corrupt states have the most numerous laws. (Tacitus, Annales 3:27)
    6. Re:Because QT looks like ass on Mac by Bulln-Bulln · · Score: 1

      You obviously don't know Mac users.

      I *am* a Mac user! I also know quite a few other Mac users.
      Just because you care about the menu layout, it doesn't mean that all the other Mac users think that way.
      Just look at browser use on Mac. Firefox has lots of users on Mac. "Help --> About" isn't Mac like. Not all buttons are Aqua buttons.
      So how do you explain the popularity of Firefox on Mac?

    7. Re:Because QT looks like ass on Mac by melted · · Score: 1

      >> Many Mac users hate MS

      To the contrary. Many Mac users like MS because they release Office for Mac and it's a good product. It's actually a better product than Windows version of Office.

      Folks switch from Windows to Mac PRECISELY because it still runs Office, but without all the annoyances of Windows and does so on better hardware and with more polished UI.

      If you thought it was hard to compete with Office on Linux (where there's no official port), that was nothing. It will be 10 times more difficult to compete with Office on Mac. The only company that can pull this off is Apple, because they'll write a native polished app that will be good enough and cost 3 times less.

    8. Re:Because QT looks like ass on Mac by lpontiac · · Score: 1

      Great, but my Qt application has a tab widget in it.. and Qt renders it 10.2 style on everything, including MacOS X 10.3. (Apparantly to be fixed in Qt 4).

    9. Re:Because QT looks like ass on Mac by Bulln-Bulln · · Score: 1

      To the contrary. Many Mac users like MS because they release Office for Mac

      And all those "Now I can finally ditch MS Office" posts on various web sites when iWork was announced were just my imagination? Er... no.

    10. Re:Because QT looks like ass on Mac by melted · · Score: 1

      Yeah. That sure is representative of Mac userbase as a whole. :0) I mean 20 users out of millions can't be wrong, right?

    11. Re:Because QT looks like ass on Mac by Anonymous Coward · · Score: 0

      Mac people like polished apps

      I think it'd be more accurate to say that people who like polished apps like Macs.

  29. good by Triumph+The+Insult+C · · Score: 0, Troll

    Apple is not OSS friedly. Sure, there is that whole Darwin thing, but really, they take a lot and don't give much back. If companies aren't going to give back a little for as much as they have recieved, I say this is good.

    --
    vodka, straight up, thank you!
  30. Re:Of course they won't by sebFlyte · · Score: 1

    Why on earth would Apple sue OpenOffice.org to death? I don't buy the 'just because they can' argument, since it simply doesn't make business sense.

    If Microsoft has so far restrained itself from suing the OOo developers (though, from what I've heard they've come close), why would Apple do it?

    In my view, what Apple should have done is included support for the open standards that OOo, StarOffice (and, i'd guess NeoOffice.org, but i don't know) in iWork. I can understand why they left out spreadsheet functionality -- they realise that it is important to keep MS producing Office for the mac, as it's going to be a long time before there is serious enterprise takeup of open standards, and even those who work in macs core industries (print, design, etc.) need to have office functionality for it to make business sense.

    --
    "Nothing can shake my belief that this world is the fruit of a dark god whose shadow I extend." - Emil Michel Cioran
  31. Bad for apple by digitalgimpus · · Score: 1

    I'm personally not very certain the bloated Office for Mac will continue forever. Not certain at all. Each time it looks like less and less of an effort was made.

    OpenOffice is fast, pretty sleek, and pretty dang compatible. If Office SBE didn't come with my XP laptop, I would have just passed on it, and used OpenOffice. It's more than enough for most users.

    This makes Apple depend more on Microsoft for it's remaining business market. This isn't good. AppleWorks/i{Product} isn't good enough for corporate use.

    IMHO Apple would be wise to invest a bit to bring OpenOffice to the Mac. Even if it's not quite Aqua. Something simple to install, fast, and stable.

    Apple needs a business suite. OpenOffice is currently the only non-microsoft product with potential to stand up against Office. It's got the necessary features, and compatibility.

    Apple would be wise to put a few employees on OpenOffice and get some builds churning. Apple needs that security.

    1. Re:Bad for apple by Anonymous Coward · · Score: 0

      You've hit the point.

      Apple doesn't seem to have an interest to support open source software on Mac OS/X

    2. Re:Bad for apple by redmoss · · Score: 2, Informative

      Check out NeoOffice. They seem to be doing just fine. Help/funds from Apple would certainly not hurt, but I'd say the "native-looking" OS X oo.o version is here to stay.

    3. Re:Bad for apple by 1_interest_1 · · Score: 1

      What? Back up the train a minute here buddy!

      "Bloated" Office for Mac? Have you ever used MS Office on OS X? It's absolutely gorgeous! It's better than Office for Windows!

      AppleWorks/i{Product} not good enough? Damn man, have you even used iWorks yet? It's the direction of the future!

      Shit just works on the Mac. Shit just doesn't work on Windows.

      There is no way in hell that Apple would invest in OO - it's a bloated piece of shit.

      "Simple to install"? That's not even a requirement on OS X, that's a given for *every* application. You drag and drop to remove, you download to install. End of story.

    4. Re:Bad for apple by Anonymous Coward · · Score: 0

      > "Bloated" Office for Mac?

      Office for OS X is a great fucking suite, but it is also pretty sluggish especially wrt the Windows version.

    5. Re:Bad for apple by Valafar · · Score: 1

      I see a lot of people talk about this is bad for Apple, or Apple doesn't do this... The interesting thing is that I think they do this intentionally. There is a *HUGE* opportunity to find niche markets for software on the Mac simply because Apple doesn't fill in the gaps like Microsoft. Look at the previous story about Digital Monster. These guys wrote what amounts to shareware, charged 40 bucks a copy and have been wildly successful.

      I hope that others will recognize the opportunity and take it! Apple has managed to blend commercial and OSS in a brilliant way...

    6. Re:Bad for apple by Ohreally_factor · · Score: 1

      Did you mean the story on Delicious Monster?

      --
      It's not offtopic, dumbass. It's orthogonal.
  32. there's always Ragtime solo.. by Wire3117 · · Score: 5, Informative

    http://www.ragtime-online.com/ it beats Openoffice hands down. just my ,02

    1. Re:there's always Ragtime solo.. by gl4ss · · Score: 1

      for 700$ it better beat openoffice!

      --
      world was created 5 seconds before this post as it is.
    2. Re:there's always Ragtime solo.. by Anonymous Coward · · Score: 0

      If you had taken off your penguin-glasses for a second and actually looked at their homepage you'd have realized they are giving RagTime away for free for Home users. And making it WORSE than the POS OpenOffice currently is would have been quite a feat, yeah. ;)

  33. Re:FREE MAC MINIS by Anonymous Coward · · Score: 0

    thank you captain obvious.

  34. Mod parent down! by fname · · Score: 1

    Mod parent down! No one has ever claimed Slashdot is any way related to journalism. Geeze, talk about building up a strawman just to knock it down. :)

    (Actually, mod it up. Pretty informative.)

  35. Re:More Mac Zealotry by Anonymous Coward · · Score: 0

    STFU, at least i have my iLife with my ibook and my imac and my ipod and my iphoto and my ishuffle and my imac mini and my imovie and my itunes so fuck off go play with your "l33t nix boxen d00d"

  36. Java indeed by barryvoeten · · Score: 2

    The java-nised NeoOfficeJ is the project you're talking about. It runs in darwin and works. The official openoffice requires xdarwin and runs as good as your X.

  37. no native port = bad experienc by maryjanecapri · · Score: 3, Insightful

    i've been a Linux user for about 10 years and a Mac user for about 2. when i went to install OpenOffice on my ibook i had to jump through hoops i hope to never have to jump through again.

    So bad where these hoops that i've pretty much tossed OO (using X11) and am using NeoOfficeJ with fairly good success.

    If the OO team wants Mac users to migrate from MS Office to OO it would probably be smart to focus some time and energy on a native port. Very few people are willing to take all the necessary steps to get OO running on OS X with X11. not only that but it's slow, doesn't have nearly as nice an interface, and DRINKS DOWN the memory.

    --
    nature loves variety::society hates it get your variety at http://www.monkeypantz.net
  38. Dumb mistake in the Mac market by mmarlett · · Score: 4, Insightful
    X11 Will Always Look like Other Platforms: Many people deploying OpenOffice.org count the identical look and feel on all supported platforms as a major benefit. It helps them reduce training and, in many cases, implement a single multi-platform solution using OpenOffice.org as middleware (such as extendedPDF). Any native work that changes the interface would remove this as a critical selling point for OpenOffice.org for these users.

    Ask Microsoft how well Word would be accepted if it didn't follow the basic UI outlines of the Mac OS. There used to be a time when Word (and all Microsoft products) made up their own key combos, their own look and feel and were generally willy nilly -- a lot like many X11 offerings now. Word was the same on Windows (albeit 3.11) and Mac (6 or 7) but it didn't play well with the other programs.

    As a tech support, do you think you'd get more questions from people about why copy and paste doesn't use the same buttons on the Mac/PC/Linux versions or do you think users are more likely to not understand this one program that doesn't act anything like the other Mac programs? How many users are going to hop from machine to machine versus program to program? And then consider that it is just a word processor. Screw it. I wouldn't want those support calls.

    This has been the downfall of many otherwise fine pieces of software on the Mac OS. It's users expect consistancy.

  39. Too bad. by ThousandStars · · Score: 4, Informative
    I'm sorry (but not surprised) to hear the formal announcement. It's particularly strange to see so soon after I wrote this post on /. alluding to the technical challenges. Anyway, if you want to see the larger reasons why the port isn't going to happen, look at Patrick Luby's post here. The highlights:
    2. Event handling, fonts, and printing will take up most of your time Most of the postings that I have seen about Aquafication refer seem to focus solely on getting Aqua widgets on the screen. In other words, everyone gravitates to the "sexy" engineering work. Surprisingly, this is not the hard engineering work. The really hard engineering work is getting all the tedious details of event handling, font layout and rendering, and printing implemented correct. Essentially, VCL is a full-featured cross-platform GUI framework (similar to QT, Java AWT, etc.) so you need to reimplement almost all of that framework before OOo becomes even reasonably stable. When I first NeoOffice/J, getting native windows, buttons, lines, etc. to draw on the screen was finished rather quickly. But implementation slowed to a crawl when I implemented event handling and font rendering. Why? Because the native event handling and font rendering behavior is wildly different on Mac OS X than it is on X11 but your VCL framework implementation must ensure that this different behavior is properly mapped to VCL's platform independent behavior.

    I looked at OOo with the thought of helping out with the native port, but recoiled when I actually looked at ths sheer size and complexity and skill necessary. Another important point in the linked post is that moving to Aqua will take "a couple thousand hours of developer time," which I actually think is being optimistic. Unless an experienced somebody or, more likely, team of sombodies is willing to put their nose to the project 40 hours a week, like it's a full time job, it's not going to happen. And even if it does happen, it will break compatibility with the rest of OOo.

    OOo, I'm sorry to see you go. At this point it might be easier to start from AbiWord and move out to develop a full office suite on the Mac. The tension between being "Mac-like" and coordination with the rest of OOo -- which isn't anywhere near as mature as MSO, yet, anyway -- is too great.

    1. Re:Too bad. by Anonymous Coward · · Score: 0

      ...but AbiWord is just a word processor which cannot compare to OpenOffice.org Writer...

    2. Re:Too bad. by lrucker · · Score: 4, Interesting
      Unless an experienced somebody or, more likely, team of sombodies is willing to put their nose to the project 40 hours a week, like it's a full time job, it's not going to happen

      It could be one somebody, but yeah, it's a full-time job - I wrote the original Swing MacLookAndFeel from Apple and if I hadn't started when Swing first came out, long before anyone else thought it was important, it wouldn't have been ready when OS X shipped.

      (This was the second MacL&F, actually, but the first one was really only a "look". I had nothing to do with it)

    3. Re:Too bad. by ThousandStars · · Score: 1
      Do you/did you actually work for Sun or Apple? It sounds like the latter but I'm not sure. Either way, I'm impressed.

      I still think that even if one somebody took over OOo native, it would still take that somebody years just to get OOo native aqua working with all its pieces functional. And that somebody would need greater skill than I possess. I do have sufficient skill to grasp the enormity of the task, though, the scope of which I do not think everyone posting in this story understands.

      I haven't actually counted the number of lines in OOo, but I wouldn't be surprised if it were in the millions.

    4. Re:Too bad. by ReinoutS · · Score: 1

      Abi may not be as feature complete as Writer, but it's also open source you know. I don't think input from the Mac community would hold back its development...

    5. Re:Too bad. by lrucker · · Score: 1

      I worked for Sun, at Apple, with the Apple Java team. Got laid off in 2001.

    6. Re:Too bad. by Anonymous Coward · · Score: 0
      OOo, I'm sorry to see you go. At this point it might be easier to start from AbiWord [abisource.com] and move out to develop a full office suite on the Mac. The tension between being "Mac-like" and coordination with the rest of OOo -- which isn't anywhere near as mature as MSO, yet, anyway -- is too great.


      Maybe port AbiWord and Gnumeric to the mozilla/firefox GUI then it should be cross platform GUI on OSX, Linux, Windows, etc.
  40. Apple needs to pick up the ball by sydsavage · · Score: 1
    I'm as excited as anyone else about Pages, but I think having a native office suite that is a drop in replacement for MS Office is critical to wider adoption of the Mac. It's been obvious for a while that no one is going to do it for Apple. What I feel they need to do is take the OO code, and set their best and brightest on the task of making it a seamless native Mac application.

    They could even outsource it to the good guys at The Omni Group, who seem to have a handle on making beautiful Aqua applications, and have experience porting applications to the Mac platform.

    At any rate, they need to be prepared for the inevitable dropping of Mac support from MS Office. Internet Explorer was just a warning shot, but now that Apple is poised to step further into Microsoft's perceived territory, retaliatory strikes are simply a matter of when, not if.

    1. Re:Apple needs to pick up the ball by Anonymous Coward · · Score: 0

      "...but I think having a native office suite that is a drop in replacement for MS Office is critical to wider adoption of the Mac."

      Actually, anyone who needs MS Office for the Mac just goes out and buys MS Office for the Mac, just like anyone who needs Office for Windows buys Office for Windows ("Needs" and "nerds" are two different words, being the latter doesn't mean you understand the former). Price has always been the most cited reason for not buying Apples, not the availability of a compatible office suite.

      "What I feel they need to do is take the OO code, and set their best and brightest on the task of making it a seamless native Mac application."

      Why? If they already have a program that runs natively, can open and edit Word documents (and a host of other formats), and maintains the Mac look and feel (a major selling point of the platform, after all), surely trying to beat crufty code into shape is flogging a dead horse; there is no logical reason for them to use the OOO codebase over an in-house design if it is functionally equivalent. Apple probably considered Open Office and decided they could do better, plus they could maintain open standard compatability without giving away their optimizations (its called "competitive advantage", which may be a confusing concept for the "free-as-in-beer" fanboys). In fact, if Apple create a program that can do everything Word or OOO can, with the usual ease of use that accompanies most of their software, that in itself will draw more users to the Mac platform (contrary to popular belief, Apple does have a strategic planning department, it isn't just down to the Will-of-Jobs).

      "At any rate, they need to be prepared for the inevitable dropping of Mac support from MS Office.... retaliatory strikes are simply a matter of when, not if."

      You're saying is that a cluey businessman like Ballmer is going to close down a profitable division of Microsoft (IE for Mac didn't earn any revenue for MS, remember) simply because they can't stand some competition? Talk about cutting off your nose to spite your face. Perhaps it will make MS work that much harder on their Office suite, like the way competition works in most industries.

  41. Not a big deal by admiralfrijole · · Score: 4, Informative
    Contrary to what Slashdot headline and article writers would have you believe, this isn't that big of a deal people.

    First of all, we have some nice, juicy, out of context quotes like this one:
    no MacOS X work has been done since 2003
    when in fact the page linked to states:
    all engineering for OpenOffice.org Mac OS X has been focused on X11 graphics, that is, OpenOffice.org Mac OS X (X11).

    Then, faithful Slashdot reader, we are informed that: there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :(
    When in fact, although there will not be an official OOo in Aqua, there is this:
    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.
    So you can just use NeoOffice/J

    So basically what we have are a group of developers not willing to take the time and effort to go headlong into learning a specific OS's nuances and tweaks, and majority reworking the code to run natively in OS X, but who will keep making an X11 version that keeps up with the other platforms, and there is a 2nd set of developers working that into a native port. Doesn't seem like the end of the world to me.

    So have no fear, OOo is here to stay on OS X, and NeoOffice/J is here to work on a native port.

    --
    e to the pi i plus one equals zero
  42. iWork not really a killer... by SuperKendall · · Score: 1

    The only overlap to me is really PowerPoint (or whatever the OO version is called) and Keynote - the second program announced, Pages, is really more of a simple layout program that a word processor.

    So I don't think Pages will take away much market from either Word or OO Word, as it is meant for different things.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  43. No... by Nexum · · Score: 1

    Just want to say how much my stomach lurched when reading this on the front page.

    I love OS X, it's the only platform for me, it's incredible 'fit and finish' makes it such a nice place to be, and I have been hoping for over a year now for the Aqua OOo to be delivered.

    Currently we only really have MS Office on the platform, and some smaller individual app (non-suite) offerings... this is such a disappointment. I have known for a long time that the project was struggling, but I had never imagined it could be cancelled.

    I'm really upset I now have to keep using MS Office, but I do offer my extreme thanks to those people who have put work into the project so far... I'm sure they are more upset than me.

    - Nex

    --

    This sig has been deprecated.
  44. Can not say I am shocked by Logicdisorder · · Score: 1

    I read awhile ago that Sun and Apple were talking about this and it was pretty clear Apple was not fused about getting OO working %100 in OSX. And now with there own one coming out I can see why.

    --
    "The most dangerous creation of any society is that man who has nothing to lose." - James Baldwin, American author
  45. FLAMEBAIT? by Chordonblue · · Score: 1

    Why? I thought this also. I think that iWork might've been the final 'push' to this decision...

    --
    "...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."
  46. X11 not a default install for OS X by pbooktebo · · Score: 3, Informative

    One problem with this is that X11 is not installed by default in Panther. You have to choose "Customize" and then click on X11. As most people don't know what it is for, most will not install it. This, more than perhaps anything else, is a hurdle for basic Mac users.

    I really was hoping for an Aqua port that worked well. X11 is just a bit of a pain for those who thrive on Apple's consistent UI.

    iWork looks nice (I played with it more than a bit at MacWorld this week), but I would prefer OO in Aqua (Pages, to me, seems more of a page layout tool than simple text editor that replaces Word).

    In short, there's still plenty of options (even TextEdit is a fine basic editor), but I had really been hoping this would come through. Let's hope that things may change and a port comes through in the next few years.

    1. Re:X11 not a default install for OS X by Anonymous Coward · · Score: 0

      Try NeoOffice/J. You can use it right now.

  47. Re:WiApple now getting into the office suite arena by Anonymous Coward · · Score: 1, Insightful
    With Apple now getting into the office suite arena, I'm far more inclined to buy it then get the free Open Office anyways.

    Yes, I'm willing to pay for superior alternatives.


    I like Apple stuff too, but this is just stupid rapid fanboyism.

    1) Do you have iWork yet? Can you say what about it makes it "superior"

    2) What part of the "superior" iWork replaces the spreadsheet functionality of OpenOffice.org?

    Undoubtedly, the iWork stuff is going to fit in with the Mac "experience" flawlessly, but to say that there is no value to OOo now is ridiculous. I haven't seen any indication of iWork's MS office compatibility, have you? That tends to be a fairly important part of an office suite these days.

  48. GCJ by alext · · Score: 1

    GCJ

  49. thanks alot by Anonymous Coward · · Score: 0

    for stringing us along!

  50. Re:good Mod parent down by aristotle-dude · · Score: 4, Informative
    Even though you are trolling, I'm going to attempt to educate you a bit about Apple's relationship with open source.

    http://www.apple.com/opensource/

    How do you like the contributions to KHTML that Apple provided? What about the PPC additions to GCC?

    They are fully compliant with the licenses of the software they use and modify. Did they have to give the Streaming Server to Open Source? No. Did they have to open source Rendezvous? No.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  51. The difficulties by killa62 · · Score: 1

    The licensing, political, and fundamental engineering difficulties=introduction of iLife and paper and stuff...

  52. Eh, no big deal by Durandal64 · · Score: 3, Insightful

    They wouldn't be able to do it right anyway. Seriously, a lot of people are under the misconception that Aqua is a set of nifty-looking widgets. It's an interface standard for clean apps.

    If your app has some shitty Office-like toolbar consisting of a row of 20 NSButtons, that's a shitty design. If your app's preferences are organized into 3 rows of 10 tabs each, that's a shitty design. If you can find the same function in 4 different places, that's a shitty design. Doesn't matter if it has an Aqua titlebar and Aqua buttons. Look to Office 2004 as an example of how Aqua cannot save fundamentally bad UI design. The OO.org guys would've just made the same mistake.

    1. Re:Eh, no big deal by Guy+Harris · · Score: 2, Informative
      Seriously, a lot of people are under the misconception that Aqua is a set of nifty-looking widgets. It's an interface standard for clean apps.

      The Apple Human Interface Guidelines, to be precise.

      I don't know whether all the issues you mention are described there, though - I didn't see anything that addressed the number of toolbar buttons, but it does give other recommendations for toolbars, so if by "a row of 20 NSButtons" you mean "something just using a row of NSButtons rather than using NSToolbar", doing the latter might give you toolbar behavior suggested in the Human Interface Guidelines that you wouldn't get with a row of NSButtons.

      Now, the GNOME Human Interface Guidelines 2.0 does recommend not having too much in your toolbar in the section on toolbars:

      Guidelines
      • Place only the most commonly-used application functions on your toolbars. Don't just add buttons for every menu item.

      The KDE User Interface Guidelines doesn't say anything about keeping the number of toolbar items down in its section on toolbars - in fact, it gives a list of items that should be in the toolbar if you have them in menus, so it might recommend increasing the number of toolbar items. (I think NSToolbar might give you a toolbar that can be customized, so you can have a set of buttons that the user could add to the toolbar if they wanted to, without having them in the default toolbar; the user can also remove items from a customizable toolbar.)

      To add one more online HIG to the collection, the Windows Official Guidelines for User Interface Developers and Designers doesn't recommend, in its section on toolbars, that you keep the toolbar from being too cluttered, and its examples do have a number of buttons; it does recommend that you let the user configure it, at least.

    2. Re:Eh, no big deal by sugar+and+acid · · Score: 2, Insightful

      Wordprocessors and spreadsheets are complicated applications, and at some point trying to simplify things fails and you have to increase the complexity of the UI to provide functionality. Wordprocessors have always had the toolbars with a collection of buttons providing various functions and access to other toolbars along the top of the screen. And iWork follows this model to some extent to.

      It is either have those buttons in a toolbar somewhere for easy access to common functions or waste time opening the top level menus, or learn obscure shortcut keys.

      Look at some other complicated applications, say photoshop. This has a huge number of complicated toolbars. At some point you have to learn what each icon in the toolbar means. And their is no way to get around it.

      I have never understood the logic that says having more than one way of doing something is bad UI. It would seem to me to be benificial to finding functions quickly if their is more than one place to find them.

      Having multiple tabs in preferences. This kind of design, keeps all preferences in one preferences window, and clearly distinguishes between them by the name on the tab. The other common way is to have Icons in a folder, like the OSX system preferences which has a downside of having to return to the main window to access another preference pane, or something like a firefoz/mozilla style tree with nested preference panels under top level tabs which is probably the best, but can be frustrating at times when you are trying to track down the exact right preference panel if a preference doesn't fit neatly into one of the top level tab definitions.

    3. Re:Eh, no big deal by Durandal64 · · Score: 1
      I don't know whether all the issues you mention are described there, though - I didn't see anything that addressed the number of toolbar buttons, but it does give other recommendations for toolbars, so if by "a row of 20 NSButtons" you mean "something just using a row of NSButtons rather than using NSToolbar", doing the latter might give you toolbar behavior suggested in the Human Interface Guidelines that you wouldn't get with a row of NSButtons.
      Exactly. And, the last time I tried NeoOffice, it did this same thing. It used a non-standard toolbar that had Aqua "drapes," but was clunky and had way too many functions.

      And yes, NSToolbar will give you a fully customizable toolbar via drag-and-drop.

      But I wasn't really ranting on interface guidelines. Most of them make sense, from the HIG to Gnome's, KDE's and Windows'. But most app developers simply don't follow them, not even the people who write them. Apple, for example, keeps finding new excuses to use the awful brushed metal appearance for apps which have no need for it. Microsoft loads up toolbars with hoards of shit, and the interface for customizing those toolbars just blows. Every time I try setting up a customizable toolbar in Word, I have to hunt through about 10,000 different options before I find what I'm looking for. That's frustrating and just fucking dumb.

      And frankly, having 32x32 pixel toolbar items is a stupid idea held over from when there was too little screen realestate to implement something more effective. On today's high-resolution monitors, the icons are way too small, there are no static text labels and they're difficult to target. Apple had it right when they introduced 128x128 toolbar icons.
    4. Re:Eh, no big deal by Durandal64 · · Score: 1

      One word: palettes.

      As to the multiple rows of tabs, it's a poor design. I always managed to confuse the fuck out of myself when trying to wander through an Office app's preferences. When I click a tab in one row, the whole layout of the window changes. How much sense does that make? Apple has a system for application preferences where each preferences is a toolbar icon that is ever-present in whatever form the user wants (icon and text, icon only, text only, or just not there at all). And it works a whole lot nicer. You have each category dilineated by an icon rather than some tab, and you don't end up playing musical tabs every time you switch categories.

  53. Isn't Aqua Open Source? by Anonymous Coward · · Score: 0

    Since Apple is now friendly to hackers by having made OS/X and Aqua open, it should be ease to port Open Office to the Mac.

    1. Re:Isn't Aqua Open Source? by mabinogi · · Score: 1

      no, not it's not.

      And even if it was, being open source doesn't make some magical open source porting fairy make the porting easy.

      If there's a mismatch between the way things work, then it's not gong to be easy, no matter how much source access you have.

      --
      Advanced users are users too!
  54. Openoffice is slow? by alassiry · · Score: 2

    Openoffice is a great office suite, but it reminds me of mozilla, what we really need is a set of re-engineered applications with the same core (smaller-lighter-easier just like mozilla's firefox and thunderbird).

    --
    _________________________________________________ Just another Crazy Linux/Perl Maniac
  55. One other thing by ThousandStars · · Score: 2, Informative
    I hate to reply to my own post, but the other thing to keep in mind is that license politics played some role too, which didn't help. See this post in the OOo mailing list. I'm speaking specifically of these paragraphs:
    I thought that, apart from bug-fixing the 1.1.x effort, we would get together with the 2.0 tree, and start adding the Aqua gui on the basis what Ed and Patrick have done and learned. Now that Ed and Patrick have problems with the license that is imposed, that does not change most of this arrangement. Only their Gui-code would reside outside the official OpenOffice tree. NeoOffice imports the complete OpenOffice tree, and builds on top of that.

    So there could be as many as three OS X versions -- NeoOffice/J, X11 and "native." With different license possibilities for each. It gives me a headache just trying to keep it straight on paper, let alone trying to somehow coordinate all three of these efforts.

  56. Re:Of course they won't by Anonymous Coward · · Score: 0

    If Microsoft has so far restrained itself from suing the OOo developers (though, from what I've heard they've come close), why would Apple do it?

    well Apple is actually one of the more trigger-happy companies when it comes to suing. Even suing their own fan web sites for talking about coming products (ref. earlier /. story)

  57. Has anyone tried hiring a MacOS X developer? by jbn-o · · Score: 2, Interesting

    Has anyone tried hiring a MacOS X developer or consultant to port OO.org to MacOS X? It seems like a native OO.org isn't really desired if all people do is complain that a nativa MacOS X OO.o doesn't exist and someone else won't do the work for free. Perhaps a bunch of MacOS X users would be willing to chip in US$20 to pay for something that can get the ball rolling.

    1. Re:Has anyone tried hiring a MacOS X developer? by Anonymous Coward · · Score: 0

      I'd chip in $20 for a port, if it could actually open more versions of Word documents than Apple's TextEdit. Hmm, let's see: "Free with the computer vs $20 for reduced functionality"; tough choice...

      Besides, isn't asking Mac users to pay for the same product everyone else gets free a disincentive to use the software? And why is it so important to use the Open Office code base, if Apple can make something that's more user friendly while using the same open standard formats? I thought the standards were more important than the software using them...

  58. iWork by Anonymous Coward · · Score: 0, Redundant

    Heard about iWork! It totaly did it! Nothing more, nothing less.

  59. [OT] Sig by HeghmoH · · Score: 1

    Given the fact that a pyramid scheme is guaranteed to leave the vast majority of the people who get sucked into it with absolutely nothing, do you actually expect you have a good chance to get your free stuff? What makes you luckier than the next guy?

    --
    Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
    1. Re:[OT] Sig by Anonymous Coward · · Score: 0

      Wave a "free" Apple product out in front of the zealots, and logic goes right out the window.

  60. Maybe Apple doesn't care! by Theovon · · Score: 2, Interesting

    There is a certain amount of logic to the idea that they should focus on X11. But the truth is that if Apple really wanted an Aqua version, there would be one. Apple has been known to be rather snobby, and they're probably suffering a bit from the NIH complex, because they're working on their own productivity suite.

    It's kinda like expecting really good support from Apple for Mozilla when they'd rather push Safari.

    1. Re:Maybe Apple doesn't care! by shawnce · · Score: 4, Informative

      Just because the didn't pick your pet horse...

      It's kinda like expecting really good support from Apple for Mozilla when they'd rather push Safari

      You do know that Safari is built using KHTML & KJS (both part of KDE) and Apple is supporting them by feeding back bug fixes, enhancements and optimizations.

      Also they have made those frameworks available to other developers, outside of Safari, on Mac OS X by bundling them with the OS distribution.

      WebCore

    2. Re:Maybe Apple doesn't care! by shawnce · · Score: 1

      Oh I should point out that WebCore is exposed to developers via the Web Kit framework.

  61. Mac users live and die by their aesthetic by Anonymous Coward · · Score: 1, Funny

    It's not native to Aqua and it shows. Mac people like polished apps

    Me: "Check out this cool new Open Source iPod app. It's on Linux and Windows too, I think."

    Them: "Neat. It does a lot more than iTunes. Flac and Ogg transcoding? Cool. Syncing to multiple machines? Wicked. Built-in web server to browse/share my collection online? Awesome. Wish I could use it too."

    Me: "Hey, here's the OSX version. You can use it!"

    Them: "Hmmm. The buttons look crappier than iTunes. Scroll bars look weird. I'll keep using iTunes, thanks."

    1. Re:Mac users live and die by their aesthetic by Anonymous Coward · · Score: 0

      >>Me: "Check out this cool new Open Source iPod app. It's on Linux and Windows too, I think."

      Them: "Neat. It does a lot more than iTunes. Flac and Ogg transcoding? Cool. Syncing to multiple machines? Wicked. Built-in web server to browse/share my collection online? Awesome. Wish I could use it too."

      I call bullshit.

      1. Most users have never heard of FLAC or Ogg and don't care. They know what mp3's are and maybe they have heard of Windows Media and MPEG-4. They will use the default presets (AAC/mp4 in iTunes) which work with their iPod, or switch to mp3 with a different player (although you just said 'iPod app'.) AAC and Apple Lossless are functionally equivalent to FLAC and Ogg and (amazing!) both are supported on the iPod.

      2. Syncing isn't much of a need on a network, especially if you have an iPod. Why not just use iTunes' built-in sharing features? How smart is it to maintain multiple (identical) music libraries anyway? If they are different it might make sense, except the syncing requirement goes away.

      3. Web server huh? Gee, OS X ships with Apache- think that's good enough? Of course, it isn't some lightweight potential security hole, but hey it's a great feature right? See my answer #2 for more details.

      4. iTunes is a pretty good application- its in active development, is easy to use, has decent features (things that users actually WANT instead of fluff) and is a well-behaved Macintosh program. It also supports things like the iTunes Music Store, iLife, QuickTime, AppleScript, Keychain, Altivec, Airport Express and Rendezvous. Finally, there are lots of add-on scripts and plug-ins available, none of which can be found for your Open Source marvel.

      Don't get me wrong, I am all for the idea of Open Source software development. Just don't be stupid by pushing a program that is inferior AND has a suckass interface over a highly-rated and popular program that actually serves the users needs.

  62. hmm by Slipped_Disk · · Score: 2, Interesting

    Well, I do understand their reasoning, and as others have pointed out, Apple will always be a "niche market" for OOo.

    Of course, as a mac user I am somewhat pissed off that the platform is being relegated to the status of a second-class citizen. OSX X11 takes quite a while to start up, and incurs a NOTICABLE overhead compared to the Windows native version of OpenOffice.
    Also, on a platform that makes it name based on simplicity, having to install X11, with its cumbersome (and possibly confusing to users with no *NIX familiarity) configuration choices may drive users away.

    On the flip side of this coin, Apple's iWork suite may get a boost from this (OpenOffice will never be native, iWork is native & integrates seamlessly with the rest of the iEverything world), which will help Apple's bottom line - so this isn't all bad.

    Still, I was hoping for a native OpenOffice in v 2.0. Cest' la vie.

    --
    /~mikeg
    1. Re:hmm by DarkKnightRadick · · Score: 1, Interesting

      One, it's c'est la vie :p

      Two, don't get pissed at OOo, talk to Apple. If Apple wants other apps to be able to work natively on its platform, they're going to have to open up. I don't see how anyone expects significant work to be done when everything has to be reversed engineered. This is what pisses me off about people who complain about GAIM's lack of options compared to the protocol-native clients for each service (AIM, Yahoo!, ICQ, Jabber, IRC, etc.).

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    2. Re:hmm by Yosho · · Score: 1

      What exactly do you want them to "open up"? Their system documentation is quite extensive.

      --
      Karma: Terrifying (mostly affected by atrocities you've committed)
    3. Re:hmm by LMariachi · · Score: 1
      Two, don't get pissed at OOo, talk to Apple. If Apple wants other apps to be able to work natively on its platform, they're going to have to open up. I don't see how anyone expects significant work to be done when everything has to be reversed engineered.

      What the hell are you talking about? Apple's IDE is free beer, and the vast majority of its APIs are published. Reverse-engineering is only necessary if you want to, say, change the fundamental behavior of the Finder (examples), or interface with the occasional inexplicably undocumented API (e.g. iSync.) You certainly don't need it to write a native office suite.

  63. On java applications by Craig+Ringer · · Score: 3, Interesting

    I personally feel that while in an ideal world Java would be good solution, I'm not convinced its the answer to all the world's software portability problems.

    ANSI C is very portable. It's also utterly useless for things like GUI applications, unless you feel that writing your own GUI toolkit and low-level system interface is fun. Portability problems are introduced by the system APIs and GUI toolkits used to do interesting things - not by the language.

    Java provides a standard GUI toolkit, plus some very good abstractions of platform APIs. If, however, you want to go beyond those platform APIs, you're back at square 1 - re-implementing the platform service, or writing an interface to it to abstract it for cross platform use. Bang! Your Java app just ceased to be portable.

    To get the sort of OS integration the mac users rant about, I'd be very surprised if you didn't have to write a few extensions for platform API interfaces.

    Another issue with Java is the GUI toolkit. IMO Swing is clunky, ugly, and gives everybody the SAME poor "user experience". Even tools like JEdit that I've seen held up as examples of how well things can work feel pretty painful in my experience when compared to a native app. I'd find Java a lot more interesting if Sun would bite the bullet and put their weight behind SWT.

    In the mean time, I'll be sticking to C++ and Qt - IMO the next best thing for portability, and much better when it comes to GUI work. Of course, Qt borrows liberally from the Java APIs where they're good, and I'll for that.

    As for Mozilla, I'm pretty sure they implement their own GUI toolkit - not a window system. I'm with you on the slow RAM hog, though.

    I'm not one to argue that Java is fast, but IMO until they Sun addresses the Swing albatross Java won't be a viable first choice for implementing serious GUI applications where "user experience" is a major concern.

  64. OOo on Mac is dead for multi-byte users then by Anonymous Coward · · Score: 0

    I think more "real" concern is that there's no native language input support though.

    For example, there's no practical way of using Japanese input system like ATOK and Kotoeri under X11 app, and even simply making it display Japanese, I have to tweak a lot of different files, and then it looks ugly as font choices are pretty limited to fonts that sucks. (beside, I actually ahve to get special font, just for it -- can't use built in fonts.)

    So, for most Japanese users (or Chinese, Korean, or others who use many two byte languages, OpenOffice won't ever be a viable choice on Mac.

  65. Compiling Java to native object code by Craig+Ringer · · Score: 1

    Many others have mentioned GCJ, and that's all fine. Personally, I'm not convinced compiling to native code is necessary a lot of the time. The JVM is awfully fast for most tasks already (though RAM consumption can be an issue).

    My (admittedly limited) experience has been that most of the performance issues with Java have been with Swing. I'd be interested in seeing how that was affected by native compilation, but I'm not aware of any project that can do that yet. A native _implementation_ of Swing for a platform would interest me more.

    1. Re:Compiling Java to native object code by Geoffreyerffoeg · · Score: 1

      Second, related question that I was kinda implying with native compilation:

      Can programs running under the VM behave like native programs? That is, keep the same UI (preferably through compiler-added system calls instead of through copied bitmaps); assocate with filetypes properly; interface with other programs as if they were native applications, including exposed APIs, basic scripting (on Mac OS), possibly OLE (on Windows); run from an executable stub and behave taskbar/Dock-wise like a regular application; and so forth?

  66. I DO NOT AGREE! reasons: by cies · · Score: 0

    I do not agree!

    Qt apps can look quite nice on MacOSX, okay it OpenWriter will not look as native as Apple's own 'Pages'.

    Pages:
    http://www.apple.com/iwork/pages/word.html

    Native Mac apps often have different GUI layouting. An as you say...

    > Mac people like polished apps ... Mac users like that.

    OSX apps do not just use Aqua for the Widgets, they have a completely diferent approach to GUI design!

    I think the Qt NWF http://people.redhat.com/dcbw/ooo-nwf.html
    will be a good basis for a version of OOo that blends in with MasOSX, since:
    - Qt uses more native Aqua routines in every new release
    - if there is a MacOSX version of OOo using Qt-lib then it will be much easier to just ajust the GUI of OOo that it matches the OSX feel (i.e. get some nice big icon in that toolbar)

    Conclusion:
    Yes, I do have confidence in the Qt road to a MasOSX port of OOo, because it is a much better startingpoint than the current OOo version running on OSX:

    http://www.openoffice.org/screenshots/images/swrit er_osx.png

    Which is plain ugly (as you can see) and needs X11 AFAIK.

    Just see how KOffice (using Qt) is doing in comparison:
    http://ranger.befunk.com/screenshots/qt-mac-kword- 20040101.png
    And this is only a proof-of-concept kind of quick-port. No addional GUI refactoring has been done! Since that is what every GUI apps that is ported to OSX needs!

    Last screenshot to prove my last statements:
    http://www.openoffice.org/screenshots/images/compa re_ms_osx.png
    This is the current difference between OOoWriter-for-OSX an OSX' most used wordprocessor: MS Word. This prove 2 things IMHO:
    - OSX users do massively use badly intergrated apps (i.e. MS Word)
    - OOo cant get much worse...

    _cies.

  67. Re:X11 Aqua? by AddressException · · Score: 1

    Surely if they maintain their positioning and colouring, then one doesn't need the icons at all.

    In graphite mode, they may be all the same colour, but are still in the appropriate positions.

    If I know the leftmost button closes the window, what does it matter if there's an icon there or not?

  68. Not Flamebait by eomnimedia · · Score: 1

    If you listen to Steve Jobs' presentation where he describes iWork, notice he says that they are hoping iWork will entirely replace AppleWorks. For those in the know, AppleWorks integrates a word processor and spreadsheet (and other stuff).

    iWork is the potential M$ Office killer on the Mac platform. Is it free and open source? No, but Mac folks will stick to iWork like krazyglue in a nail salon.

    If you want free and Aqua, NeoOffice or AbiWord are the way to go.

  69. MS Office by Saeed+al-Sahaf · · Score: 0, Troll

    Microsoft to Apple: "OWNED!"

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  70. Re:Need help w/ my Mac by Mr.+Cancelled · · Score: 1, Insightful

    No offence, but your problem seems to be much more a user issue, than a computer one.

    I'm a fairly recent Mac convert (who still works with x86 boxes), but the Mac has done nothing but continue to impress me with both its speed, and with it's depth (Most of the time, if you're still finding new capabilities with an app after 6 months of usage, it's indicative of a poorly designed GUI. With the Mac, there's just so damn many features/capabilities that they're often not evident to the casual user).

    The file copying example you refer to could be many things, from software conflicts, to physical issues with the memory. There's just so many variables, it's not really answerable without more details (not that I'm trying to troubleshoot it... Just pointing out that your complaint can be applied just about any PC, dependant upon circumstances.). My guess is that your slow Mac may be running less than the optimal amount of memory (OSX is much more "memory hungy" than any MS OS).

    I know that in my case. my Mac often copies small to medium sized files (less than 40mb) so quickly, I'll have to re-verify that the copy actually took place. And this is on a dual 2ghz Mac, with 512mb ram (which really needs to be upped to 2.5gb ASAP - Speed should increase quite a bit just getting it up to 1gb, as right now I've got a lot of disk swappin' going on).

    I'm also unsure as to your Mac experience from your posting, but daily use of my Mac continues to improve my efficiency. You seem to be growing more frustrated with your Mac experience (which begs the question of why you're using it - Toss it my way if you'd like, and I'll put it good use!), whereas increased usage continually reassures me that my Mac was money well spent (and believe you me, it took me awhile to finaly take the plunge and buy me a Mac).

    It's all been said before, but features which make the Mac great are many: Fast (contrary to your experiences), well thought out GUI and features, it's incredably easy to get to grips with just about any Mac program, and once you're ready, most apps offer a small ton of features which increases their value/longetivity even further.

    Then of course, we have its Unix capabilities, Applescript, built in PHP, Perl, Ruby, Java, and all the dev tools one could ask for. All capable of system programming.

    Then there's those programs which which make the Mac stand out so much over its competition: Delicious Monsters Library, the very impressive Platypus, and of course the "can't do without" Quicksilver.

    I won't turn into a gloating "Mac Fanboy" here, but the Mac is a power users dream. Its power and efficiency continues to amaze me. I only hope that the MacMini allows "John Q. Public" to experience the joy that is OSX first-hand.

  71. Swing is NOT Slow, and Ugly..... by tonywestonuk · · Score: 1

    But, if people don't know how to program it..... This is what it becomes...

    Take forexample this demo program here:

    http://weston.kicks-ass.net/imsg.jnlp (Java webstart Required)

    There is a 1/4 million row Table in this app. Just try doing this in any Gui toolkit rather than swing?!

    Cheers,
    Tony.

    1. Re:Swing is NOT Slow, and Ugly..... by Anonymous Coward · · Score: 0

      Arrow keys do not scroll the table. Page keys don't scroll the table. Clicking the scroll bar to move a single cell takes a little less than one second with a 2.1GHz Thoroughbred B to complete. Scrolling in the table is slow and jarring. One cannot select objects through multiple pages in the table.

      In short your demo sucks pretty hard.

    2. Re:Swing is NOT Slow, and Ugly..... by Anonymous Coward · · Score: 0

      I just did it in Python using wxWidgets (wxPython) in a couple of minutes. wxListCtrl allows for a virtual list size, and combined with a decent database caching algorithm it would be damned fast, and responsive to all normal keyboard controls - unlike your demo. I don't have a database with 250000 records handy, so I just used strings like "This is item #xxx" - the hard part would be in guessing what the user is likely to want next, and really, if you're presenting a quarter of a million records to someone with the expectation of them scrolling through it to find what they want, your app needs redesigning anyway.

      Anything that can be done in Java can be done in another language. There's nothing magical about it.

    3. Re:Swing is NOT Slow, and Ugly..... by Craig+Ringer · · Score: 1

      I can't seem to run it - I may not have the JVM installed on my laptop. No big deal.

      The only other toolkit I know of that can do that is Qt, and even then I think you have to jump through a few hoops. That's a pretty nice table widget.

      Individual bits of Swing are pretty good, and I think a lot of the API is nice, with a good collection of widgets (if often rather verbose). It's just that the few non-trivial Swing apps I've used have been very sluggish, and really haven't fitted in with the rest of the OS's widget set. "Java 5" - jvm 1.5 - helps a lot with looks, but at least on *nix Swing is still very much the in the distinctive knobbly sun style. I don't know if they've made a big and much needed performance improvement for Swing in 1.5 too - I no longer use any Swing-based apps regularly, having found better alternatives.

      I'd be very interested in seeing a non-trivial app written in Swing that had a UI as snappy and responsive as one written in, say, Qt.

    4. Re:Swing is NOT Slow, and Ugly..... by Anonymous Coward · · Score: 0

      You can't even run it, but you can say that only one other toolkit can "do that"? What, show a list of 250,000 items? Bollocks. Name one GUI toolkit that CAN'T do that!

  72. What's the point? by vijayiyer · · Score: 3, Insightful

    On the Mac platform, there's Microsoft Office available natively, and now Keynote and Pages. OpenOffice arguably competes with MS Office essentially only on the basis of price, not by being better. However, people who buy macs have already demonstrated a willingness to pay a premium so that things "work". Therefore, it's not worth the manpower to maintain a native port for a small percentage of a small market. I keep MS office around solely for opening other people's files, and use LaTeX, Matlab, and the Adobe products for preparing documents.

    1. Re:What's the point? by burns210 · · Score: 1

      Choice is a good thing. Competition, is a good thing.

  73. Apple cares by poemofatic · · Score: 1

    about usability, consistent interfaces, and Human Interface Guidelines.

    Open Source cares about Programmer Interface Guidelenes, or rather Tweaker Interface Guidelines. And as usability isn't something that you can bolt on, Apple has to roll their own. And the clincher argument is those who think "Aquafication" consists of getting translucent dialogs into the app.

    My mother can use apple software pretty well, but no way in hell can she use OOo or MS office. We'll see about iWorks.

    --

    When in doubt, have a man come through a door with a gun in his hand.

  74. Wrong - signed OpenOffice.org developer by oo_waratah · · Score: 4, Informative

    Firstly the anouncement is purely for the Version 2.0 codeline. This is an excellent idea because it focusses everyones attention on getting the best Mac Port possible in the timeframe, not scattering resources trying many things.

    The Mac effort is one of the most intense efforts in OOo today by FOSS developers. There are many volunteers and almost daily offers for additional help. So as they say, news of my (OOo) death is premature.

    Ultimately the NEO office port will be merged with the mainline OOo. At this stage there are some issues with doing this cleanly so it is managed (extremely well) by a third party. This will continue until the whole thing becomes clean enough to merge. Try NEO if that works for you that is still a win for OOo in my book, I do not care about the brand name frankly my effort in making OOo better in a number of small ways is paying off, I am proud.

    Finally do not forget that this is an Open Source development. Any predictions that something will not happen are just very unlikely because someone with a bee in his or her bonnet will do what you do not expect. If you want an Aqua port more you want a serious stable Office Suite using X on Mac then please by all means, do that.

    1. Re:Wrong - signed OpenOffice.org developer by cyberphotographer · · Score: 0
      • So as they say, news of my (OOo) death is premature.
      Originally Twain wrote 'reports of my death are exaggerated'. It's the way you tell 'em...
  75. MAC and Linux by DanielJS · · Score: 0

    I like the MAC hardware, I hate OSX. I have two MACs . A new one (g5) and an older one. I have Linux on both of them. So much better than the bloated OSX.

  76. Just an idea... by the_true_cirrus · · Score: 1
    Ok, AFAIK the specs for OpenOffice XML file formats are freely and openly available (from OASIS, I think), so why does no one write a new Office Suite from scratch (or update an existing one) that supports them and give a proper Aqua interface?

    When rumors started spreading that Apple was making a new Office suite I was really really hoping they'd make it open and save using the standardised OpenOffice formats. Imagine - document compatible with OOo (which would have benefitted both Apple and OOo) yet a proper OS X interface! How sweet would that be?!? I'm so disappointed that they didn't do it! Likewise I think it's a shame that no other non-OOo programs (correct me here if I'm wrong!) fully support the OpenOffice formats.

    OpenOffice is very nice, but like MS Office it has loads of features that I as a casual office app user rarely need. It would be great if I had a choice of office apps - some fast and basic ones for people like me, some feature rich ones like OOo for power users and maybe some inbetween too.

    iWork, Abiword, K-Office, Gnumeric and of course OpenOffice/NeoOffice would all be so much more useful if they used compatible formats. And since OOo's formats have already been submitted to a standards organisation they seem a good one to use!

    Ah well, one can dream....

  77. Dock Icon? by SHEENmaster · · Score: 1

    Why can't X11 apps get dock icons in Aqua as they do in GNUStep? I realize Aqua's dock format isn't as powerful, but there has to be enough common ground for X11 apps to have their own icons.

    --
    You can't judge a book by the way it wears its hair.
  78. apple killing 3rd party developers by Jah+Shaka · · Score: 0

    now not even open source guys want to support apple - let them do it all themselves and cater to the preppy's of the world - the rest of us will use linux :)

    1. Re:apple killing 3rd party developers by Anonymous Coward · · Score: 0

      let them do it all themselves and cater to the preppy's of the world

      After all, freedom isn't a basic human right, it's just a fashion accessory for people with no sense of style.

    2. Re:Apple killing 3rd party developers by hunterx11 · · Score: 1
      --
      English is easier said than done.
    3. Re:apple killing 3rd party developers by Anonymous Coward · · Score: 0

      After all, freedom isn't a basic human right, it's just a fashion accessory for people with no sense of style.

      Well, it isn't - a 'basic human right'. It's a human desire - and whether it's basic or not is debatable. Society only concedes various amounts of freedom for the sake of efficiency. Case to the point: laws (you're 'free' to break them, but you're not 'free' to escape the consequence if they jail you)

    4. Re:apple killing 3rd party developers by Anonymous Coward · · Score: 0

      It's one of many human desires, and not always on...

      Or are we talking Fries?

  79. Programmer who wrote this story is ED from Neo/J! by Anonymous Coward · · Score: 1, Informative

    There ARE still plans to do OpenOffice.org 2.0 in Aqua. It's just going to be done as NeoOffice/J and not as an official OpenOffice.org port. Which is fine because the people who WERE working on the official OO.o port are now working on NeoOffice/J.

    So it's the same thing. The guy who wrote that recent post on OO.o linked in the article *IS* one of the two main NeoOffice/J programmers.

    This is a pretty misleading story headline.

  80. Re:Need help w/ my Mac by Anonymous Coward · · Score: 0

    Have you actually turned the computer on?

    You deserve to be flamed for such a waste of a post that obviously is just an excuse to bitch about the Mac for no real reasons whatsoever.

  81. Re:Need help w/ my Mac by Anonymous Coward · · Score: 0

    A response to one of the oldest trolls ever is insightful?

  82. Apple killing 3rd party developers by Jah+Shaka · · Score: 0

    reality is apple no longer encourages 3rd party developers on their platform... they have a 'holier than thou we can do it ourself' - open source is all about collaboration and if apple wont help then why should anyone help them?

  83. Re:X11 Aqua? by TheRaven64 · · Score: 1
    remember, OOo is very much sun backed, the company who believe that a native java UI (Swing) is better than tight integration with the base OS.

    A swing UI with a metal look and feel is often better than a UI with a native look and a developer's-platform-of-choice feel, since at least this way Java apps are consistent (at least in theory) and the user gets visual clues that they are different from the rest of the system (as happens when running Mac classic apps on OS X, for example).

    --
    I am TheRaven on Soylent News
  84. Re:WiApple now getting into the office suite arena by Guy+Harris · · Score: 2, Informative
    I haven't seen any indication of iWork's MS office compatibility, have you?

    Yes - the Compatibility page for Pages says

    Simply Opens AppleWorks and Word Files
    In fact, here's how easy it is to open an AppleWorks or Word document in Pages: find the document you'd like to open and drag it onto the icon for Pages in the dock or on your hard drive. If you already have Pages running, you could also simply pull down the File menu and choose Open. The dialog lists AppleWorks, Word, Text Edit and documents saved in Rich Text Format (RTF), making it, once again, easy to select and open them. And, by the way, those Word and RTF documents could be PC documents. Pages doesn't care.

    How will they look when you open them? Just like they did in your other word processor. Wherever possible, Pages preserves virtually all of the formatting they had. What's more, if you assigned styles in a Microsoft Word document, Pages will import them right along with the text. Now that's compatibility.

    and the Compatibility page for Keynote 2 has a table showing that it can read and write PowerPoint presentations.

    Nothing about Excel spreadsheets, but given that iWork doesn't have a spreadsheet....

  85. C is standardized, not portable. by rjh · · Score: 1

    ANSI C isn't portable; it's only standardized.

    Take a look at a wonderful list of C weirdness which is mandated by the ANSI C89 standard, but which is supported spottily across different platforms.

    ANSI C doesn't even specify how large a char should be, for crying out loud. C is many things, but portable ain't one of them. Try taking a codebase written in ANSI C for an embedded microprocessor and compile it for Big Iron. Dollars to donuts says that somewhere in your codebase there are going to be implicit assumptions (about the size of a word, about how memory is allocated, etc.) which are going to be wildly platform-dependent.

    ANSI C is standardized, which for some reason people confuse with being portable.

  86. Calm down... by Anonymous Coward · · Score: 0

    All this update to the timeline is saying is that the Aqua porting effort is being focused in NeoOffice/J. The headline that "Aqua OpenOffice 2.0 Cancelled" is misleading..

    You'll get your 2.0, it'll just be called NeoOffice/J 2.0.

    The guy who posted that update on OO.o's website is one of the two primary programmers for NeoOffice/J btw. He's just saying "I'm working over here instead..." but it's being taken WAY out of context.

  87. Re:More Mac Zealotry by Anonymous Coward · · Score: 0

    iSee your point.

  88. Reasons by saterdaies · · Score: 5, Insightful

    First, this isn't a surprise. They announced a while back that they might not even have an X11 port of OOo version 2 for OS X. While it is kinda crappy that they are completely abandoning it, there isn't much they can do if they don't have the developers.

    As for their reasoning that an X11 port is better, it is completely flawed. Firefox shows that reason 1 and 2 are bogus as it is to market at the same time on all platforms with equal stability, reason 3 is actually a draw-back that they are trying to market as a feature (gotta love the Microsoft-ian logic there), and the last one is basically a way of stating that we already have an X11 port so it means less work for us. If any of these were valid points, Windows users would be running it in Cygwin right now. They're all just a way of saying "we don't care in the slightest about your platform, but we don't want to look like we don't care." Frankly, if you don't care, that's cool. This is your work. You don't have to support Mac OS X if you don't want to. Anyone is free to come along and pick it up if they are interested. That's what is so great about free software. Just don't trip me and tell me you did it because I looked lonely and you thought I could use a hug from the ground.

    More importantly, OOo just isn't that good. It's amazingly slow and ugly, uses a fileformat that takes forever to save and creates huge files, and just plain worse than the other options out there. It's why there haven't been a lot of developers flocking to it from the Mac community. Something like Adium gets developers because it is the best. It's fully native, it's fast and clean, etc. There are a lot of other OSS projects on the Mac as well that are all good projects. OOo, by comparison, seems to employ a pretty terrible codebase and interface. While it has more features than AbiWord, AbiWord is clearly a better base. When you add Mac uses tendency toward well-done software with the fact that Mac users also don't mind paying for software as much as users of other platforms (lets face it, even Windows users don't pay for software - they pirate it), it means that OOo on the Mac doesn't have as much interest.

    One of the big problems is that OOo only has the "free" aspect to draw users. WordPerfect Suite and Microsoft Office are still much, much better applications - this is coming from a user whose computer only has Ubuntu on it, not some OSS hater.

    I've come down pretty hard on OOo here, but as a long term Mac user and now an Ubuntu user who loves Gnome, OOo is just terrible. Now, if you want the most featured office suite available, OOo is a great option for you. For a user like myself, and most Mac users, the features of OOo don't make up for the bloat and interface. Things like AbiWord and Apple's new Pages are much more attractive options even though they do less. Hopefully, OOo will become better in the future (I've run some of the 2.0 previews and wasn't that happy). Maybe AbiWord and OOo will start to converge toward each other like mySQL and PostgreSQL. But until OOo cleans itself up a lot, there isn't going to be the interest needed to bring it to the Macintosh because of how Mac users like their applications to work.

    1. Re:Reasons by mkosmul · · Score: 1

      > More importantly, OOo just isn't that good. It's amazingly slow and ugly, uses a fileformat that takes forever to save and creates huge files,

      While I do agree that startup time and the non-standard GUI are major issues with OpenOffice, I don't understand your "huge files" argument. What are you comparing the sizes of files OOo produces to? My experience is OOo files are usually much smaller than their MS Office counterparts.

  89. Er, no, bad.. by Lysol · · Score: 1

    Yo, dude, Windows is the worst non-OSS friendly OS out there! Are you gonna say now that people should quit making free software for Windows?!

    Didn't think so and fyi, OS X has a hell of a lot more OSS under the hood arriving at your doorstep than M$ ever will. So I'd say this is, if anything, not good!

    Luckily NeoOffice/J will pick up the slack.

    1. Re:Er, no, bad.. by Anonymous Coward · · Score: 0

      Actually, Windows has a lot of OSS from BSD under the hood.

  90. Good riddance... by ztwilight · · Score: 1

    They should make the product better, not work on a half-baked Mac port. I can't stand to use office software anymore, and all because of bloat.

    --
    Who moved my sig?
    1. Re:Good riddance... by megabyte405 · · Score: 1

      AbiWord? www.abisource.com

      Just a word processor. Powerful, but not more than you need.

      disclaimer: I help out with qa and art a bit.

      --
      I recognize people by their sigs. Is that a bad thing?
  91. Re:WiApple now getting into the office suite arena by tverbeek · · Score: 1

    Calling iWork an "office suite" is a bit of a stretch. Yes, Keynote is roughly analogous to PowerPoint, but Pages is more of a publishing package (a la Publisher) than a direct replacement for Word/WordPerfect/OOoWriter/AbiWord, and there's no Excel/123/Quattro/OOoCalc/Gnumeric equivalent anywhere in the box.

    --
    http://alternatives.rzero.com/
  92. MOL by kardar · · Score: 1

    maconlinux.org

    You can run OS X from within Linux - you could even use a really really clean window manager (or an artsy one like Enlightement), perhaps "fullscreen" that OS X window on one virtual desktop, and then do other linux apps on other virtual desktops or something like that.

    Probably not the best idea for the cutting edge latest hardware, but it could probably breathe some new life into something a little less brand new. Interesting, anyway.

  93. Re:Need help w/ my Mac by kiddygrinder · · Score: 1

    This is a By-The-Book troll people. Move along, nothing to see here

    --
    This is a joke. I am joking. Joke joke joke.
  94. Your app is a great demonstration of my point by melted · · Score: 3, Insightful

    You should read Apple Human Interface Guidelines. For your reference, toolbars DO NOT look like this in Cocoa. Also, UI elements are not placed at random within Aqua. Apple Interface builder shows dynamic guides when you place controls, and these guides help you to comform to HIG. Items should be aligned. Push buttons should have descriptive text on them, there should be sufficient spacing between UI elements.

    Merely using Aqua controls is not enough.

    1. Re:Your app is a great demonstration of my point by danila · · Score: 1

      Another great demonstration of your point could be this screenshot. You can skin a Windows desktop, remove menus from Explorer and use a bunch of icons ripped from OS X, but it would still be a Windows desktop.

      Still, a properly Aqua-skinned application is better than one which is not even skinned. I don't understand why it's so hard to port OO.o even at that level.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    2. Re:Your app is a great demonstration of my point by Brandybuck · · Score: 1

      My point was that my application was a native application, *NOT* that it had Apple's imprimatur upon it. As such, I have plenty of company with other native Mac applications.

      With regards to my application, the Mac user has two choices. The first choice is to use my Qt/Aqua application as-is. The second choice is to wait until I aquire a Mac of my own and spend several months rewriting my application from the ground up specifically for the Mac. If yours is the second choice, be aware that you might be waiting a very long long time.

      --
      Don't blame me, I didn't vote for either of them!
  95. Re:MOD UP (+1 Truth) by Anonymous Coward · · Score: 0

    /me agrees; MOD PARENT UP

  96. File formats. by IGnatius+T+Foobar · · Score: 1

    Amazing ... all these posts and nobody is talking about file formats. What I'd like to see, is to have Apple's new office suite speak the OOo XML file formats. This would provide an even greater incentive for vendor-neutral formats to be used -- and then it won't matter if you're using OpenOffice or Apple iOffice (or iWhatever it's called now) because they'll all be interoperable.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
    1. Re:File formats. by Geof · · Score: 1

      Agreed. For me to use any word processor, the file format needs to be open, and it needs to be clean enough that I will always be able to get at my data. The cost of file format lock-in exceeds all other considerations.

      No matter what happens, I will *always* be able to get at my OO.o XML files on any platform, or convert them into another format. Furthermore, I can write scripts to extract whatever I need from my documents. I have a script which constructs a blog from regular OO.o files; in the future I'm considering doing something similar to build a comprehensive bibliography automatically from papers I write.

      I switched to Mac just recently; the two key considerations were the availability of native Unix development tools (e.g. Perl, Python, Apache, Ant) and of Open Office in the form of NeoOffice/J. If not for NeoOffice, I would be running Windows and Linux right now.

      Down the road, a standard XML document format could turn word processors into front-end user interfaces for all kinds of authoring, just as spreadsheets are often used as user-friendly front-ends to data processing software today. Apple should seriously consider supporting the OO.o file format standard.

  97. Re:X11 Aqua? by Anonymous Coward · · Score: 0

    Maybe if Apple fans could realize that 99.9% of the world doesn't use Aqua, then they could understand the wisdom behind Open Office's stance. Instead of complaining to the OO.o folks, they should complain to Apple. Apple should provide a killer X11 SDK which would allow porting of X11 apps to an Apple "look and feel". Apple is responsible for supplying the "magic", not OO.o.

  98. Has Apple abandoned 'traditional' computing by gelfling · · Score: 0

    Doesn't it seem that Apple and its minions have quietly abandoned the traditional desktop office computing realm? Does't it look like Apple has decided to focus on consumer electronics, multimedia, video and mastering. Doesn't it look like Apple is poised to become the ultimate sealed box to do every kind of mulimedia 'thing' under the sun and the hell with desktop productivity applications and systems altogether?

  99. Re:Sour grapes by mattkinabrewmindspri · · Score: 4, Insightful
    How is that insightful?

    Don't blame Mac users if you don't write an application to look like the platform you put it on.

    You wouldn't write an Apple IIe-type program for Windows and expect people to think it looked nice.

    Why would you expect to write a program for one type of GUI, port it, but keep exactly the same interface, and expect the people on the second platform to think your program works very well?

    Programs on different operating systems should not look exactly the same. If you have a program for one OS that looks like it was written for a different OS, you can expect people to see that application as a half-attempt, and you can expect them not to regard the program very highly.

    And as for open-source on the Mac OS, most Mac users I know love open-source software. I have nine open-source applications in my dock right now, and numerous others on my system. Most of them have been much more successful than OO.o. I would say that 99% of the problem OO.o has on the Mac is that it doesn't look like other Mac programs and doesn't try to.

    Most Mac users don't want to run second-hand programs, and second-hand is exactly the impression OO.o leaves on the Mac.

    I was really looking forward to an Aqua port of OO.o.

  100. Ximian OpenOffice by Stevyn · · Score: 1
    I've only seen it in portage, but you can get a version of openoffice called ximian openoffice. You can compile it to integrate with gnome or kde. It makes the ugly interface much nicer to deal with. Some people claim it's faster too which may be because it uses a toolkit you've already loaded into memory. I don't know specifically how they do this, so I appologize if I've made an error, but people should check it out nonetheless.

    This screenshot is integrated with kde and it is similar to what I use.

    http://www.gentoo-portage.com/Image/136

  101. Re:Sour grapes by Hanji · · Score: 1

    No ... really. Under X11 on OS X, at least, OOo is incredibly ugly and slow. (dual Ghz G4 tower, here). I'm sure it's faster, at least, under Linux, and at the very least the UI doesn't stand out so much, but he's not trolling. It really does hurt to use, at least in my experience.

    --
    A Minesweeper clone that doesn't suck
  102. Re:X11 Aqua? by arodland · · Score: 1

    If, on the other hand, you don't know that, you're going to spend half an hour trying to figure out how to make the window go away, and then once you do, you're going to wonder whether that little gumdrop closed the application, made the window go away, or just sent it somewhere else.

  103. Re:Need help w/ my Mac by Anonymous Coward · · Score: 0

    Well, it's a pleasant response. That in itself deserves *some* kind of attaboy.

  104. Spreadsheet by emjoi_gently · · Score: 1

    It's what everyone has been commenting on. The big thing left out of iWorks. If Jobs has any sense, he'll listen.

    Unless it's a deliberate attempt to pander to Microsoft. Killing off "Office for Mac" would be a Very Bad Thing for Apple. Outside Slashdot, a large chunk of Mac users think Office is vital. And to be fair, MS has done a good job of making Office Mac friendly. It's not just a Windows port.

    OO just isn't neat and simple enough for Apple's Volvo image. And again, it would upset Microsoft.

    1. Re:Spreadsheet by Anonymous Coward · · Score: 0

      I want a windows port of MS OFFICE for Mac!

  105. This is pitiful by Anonymous Coward · · Score: 0

    This is absolutely pitiful on the part of the Oo team. For YEARS now they have said "we don't work on an Aqua port because it makes no sense to do so before 2.0 yadayada bla bla" and what do we get now? a cancellation!

    I have been using Openoffice for many years. even on Mac (grinding my teeth every hour I had to make do with it) because it's the only real cross platform office suit worth anything. Stab me in the heart, will you!?

    But it's okay. In the future, I won't be needing cross platform support anyway. Linux is - for me anyway - going the way of the Dodo, as I have simply no time anymore to fiddle with stuff. I'll kill off my last linux installation, and I'll order another Mac (maybe one of the Mac minis) to be my desktop PC instead of my iBook. I'll be buying iWork from Apple instead. At least I can be sure that will work decently.

    My PC will get Windows... for gaming.

    See, Oo team, that's what you do to people!

    I do hope you feel at least a little bad :(

  106. Apple also has a forth coming Office Suite by carl0ski · · Score: 1

    [quote]Ant writes "According to MacSlash's story, a recent post on OpenOffice.org said no MacOS X work has been done since 2003 and that there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :("[/quote] I not sure why people are blaming/flaming Sun like a bunch of idiots. It is never a good idea to jump to an extreme conclusion, Sun is only one sponsor, IBM, various governments and business users also contribute levels of funding. Apple is to produce an Office suite very soon, and the OpenOffice may be related, Apple recently likes the stability and cut costs of open source software. The MAC osx core is based upon the linux Kernel Safari was based on the code base of Konqueror webbrowser Iwork based on OpenOffice is quite probable. It takes years to produce a fully functional Office Suite and maybe Apple has quietly funded OOo and contributed apple coders to produce a better functioning OOo suite to suit MAC OSX better.

    1. Re:Apple also has a forth coming Office Suite by mh101 · · Score: 1

      If you're referring to Apple's iWork that was announced last Tuesday and will be available this Friday, I don't think it really counts as an "office suite." It's just a word processor and presentation software. I suspect that they'd have to at least include a spreadsheet for it to count as an office suite.

      And from what I've seen, it's a whole lot better than what I've seen of OOo! So if it is based on OOo in some way, they did a phenomenal job at fixing it up! I've played with OOo a bit, and I've always thought it was kinda ugly. Even more so, since I got my Mac.

      That being said, I would gladly run out and by iWork this Friday if there weren't other financial considerations... ;(

      And regarding your point about OSX being based on the Linux kernel, you're close, but mistaken. OSX is based on BSD, and uses a Mach kernel and not Linux. But it's still Unix based nonetheless.

      --
      Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together.
    2. Re:Apple also has a forth coming Office Suite by Phroggy · · Score: 2, Insightful

      If you're referring to Apple's iWork that was announced last Tuesday and will be available this Friday, I don't think it really counts as an "office suite." It's just a word processor and presentation software. I suspect that they'd have to at least include a spreadsheet for it to count as an office suite.

      I'd be very surprised if they don't - but they're focusing on one piece at a time (Keynote, then Pages, then...) and releasing them that way, instead of developing them all at once (spreading resources thin). I'd expect a spreadsheet to be next, then a database - perhaps a front-end to SQLite.

      So if it is based on OOo in some way, they did a phenomenal job at fixing it up!

      It isn't. It was easier for Apple to start from scratch, than to add a nice UI to OOo. Besides, they'd have to release it as open-source, and they'd rather charge $79.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  107. I'm sorry, but that looks like ass by tm2b · · Score: 1
    no one can tell it's really developed under FreeBSD.
    Maybe not, but they can definitely tell that it wasn't developed by a competent Mac developer, or with recent Apple tools. If I didn't know about Qt/Aqua, I'd assume that this was a Carbon app put together with some ancient Mac OS 9- kit.

    Take a look at Apple's XCode (and Interface Builer), it makes it a lot more difficult to ignore the Aqua Human Interface Guidelines (like your apps does, as another poster commented). It will give you a much better idea of why native Mac OS X (Cocoa) apps integrate as smoothly as they do and why even clever fakes just don't cut it.

    You can get the latest version of XCode, etc., from Apple's Developer Site with a free registration.
    --
    "It is our blasphemy which has made us great, and will sustain us, and which the gods secretly admire in us." - Zelazny
    1. Re:I'm sorry, but that looks like ass by Brandybuck · · Score: 2, Insightful

      I am reminded of a time years ago when I was in France. A certain wineseller refused to sell to me because my French was good enough for him. Somehow it seems that you're embarassed that I don't speak perfect Mac. I get the sense that you wish I had never ported my software to the Mac at all. But I have lots of letters of gratitude from Mac users that assure me I made the right decision.

      Maybe my application isn't a native Mac app, so what? At least I speak Mac well enough to be understood. Maybe I've got a slight accent, so what? I'm covering a market niche that no one else in Mac-land has bothered to cover. Before my Qt/Aqua port all my Mac users had to perform painful contortions with Fink and XFree86. If you think my Qt/Aqua port has an unacceptable accent, you should have seen it when it had a Motif accent!

      No, I didn't use XCode. That's because I use Emacs and GCC. Heck, I didn't even know XCode ran under FreeBSD. In any case, I could have redone my interface to make it adhere better to your sensibilities. And I could have done it in Qt/Aqua. But that interface would have been so different from the X11 and Windows interfaces that I would have had to either fork the code, or befoul it with scores of additional #ifdefs (and the resulting illegibility and unmaintainability they cause). I could have done this. But Mac users would have had to wait a lot longer to see the finished product.

      I'm not claiming that my application is a perfect example of Mac ideals. I merely claimed that you couldn't tell it wasn't developed natively. Your initial impession that it was a Carbon app validates my point. If I would have spent the extra time to fix some niggling minor "foreign accents" in the interface, I could definitely have made it look as if Steve Jobs himself has written it. And it still would have been written in Qt/Aqua.

      But I don't even own a Mac. Which is why I think my porting attempt is pretty damned good. Even if it pisses off elitist French winesellers.

      --
      Don't blame me, I didn't vote for either of them!
  108. Re:X11 Aqua? by HiThere · · Score: 1

    I believe that's closer to "95% of the computer world doesn't use Aqua".

    Your point is still significant, but by no means as overwhelming as you present it. Probably, however, what they are realizing is that 99.9% of their developers don't use Aqua.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  109. Re:X11 Aqua? by HiThere · · Score: 1

    Sorry, that previous post was a bit garbled. This is a corrected version:

    I believe that's closer to "95% of the computer world doesn't use Aqua".

    Your point is still significant, but by no means as overwhelming as you present it. Probably, however, what OpenOffice.org is realizing is that 99.9% of their developers don't use Aqua.

    Apple may well have a good point, but that doesn't help OpenOffice.org do the development.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  110. Re:Mac OS X = Mac Porn X!!! by bob+beta · · Score: 2, Funny

    How expensive is Apple's PowerPC?

    I bought a whole skid of PowerPC Macintoshes (beige case) at auction last summer for a dollar.

  111. Re:X11 Aqua? by line.at.infinity · · Score: 1

    Apple should provide a killer X11 SDK which would allow porting of X11 apps to an Apple "look and feel".
    That might bring in a lot of competition and piss off loyal Mac developers.

  112. Can't see what the big fuss is about by discogravy · · Score: 1

    Most old-school Mac users won't care -- they'll either want or prefer their old AppleWorks (or the new Apple offering, iWorks,) or stick to using BBEdit (or similar) for word processing tasks, and new Mac users will be getting either iWorks or MS's Office X. Old Mac users are not averse to paying for software they want and like, and new mac users will probably want to stick to what they know will work -- Office X would win out, even despite the cost, I'd guess. So this appeals to...linux and unix users who alreayd know and love OO.o.

  113. Amen by nyjx · · Score: 1
    this seems to me to be the key issue here. Its a shame that something like OOo won't run native on the Mac but what's critical is that we preserve file formats - leaving apple (and others) free to "differentiate" with their UI but keep compatibility across platforms.

    Of course its not that simple since the features of the the system also have a big influence on what you might desire in the format.

    On poster mentioned that you can browse the files of the Pages files as directories earlier - er, an did you check that you're not violating copyright if you were to write another app that did that? Long live the OpenDocument initiative - even more necessary now.

    --
    .sig
  114. Re:X11 Aqua? by Hatta · · Score: 1

    Umm, I have yet to hear one negative comment regarding Aqua interfaces (done right).

    Here's one, you can't type a path into a find/open dialog. Man that bothers me. GTK is doing it now too.

    --
    Give me Classic Slashdot or give me death!
  115. Re:X11 Aqua? by aptenergy · · Score: 1

    Type Command-Shift-G when you're at the dialog. Problem solved.

  116. Re:Sour grapes by killjoe · · Score: 1

    "I was really looking forward to an Aqua port of OO.o."

    So what are you going to do then? Now that insulting the OO guys and berating their work didn't result in a native build of OO what's left?

    Will the mac userbase start an open source office project? Will they try and port OO themselves? Will they try and port koffice or something.

    Honestly will the mac user community do anything about this or will they simply pay for msoffice and call it a day?

    --
    evil is as evil does
  117. Open Standards != OpenOffice by Anonymous Coward · · Score: 0

    What nobody seems to have realized is that the important issue is open standards. Whether a program is based on Open Office, MS Office, or even WordStar* is irrelevant, as long as it's well coded, reliable and fully standards-compliant. That is all most users care about, OSS ideologues can go hang.

    This idea the we all MUST use OpenOffice-derived code if other programs are capable of the same functionality is absurd and irrational. Its like insisting that everyone must drive semi-trailers, even if they only need mo-peds, because semi-trailer parts are fully documented. Who cares, if the road (the standard) works equally well for both and people still get from A to B (tasks done)?

    *Sometimes I feel really old.

  118. API integration of Java apps by Craig+Ringer · · Score: 1

    I don't think the JVM supports such things directly. If it does, I'll be very impressed, since it certainly didn't have anything like that when I was last using Java for my own code (admittedly in the we're-still-using-AWT days).

    Java does provide the ability to build extensions, so there's no reason you couldn't provide extensions to do these things. Ideally you'd write a platform neutral API and then implement it for each platform you ran on, so your Java code didn't have to care about what platform it was on. For some stuff, of course, this just won't work and you'll have to handle each platform differently or port some of your java files for each platform.

    It may well be worth looking into third party tools to do some of this. For example, I'd be very surprised if OLE wasn't availible either built-in with the JVM, or as a 3rd party add-on.

    You may run into more trouble with things like making "feel" like apps for your platform. SWT is probably worth looking into for this, and may be what you're after when it comes to Java GUIs.

    In the end, this is part of my gripe about java - while its cross platform, it doesn't really fit in well on any platform.

  119. Re:WiApple now getting into the office suite arena by The+Original+Yama · · Score: 1

    Apple provides no detail on how well their compatibility with other formats really are. It took years for OpenOffice.org to reach the level of compatibility that it presently enjoys, and it still cannot claim to be 100% compatible with the proprietary MS formats.

  120. Standardisation vs portability by Craig+Ringer · · Score: 1

    That's a very good point. One certainly does have to jump through more than a few hoops to get sensible sizes, deal with endianness and word size issues, etc.

    Very ugly hoops.

    I should've said that it is possible to write portable apps in C, and that an app written with portability in mind shouldn't be too painful to port to a new platform. This is especially true if you make a point of testing on, say, a big-endian 64 bit PPC machine.

  121. RE: Why would Linux users care one iota..... by Anonymous Coward · · Score: 0

    Then why do they worry and complain about Windows so damned much? It doesn't effect their life in any way. Windows and OSX are main stream desktop OS's, GNU/Linux is a server operating system with desktop enhancements cobled into it. Now before you go calling me a troll, saying that OSX is based on BSD let me say this, BSD is not Linux, and OSX doesn not run on top of BSD. OSX runs on top of Apples own BSD based fork, which was designed to be stable in both server and desktop enviroments. It is not laden with 20 text editors, 5 e-mail applications and loads of daemons most users will never need.

    Basicly what I'm saying is that if GNU/Linux wants to compete on the desktop, it will require alot of work to the OS it self, no mater how hard the Gnome and KDE teams work. Also X11 alows each program to use it's own GUI kit, while is is great for hobbyists, it's a kick in the pnats for desktop use, it limits the ability to quickly switch between apps and feel "at home."

  122. Reality bites by Anonymous+Brave+Guy · · Score: 4, Interesting
    That's just a lame excuse for "We are the mighty Sun, but we don't help those Mac faggots, because Apple is now competing with us in servers. [...]

    I always look at these threads with amazement. How can anyone really believe that a major corporation supports OSS for philosophical reasons? They do it because of basic economics, which they expect to benefit them in the long run. Typically, they are attempting to commoditize software on a particular hardware or OS platform they control, in order to increase the value of their position in that hardware/OS market, or more likely today in related service sectors. It is not surprising at all that Sun won't divert resources to support OSS on a competing platform!

    It's also amazing that a few OSS evangelists can still chant the "if you don't like the development direction, you can just fork" mantra and maintain that OSS is future-proof and highly portable on this sort of basis. To an impartial observer, it's obvious that most of the major OSS projects (from Linux on down) are developed principally by a small number of commercial concerns, who have those same reasonable economic drivers for doing it. Unfortunately, it just isn't realistic for a handful of individuals who haven't been involved for a long time to pick up projects on this scale and carry on development. It has never been a good situation in the commercial, closed source world, and just opening the source to everyone (typically laughable documentation and testing included if you're lucky) doesn't make it any more likely that it will happen. Sun apparently understands this, and knows that in reality they still have far more control over StarOffice/OpenOffice development than anyone else, and will therefore use it to their advantage if they're even remotely smart.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Reality bites by nileshbansal · · Score: 3, Interesting
      "most of the major OSS projects (from Linux on down) are developed principally by a small number of commercial concerns, who have those same reasonable economic drivers for doing it."
      "Unfortunately, it just isn't realistic for a handful of individuals who haven't been involved for a long time to pick up projects on this scale and carry on development."
      Look at KDE. A great-well-managed giant project which is not driven by some commercial interest. Study KDE project, and you will start believing in poer of OSS.
    2. Re:Reality bites by Anonymous Coward · · Score: 1, Insightful

      But if that were true, then Sun wouldn't have any problem open sourcing Java. They don't do it exactly because they are afraid of fragmentation!

    3. Re:Reality bites by Anonymous+Brave+Guy · · Score: 1
      But if that were true, then Sun wouldn't have any problem open sourcing Java.

      Java is the oddity in Sun's strategy, and something no-one seems to be able to work out. For example, if their strategic objective is to promote their hardware platform, then tactically supporting a fundamentally cross-platform development language is exactly the wrong thing to do.

      What Sun probably should do is kill Java as fast as possible on all non-Sun hardware platforms, and attempt to drive all that investment other organisations have now made in Java code onto Sun servers. But they don't seem to have spotted that yet.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  123. What is bytecode? by tepples · · Score: 1

    By native code I mean machine language vs. bytecode, not platform-specific C vs. portable C or Java.

    Is this distinction useful? Compared to RISC platforms' machine language, x86 machine language is a bytecode, and a few companies have demonstrated products that decode and execute JVM bytecode in hardware.

    Besides, where does GCJ + SWT fall down?

  124. Not Linux kernel (OT) by OldMiner · · Score: 1
    The MAC osx core is based upon the linux Kernel

    Different kind of Free. BSD license instead of GPL. The OS X kernel, Darwin, is based upon BSD Unix.

    --
    You like splinters in your crotch? -Jon Caldara
  125. Re: Why would Linux users care one iota..... by Guy+Harris · · Score: 1
    OSX runs on top of Apples own BSD based fork, which was designed to be stable in both server and desktop enviroments. It is not laden with 20 text editors

    Yeah, only 4 of them (if you don't count TextEdit), unless I've missed one - vi, GNU EMACS, pico, and ed.

    5 e-mail applications

    Yeah, just Berkmail.

    and loads of daemons most users will never need.

    Yes, OS X has a smaller load of such daemons (I suspect most users aren't going to use distccd or the CORBA Object Request Broker Daemon orbd, for example).

  126. My OpenOffice success story by bgspence · · Score: 2, Funny

    I had been using an ancient version of MS Office on System 9 under OSX. I decided it was time to move forward, but really did not want to support Microsoft. So, I installed OpenOffice and gave it a try.

    In no time at all my Office needs were resolved. OpenOffice ran like such an ugly slug that it overcame all my Microsoft objections. I immediately bought MS Office for OSX. Without the OpenOffice experience I could never have been happy buying a Microsoft product.

    Thank you, OpenOffice team, for peace of mind.

  127. One man's traditional is another's rarity by Anonymous Coward · · Score: 0

    "Doesn't it seem that Apple and its minions have quietly abandoned the traditional desktop office computing realm?"

    Except for a few die-hard oldies who bought Excel version 1 (Mac only, the 8086 couldn't cut the mustard for spreadsheets) and have brand loyalty, most of the desktop office world shifted to Wintels years ago.

    Macintosh has long been the platform of choice in audio, video and publishing (Does anyone remember Sonic Solutions, ProTools pre v.5, or Avid pre v.6 for Windows? They didn't exist. And PhotoShop under DOS? Come on...), and although many of those titles exist on the PC, the Mac is still dominant in pro shops*. Apple are choosing to focus on the market that never abandoned them for cheaper Wintel boxen (professionals for whom reliability is more important than the capacity to tinker or achieve 140,000 fps on Quake), and trying to push the same capabilities into the lower end market without sacrificing reliability or ease of use. iMovie is the best example: cheap DV camera + cheap Macintosh = easy home movies, within 15 minutes of opening the box. Cheap DV camera + cheap PC = ...well, try it for yourself, I'd bet an iBook (widescreen+superdrive, please) it will take longer than 15 minutes.

    So to paraphrase your observation from Apple's perspective: "PCs are jumped-up typewriters & games consoles, Macs are what you use when you want to be creative. Oh, and you can use a Mac as a typewriter, if you haven't got anything better to do". The only real difference is Apple's marketing focus and software development strategy.

    *An example: a few years back Sydney's Daily Telegraph tried creating an all-PC network (NT 4), including the art department (naturally, the consulting firm had no idea you could attach Macs to a PC network, and management wanted cheaper boxes). The new computers lasted 2 weeks, extra mouse button not withstanding. One of the major problems was the graphics tablets (big, expensive ones, not cheap little Wacoms) simply wouldn't work, and all the designers started calling in sick with RSI from mousing. Not a good situation for a daily publication!

  128. Re:X11 Aqua? by Nailer · · Score: 2, Insightful

    Agreed.

    Short version:
    More people run multiple apps on one platform than run one app on multiple platforms.

    Appendix:
    Dur.

  129. Re:Need help w/ my Mac by Anonymous Coward · · Score: 0

    The parent is a re-post. It's a copy and paste from an older article.

  130. Re:Sour grapes by Haeleth · · Score: 2, Interesting

    Why would you expect to write a program for one type of GUI, port it, but keep exactly the same interface, and expect the people on the second platform to think your program works very well? Programs on different operating systems should not look exactly the same. If you have a program for one OS that looks like it was written for a different OS, you can expect people to see that application as a half-attempt, and you can expect them not to regard the program very highly.

    The success of iTunes for Windows suggests that this is not universally true. I know some people who avoid it because the interface is weird compared to what they're used to, but there are plenty of people who really don't seem to have any problem running something that looks like a Mac app on their PC.

  131. Re:X11 Aqua? by 9mind · · Score: 1
    I really don't understand your FUD statement at all. Frankly I think what they are saying about training and having the same look-and-feel across platforms makes perfect sense.

    For example... I'm trained to use OpenOffice on Windows... Everything is where it is should be if I move to Linux... but then I got to a Mac and have to relearn the interface? That throws all my training out the window... as I now have to get up to speed....

    There argument is very relevant, ask any Designer who started with Photoshop on a Mac, and then had to move to a Windows version and relearn the interface... because it was designed to accomodate the Windows Users.

    I have always believed that interfaces should function relatively the same across platform if you are calling it the same product. Thus, when you tell someone you are proficient in Photoshop or OpeneOffice, you can sit down and get tow ork right away... not muck around with trying to figure out all th enuances in every interface.

  132. Re:Mac OS X = Mac Porn X!!! by StarKruzr · · Score: 2, Funny

    I fucking hate you, dude.

    How the hell did you pull that shit off? ...

    And wanna sell one for $2? 100% profit! Can't beat that!

    --

    +++ATH0
  133. oops by poemofatic · · Score: 1

    Sorry to reply to my own post, but I meant to say "windows and solaris SPARC" not "solaris PPC". Preview, preview.

    --

    When in doubt, have a man come through a door with a gun in his hand.

  134. A serious answer by Anonymous Coward · · Score: 0

    It is possible to put X11 apps in the Dock, provided you can work out which UNIX executable file is the core of the program and drag it there yourself (I used to do exactly this before I gave up on OOO, since I found the launcher to be less than reliable). This is not something I would expect the average user to accomplish, or even realize is possible.

    Part of the problem is that programs running inside X11 are treated as sub-processes, so are invisible to Aqua (just like terminal commands which are also UNIX executables can only be accessed through the Terminal and not the Dock...probably a Good Thing(TM), since its kind of hard to distinguish between one Unix executable and another if function rather than file type is the only difference, and you don't want users playing "click the generic icon" in low-level-land). Its almost like expecting to be able to launch IE inside Virtual PC from the Dock; of course it won't work, because without the shell program, the link is meaningless (X11 isn't even part of the standard system installation on the Mac). GNUStep, IIRC*, uses X-windows for the Dock itself, so having it communicate with other X-windows programs is easy.

    So it really has nothing to do with the Dock format being more or less powerful (a matter of opinion, anyway), its about hiding non-user processes that are best left alone where they can't be fouled up. No UNIX executable appears in the Dock when running, and this is intentional.

    *IIRC="I have no idea what I'm talking about, but I do have dim recollections of something someone said late at night after about a dozen drinks, so rather than exercising caution I'll talk through my arse and post anonymously"

  135. Mac people???? Oh, you mean fanbois! by Anonymous Coward · · Score: 0

    "Mac people don't want what open-source people think is a good interface"

    Mac people want whatever jobs tells them they want.

    For instance, the recent debacle sueing a fan site because it printed a rumor.

    The debacle of their installed base dipping to a historic low of 2%.

    The debacle of introducing an ipod *with no display, and no way to choose songs* (I'm just waiting for some a55hole fanboi to defend that bit of stupidity)

    The debacle of having a "Powerbook" which has a FSB of 167mhz and the performance to match the state-of-the-art in 2000. Unfortunately, its 5 years later. The real fanbois will tell you "The Powerbook is fast enough! Just buy one"

    Please. If Jobs were killing babies with a pitchfork, Mac people (fanbois) would defend it.

    The funny part is most of these guys never do anything more than buy used Macs. People like me buy new stuff from apple from time to time and you idiot fanbois tell us we're wrong when we point out the numerous stupidities that Apple does because its run by a one-man cult instead of like a normal business.

    "and don't want to shell out money for Microsoft Office"

    [rolling eyes]

  136. POWERbooks? more like Mediocrebook by Anonymous Coward · · Score: 0

    "on my 1Ghz G4 Powerbook"

    You know what's funny? This speed was marginal when it came out, 1.5 is too goddamned slow for a POWERbook and yet people are buying them.

    Is it any wonder I'm hanging onto my Pismo until Apple get their head of out of their collective bungholes and make a G5 POWERbook?

    1. Re:POWERbooks? more like Mediocrebook by Anonymous Coward · · Score: 0

      That's it, NO SOUP FOR YOU!!!

  137. Re:Thundercats by Anonymous Coward · · Score: 0

    I still jack off on my Liono action figure daily.

    Sincerely,
    Michael Moore

  138. MOD THIS DOWN by Anubis350 · · Score: 1

    this is so patently not true its laughable.

    1) drag and drop is supported (just tested this on my powerbook), just drag a file to "start OpenOffice.org.app"

    2)Copy/paste works fine for X11 (in fact apple stresses this in their promotion of having an X server in OSX, I also just tested this on my powerbook, I use this all the time between gaim firefox and openoffice), you just need to use control instead of command.

    should I assume this is a troll or a clueless mac user?

    --
    "goodbye and hello, as always" ~Prince Corwin, from Zelazny's Amber series
    1. Re:MOD THIS DOWN by Bulln-Bulln · · Score: 1

      2)Copy/paste works fine for X11 (in fact apple stresses this in their promotion of having an X server in OSX, I also just tested this on my powerbook, I use this all the time between gaim firefox and openoffice), you just need to use control instead of command.
      Of course it works between OpenOffice and GAIM, because both are X11 apps!
      I can't paste text from a native app into an X11 app! Maybe if you use another X-Server. I use the plain Apple X11 that came with Panther!

    2. Re:MOD THIS DOWN by Anubis350 · · Score: 1

      copy paste works between any two apps, X11 or otherwise, on OSX (and yes, I use the normal Xserver that apple ships with panther). as I said in the previous comment: "gaim firefox and openoffice". Firefox runs OSX native... . I use the clipboard to go between all my apps, X11 or otherwise all the time. If you can't, the problem may be one with the computer's clipboard settings or you may have some strange glitch in you X11 installion. I however have never had any problems (on my mac or anyone elses) with copying from apps running on the X sever to apps running native on Aqua. Oh btw, when I say anyone elses I also mean the several hundred macs on my universities campus I do client support for too.

      --
      "goodbye and hello, as always" ~Prince Corwin, from Zelazny's Amber series
    3. Re:MOD THIS DOWN by Anubis350 · · Score: 1

      I just saw another article on /. that applies to your comment. I dont know if you check for responses but if you do here goes:

      1st of all, link to article here

      2nd of all, important excerp:

      this is excerped from "X11 and Quartz Integration" section of the article

      quartz-wm also provides the pasteboard integration that allows text copying between windows. For example, you can copy text from a Terminal session to an xterm window running under X11. Note that because the key mappings differ between the two environments, you need to use the UNIX equivalents for text manipulation on the X11 side. Command-C copies selected text in both Mac OS X and xterm. But while Command-V pastes in Mac OS X, in X11 the paste key sequence differs across applications. For example, in xterm you use Option-Click to paste the buffer contents into the current xterm window. This simulates clicking with the middle mouse button held down; UNIX systems typically have multi-button mice. Other X11 applications may behave differently. See the X11 FAQ (Technical Q&A QA1232) for a more detailed discussion.

      link to more info curtesy of the same article.

      exerpt from that faq which should help you:

      Q: How do I copy and paste using X11 for Mac OS X?
      A: X11 for Mac OS X allows cut and paste between X11 and native applications using PRIMARY and PASTEBOARD selections. You can cut text from X11 applications by selecting the text, performing a cmd-c or copy operation. You can paste in native Mac OS X applications as usual using Cmd-V. Because there is no standard for pasting in X11 applications (some use middle mouse button, some use control-v, etc.), cmd-v doesn't work for pasting in X11 applications by design. As a result, the "Paste" menu item will be grayed out when X11 applications are in focus. You should use the control-v or the middle mouse button instead for pasting (See X11 Preferences for emulating a middle mouse button). The "Paste" menu option will be active when non-X windows are active within X11.app (e.g., when entering text in the "Customize Applications" menu item). A common request has been to make cmd-v work across all X11 applications. This isn't possible without re-writing all X11 applications to standardize on a single approach, which is outside the domain of X11 for Mac OS X


      I hope this answers any questions you have about X11 and OSX clipboard probs so you can get back to happy OSX'ing.
      cheers,
      Anubis

      --
      "goodbye and hello, as always" ~Prince Corwin, from Zelazny's Amber series
    4. Re:MOD THIS DOWN by Bulln-Bulln · · Score: 1

      I dont know if you check for responses

      I did. Thanks. I'll try it soon.

    5. Re:MOD THIS DOWN by Anubis350 · · Score: 1

      not a prob, hope it helps

      --
      "goodbye and hello, as always" ~Prince Corwin, from Zelazny's Amber series
  139. Interesting that all of the parents are modded +5 by ziggy_travesty · · Score: 1

    Maybe this indicates a more serious disagreement at a fundamental level between the Stallmanites (developer-centeric vs. Mac/Design centered folks (Customer-centric).

    IMHO, as someone who isn't enirely broke, I would pay the extra $200 or whatever for a superior product. People want to use the best tools...look at the success of Firefox which is clearly better than IE.

    I think the success of projects like this will depend on ditching the Stallmanite mentality of "good enough" and moving to what customers want.

  140. NeoOffice/J by cks3 · · Score: 2, Informative

    Sure, it is java, but NeoOffice/J is a pretty nice non-X11 dependent OS X port of OOo, complete with an aquafied menu, and continued development. Check it out: http://www.planamesa.com/neojava/en/index.php

    --
    http://www.sampletheweb.com
  141. Re:Sour grapes by neverkevin · · Score: 1

    "Honestly will the mac user community do anything about this or will they simply pay for msoffice and call it a day?"

    Since when did buying software become a bad thing?

  142. not well supported by Apple by idlake · · Score: 1

    Setting up X11 on the Mac is non-trivial, and it is impossible for X11 applications to behave like normal Mac applications. Basically, if you must, you can get it to work, but it's not a solution you would want to deploy for a whole computer lab.

    The solution to this problem is, however, not to convert every X11 application under the sun to Cocoa, the solution is to fix X11 integration on the Mac.

  143. get your facts straight by idlake · · Score: 1, Informative

    First, X11 on OS X is slow; that's not X11's fault, it's a problem with the X11 implementation on OS X. In fact, run natively, X11 is much faster and less memory intensive than Quartz on the same hardware. Second, as for "ugly", that's a matter of opinion. People shouldn't take the FUD of Macintosh zealots like you as a fact, they should look for themselves.

    At this point, Gnome and KDE are probably better desktops than Aqua: better integrated, more consistent, more efficient on comparable hardware, and better looking. And it's only getting better with X.org.

    Don't believe the Macintosh marketing FUD: Gnome and KDE are excellent desktops.

    1. Re:get your facts straight by ColMustard · · Score: 1
      Haha. Did you just say Gnome/KDE is probably more integrated and consistent than Aqua? Oh boy... And what's so great about X.org? It just added eye candy and Aqua has been able to do that since its release in 2001. It's even been hardware accelerated for a couple years now and X.org isn't even close to that.
      Don't believe the Macintosh marketing FUD: Gnome and KDE are excellent desktops.
      While it's great if Gnome & KDE work for you, but your comments about Aqua are misguided and show that you've probably never or have had very little use of Aqua. It's not a matter of Apple's marketing, it's a matter of real-world user experience.

      Being able to sit down with a program you've never used and automatically know how to use it is a powerful thing, my friend.
      --
      Moof.
    2. Re:get your facts straight by idlake · · Score: 1

      While it's great if Gnome & KDE work for you, but your comments about Aqua are misguided and show that you've probably never or have had very little use of Aqua.

      Quite to the contrary: I have used Aqua quite a bit, as well as helped other people using it. It's not bad, but it's not better than any of the other desktops out there. When I talk about systems, I have actually used them day-to-day.

      Can you or all the other Apple zealots here on Slashdot say the same about KDE and Gnome? Or does your experience of other systems come down to "tried it for a couple fo weeks and didn't like it"? I suspect it's the latter.

      Being able to sit down with a program you've never used and automatically know how to use it is a powerful thing, my friend.

      Yes. Too bad that Macintosh doesn't achieve that any more than any of the other platforms. In fact, some of its gratuitous incompatibilities (menu bar, one button mouse, weird window management, etc.) make it unnecessarily hard to use for users. And my statement is based on real-world observations of real-world users.

      Haha. Did you just say Gnome/KDE is probably more integrated and consistent than Aqua?

      Yes. While people like you like to make unfounded assertions about the degree of consistency in systems like Macintosh, there is actually no formal measure of that. So, which system is more consistent is a matter of opinion. My opinion is that Gnome and KDE are more consistent than Macintosh. But you may have a different opinion. Just don't present your opinion as an irrefutable fact. In fact, most of the claims about Macintosh are just opinions, not facts.

      Oh boy... And what's so great about X.org? It just added eye candy and Aqua has been able to do that since its release in 2001.

      What's so great about it is that it provides an open, general, and efficient approach to those features that is preferable to Apple's proprietary and complex DisplayPDF system.

      It's even been hardware accelerated for a couple years now and X.org isn't even close to that.

      X11 servers have had hardware acceleration since the 1980's.

    3. Re:get your facts straight by ColMustard · · Score: 1

      Actually, I do use KDE on my NetBSD box and have been for more than a 'couple weeks.' You don't gain credibility by calling anyone who disagrees with you a 'zealot.' Desktop experience is, after all, a matter of ones own personal preference. If you think KDE & Gnome are better desktops than Aqua, good for you. Personally, I don't even think they are quite up to Windows' standards.

      Apart from that, there are places where you are are completely wrong. X11 is a standard, so it makes little sense to say it has hardware acceleration when it's really a network-based protocol. Ignoring that, X.org is definitely not hardware accelerated either. No, those little video card driver hacks that gain 1% performance increase aren't really what I had in mind. I'm talking about real hardware acceleration on par with Quartz Extreme.

      --
      Moof.
    4. Re:get your facts straight by idlake · · Score: 1

      You don't gain credibility by calling anyone who disagrees with you a 'zealot.'

      I don't call "anybody" who disagrees with me a "zealot", I call people who behave like zealots "zealots". People like Zelet and you.

      Desktop experience is, after all, a matter of ones own personal preference.

      Good that you realize that now. You should think about that before you post. Also go read the parent post that I originally responded to.

      X11 is a standard, so it makes little sense to say it has hardware acceleration when it's really a network-based protocol.

      X11 server implementations have had hardware acceleration for graphics since the 1980's. In fact, a lot of hardware has been specifically designed to support X11 graphics, and is to this day.

      I'm talking about real hardware acceleration on par with Quartz Extreme.

      Quartz's use of hardware acceleration is very limited; it doesn't even accelerate all the graphics operations that are accelerated in a good X11 server, and it shows in Quartz's sluggish performance. X11-based desktops are far more responsive on the same hardware as Aqua.

      You know, most people wouldn't give a damn about what you think about your Macintosh. But people like you and Zelet should stop badmouthing and spreading FUD about Linux and X11 and making exaggerated claims about Macintosh technology: the Macintosh is a decent desktop machine, but that's all.

    5. Re:get your facts straight by ColMustard · · Score: 1
      I don't call "anybody" who disagrees with me a "zealot", I call people who behave like zealots "zealots". People like Zelet and you.
      However when you review my original response, you should note that all I did was disagree with you and point out possible misstatements. So again, if you consider a zealot to be anyone who disagrees with you, then you're right on the money; I'm a zealot.
      X11 server implementations have had hardware acceleration for graphics since the 1980's. In fact, a lot of hardware has been specifically designed to support X11 graphics, and is to this day.
      Got a link? Here's mine. If you do, then great; I don't mind being proven wrong. [I don't think you'll find a real 'zealot' by most people's standards to make such a statement.]
      Quartz's use of hardware acceleration is very limited; it doesn't even accelerate all the graphics operations that are accelerated in a good X11 server, and it shows in Quartz's sluggish performance.
      Quantz is limited, not very limited as you say, but obviously it has limits. Odd limits, too; for example text rendering is dog-slow--not optimized at all. Obviously there is room for improvement. I didn't say everything about Quartz made Aqua automatically faster than X11 implementations anymore than I said everything about Aqua itself is better than X11 desktop environments. All I can say is generally, QE has done a better job of speeding up desktop rendering than X11 with its DRI, based on my own experiences.
      X11-based desktops are far more responsive on the same hardware as Aqua.
      I assume this comment is based on perceived speed and not measured benchmarks--unless you can provide a link. Keep in mind that Aqua has more [complex] eye-candy than do X11 desktop enviroments. Perhaps you should try again after turning off Aqua's fancy effects for a more fair comparison.
      You know, most people wouldn't give a damn about what you think about your Macintosh. But people like you and Zelet should stop badmouthing and spreading FUD about Linux and X11 and making exaggerated claims about Macintosh technology: the Macintosh is a decent desktop machine, but that's all.
      I don't care who gives a damn about what I think about what. I believe you should reevaluate your zealot-detecting methods so you don't embarrass yourself in the future. I've been a X11 (KDE) user for longer than I've been an OS X user and am quite the opposite of a zealot. I'm very open to new technologies and what people have to say about them, and you should probably be the same. All I've done is give you an alternate point of view. You should probably not mistake FUD for "just another random guy's experiences." It makes you look silly.
      --
      Moof.
    6. Re:get your facts straight by idlake · · Score: 1

      However when you review my original response, you should note that all I did was disagree with you and point out possible misstatements.

      That's why you start out your post with the phras "Haha"?

      Got a link?

      Sure: got to "sgi.com", "hp.com", or "sun.com". They have been designing and shipping X11-specific graphics hardware for nearly as long as they have been shipping workstations. Of course, their old products aren't even on-line anymore.

      Odd limits, too; for example text rendering is dog-slow [...] I assume this comment is based on perceived speed and not measured benchmarks--unless you can provide a link

      You just provided one yourself.

      Keep in mind that Aqua has more [complex] eye-candy than do X11 desktop enviroments. Perhaps you should try again after turning off Aqua's fancy effects for a more fair comparison.

      Just a text console will do nicely to see how slow it is. Graphics drawing is slow, too, though, in my measurements.

      I don't care who gives a damn about what I think about what.

      And I don't care what you think either. What I care about is when people like you lie or distort the facts over Linux and X11 out of some fanboy-ism for Apple. And the facts are that Apple has never proven that OS X usability is better than any other platform, and nobody has provided any benchmarks proving that Apple's Quartz Extreme is anything other than a marketing gimmick. And, in fact, you yourself point out that important operations (like text rendering) are "dog-slow" (your words).

      If you do, then great; I don't mind being proven wrong.

      So, your approach to communication is to uncritically repeat Apple marketing claims and then insist that other people have the obligation to prove you wrong. Well, that's what makes you a zealot. The correct order of things is that if people make claims about a commercial product, they prove them first, since vendors have a strong interest in exggerating the performance and capabilities of their products.

      Verifying Apple marketing claims is particularly important since Apple apparently has a problem with facts: for example, for years, they claimed that the G4 was much faster than its clock rate indicated, but when people actually did the benchmark, it turned out that was a lie. They also claimed that their machines were the first 64bit personal computer--wrong, and they knew it.

    7. Re:get your facts straight by ColMustard · · Score: 1
      So, your approach to communication is to uncritically repeat Apple marketing claims and then insist that other people have the obligation to prove you wrong. Well, that's what makes you a zealot.
      Um, no... Like I said in my very first response; I based my answers an real-world experience, not on Apple marketing. Keep up sparky.
      Verifying Apple marketing claims is particularly important since Apple apparently has a problem with facts: for example, for years... blah blah blah.
      Again, that's why I don't base my opinions on any company's marketing. I don't know in how many ways you want me to repeat this. Again, everything I said is based on my experiences relating to what we're talking about.

      About the quartz, duh the console will be slow. I already said quartz has no optimized text rendering. The argument is that generally, QE makes for a faster desktop experience than X11 w/ XDI. Again, this is based on my own experiences (perhaps I should repeat this every other sentence so you remember) and no that doesn't mean that I think Quartz is the fastest and best thing in every possible way.

      Okay so in summary, if you find X11 fast and can stand KDE or Gnome then keep using it. It's free, so why not. I get no benefit from you 'switching' to anything else and I never suggested you do so. Use whatever you want (yeah, I sound like such a zealot). Your silly accusations of me being a zealot are boring me and have led me to consider you as somewhat of a troll so I don't think I'll be spending anymore time toward this enlightening conversation. Take care, friend.
      --
      Moof.
    8. Re:get your facts straight by idlake · · Score: 1

      Um, no... Like I said in my very first response; I based my answers an real-world experience, not on Apple marketing.

      Your real-life experience doesn't tell you supposed "facts" like Quartz being accelerated and X11 not. You are parrotting Apple marketing claims, you just mistake it for your "experience".

      About the quartz, duh the console will be slow. I already said quartz has no optimized text rendering.

      Yes, you said that. After berating me for claiming that Quartz is slow.

      The argument is that generally, QE makes for a faster desktop experience than X11 w/ XDI.

      Quartz Extreme does make for a faster desktop experience than X11 in many cases, not because QE is faster (which it isn't), but because it spends a boatload of memory on caching window contents on the server. That's how Quartz gets away with slow, unaccelerated drawing operations and still looks like it's fast. You can get some of the same effect in X11 by enabling backing store.

      Your silly accusations of me being a zealot are boring me and have led me to consider you as somewhat of a troll so I don't think I'll be spending anymore time toward this enlightening conversation. Take care, friend.

      The "troll" is people like you, who go into an open source advocacy site (and that's what /. is to a large degree), make unsubstantiated claims about the inferiority of open source software.

      If you at least accompanied your assertions by evidence, one could use them as a starting point for improving OSS further. But the problem is: there is nothing; one can't improve OSS software like X11 or Gnome in ways that would appeal to you because you guys can't even demonstrate what you think is wrong.

  144. right decision by idlake · · Score: 1

    Rather than wasting time on porting OOo to Cocoa, the time is better spent on improving the integration of X11 into the Macintosh desktop and improving X11 performance when run as a guest under Quartz. That way, all developers of X11 applications benefit.

    OOo might, for example, have a little wrapper that tries to find X11 (it is usually around as an uninstalled package on the machine) and install it if it's not there.

    And X11 might get a small Macintosh-specific extension or helper app that allows things like drag-and-drop and the menu bar to work better.

    And the OOo developers are exactly right about consistency: consistency of OOo (and Mozilla, Firefox, Thunderbird, etc.) is more important than consistency within the Mac environment, both for development and for many end users (who usually end up having to use multiple platforms anyway).

  145. Nature of BSD by Anonymous Coward · · Score: 0

    This is the nature of BSD: BSD developers Do Not want to burden users with an obligation to give returns. You can only "rob" from BSD by not crediting the code you use or credit yourself for others' BSD code.

    Since Apple and others have been known to use OpenSSH and other BSD code without supporting BSD developers, we don't need to and we shouldn't support them. Besides, Apple is full of DRM and lock-ins anyway.

  146. Re:Sour grapes by Anonymous Coward · · Score: 0

    So what is really true is the fact that a mac app looks like gold on any platform and apps for other platforms look like crap on a mac desktop. What does that say about the general desktop experience of other platforms........

  147. Apple will do the Aqua port eventually by tentimestwenty · · Score: 1

    You hit the nail on the head. Mac users want consistency and they'll pay for a commercial product just for that. Eventually though, if OpenOffice gets popular enough and becomes a standard in itself, Apple will step in and do an Aqua port so that its customers give their money to Apple instead of Microsoft. For the time being the gains just don't outweigh the risks for Apple or for their customers so they're not going to do it but in time it will have value.

    Who really thinks that iWork is only about word processing and presentations... it's just the beginning of Gen 2 of their office suite.

  148. More of a problem for Apple than for me by Nice2Cats · · Score: 4, Interesting
    I use OOo with Apple's X11 and right off the bat I have to confirm what other people have said here: It works (except that you don't get italics on some fonts), but it is slow, poorly integrated and looks like crap once you are used to Aqua. You don't notice this that much with KDE/Linux or Win XP (the other two systems in our house) because their icon sets are cruder than Aqua anyway, but it is really glaring with OS X.

    But it works, and since we got so fed up with different file formats at home and switched everything to the free OpenOffice XML (OASIS) format, this is what counts here. Those of you who think OpenOffice XML is some isolated open source thing should keep in mind that the European Union (400 million people and counting) is probably going to make OASIS an ISO standard (Sun is pushing this like mad), and that open source projects of all kinds are converging on it as a common standard: Koffice is the biggy next to OpenOffice.org. The standard is here to stay. If you want to play the game, sooner or later you either have to have a monopoly or support it.

    Which brings us to the reason why this new announcement is more of a problem for Apple than for the average Slashdot user: The OS X platform does not offer a free full-fledged office suite. AppleWorks is a joke, basically one of those toy apps left over from when they had that toy operating system OS 9, and iWorks is neither a full suite nor does it support OASIS. And there is no way I am going to pay for Microsoft Office, since it does little more than OpenOffice for some ridiculous price. I mean, when it comes down to it we're talking about the choice between buying an iPod or buying Microsoft Office. Duh!

    I've said this before and I'll say it again: Apple should do a Safari (Darwin, Cups, GCC...) here and admit that they can't produce a first rate office suite by themselves. Keep Keynote if you must, but get the rest of the people wasting their time with iWorks behind an Aqua OpenOffice port. This would rid Apple of the last area where they are dependent on Microsoft, and give them the office capabilities the Mac currently lacks.

    1. Re:More of a problem for Apple than for me by 99BottlesOfBeerInMyF · · Score: 3, Insightful

      Apple should do a Safari (Darwin, Cups, GCC...) here and admit that they can't produce a first rate office suite by themselves.

      I strongly disagree. For quite some time I hoped that Apple would pick up the Mozilla source and run with it. Instead they picked up the Konquerer source and ran with it. It was probably a good engineering decision on their part and it resulted in corporate sponsorship for a second open source rendering engine. This helps open standards and keeps web developers from writing gecko specific code to go with their IE specific code.

      I've used open office, and a huge number of other word processors, and layout programs. There is huge room for improvement over either OpenOffice or Word. I'd like to see some of the best features of Word, OpenOffice, Indesign, and Framemaker all put together with some top notch usability. I don't think Pages will be there in it's first iteration, and maybe never. But from what I have seeing it may be a better, and more flexible base than OpenOffice would have been. That is not to say that I don't think support for open formats is not important. They have a good start on compatibility but seem to be lacking support for OpenOffice, Latex, PNG, SVG, and a few others. Also, I hope their native format is XML based, like Keynote. Ideally, they will have a plug-in format so any developers can easily incorporate import/export filters to a given format.

      Basically what I am saying is that while I appreciate OpenOffice, I'd much rather see a system designed right from the ground up, rather than another Word clone, regardless of the quality.

  149. those who ignore history... by Anonymous Coward · · Score: 0

    It's amazing how basically nobody seems to know the history of StarOffice.

    It originated as a DEMO of a multi-platform (Windows, OS/2, X11, MAC) GUI toolkit! Only later did it grow into a usable office suite. It's strange that guys claiming to have worked for Sun on StarOffice don't know that ("whatever company did the OS/2 port" stuff). I and many other OS/2 users remember downloading StarCalc when that's all there was.

    It seems to me that the people currently involved with the code have broken the portability that the original developers intended. That's really too bad.

    Anyway, there is a native version of AbiWord, and soon there's iWork. OOo can go ahead and start fading into obscurity as far as Mac users are concerned.

  150. Join the Fucking Cluetrain by Anonymous Coward · · Score: 0
    Yes, it is major suckage that there is no OS X port (NeoOffice not withstanding). Yes, Mac users want that "precision look and feel experience we pay through the nose for". Yes, MS Office is the 800 lb. gorilla of the business world when it comes to office suites. Yes, the whole Qt/Mozilla/X11 arguements are "merely fringe annoyances" to the Mac crowd ("Eew! Icky gray buttons! Not pretty!")

    Everyone has managed to completely forget the clue train. As usual.

    So, I have a question.

    What the hell happens to your documents 8 years from now? You know, the MS Office docs that require a new version of Office. How about when Apple grows tired of supporting all of those old iWork installations?

    For shit's sake, OO may be ugly, but at least when I save my data, I know that it's gonna remain my fucking data - forever. Explain to me how the ability to unzip a file and extract ASCII-based XML is going to "force me to abandon" this? Oh, could it be that I will not be able to compile the damn program myself? Would it be that the software - OpenOffice itself - ceases to exist? (Hint: it's the source code, stupid)...maybe I'll be incapable of figuring out XML from the structured text, no that's not it...ah! we'll forget that ASCII exists...but everyone's been using it for decades, that's not it either...oh, I know, the Zip standard will be hidden from view and erased from memory as our new Neural implant DRM chips are grafted to our skulls by our American Emperors... (in which case, (a) the nation of zombies won't give a shit and (b) we all have bigger problems)

    • Who cares about 8 year old documents? At that age, it's worthless anyway...

      Complete horseshit. Those who forget history are condemned to repeat it. Those who use proprietary formats to store their hard-worked data in will be condemned to recreate their work. There's no arguing this point, and if you think you can, then I suggest you go to your local library and tell the librarians to "remove all of the books on the shelf that are over 8 years old - because they're obsolete." How long do you think it will take for them to stop laughing at you and tell you to get the hell out?

    • But it's so ugly...I can't stand it...

      There's practical, and then there's goddamn picky. Keep looking that gift horse in the mouth, Mac Community, keep looking...(emphasis on the GIFT portion of that last sentence - OO is a gift that you have chosen not to take. So be it...)

    • But there's Microsoft Office...

      This is probably the dumbest excuse. The only reason you have MS Office is because the Microsft Mac Business Unit (aka. the folks that make MS Office for Mac) are making a shitload of money (like, some $500 million - gee Johnny, can you say "half a billion dollars"? I knew you could!). Of course, if Steve-o comes up with a workable spreadsheet, people will shitcan MS Office quickly...guess what happens then? Of course, I doubt that many of you remember when you lost your Word for Mac documents years ago because MS wanted to fuck the Mac crowd over for some money...

    • There's NeoOffice...

      Ahem. There's a fork of OO that may or may not stay compatible. Or maybe it will break in 1-2 generations of OS X (remember how things broke between 10.2 and 10.3? Oh, that's right, I shouldn't mention that...)

    That's what I thought - none of you have an answer for this.

    No, wait a minute - you have an answer. It's the same answer that the Microsoft customers have. It's bend over and lube up (be sure to use the plain kind - I hear that the icy hot stuff stings).

    Flame away if you like, but I'm merely the messenger. Mac community, you need to wake from your slumber, and realize just how precarious your position is...the Mac is a great platform, but you can't mold the world to fit it's shape, you'll just pay the price in the end...the Linux crowd has been trying that for some time and have already paid dearly...heed the words you don't want to hear before you REALLY are hurting...

    P.S. It's actually not too hard to figure out a way to put Apple out of business in 5 years or less. But I'll leave that as an exercise to the reader...

  151. Did you read the article? by realkiwi · · Score: 1

    It said that X11 version continues and it will be Aquafied by NeoOffice/J. It said that an Aqua fork was not sustainable. This has been the case for quite some time now.

    --
    realkiwi
  152. Spot on by microbox · · Score: 1

    Most Mac users don't want to run second-hand programs, and second-hand is exactly the impression OO.o leaves on the Mac.

    The very first chapter of the original "Inside Mac" talked about how GUI programs should communicate with the user. One major point that was made over and over again was consistency. If Mac does something one way, then anything else just isn't "Mac". Every OS has a feel like that, but on the Mac it's more consistent.

    Pushing the rules of another interface guidline make OO.o appear clunky, and ill conceived.


    I was really looking forward to an Aqua port of OO.o.

    Yep.

    --

    Like all pain, suffering is a signal that something isn't right
  153. Re:Sour grapes by mrchaotica · · Score: 2, Insightful
    Since when did buying software become a bad thing?
    Since we were forced to buy it from Microsoft!
    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  154. Re:Mac OS X = Mac Porn X!!! by setmajer · · Score: 1

    How bad is Mac OS X?

    As a platform for running OOo? Really, really, really bad.

    For lots of other things, it's really, really great (I'm using it to write this post).

    How expensive is Apple's PowerPC?

    US$ 499
    --

  155. Re:Sour grapes by killjoe · · Score: 1

    I didn't say it was a bad thing. I simply pointed out that it's an option.

    Just pay for something and call it a day.

    --
    evil is as evil does
  156. Re:Sour grapes by angel'o'sphere · · Score: 1


    Honestly will the mac user community do anything about this or will they simply pay for msoffice and call it a day?


    As long as nly MS Office is available. YES.
    If OO was available we would pay for that as well.
    Most Mac users are USERS, not coders. I asume your question wants to imply: get up your ass and start coding if you want a native aqua app. Sorry. 85% of the mac users are USERS. The other 15% are coders who code aqua based software or multiplatform software in Java.

    And yes, like some other posters point out: OO sucks big time on a Mac. It starts with installing. On my Mac Jaguar upgraded to Panther I needed several days to get X11 running. As I had the option to use Apples X11 or a X11 app included (or recomended) with OO.

    For some reason I did not get it running ... the installation process allways claimed I had no X installed and when it asked t install it I said yes. When I started any OO app it failed to start the X11 Server. So I installed one manually. OO did not like it. So I installed OO again. It complained I had no X11 .... and so on.

    Suddenly it worked, no idea why. My girlfriend has a younger Mac. She jsut downlaoded it and double clicked teh installer ... that was all and it runs.

    Anyway. OO on a Mac is difficult to use ... slow and ugly. Its simply depressing to have switched from windows and see a application on your desktop which is even uglyer than a windows application.

    Finally, to answer your question: I rather payed $400 for OO than $400 for MS Office. But the former I can not even get for good money as native aqua app :D

    angel'o'sphere

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  157. Can't wait until 2006 by Anonymous Coward · · Score: 0

    When Microsoft Longhorn makes Linux it's bitch!

  158. ahhh.... they can't compete with MS Office... (-) by Anonymous Coward · · Score: 0

    ahhh.... they can't compete with MS Office...

  159. Screw all you Airy Fairy Macophiles! by Chas · · Score: 1

    Wah! A product that isn't meant only for us isn't going to waste their time catering exclusively to our infantile wants!

    Wah! It's gotta look just like all the other crap on our system or we'll whine!

    Wah! They suck because they won't give us exactly what we want!

    You know what? If you don't like it USE ANOTHER FUCKING PRODUCT YOU FUCKING CRYBABIES!

    Or get off your asses and devote some of your copious free time and dubious talent to the actual development efforts instead of being leeching little fucktards.

    Yes. I know this will get modded as a troll. I don't particularly care. It needs to be said.

    --


    Chas - The one, the only.
    THANK GOD!!!
  160. Re:Sour grapes by Denyer · · Score: 1
    Why would you expect to write a program for one type of GUI, port it, but keep exactly the same interface, and expect the people on the second platform to think your program works very well?

    There's often a difference between things working (performing a function) and looking nice.

    --
    Ph-nglui mglw'nafh Gates M'dna wgah'nagl fhtagn.
  161. The OOo Mac Cancel by Anonymous Coward · · Score: 0

    Well. This is too bad.

    As far as for my small company this means that we will throw out our Linux desktop machines and replace them with Mac Mini's. The tie that tied our Linux machines together with our Mac- and Windows machines, OpenOffice/Win/Mac/Lin, is no longer there. Out goes Linux desktops and OpenOffice, replaced by MS Office/Mac/Win and Mac Mini desktops. We had hoped for a "unified" cross platform office application that would enable us to use all three platforms, but this will clearly not be the case.

    Sorry for those that spent money on OOo/Mac-native. And thanks for the 1 update on 18 months on the "porting OOo for mac"-homepage.

    Trustworthy development

    I am truly sorry

    1. Re:The OOo Mac Cancel by Anonymous Coward · · Score: 0

      NeoOffice/j is still there. neooffice.org
      it works great, i use it daily, based on OO.o1.1.3
      has native printing, and fonts. check it out. save some money.

    2. Re:The OOo Mac Cancel by wordtech · · Score: 2, Interesting

      I first tried NeoOffice/J a year or so ago. It was huge, took forever to boot, and ran dog slow. I wondered: why on earth would anyone rewrite a beast like OO.org in Java?? Didn't realize the Java part was a lightweight wrapper around the OO core.

      Anyway, I went back to using OO.org X11. It's huge, and runs pretty slow, and looks like crap, but it works. The Start OO.org AppleScript launcher, which provides an icon to start OO.org, and also provides support for OO filetypes with icons, is a nice supplement.

      After seeing this today, I tried the current version of NeoOffice/J. I didn't realize it was this far along. A real Mac menubar! Aqua print dialogs! Starts up reasonably fast! No X11 required! Compared to OO.org X11, this is already a native port. Yes, it has a little further to go, but my gosh, what a good job for a project with two or three developers.

      Great job, guys!

  162. Re:Interesting that all of the parents are modded by Anonymous Coward · · Score: 0

    "I think the success of projects like this will depend on ditching the Stallmanite mentality of "good enough" and moving to what customers want."

    OO doesn't have any "customers" because nobody is paying for it, so (as many others have said) just what incentive do OO developers have for supporting Mac users with a native port? Probably rather less than all those commercial software shops who also ignore Mac users. At least OO actually runs on Macs, which is more than can be said for many closed-source programs!

  163. Why not port OpenOffice to SWT? by jalkipalki · · Score: 1

    Is that at all possible, or is that silly? Wouldn't the whole porting issues we have now disapear. If we did that.

  164. iWork and spreadsheets by Saint+Fnordius · · Score: 1

    I suspect that database and spreadsheets are things Apple sees as "not used" by about hapf of the potential iWork audience. Everybody writes letters, but how many use the spreadsheet program?

    Instead, I think Apple will refer these customers to FileMaker, I personally find works fine as an Excel replacement. All of my spreadsheet needs are elegantly filled, and if I want I can slap a graphical mask on it.

    Besides, Apple wants other companies to write the software for the Mac so they can concentrate on making hardware. Maybe the spreadsheet hole is one they left open on purpose to encourage third-party solutions. (I can see the ad copy now: "the spreadsheet solution that seamlessly fits together with iWork!")

    I think iWork is intended to play the same relation to full-fledged office suites that iPhoto plays with Photoshop: a low-cost alternative that meets basic needs well, for those customers who don't need all the tools the high-end programs offer.

  165. It's not just the GUI toolkit by Craig+Ringer · · Score: 1

    It'd be nice, but as explained in the article wouldn't solve the whole problem. You still have event model integration, you still have the nightmares that are fonts and printing, etc.

    It'd still be nice, though.

  166. Why not use Wx? by Anonymous Coward · · Score: 0

    I think that for cross platform gui builds you should really be looking at buliding your apps abstracted to use Wx libraries. I've heard lots of flame on the subject, however Wx is pretty solid and good today. If OOffice wants to be seen as a viable all round alternative to Mircosucks Office, they should really make sure that Aqua, Windows and X11 are all supported. I don't particularly like using Open Office through X11 on my Mac. Mostly because I get the same non-tarnsparent feel as though I were running it through an emulator on my old G3. It crawls. I'm ashamed to say I actually prefer to use Mac Office on my mac; whilst I avoid using microsucks at work by using Open Office on my Blade. Anyway, as I said, they should use Wx as a wrapper around native widget sets.

  167. Re:Mac OS X = Mac Porn X!!! by TheRaven64 · · Score: 1

    I have a dozen or so PowerPC-based Macs (and one or two 68040 based ones) sitting in my attic. Attempts to give them away have so far failed completely. Of course, they're only 60/66MHz...

    --
    I am TheRaven on Soylent News
  168. Twisted Logic by mlg98 · · Score: 1
    So calm down. This isn't an Apple conspiracy, or the end of OpenOffice for Mac OS X. OpenOffice will continue, in X11 form AND in the likes of things such as NeoOffice. If anyone is to blame for the official OpenOffice.org Aqua port going by the wayside, frankly, it's a lot closer to Sun than anyone else.


    Right, so now it's Sun's fault for not using their infinite engineering resources to port OO to a proprierary API with less than 5% of the target user's marketshare.

    If anyone is to blame, I would say it is Apple. OO is an open source project. Apple's could support the project and provide engineering resources if they really cared. Why should it be Sun's responsibility to support every niche OS out there?
    --
    Code to live, live to code.
  169. Re:Sour grapes by jedidiah · · Score: 1

    When you constantly buy the same thing over and over again for more than 10 years.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  170. Re:X11 Aqua? by jeremyp · · Score: 1

    No.

    Interfaces should conform to the guidelines of the platform they are running on. This is because most people use lots of apps on one OS, not one app on lots of OS's.

    --
    All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
  171. OOo X11 isn't competitive on OSX by arete · · Score: 1

    First, let me say that the only microsoft product I still recommend, even if they're all free, is the Office suite for OSX, because there are no powerful, viable alternatives (except possibly iWork, now) and because it's the best software I've ever seen Microsoft come out with.

    For a while I was using an OSX laptop that didn't have it, and despite having OOo installed I'd literally go to another machine with a different OS and use OOo there instead of using it on the mac.

    Keeping in mind that I'm a geek and that I professionally maintain Windows, OSX and linux systems - Getting X11 and OOo to install correctly was a pain, especially for it only take one double-click to start OOo. Starting it up takes too long. It's tricky to exit cleanly out of it, because there's no X11 integration with the dock, which also means window switching doesn't really work right.

    It's plausible they've fixed some of this...

    --
    Looking for freelance Actionscript (Flash/Flex) or ColdFusion work and/or freelance developers. Email me, put Slashdot
  172. Re:Mac OS X = Mac Porn X!!! by chrish · · Score: 1

    I've got a UMAX s900 DP180 (dual processor, 180MHz PowerPC 604e Mac clone) that nobody loves, that I'd be happy to part with.

    --
    - chrish
  173. Re:X11 Aqua? by steve_l · · Score: 1

    I agree there, but also think that Eclipse's SWT kicks swings overweight butt, and, because it is OSS, can be used in Kaffe without any need to do a reimplementation...

  174. AppleScript versus Unix world by DrYak · · Score: 1
    AppleScript. Do all YOUR [assume you're a Linux user for a minute, please] graphical applications support scripting -- and more importantly, cross-application scripting? Mine do! And I can mix Applescript and Bash script in the same file.


    Yes. And it's called "a pipe".
    I'm not speaking about GIMP's built-in Lisp engine.
    I'm speaking about the fundamental difference between "big iron OS" like Windows and Mac OS, on one hand :

    - where application are monolithic big irons the you must install from 1 if not many CDs. They're huge integrated monsters that should be self-sufisant (or that's what the marketing compagny thinks). And if you want to do something different : it's either "Sorry our GUI isn't intented for this. And we cannot waste ressource on some obscure feature that only 1% of our market share is interested in" (Windows World) or "Look ! It's incredible ! You can actually launch individual functions of our applications from your scripts ! The Mac invented the wheel !" (Apple style)

    on the other hand, you have the Unix "keep it in small useful units" style :
    - an application is just a tiny bit of code specialized in doing only 1 single function. It it does it very well, with lot of parametrability. And it's up to the user to combine these function and do work the developper never though of before.
    All this using a dead simple stuff like "¦".
    Or using a nice GUI that ties everything together (see CDRECORD, CDRDAO, MKISOFS, etc... and K3B. I guess that using LAME inside a huge CD-Burning application, wasn't LAME developpers main purpose)

    Mac people are happy because Adobe photoshop supports AppleScript ? So you can write scripts that automagically download pictures from your digital camera, convert them, and upload them to your blogs ?

    We linux people have things like imagemagick, pbm, whatever... that can be glued with command lines, shell scripts, perl programms or whatever. And we can do most of the same things you can do in AppleScript. Except we don't need to install an application that comes on 2 CDs and costs 299$.
    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:AppleScript versus Unix world by forkazoo · · Score: 2, Insightful
      Okay. I have a fair amount of experience with OS's. Solaris (SPARC and X86), Linux, Windows, OS X, old Mac OS, Irix...

      Fundamentally, I agree with you. I like it when I have small utilitues that do small things very well. I've burned a lot of CD's using cdrecord, for example. (Mainly to make boot CD's for my dreamcast - I have yet to find a slick integrated monolithic GUI app that makes developing boot CD's for obscure platforms a convenient thing...)


      - where application are monolithic big irons the you must install from 1 if not many CDs. They're huge integrated monsters that should be self-sufisant (or that's what the marketing compagny thinks). And if you want to do something different : it's either "Sorry our GUI isn't intented for this. And we cannot waste ressource on some obscure feature that only 1% of our market share is interested in" (Windows World) or "Look ! It's incredible ! You can actually launch individual functions of our applications from your scripts ! The Mac invented the wheel !" (Apple style)


      Now, let us ponder for a moment... Not everything is done best by small command line utilities. For example. Let's suppose that you have PowerPoint, or a PowerPoint type clone. It makes sense for it to be a fairly monolithic app. But, it also makes sense to be able to script your presentations.

      The Windows way would involve VB. So, no right thinking person need consider the Windows way.

      The Linux way would involve exposing as much as possible of the GUI to the command line. Possibly inventing some sort of scripting language. It would sloiw development, because it would require substantial resources to impliment well, and keep current with the GUI, and make all GUI functionality available to the command line API.

      The Mac way would, naturally, be AppleScript. The develoiper doesn't need to make a bunch of little utilities to go along with his monolithic app. He doesn't need to maintain an API. Adding Applescript requires a tiny amount of work for a native app. It exposes large amounts of functionality conveniently. In the hypothetical presentation app, it would be trivial to allow the scripts to set a presentation to have as many slides as there are images in a directory, and add text on the slides extracted from EXIF data in the JPEG's, and then overlay some lines and such, and set random transitions between them all.

      Sure, you could just use ImageMagik to add text on top of the slides, and add some graphical elements, and save them out as a different set of JPEG's, but if that isn't what you want to do, it doesn't help you. Sometimes you really want to use a monolithic app because it is the right tool for the job, and no amount of chanting UNIX mantras will cause your spplications to change into something else, and more than a Windows user chanting his mantras will turn sed, awk, and teco into a monolithic friendly GUI application.

      By having a sane systemwide scripting language, you have the ability to make use of those monolithic GUI apps, and still use the little utilities (in my above example, you would probably use a "classical" command line utility to get the EXIF data to tell the presentation program to put on the slide)
    2. Re:AppleScript versus Unix world by mrchaotica · · Score: 1
      And we can do most of the same things you can do in AppleScript.
      Most, but not all, which is exactly my point!

      Macs DO have the UNIX "keep it in small useful units" style, but we ALSO have Applescript. So I can write a script that grabs pictures from my digital camera, runs them through Photoshop or ImageMagick, imports them into my iPhoto database, uses iPhoto to make a CD slideshow of them, and copies them into my website folder and generates a web page gallery so that Apache (which comes installed by default in Mac OS, dontchaknow) can serve them!

      I can make a script to burn cds by piping together CDRECORD and whatnot... but I can select the tracks to burn by reading them from a smart playlist in iTunes!

      Now, Gimp's Lisp engine is a great thing, but just imagine how much better it would be if it were integrated with the rest of your apps so that you could script a workflow that used Gimp, Firefox, OpenOffice presenter, etc. That's what I'm talking about!

      And if I want, any script that works in Linux will work on my Mac too (especially since most of the programs involved are either already installed or available via Fink).
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    3. Re:AppleScript versus Unix world by DrYak · · Score: 1
      Fundamentally, I agree with you. I like it when I have small utilitues that do small things very well. I've burned a lot of CD's using cdrecord, for example. (Mainly to make boot CD's for my dreamcast - I have yet to find a slick integrated monolithic GUI app that makes developing boot CD's for obscure platforms a convenient thing...)
      I definitly see what you mean... Maybe we should pair efforts and try to write some small but nice interface to assist burning booting CDs.
      Now, let us ponder for a moment... Not everything is done best by small command line utilities. For example. Let's suppose that you have PowerPoint, or a PowerPoint type clone. It makes sense for it to be a fairly monolithic app. But, it also makes sense to be able to script your presentations.
      Altougth I agree with you on this point (It's hard to imagine complex documents handled only with small programms and no Office-like suit), this case of complexe documents brings another point, beside scriptability, that I hate in Windows environment : the format. (Sorry for the digression) Under Windows, if you think of a presentation, too often you'll be forced to use MS-PowerPoint. And PowerPoint is the only software capable to handle such documents, so you're stuck. One thing I would like to see more, is the trend that lot of linux application have to use standart and well documented format. In the case of the presentation, under Linux, you're very likely to encounter presentation using a standart format like HTML or XML (and PNG/JPEG for the image). This files can also be handled by other tools, like HTML handler or text-tools that were never initially intended to handle power-point-like documents. You can automatically edit OpenOffice Impress documents using only "zip" and "sed". That's something that I miss a lot in "huge monolitic apps". They're so stuborn with their "everything should be done from inside our application"-idea, that their software create files that are completly useless outside their application. Some people may complain about XML and other human/machine/readable document (recent slashdot story about streaming and binary XML). But on the other hand, these formats enable you to do easily wonderful thing with standart tools.
      --
      "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  175. Re:Mac OS X = Mac Porn X!!! by hub · · Score: 1

    Looks like those UMAX Dual CPU that Be gave away as prize... Should work great on Linux. Is it still working. Were are you located ?
    (contact info profile)

    --
    Hub
  176. Re:Mac OS X = Mac Porn X!!! by StarKruzr · · Score: 1

    Sold.

    Email address is starkruzr@starkruzr dot com. We can talk price later :)

    --

    +++ATH0
  177. Re:Mac OS X = Mac Porn X!!! by StarKruzr · · Score: 1

    I'll take one (or four). Where are you?

    --

    +++ATH0
  178. neooffice/j review by cellocgw · · Score: 1

    Many posts so far have rightfully complained about the slow performance of OO.o under X11. But if you install NeoOffice/J instead, it boots and runs rather smoothly. This is still a wrapper of sorts around OpenOffice, so the actual window, toolbars, and so on are the same. But I think you'll find NeoOffice/J to be quite good enough for freeware.

    BTW, regardless of platform, OpenOffice has just GOT to implement "Normal View" for its word processing module. This has been on their wish/bug list for a couple years now. What's the holdup?

    --
    https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
  179. There's a third option by melted · · Score: 1

    Just replace that ugly toolbar, and trick QT into conforming to HIG. Nobody will tell you're using QT. Right now I can see your app is QT based from 10 miles away.

    1. Re:There's a third option by Brandybuck · · Score: 1

      The HIG everyone gives me a link to was written in 1997, doesn't cover Aqua, and doesn't say one damned word about toolbars.

      So tell me, is my app to fscking embarassing to you Mac purists that I should completely cease all Mac development efforts? That's sort of the impression I'm getting. It's no skin off my back, because it would leave me more time to develop actual features instead of worrying about offending someone's aesthetic sensibilities.

      --
      Don't blame me, I didn't vote for either of them!
  180. Aqua HIG by Anonymous Coward · · Score: 0
    Aqua Human Interface Guidlines.

    "Last updated: 2004-12-02"

    Not really that hard to find.

    1. Re:Aqua HIG by Anonymous Coward · · Score: 0

      Not really that hard to find.

      No it's not. Which makes it even more surprising that people kept posting the WRONG link.

  181. Why do you have to view everything in a negative by melted · · Score: 1

    way? How about just putting in that extra bit of effort necessary to be a first class citizen on a desktop platform that's more popular than your primary development platform? Or at least asking someone with a Mac to do it for you?

    In order to fix the problem you need to acknowledge its existence. I'm not a Mac purist. In fact, I'm typing this from my Win XP laptop. However, I do have a Mac, and I know of at least one case where I didn't buy a product (Bibble from Bibble Labs) precisely because it was QT based. It looked bad. It was functional, it did everything I wanted but it looked bad. I've downloaded a demo version and after about an hour I decided there was no way in heck I'd torture myself with something like this. It used Aqua widgets, too, but it neglected spacing, layout and "feel". It was alien.

    Luckily there was a native, polished version from another company (Capture One LE by Phase One), selling for the same price. They got my $100 that evening.

  182. Re:Why do you have to view everything in a negativ by Brandybuck · · Score: 1

    Why do you have to view everything in a negative way?

    Because until this thread I have never received any complaints about the Mac version of my software. Quite the opposite, I've received dozens of letters of gratitude. But then there's this thread.

    Apparently my widgets are layed out randomly. I've been called incompetent. My application doesn't cut it. And of course, it "looks like ass."

    How about just putting in that extra bit of effort necessary to be a first class citizen on a desktop platform that's more popular than your primary development platform?

    First of all, my primary platform is NOT Windows. It's FreeBSD. Last I heard it wasn't more popular than OSX, but I guess I'm behind the times.

    Second, I've put in a LOT of extra bits of effort. But apparently I haven't put in enough extra bits of effort. Excuse me for not owning a Mac, okay? This is why I'm so pissed! I put in that "extra bit of effort" and it's not good enough! The lesson is that it's better to never have tried then to try and come in second place.

    I'm not claiming that my software is finished. There are a lot of "extra bits" needing to be done, on *ALL* platforms. But I don't have to time to devote myself 100% to creating the epitome of the perfect Mac application.

    All I said in my original post was that Qt/Aqua made my application appear to be native. I still stand by that statement, because "native" isn't synonymous with "perfect".

    --
    Don't blame me, I didn't vote for either of them!
  183. Re:Interesting that all of the parents are modded by jbolden · · Score: 1

    What exactly does Stallman have to do with "good enough" and not being customer centric? I can't think of a single quote of that nature in all of his writings. He has consistently advocated the opposite position that free software should aim to be far better than the commercial products, far exceed user expectations....

  184. An Alternative Solution? by Anonymous Coward · · Score: 0

    Perhaps an alternative solution would be to petition Apple to add OOo format compatibility to their new office suite.

  185. you confused... by Anonymous Coward · · Score: 0

    Wow. You sound an angry little anti-fanboi.

    I think you have it backwards. Jobs has a knack for making what some people want, and this in turn creates die-hard fans. It's not the other way around.

    Also, I do not think that word you keep using (debacle) means what you think it means:

    - the goal of the iMac mini is to increase market share

    - the jury is out on the iPod Shuffle...pundits bagged on the iPod Mini when it was released.

    - powerbook sales are good, despite rumors of a G5 Powerbook coming down the pipe.

    Last, you ramble using "Mac people" and "fanboi" interchangeably in a most confusing way. You seem to be saying that all mac people are fanboi's, and that most mac people buy used mac's on eBay, sold by you, apparently, who is not a mac person, but buys new stuff from Apple from time to time. This makes little sense to me.

    You may bag on Jobs, but the Q4 numbers speak for themselves.

  186. Re:Interesting that all of the parents are modded by Anonymous Coward · · Score: 0

    > What exactly does Stallman have to do
    > with "good enough" and not being
    > customer centric?

    Free Software values the freedom higher than the quality of the software. The quality will improve automatically because the software is free.

    Of cause, this requires an apropriate environment and does not work well in the Mac "community".

    But as the grand grand parent already pointed out, the people who prefer to be slaves to commercial entities (heil steve!) will die out sooner or later, hopefully.

  187. Re:Mac OS X = Mac Porn X!!! by Anonymous Coward · · Score: 0

    I disagree.

    Using Apple X makes it almost seemless