> That's Sun's opinion. And as Oscar wrote, there are only 2.5 people > working on NO. Considering the problem from the user's side, It is > clear that removing X11 dependancy from the code should be considered a > priority. X11 is an anomaly in the OSX world. OSX development does not > happen on the X11 base. X11 is only here to give access to legacy > applications.
Sun doesn't put much into OOo on Mac, anyway. I mean, the best proof I have of that is that they do *not* sell Star Office for Mac. they don't think the X11 is good enough to put on the market. And, of course, they are right. I can't for the life of me understand why they keep shoving X11 down Mac users' throats, when Neo/J is obviously a *much* better solution. Using Carbon and Java (*cough cough* JAVA, Sun, J A V A) works *much* better than X11. Quite frankly, as a Mac user, I can tell you X11 sucks. Not just the OOo X11 port, the whole X11 thing. I can't stand to use GIMP on Mac, because it requires X11. The windowing system is all screwed up, things float all over the place, and if you close the wrong window, your whole program shuts down (even if you have 5 or 6 *other* windows open). In native Mac, as with Neo/J, if you close *ALL* the windows, the program is still running, unless you told the program to close. So closing windows is common, and having to have all the windows open to ensure that your program doesn't crap out on you is a pain. > If Sun thinks providing what looks like legacy applications on OSX is > an option, it is very possible that OSX users will not show much > interest in OOo. That may be why Sun doesn't want to try to fix anything. I don't think Sun has enough faith in OOo, (or StarOffice) to put it up against the heavy hitters on Mac. Microsoft Office 2004, AppleWorks, and the new iWorks, are all very slick, very user friendly programs, very *Mac*. OOo X11 is not. Neo/J isn't as slick as the others, but it is at least Mac-like in appearance and function. Heck, even AbiWord looks great on the Mac. I'd use AbiWord (which is Mac native) long before I used OOo X11. Of course, with Neo/J I don't have to limit myself. > Why can't Sun take the responsibility of working on removing X11 > dependancy and still keep a portable code base ? Ask Louis. It all "makes sense". ::-| X11 is "the way to go".... Don't make me laugh... -Chad Smith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
