Slashdot Mirror


At Long Last, NeoOffice/J 1.1 Released

VValdo writes "After nearly five years of development, NeoOffice/J has made it to its first stable release. NeoOffice/J 1.1 is a Mac OS X-integrated office suite based on OpenOffice.org 1.1.4 that includes word processing, spreadsheet, presentation and drawing applications. Key Macintosh features include a standard Mac OS X installer, a native Aqua menu bar, use of the native printing system, full clipboard support, drag-and-drop, Mac "command" key shortcuts, mouse scrolling, integration with major Mac email clients and native support for Mac fonts. The full announcement is here."

336 comments

  1. That's nice, but... by Anonymous Coward · · Score: 1, Funny

    does it run on Linux?

    1. Re:That's nice, but... by DarkVader · · Score: 1

      Do you have NO CONCEPT of a sense of humor at all?

      I service and sell Macs for a living, and I thought it was funny.

    2. Re:That's nice, but... by theTerribleRobbo · · Score: 0, Offtopic


      PearPC. :P

    3. Re:That's nice, but... by caseih · · Score: 1

      Have you ever used a java program under OS X? If the program follows OS X conventions and uses Swing, Java apps look and feel just like normal mac applications. No Java hasn't failed on the desktop. Java on the OS X looks and feels like a first-class application environment.

      NeoOffice/J only uses java to implement some things and doesn't use swing. Therefore at this point, it's simply OpenOffice/X11 with the X11 parts replaced with Java drawing code and a native menu (as well as finder integration).

    4. Re:That's nice, but... by they_call_me_quag · · Score: 1

      > If ... balh, blah blah... Java apps look and feel just like
      > normal mac applications.

      First of all the article is about NeoOffiice/J, which is a Java app running Mac OS X. And it looks like crap. I have no visibility to the decisions the NeoOffice/J developers made. All I know this is a Java application and it looks like ass. End of story.

      But, to answer your question, yes I have tried to use some Java applications on Mac OS X. Most of them suck. They have slow start-up times, weird ui, and little support for native technology. I don't really care that it might be possible to make a nice Mac app in Java, I care that nobody actually does it.

      And how much desktop software is written in Java anyway? Not much. What happened to all of these Java-on-the-desktop gems?:

      * Netscape Communicator
      * Wordperfect
      * Quattro Pro
      * Lotus eSuite

      Every one of these applications was supposed to get totally rewritten in Java. (Go search for the press releases and news stories... they are still out there.) These promises were made by Sun's partners and promoted loudly by Sun's PR machine.

      Did a single one of these mythical Java apps ever ship?

      No.

      Java has failed on the desktop.

    5. Re:That's nice, but... by yoxi · · Score: 1

      NeoOffice/J is NOT a java app - most of the coding that makes this port of openoffice.org work on the mac without needing X11 is written in c++ - the java (such as it is) is there for carbon integration. This was the quickest way to get this up and running stably. The look of it is - so far - entirely the OOo code's fault, you can blame the OOo developer community (who are almost entirely developing that for win/linux) for the looks. The NeoOffice/J team have had a load of hard work to do getting what native stuff they already have into Neo/J - OSX printing and fonts, never mind the menu bar (oh, and nice maccy icons for the toolbars are on the way too). The point was to get something out there that really worked, and was stable, and then concentrate on the continuing aquification, and the move up to v2 code and away from java 1.3.1 dependency. It's a process, innit. repeat: this is NOT a java app, any more than OOo on its other platforms is.

  2. What's with the J? by ziggamon2.0 · · Score: 0, Redundant

    What's with the J? Can anyone explain?

    1. Re:What's with the J? by Anonymous Coward · · Score: 4, Informative

      J stands for Java.

    2. Re:What's with the J? by DavidLeblond · · Score: 0, Redundant

      Stands for Java. Five guesses as to what the majority of NeoOfficeJ was written in. First 4 don't count.

    3. Re:What's with the J? by Ford+Prefect · · Score: 1, Funny

      Stands for Java. Five guesses as to what the majority of NeoOfficeJ was written in. First 4 don't count.

      C++, of course!

      What do I win... ;-)

      --
      Tedious Bloggy Stuff - hooray?
    4. Re:What's with the J? by thelamecamel · · Score: 2, Informative

      Actually most of it's written in C++ (IIRC, the FAQs are down), same as OpenOffice.org. Only the OS X specific bit's in Java.

    5. Re:What's with the J? by CleverNickedName · · Score: 3, Funny

      It's the next version up from Apple's iVersion.

      --


      Unfortunately, I am not Wil Wheaton
    6. Re:What's with the J? by volsung · · Score: 4, Informative
      The main issue with porting OpenOffice to the Mac (and NOT using X11) is how to interface with the Mac OS APIs to draw the GUI, handle the clipboard, etc. Apple offers C, Objective C and Java bindings to these APIs.

      So, once upon a time there was a NeoOffice/C which used the C bindings, but for some reason it was very difficult to develop. The authors then abandoned it and used the Java bindings instead, producing NeoOffice/J. This was only feasible because OpenOffice makes heavy use of Java internally.

      (One minor point of confusion for me: The NeoOffice FAQ claims that NeoOffice/C used the Cocoa API, but I thought that was only for Objective C and Java. I thought for pure C you had to go with the Carbon API.)

    7. Re:What's with the J? by bsharitt · · Score: 4, Informative

      Just as with C++, regular C code can be used in an Objective C program, but still be treated the same, so you can us C with Cocoa.

    8. Re:What's with the J? by tverbeek · · Score: 1
      J is for Java, which was one of two toolkits the NeoOffice developers tried using to integrate OOo into OS X. The other version was NeoOffice/C, which was an attempt at creating the legendary "native Mac app" version of OOo. It didn't go well.

      Meanwhile, the NeoOffice/J project used OS X's Java toolkits, and worked rather well, rather quickly. The NeoOffice/C project was abandoned as the porting equivalent of beating one's head against a brick wall to make a doorway, when you've got an Acme Doorway Cutter tool sitting next to you.

      For the record, most of the guts of NeoOffice are the same compiled C++ code as the Linux/BSD/Solaris version of OOo. Java's just used to tell OS X what kinds of pretty window dressing, fonts, etc. to put on the screen.

      --
      http://alternatives.rzero.com/
    9. Re:What's with the J? by DesScorp · · Score: 1
      This was only feasible because OpenOffice makes heavy use of Java internally.


      So that's why OpenOffice is a dog, speeedwise. I've got a 2 gig P4 at work, and I'd had wounds heal faster than OO.org starts up at times...
      --
      Life is hard, and the world is cruel
    10. Re:What's with the J? by Anonymous Coward · · Score: 0

      Five guesses.... First 4 don't count.

      If you're going to give us nine guesses, just say nine guesses!

    11. Re:What's with the J? by con · · Score: 1

      > This was only feasible because OpenOffice makes heavy use of Java internally.

      This is just a myth. Java is not used much internally in OOo. It is however used for several purposes :
      1) the build environment to produce files needed for the final product ( the help files I think, and maybe more)
      2) in 1.1 for the report generator
      3) in 1.1 for some of the "export as" features
      4) in 1.1 possibly in one other minor area which escapes me now

      It is true that in 2.0 Java will be used a bit more :
      1) for mail merging
      2) for some wizards
      3) for media playback
      and maybe other "additional" areas.

      Of course it is possible to write add-ons in Java, but this is also true of StarBasic and Python.

      None of the above constitutes "makes heavy use of Java internally".

    12. Re:What's with the J? by Anonymous Coward · · Score: 0

      It's the next version up from Apple's iVersion.

      I don't think so. Microsoft beat Apple to it. See jAnus.

    13. Re:What's with the J? by Uncle+Asad · · Score: 1

      Most or all of the new database component in 2.0 is Java. I still don't think that constitutes "heavily"--but it probably does mean that OOo 2.0 has more Java in it than NeoOffice/J! ;)

    14. Re:What's with the J? by CarrionBird · · Score: 1
      The J stands for slo...er java

      Sorry, couldn't resist.

      --
      Free Mac Mini Yeah, it's
  3. How much Java? by /ASCII · · Score: 1

    I seem to remember reading the a large part of NeoOffice was done in Java. I can't check the wiki since it has been slashdotted, does anyonw know how much Java is in NeoOffice?

    --
    Try out fish, the friendly interactive shell.
    1. Re:How much Java? by AKAImBatman · · Score: 2, Insightful

      I can't check the wiki since it has been slashdotted, does anyonw know how much Java is in NeoOffice?

      A LOT. NeoOffice/J more or less uses the core of OOo for opening/saving files, and rendering the GUI to a back-buffer. Everything else, such as the screen handling, clipboard, I/O, and anything else machine specific, is done through Java.

    2. Re:How much Java? by Anonymous Coward · · Score: 1, Informative

      Very little. Most of the Mac-specific code is Carbon. Java is used primarily for screen drawing and a bit for configuration.

    3. Re:How much Java? by DarthWiggle · · Score: 1

      Venti?

  4. Just when they get if finished.... by steveyT · · Score: 4, Funny

    Apple go and change the architecture they're running on :D

    1. Re:Just when they get if finished.... by harvardslacker · · Score: 2, Interesting

      Will that be a huge setback to the project, or will they just be able to check a box and recompile, as Steve Jobs suggested in his keynote? I guess it's probably the former, since they're probably not using XCode. Alas. I'd check the Wiki to see, but it's /.ed.

      Greg

    2. Re:Just when they get if finished.... by Jungle+guy · · Score: 1
      The architecture change made me postpone the acquisition of a Mac Mini. The change might be beneficial in the long run, but on the short term we will have lack of software available for the "Mactel" platform.

      I hope Apple at least send a Mactel workstation for the NeoOffice J team for free. These guys have been working for free, to the benefit of the community of users of the Macintosh. I hope Apple acknowledges the effort, and that, in the day the Apple Intel computer is released, the port of NeoOffice J is finished.

    3. Re:Just when they get if finished.... by Anonymous Coward · · Score: 0

      Perhaps Apple's use of Transitive's product will alleviate the problem :-p

    4. Re:Just when they get if finished.... by jcr · · Score: 1

      on the short term we will have lack of software available for the "Mactel" platform.

      Guess again.

      First of all, Rosetta runs PPC apps really fast, and secondly, recompiling Mac OS X apps to include native Intel code is something that every developer can do by the time Apple ships a Mac with an Intel CPU.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    5. Re:Just when they get if finished.... by FatherOfONe · · Score: 3, Informative

      Well seeing that this had a "J" in the title and it appears to have used enough Java in it to warrent that name, I would bet porting "may" be easier than you think. Easy being a relative term in all...

      Now "if" it was totally written in Java, then I would say it would be very easy to port :-)

      My gut feeling is that a significant portion of it was done in C, and thus it will take some time to get that part compiled and working again.

      --
      The more I learn about science, the more my faith in God increases.
    6. Re:Just when they get if finished.... by Shisha · · Score: 2, Insightful

      You don't have to use XCode to be able to do that. In fact, if they wouldn't be bothered about producing fat binaries, they could probably just simply recompile it. Since OpenOffice is multiplatform and Java should be also, they're unlikely to run into problems because of differences in bit ordering (least significant first or most significant first?). I also don't suspect them of having produced too much PPC specific assembly code.

    7. Re:Just when they get if finished.... by Anonymous Coward · · Score: 1, Informative

      - OpenOffice runs with x86, so that part should not be a problem
      - The parts that are done in Java should not be a problem, too (except if you write really, really ugly code)
      - So leftover are parts that are written in C AND are not part of standart openoffice AND rely on big endianess. I'm pretty shure that should not be much.

    8. Re:Just when they get if finished.... by squiggleslash · · Score: 2, Insightful
      I would guess actually the latter. The major issues are - does it compile with the Apple supported tools (my understand is, yes, it uses GCC etc, it just doesn't access them via the XTools GUI), and will it require modifications to deal with endianisms etc (my guess is almost certainly no, because it's based upon the already architecture independent OpenOffice.org, with some additional code written in Java.)

      So for the most part, even if generating a univeral binary is "hard" (and I doubt it will be, I don't have access to Tiger so can't use the latest XCode but I'd be surprised if it's not just the old NEXTSTEP "one binary per architecture in a certain directory, with all the shared files in Resources as usual" thing, generating a binary that'll work on "the other architecture" will be a simple matter of compiling it there.

      --
      You are not alone. This is not normal. None of this is normal.
    9. Re:Just when they get if finished.... by Ford+Prefect · · Score: 4, Insightful

      Will that be a huge setback to the project, or will they just be able to check a box and recompile, as Steve Jobs suggested in his keynote?

      Sounds like it'll 'simply' (heh) involve porting to GCC4...

      What they really need is (a) more programmers with some highly esoteric combinations of skills, (b) a Mac-Intel box or two, and (c) monetary donations! :-)

      --
      Tedious Bloggy Stuff - hooray?
    10. Re:Just when they get if finished.... by R.Mo_Robert · · Score: 2, Funny

      More like....just when they get it finished, OpenOffice.org 2 is almost out!

      --
      R.Mo
    11. Re:Just when they get if finished.... by beef3k · · Score: 1

      Apple go and change the architecture they're running on :D

      ...and OO.org are on the steps of releasing 2.0

      Hope they won't spend another 5 years porting that :)

    12. Re:Just when they get if finished.... by zymurgyboy · · Score: 1
      Actually, I'd say that's precisely when they've announced it.

      You know Microsoft can't be happy about having a (commercial) OS competitor on x86 like Apple; how else would they view Apple shifting from PPC to x86 as anything other than a swipe at their market? Apologies in advance to GNU/Linux fanatics, but OSX is the first real threat to their desktop dominance in some time. MS business is built on the rock of desktop domination.

      So what do you think they'll probably do to swipe back? My guess is, kill the MBU.

      Apple has to know this is coming down the pike, so they're (wisely? time will tell) letting their current customer base know they have something in the works that is reasonably compatible with MS Office when MS takes their own Office suite away.

      --
      If you never make mistakes, it's probably because you're not doing anything.
    13. Re:Just when they get if finished.... by zymurgyboy · · Score: 1

      precisely why they've announced it now, I meant to say.

      --
      If you never make mistakes, it's probably because you're not doing anything.
    14. Re:Just when they get if finished.... by Macrat · · Score: 1

      OOo 2.0 is mostly a rewrite that will need to be ported from square one.

    15. Re:Just when they get if finished.... by Anonymous Coward · · Score: 0

      Are you retarded?

      Yes.

      Hey I got an idea, why don't you send MS a new box to do some dev work on. After all they are helping the community.

      Are you retarded?

    16. Re:Just when they get if finished.... by wealthychef · · Score: 1
      recompiling Mac OS X apps to include native Intel code is something that every developer can do

      And of course, the programs that are not still in active development? Hmm. Kiss those goodbye. Not a huge loss, but for some people it will suck a little. Of course, they can continue to use PPC for a long time.

      --
      Currently hooked on AMP
    17. Re:Just when they get if finished.... by wealthychef · · Score: 1, Insightful

      Oops, somebody's an idiot! Rosetta, Rosetta, Rosetta. Sorry. Wasn't thinking when I hit "submit."

      --
      Currently hooked on AMP
    18. Re:Just when they get if finished.... by squiggleslash · · Score: 1
      Those apps, for the most part, will have been designed three or four years ago, when hardware requirements were lesser. As such, running them under Rosetta is almost certainly "as good as" getting a native version.

      The big exception, which neither Rosetta nor shared binaries really addresses, are "Classic" apps. The Intel Macs will not have Classic support. This is going to be a bigger PITA, for example, there is no native OS X Microsoft Exchange client. (No, Entourage isn't an Exchange client, it uses IMAP and users of it are "second class citizens" on all but the most recent Exchange Servers, and then only not if certain features have been turned on. Urgh.

      --
      You are not alone. This is not normal. None of this is normal.
    19. Re:Just when they get if finished.... by geoffspear · · Score: 2, Insightful

      Right. They're so worried that they announced that Office for Mactel was already done about 10 seconds after Jobs made the original announcement.

      --
      Don't blame me; I'm never given mod points.
    20. Re:Just when they get if finished.... by stanthegoomba · · Score: 1

      ...And since most of the interface is Java, it (ideally) shouldn't be too difficult for them to port it!

    21. Re:Just when they get if finished.... by Jungle+guy · · Score: 1
      If it is sooo easy to port a software from Mac/Power PC to Mactel, and if Rosetta is sooo fast, why did Apple broke the news one year before the release? Just to lose sales?

      I don't buy it. And I think Apple should offer some help to Neo Office J or OpenOffice. At least for now, the only complete office suite for the Mac is MS Office.

    22. Re:Just when they get if finished.... by Mage66 · · Score: 1

      There are several Classic Emulators that could be ported to a "MacTel" with just a little work.. - Basilisk II - SheepShaver - vMac - Executor And all will run classic apps.

    23. Re:Just when they get if finished.... by Anonymous Coward · · Score: 0

      And people thought Gentoo was bad.

    24. Re:Just when they get if finished.... by Carnildo · · Score: 1

      Those will run 68k Classic apps. The problem is PPC Classic apps: anything compiled explicitly for MacOS 8 or MacOS 9 will not run - PearPC is just too slow.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    25. Re:Just when they get if finished.... by Mage66 · · Score: 1

      Sheepshaver runs PPC Classic apps. Thanks anyway!

    26. Re:Just when they get if finished.... by rk87 · · Score: 1

      I'm seeding the torrent for OS X x86 .... ;)

      --
      I'M NOT ANGRY!
    27. Re:Just when they get if finished.... by tverbeek · · Score: 1
      I think Apple should offer some help to Neo Office J or OpenOffice.

      It might be swell if they did, but I don't see a compelling motive for them to do so. On one hand, it would mean biting Microsoft, whose support of Office for Mac remains import to "legitimize" the Mac platform. On another hand, it would mean biting... themselves, because their own AppleWorks and iWork are in competition with NeoOffice.

      --
      http://alternatives.rzero.com/
    28. Re:Just when they get if finished.... by squiggleslash · · Score: 1
      Sheepshaver is more of a (stripped down) Mac emulator than a Classic emulator:
      However, you still need a copy of MacOS and a PowerMac ROM image to use SheepShaver. If you're planning to run SheepShaver on a PowerMac, you probably already have these two items.
      There are probably ways in which desperate people can obtain both, but for most it'll be a legally dubious route.

      Ardi's Executor is nicer solution, but as the GP says, it doesn't run non-68k apps. One has to hope that the sudden market for third party improvements in Classic compatability born from Apple's unwillingness to produce Macs that'll run older software will give Ardi, at least, an incentive to put in the long awaited PowerPC emulation support.

      But as of now, I don't think anyone can legitimately say that there are real solutions for running (most) older, non-Carbonized, Mac software on the Intel Macs, sadly.

      --
      You are not alone. This is not normal. None of this is normal.
    29. Re:Just when they get if finished.... by boisepunk · · Score: 1

      crap post
      praise allah
      infidels fear me

      --
      main(0)
  5. Re:/.ed already by Anonymous Coward · · Score: 0

    Subscribers have been looking at that storuy for awhile - it lasted a lot longer than 30 seconds.

  6. Cached on mirrordot by bandrzej · · Score: 2, Informative

    At least mirrordot was able to save a cache:

    http://www.mirrordot.com/stories/56f602610d944ff 78 9b6ec7a2075940c/index.html

    Looks like their news page died at 17,000 hits after 12:17 today. Very sad.

    --

    LainTheWired = isgod( int Lain, int denial, float truth)

    1. Re:Cached on mirrordot by myukew · · Score: 4, Informative
  7. They recommend MS Office :) by mgkimsal2 · · Score: 3, Funny

    The NeoOffice/J 1.1 release is now available for download. Warning: all NeoOffice/J development and testing is done by volunteers so there are always some missing features and bugs. So if you expect software to be absolutely perfect before you install it, we recommend that you purchase a commercially supported office suite like Microsoft Office. (emphasis mine)

    Hrm - maybe Office on the Mac is much better than the Windows version. I've been hearing that for awhile, but it's still from Microsoft, and will still have some of the same issues that people have on the Windows version, or it'd have compatibility problems (key commands, etc).

    Still, I thought that comment about something being 'absolutely perfect' then recommending Office was pretty funny.

  8. 5 years! by fatted · · Score: 1
    After nearly five years of development, NeoOffice/J has made it to its first stable release. NeoOffice/J 1.1 is a Mac OS X-integrated office suite based on OpenOffice.org 1.1.4
    I didn't realise openoffice 1.1.4 had been out for 5 years!
    1. Re:5 years! by Anonymous Coward · · Score: 0

      That is mainly because you are retarded.

  9. Valid reason for BitTorrent by Speare · · Score: 4, Informative

    I'll keep my client running today. Will you? http://play.aelitis.com/torrents/NeoOfficeJ-1.1.dm g.torrent

    --
    [ .sig file not found ]
    1. Re:Valid reason for BitTorrent by Ford+Prefect · · Score: 3, Insightful

      I'll keep my client running today. Will you?

      Mine's chugging away, downloading - there's a fair few seeds already so it hasn't uploaded anything yet!

      Here's a nice, friendly Mac BitTorrent client for all you GUI-fiends, and while I'm at it, here's a list of conventional mirrors and translations...

      --
      Tedious Bloggy Stuff - hooray?
    2. Re:Valid reason for BitTorrent by Seumas · · Score: 1

      No.

    3. Re:Valid reason for BitTorrent by Anonymous Coward · · Score: 0

      I serendipitously downloaded NeoJ yesterday and still have the DMG. Is there any way to join the torrent without re-downloading?

    4. Re:Valid reason for BitTorrent by Insightfill · · Score: 2, Informative
      I serendipitously downloaded NeoJ yesterday and still have the DMG. Is there any way to join the torrent without re-downloading?

      Yes: simply grab the torrent and when your client asks where you want to save it, point it right at the one you already downloaded. Your client will then compare your file against the torrent and decide that you've already got it, but leave you in the swarm.

    5. Re:Valid reason for BitTorrent by Anonymous Coward · · Score: 0

      There's also another Mac BitTorrent client (Azureus) for power users and another Mac BitTorrent client ("Mainline") for people who want a lightweight one. Not just Tomato Torrent. Plus they're both nice and user-friendly as well.

    6. Re:Valid reason for BitTorrent by Seumas · · Score: 1

      There's also native (Cocoa) client called Bits on Wheels which is a very decent and functional client, with a fun little "3D Swarm" to show your transfers in an animated graphical format in real time (both sending and recieving). Sure, that's pretty useless - but when you're waiting for that important file, it keeps you occupied watching the little blocks of data whizzing around. :D

  10. Fantastic! by MichaelSmith · · Score: 3, Informative

    My sister needs a laptop for work and I have been steering her towards a G4 mac. MS office adds $AUD300 to the price, which offends me, mainly because of the huge profit microsoft make out of it.

    Having this available could make it a much easier decision for her to buy the macintosh.

    1. Re:Fantastic! by DenDave · · Score: 1

      Go ahead and get the mac. Neoffice works quite well, has done for some time. Only if your work is centered on MS VB stuff or really heavy duty excel sheets are you in a pickle. Don't forget that if word compatibilty is your main issue then you can also go for Abiword

      --
      -if at first you don't succeed, stay the heck away from paragliding.
    2. Re:Fantastic! by BioCS.Nerd · · Score: 1

      I'm at work so I can't try NO/j at the moment, but if your sister is a student (or teacher) she may qualify for Microsoft's Office Student Edition which has all the goodies anyone could ask for at a reasonable price (I think I paid ~$80 CAD for an old version of Office vX and then upgraded to the new version for free :). There's also a trial version on their website.

      I know many /nerds may have their quibbles with MS, but IMHO MS Office for OS X is pretty darn good, if not better than it's Window's counterpart. Your sister might like it. Give it a go.

    3. Re:Fantastic! by Anonymous Coward · · Score: 0

      Well, if OSX is an option then how about Linux/PPC? Ubuntu will do very nicely, with a clean easy installation and GUI, there's actually a PPC LiveCD available if you want to just try it out.

      http://www.ubuntulinux.org/

      when OO.o 2 is finally available, it'll certainly beat the hell out of neooffice, and on linux it should integrate fairly nicely with all other apps.

    4. Re:Fantastic! by WhiteWolf666 · · Score: 1

      NeoOffice/J is pretty good.

      I've been using it for around 6 months. I no longer have MS Office on my machine.

      I refuse to use MS products (I abhor their business practices, and boycott their products), and have no problems using OpenOffice.org or NeoOffice/J, both at home and at work.

      Have her play with OpenOffice.org. If she is okay with it, she'll be okay with NeoOffice/J.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    5. Re:Fantastic! by Anonymous Coward · · Score: 0
      Well, if OSX is an option then how about Linux/PPC? Ubuntu will do very nicely, with a clean easy installation and GUI, there's actually a PPC LiveCD available if you want to just try it out.


      Oh good god.. that would be like ripping the V-8 out of a BMW 7 series and dropping in a Toyota four banger.

      I own a PowerMac and numerous PCs, and coincidentally run Ubuntu on the x86 machines along with OS X on the Mac. Ubuntu is IMNSHO the BEST choice for an x86 desktop in the linux world, but in no way, shape, or form does it approach let alone approximate the ease of use and stability of OS X.
    6. Re:Fantastic! by denjin · · Score: 1

      Well, you could always just get her a copy of Pages if she just does word processing. And don't new Macs still come with Appleworks?

    7. Re:Fantastic! by varmittang · · Score: 1

      Yeah, but Pages doesn't have Grammer checker yet, only Spell checker. Something every word processor needs. Don't get me wrong, Pages is very good for the creative type, really great at handling text and pictures together.

      --
      -----BEGIN PGP SIGNATURE-----
      12345
      -----END PGP SIGNATURE-----
    8. Re:Fantastic! by uvavu · · Score: 1

      As mentioned -- iWorks only costs US$79 list, and it is a very good product. I am forced to use Microsoft applications for work, as we need to be 100% compatible (a bit pathetic given that 75% of our market is Unix, Linux, and Mac OS), but if I could use iWork instead I would be delighted. For writing presentations, for example, I've used everything from Lotus Freelance (who remembers that?) to PowerPoint, but I have never seen a tool as easy and nice as Keynote. And despite years of using PowerPoint, my presentations just LOOK better in Keynote! Pages is also very nice -- while MS Word has a lot more features, it is a lot easier to create visually attractive documents in Pages. NeoOffice does, however, bring a lot more tools (spreadsheet, project management, drawing & graphics, and flowcharting), and it is very exciting to have a Cocoa/Aqua version of OpenOffice, a product that I have enjoyed on Linux for quite some time now.

  11. Seems the better then regular OpenOffice... by afd8856 · · Score: 2, Insightful

    Looking at the integration features, it seems better then either Windows or *nix versions of OpenOffice.

    --
    I'll do the stupid thing first and then you shy people follow...
    1. Re:Seems the better then regular OpenOffice... by Moderator · · Score: 0

      Except that the Windows and *nix versions are only weeks away from hitting 2.0.

      --
      The World is Yours.
  12. What if it were written in Java? by Dancin_Santa · · Score: 4, Interesting

    I have begun to think that most, if not all, free software applications ought to be written in Java or a reasonable facsimile. Ideally, a common language and runtime that all free software could target would be available that would allow immediate porting to take place.

    To some extent we have this now with Linux as a standard OS, but even with it there is a lack of common binary compatibility. Java takes care of that such that the same binary application on one platform works on another, only relying on the base runtime to be ported.

    How much quicker could we have had NeoOffice on MacOS if it were written in an easily-ported language like Java?

    Are there any plans for such a common language runtime to which applications can target themselves in the free software ecosystem?

    1. Re:What if it were written in Java? by Anonymous Coward · · Score: 1, Insightful

      It would be quicker to develop, yes. Unfortunately, Java still looks like ass on most every platform and I don't care what people say to the contrary, Java still isn't half as 'snappy' as a native app. It's really quite bad in most cases.

    2. Re:What if it were written in Java? by alienw · · Score: 1

      Are there any plans for such a common language runtime to which applications can target themselves in the free software ecosystem?

      Yes, it already exists. It's called Java. There's also a knock-off of it called .NET or C# or Mono.

    3. Re:What if it were written in Java? by insert+cool+name · · Score: 1

      I have begun to think that most, if not all, free software applications ought to be written in Java or a reasonable facsimile. Ideally, a common language and runtime that all free software could target would be available that would allow immediate porting to take place.

      Currently java would not be such a good choice for that due to the lack of a full free (as in freedom) implementation of the api.

      See http://www.gnu.org/philosophy/java-trap.html

      A Java GUI app is also a big turn off for anyone with an older machine.

      Personally I have begun to think that most, if not all, free software ought to be written in the language most appropriate for the job it's doing.

      --
      Never trust anyone with an id greater than 889388
    4. Re:What if it were written in Java? by Cpyder · · Score: 1

      I used to think so too, until recently I saw this: http://live.managerzone.com/applet/live3d/index.ph p?id=demo&lang=en It's a 3D game linked to the football competition simulator Managerzone. It is absolutely stunning. Check it out.

    5. Re:What if it were written in Java? by Anonymous Coward · · Score: 0

      How much quicker could we have had NeoOffice on MacOS if it were written in an easily-ported language like Java?

      Some things would be faster, but Mac applications do not function like Windows applications. As such, two different interfaces have to be written anyway (or have a program that doesn't function properly on the other platform).

    6. Re:What if it were written in Java? by argent · · Score: 1

      Ideally, a common language and runtime that all free software could target would be available that would allow immediate porting to take place.

      Having it be a language that doesn't suck dirty swamp water through used oil filters would be a pleasant bonus, but that doesn't seem to be an option.

    7. Re:What if it were written in Java? by ssj_195 · · Score: 2, Interesting

      GCJ can compile a lot of Java apps to native code (and possibly toolkits...?). There are compiled versions of Eclipse (and maybe Azureus, too) floating around somewhere.

    8. Re:What if it were written in Java? by interiot · · Score: 1
      It's incredibly tempting to instinctively reply with an incoherent rant, but I'll try not to.

      One problem that I see is that languages are still evolving, and will continue to do so. Should we have left things well-enough alone at C, and not invented or rewritten algorithms in Java? Are Perl/Ruby/Python insignificant enough that nobody should have spent effort programming in them?

      Languages ARE improving, and by putting a stake in the ground, you're guaranteeing that at some point the "unified standard" would move to a new, improved language.

      So there will be two langauages everyone uses. And then three.

      So, in a practical sense, you're suggesting we use as few hardware, VM, and language platforms as possible. So Perl should have been written, but Python and Ruby are rubbish, and nobody should spend time coding for them?

      I don't know. Obviously there is overhead in maintaining multiple separate languages, VMs, hardware chipsets, glibc versions, etc. But to some extent, individual developers choose to spend more time on learning new languages, or not. It's currently up to them how much time they want to "waste" porting things, and that seems like how it should be.

    9. Re:What if it were written in Java? by Anonymous Coward · · Score: 0
      Personally I have begun to think that most, if not all, free software ought to be written in the language most appropriate for the job it's doing.
      That's really a very sweet sentiment, but frankly there are no objective metrics by which to determine how well suited a language is for any given task.
    10. Re:What if it were written in Java? by mrchaotica · · Score: 1

      Well, here's the thing: even if you do use Java it still takes time to port to Mac because Swing Java is not the same as Cocoa Java. And believe me -- Swing apps do NOT cut it on Mac OS.

      --

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

    11. Re:What if it were written in Java? by realinvalidname · · Score: 1

      How much quicker could we have had NeoOffice on MacOS if it were written in an easily-ported language like Java?

      ThinkFree Office is written entirely in Java and has been available for years. Much as I like Java though, I have to say that ThinkFree is simply awful - not so much slow as it is simply unreliable. In my (paid) experience it managed to hopelessly corrupt documents, and when I wanted to use it for a presentation at ADHOC, I discovered that its full-screen presentation mode didn't work (and that this was a known bug).

      So yes, Java means you can have it sooner. But it's not clear whether ThinkFree's wretchedness comes from implicit Java limitations, problems in Apple's Java implementation, or (most likely) the company's own failings.

      --Chris (realinvalidname)

    12. Re:What if it were written in Java? by Otter · · Score: 3, Informative
      Swing apps do NOT cut it on Mac OS...

      Sure, but at least they go over better than X11 apps!

    13. Re:What if it were written in Java? by DickBreath · · Score: 1

      Didn't you read what he said?

      I don't care what people say to the contrary

      His mind is made up.

      It does not matter that you once believed the same, but then saw contrary examples which changed your belief.

      Compilers to native code. Direct linkage to native widget sets on the native platform. Concrete examples of software compiled this way. Java will still forever look bad and be slow.

      I was reading about IKVM the other day, and was surprised at how (apparently easily) you could now compile Java to native code, access all of the GNU Classpath and Mono framework, including various user interface technologies, some of which are implemented in pure native code.

      --

      I'll see your senator, and I'll raise you two judges.
    14. Re:What if it were written in Java? by DickBreath · · Score: 1

      Having it be a language that doesn't suck dirty swamp water through used oil filters would be a pleasant bonus, but that doesn't seem to be an option.

      Did you notice that Mono supports numerious languages?

      There is not one single language. With Mono, you can (1) pick from a growing variety of source languages that (2) all interoperate on a common runtime system that is (3) portable across platforms and (4) compiles to native code.

      Doesn't this just about fit the request of the grandparent post in his search for an ideal deployment runtime for Free software?

      --

      I'll see your senator, and I'll raise you two judges.
    15. Re:What if it were written in Java? by earthbound+kid · · Score: 1

      The problem with Java (especially as a GUI) is that it works acceptably everywhere and works spectacularly nowhere. Since Java isn't open source, and since there is no one platform for which it's targeted, Java is basically a mish-mash of UI features and whatnot: Jack of all trades and master of none. No one can go back and make it closely match the look and feel of a particular OS, since it isn't open source, and Sun hasn't made it match any one OS, since there's no one OS where it thrives.

      So, were NeoOffice written in Java, yes it would have been ported much faster on the one hand, but on the other hand, it would never have a chance to become more than a port. Java applications (at least pure Java programs) always seem like ports, even on their originating OS.

      Java is great for backend stuff where you're not sure what kind of hardware you want to run on, but for GUI, it's a compromise that leaves everyone slightly unhappy.

    16. Re:What if it were written in Java? by Anonymous Coward · · Score: 0
      full free (as in freedom)

      As opposed to what? Partially free (as in cheeseburger)?

    17. Re:What if it were written in Java? by argent · · Score: 2, Informative

      Did you notice that Mono supports numerious languages?

      Did you notice that Mono is primarily an implementation of .NET, and thus subject to patent claims by Microsoft? Microsoft has stated that these patents will be avilable on a "royalty free and otherwise reasonable and non-discriminatory basis", but short of an irrevocable legally-binding release worded in such a way that it's unambiguously clear these patents can not be used against open-source software, I am unwilling to trust to their good will.

      Statements like "Furthermore, our release of the Rotor source code base with a specific license on its use gives wide use to our patents for a particular (non-commercial) purpose, and as we explicitly state we are open to additional licenses for other purposes." -- Microsoft applies for .NET patent are less than encouraging.

      In Europe, Microsoft are already showing their true colors: "If developers want to build the protocols into their products, they must agree not to distribute that product in source-code form, or to subject it to licenses that require source-code disclosure, a formula that excludes many open source licenses."

      And they have other tricks up their sleeve, "At every release the focus of Microsoft's tools that provide a compelling Linux development environment could break or prevent mono-compatibility the same way Microsoft's J++ broke Java compatibility by replacing JavaBeans, RMI,and JNI with COM, DCOM, Direct/J. At that point, you would face the choice of either forking the API's or forking over some royalty payments." --Mono developer meeting

      With Mono you can hitch your wagon to Microsoft's oxen, never knowing just where they're going to go.

    18. Re:What if it were written in Java? by BiggyP · · Score: 1

      You can use java and not produce your gui with it though.

      http://java-gnome.sourceforge.net/cgi-bin/bin/view

    19. Re:What if it were written in Java? by m50d · · Score: 0, Troll
      If it were written in Java you'd need an 8-way machine to run it. And it would look like ass. And it wouldn't be free enough. Java only relies on the base runtime being ported, yes, but it can only really be ported by Sun, and they're in no hurry to port it to obscure systems. Look at the trouble the BeOS people are having with it.

      The great advantage of free software is that you have the source, so you can compile it on any platform. That lets it run faster too.

      For free software that works on multiple platforms without recompiling I use python and tkinter or qt for the gui. I think the community as a whole is going for mono though.

      --
      I am trolling
    20. Re:What if it were written in Java? by colinrichardday · · Score: 1

      Well, should I write this kernel in Java or C?

    21. Re:What if it were written in Java? by Phred+T.+Magnificent · · Score: 1

      Java's fine if the only platforms you care about are Windows, Mac, Linux and Solaris. Once you bring in the others (FreeBSD, for instance), Java won't work anymore.

      Maybe the best solution to that problem is to persuade Sun to release JVMs for more platforms, but until that happens, Java isn't the panacea it claims to be.

      --
      Where is the wisdom we have lost in knowledge?
      Where is the knowledge we have lost in information?
    22. Re:What if it were written in Java? by caulfield · · Score: 1
      Well, here's the thing: even if you do use Java it still takes time to port to Mac because Swing Java is not the same as Cocoa Java. And believe me -- Swing apps do NOT cut it on Mac OS.

      I'm having no problems with Netbeans and JEdit. The new Java 5 update for Mac OS seems indistinguishable from WinXP. Very speedy, no crashes.

    23. Re:What if it were written in Java? by Dancin_Santa · · Score: 1

      I (badly) tried to make the point that a common language runtime ought to be made available for the Free Software community. That means that the runtime must be unencumbered by patents and licensing issues, it must be open source, and it's got to be cross-platform.

      In the most obvious case, Mono fulfills most of the requirements, but like Java it has issues that really preclude it from being acceptable for free software.

      The other obvious library is the Perl 6 Parrot runtime which is similar to .Net in that it is multi-language and multi-platform. The problem is that Parrot is simply not here yet and may not be ambitious enough to be a satisfactory Mono replacement.

    24. Re:What if it were written in Java? by marcosdumay · · Score: 1

      Binary compatibility is very important if you want to send your program via internet and be sure it opens on the other point, doesn't matter what system it is using. But it doesn't help to port things. It doesn't really matters if you have to compile your program again, most of the time is spend modifying the behaviour of the interface, that is not adequade for the new system.

      And, wile I am on it, most of Oo is written in java.

    25. Re:What if it were written in Java? by goofballs · · Score: 1

      if you write a java program w/ portability in mind, there is very little that has to be done to "port" it to mac- swing apps most certainly do cut it in os x, when done right. there's very few reasons why you'd ever need to use the java-cocoa bridge.

      you can start here for some hints on coding java apps for os x:
      http://developer.apple.com/documentation/Java/Conc eptual/Java14Development/index.html?http://develop er.apple.com/documentation/Java/Conceptual/Java14D evelopment/04-JavaUIToolkits/JavaUIToolkits.html>

    26. Re:What if it were written in Java? by Anonymous Coward · · Score: 0
      I won't indulge in your fallacious reasoning.

      You shouldn't be writing a kernel anyhow.

    27. Re:What if it were written in Java? by Anonymous Coward · · Score: 0

      Java Trap is the dumbest article I have ever read. They are complaining that though java is free, a lib you use might not be free, hence its trap! What kind of a stupid shit wrote this? Why is this not an issue with C or C++ or Perl or whatever other languages?

    28. Re:What if it were written in Java? by Anonymous Coward · · Score: 0

      Incompatibility between Linux distributions has quite a lot to do with the Community's general refusal to generate statically-linked binaries.

      There's little practical reason for ALL programs (especially something as large, complex, and desktop user-focused as OpenOffice or, say, Mozilla) to use shared libraries exclusively. The huge negatives for system manageability, application portability, etc greatly outweigh the benefits of footprint reduction of programs, etc. ...But yet we insist on kicking ourselves in the teeth over and over again.

      The Worst Days of Windows were the days of DLL-Hell, which at this point they've (mostly) outgrown. The platform (not the OS) had HUGE problems trying manage system-wide libraries for all user-space apps, and they've learned from that lesson. In Linux it's magnitudes worse since:

      1) there's such huge disparity between distros as far as where stuff goes
      2) the much larger # of shared libraries most apps depend on
      3) Crappy handling of dependencies (I don't want to start a RPM vs. Deb vs. your-package-handler-here)
      4) the fact that multiple versions of libs *tend* not to coexist. Not that they can't, but you just don't tend to see GTK+ 2.6.8 and 2.4.14 installed on the same system. On the other hand, msvcp50, 60, 70, 71.dll, etc frequently all exist on the same Windows box.

      There's an attitude that "real programmers build light programs, reuse code, and avoid bloat at all costs"... However, there are big tradeoffs to that strategy. The machismo in the attitude is cute, but strict adherence to it (or the way it's being done) isn't realistic and hurts all of us. This is definitely one of the top 5 problems holding back Linux (particularly on the desktop), in my opinion.

      Java's got versioning problems as well - anyone here working on porting their apps to J2 version 5 (1.5) and maintaining that knows what I mean. However, it's much, MUCH more manageable.

    29. Re:What if it were written in Java? by killjoe · · Score: 1

      I think parrot will be a compelling alternative to mono once it's done. It will support python and perl out of the box so that's a big plus right there. It also looks like it will probably be faster then mono but mono is not standing still and who knows what will happen by the time parrot is out.

      Parrot is targeted at hosting popular languages like perl, python, ruby etc. Rasmus has even said he might PHP to it. Mono OTOH is designed to host C# which is not that popular amongst the open source crowd (for understandable reasons). For that reason alone I think it will end up being the de-facto open source VM.

      --
      evil is as evil does
    30. Re:What if it were written in Java? by Sithgunner · · Score: 1

      It is also technically important to have a cross platforum easy environment, but then again since Java is not a complete opensource free environment, personally I don't care if everything is GPL or not, but distro like Debian refuses to put the Sun's Java by default, so either way, it's not going to be instant cross platform on many machines.

    31. Re:What if it were written in Java? by Anonymous Coward · · Score: 0

      Java Trap is the dumbest article I have ever read. . .. What kind of a stupid shit wrote this?

      That would be Richard Stallman. Not everyone is enamoured with him but this would be the first time I've heard him called stupid.

      If you're having difficutly understanding what he's saying try re-reading the article. If you have difficutly with any of the big words come back here and I'll see if I can help you out.

    32. Re:What if it were written in Java? by mrchaotica · · Score: 1

      "Very speedy, no crashes" isn't enough, which is what I meant. "Enough" means supporting AppleScript, Services, menu at the top of the screen instead of the window, etc.

      --

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

    33. Re:What if it were written in Java? by mrchaotica · · Score: 1

      Do Swing apps magically support Services and Applescript now?

      --

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

    34. Re:What if it were written in Java? by LWATCDR · · Score: 1

      "Unfortunately, Java still looks like ass on most every platform"
      I have not noticed it being very ugly running Java 1.5 under WindowXP. The trick is to pick the native native for Swing in your app. Also Swing is very pretty under MacOS/X Apple does there own java so their Swing uses native widgets I believe.
      "Java still isn't half as 'snappy' as a native app. It's really quite bad in most cases."
      Java 1.5 seem to fix that as well. I have never had a problem with Eclipse or any of the programs I have written. It is possible to write some very slow programs using Java. Bad programmers can get bad results using any language. The real problem with the "snappy" feel is start time. That is because the JRE must be loaded not a lot you can do about that except pre load it.

      The only problem I see with Java is that it maybe too closely tied to Sun. For many tasks it is a very good tool.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    35. Re:What if it were written in Java? by colinrichardday · · Score: 1

      Well, if there are no objective metrics in choice of language, then why shouldn't one write a kernel in Java?

      Also, even if there are no objective metrics, does that mean that there is no basis for "appropriateness" in language choice?

    36. Re:What if it were written in Java? by fupeg · · Score: 1
      Ok, so you're somewhat uninformed, but bring up an interesting point. First off, Neo uses the Java bidnings to Open Office so it is basically a Java program. So I will assume that when you say
      How much quicker could we have had NeoOffice on MacOS if it were written in an easily-ported language like Java?
      That what you really mean is "How much quicker could we have had NeoOffice on MacOS if Open Office was written in an easily-ported language like Java?" Otherwise your statement is just ignorant.

      Of course if you knew much about Open Office, you would realize that 2.0 has a LOT of Java in it and this has caused a LOT of controversy. You see things written in Java require a runtime, the JRE (or JVM.) If you are using a Mac, then you are using a JRE that was written by Apple with technology licensed from Sun. If you are running Windows or Linux, chances are that you are using a JRE from Sun. The JRE while being "free", as in you didn't have to pay anything to get it, is not open, i.e. you do not have the source code for it. Even if you did have the source code (which you can get for free with Java 5.0+) it still uses a license that is neither free nor open. Now this is a very big deal to many people and some of them refuse to use anything Java or they insist on using a "truly free" JRE like GCJ even though it is generally considered inferior and somewhat incomplete.

      Back to the point -- a lot of the people behind some of the wonderful, open source, free software out there have a big time objection to using Java. Apache is trying to build an open JRE called Harmony, that promises to be as good as Sun's. So maybe that will make Java more acceptable to more people.

      However, even if Apache succeeds, a lot of people are not fans of Java. Java on Windows was very slow as a GUI back in the late 90's. If you are using Java 1.4+, it is actually pretty fast now because it uses hardware acceleration, and only promises to get faster. Other synergistic technologies such as SWT can make Java as fast as "native" applications. Still you'd have to expect 5 years+ before opinions formed in the late 90s change, and who knows where Java will be by then.
    37. Re:What if it were written in Java? by syzler · · Score: 1

      Actually an X server comes on the OS install disk with a Mac. If you do not have your OS install disk, you can download the X server from Apple's website:

      http://www.apple.com/downloads/macosx/apple/x11for macosx.html

      I use the X server to run many programs on my Mac as well using it to run apps on remote Linux workstations.

      On a side note, I have used both Neo Office and the X11 version of OpenOffice on OS X. I've found the X11 version to be faster and does not bring my computer to a crawl. Although the integration with the desktop was nice with Neo Office, it was irritating slow to use.

    38. Re:What if it were written in Java? by MemoryDragon · · Score: 1

      You still have not noticed after around 8 years of Swings existence, that Swing is skinnable since day one. Some skins are ugly, the native metal on pre 1.5, the GTK is god awful, but some are really beautiful, like the native skins on Windows which work on WinXP+, or the Plastik L&F, also Apple does an amazing job, there are a handful of really neat skins around in the wild. Most programmers are just plain lazy and use the dreadful metal instead of switching it away.

    39. Re:What if it were written in Java? by caulfield · · Score: 1
      "Very speedy, no crashes" isn't enough, which is what I meant. "Enough" means supporting AppleScript, Services, menu at the top of the screen instead of the window, etc.

      Apparently, you want a native Mac application. OpenOffice will never be that, nor should it. Perhaps you should stick to AppleWorks.

      Swing has nothing to do with AppleScript, Services, or the locaiton of the menu bar, nor should it. You're confusing Swing with two proprietary platform-specific technologies and one proprietary platform-specific LaF implementation. You use the Swing API for cross-platform consistency, and the latest version (5 on Mac OS) does a great job.

      Don't spout off saying Swing on Mac OS sucks when you don't even know what Swing is.

    40. Re:What if it were written in Java? by alienw · · Score: 1

      It's easy to see that you don't know what you're talking about. First, the source for Java is available from Sun. Second, you can write your own widget sets or interface to native APIs quite easily (ever hear of JNI? Pluggable look and feel?). There are plenty of Java apps that look and feel exactly like a native program. Try Eclipse some day.

    41. Re:What if it were written in Java? by mrchaotica · · Score: 1

      I know exactly what Swing is. My entire point is indeed what you said: Swing apps suck on the Mac not because Swing sucks (I agree, it doesn't) but because they're not native. And yes, a native OpenOffice is exactly what I want, which is why I wish NeoOffice/J would be merged back in with the main OO.o tree, and that it could be conditionally compiled with support for platform-specific technologies. Get it now?

      The original poster seemed to think that using Java was some magical cure-all that would make the program be a first-class application on every operating system. I was dispelling his misconception: Swing apps are cross-platform in the sense that they run, but they're only marginally better than the current X11 OO.o.

      --

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

    42. Re:What if it were written in Java? by earthbound+kid · · Score: 1

      A) Java is open in that sense, but if you try to distribute an extended version Java yourself, Sun won't approve of it. So, you can do what you want, but this is asking a lot of work from one set of developers.

      B) Again, writing your own widgets is too much to ask of average developers.

      C) JNI is, by definition, not Java. So, you're saying, "Java is good. Just combine it with some not-Java." JNI has its place, but it exists to plug the holes in Java, not as an all purpose excuse for its failings.

      D) I used Eclipse two years ago. It didn't seem very Windows-like at the time. Has it changed?

    43. Re:What if it were written in Java? by Anonymous Coward · · Score: 0

      Interesting comment, since most of Java 5 is a knock-off of C# . . .

    44. Re:What if it were written in Java? by Anonymous Coward · · Score: 0

      Yes, but the Swing app will just run. First, you have to go out of your way to install X11 (it is not part of the default install), so Joe User most likely won't have it. Then when you actually launch your app, you have to deal with having the X11 around, which will also confuse Joe User. A Swing app however simply requires double-clicking on a JAR file, and all is taken care of.

    45. Re:What if it were written in Java? by HuguesT · · Score: 1

      Really ?

      Personnally I do all my DTP with Scribus, the Gimp, and Inkscape, all X11 apps of the highest quality.

      No more overpriced CS suite for me (that use carbon anyway)

    46. Re:What if it were written in Java? by HuguesT · · Score: 1

      There is a lot more to feeling native than a mere skin. Native dialog boxes and shortcuts for a start.

      At least the "metal" skin does not falsely advertise.

    47. Re:What if it were written in Java? by alienw · · Score: 1

      I still don't see what the big deal is. True, Java isn't free software (which is a good thing, because you have one standard, compatible version of the Sun JRE). There is no good reason whatsoever to change the JRE, just write new code to do new things.

      If you don't like Swing, use a third-party toolkit (like SWT), it will work just as well. If you just don't like how Swing looks, use a third-party look and feel (they are available; for instance there is one that closely mimics standard Windows look and feel). You have to add at most 4 lines of code.

      JNI is useful if you don't require your program to run on any platform and need to call a native method. There is nothing wrong with using it if you realize what the limitations are.

      I don't know what Eclipse looked like 2 years ago. It looks very Windows-like to me, even on Linux.

    48. Re:What if it were written in Java? by MemoryDragon · · Score: 1

      Shortcuts are not really covered by swing, some are, but it is mostly up to the programmer to do them. As for native dialogs, yes, there are deficciencies in the way swing does the windows print and file dialogs, but those become less and less. As for the other stuff, I run windows regularily, and basically 80% of the apps, come with some kind of skin. Even Microsoft basically pushes a new skin every year, so that every office version looks feels and behaves totally different than the one before. But swing constantly gets the beating that it does not look totally like windows native, while 99% of all newer windows apps, come with a totally different skin per default and nobody bothers.

    49. Re:What if it were written in Java? by Mornelithe · · Score: 1

      If you don't like Swing, use a third-party toolkit (like SWT), it will work just as well. If you just don't like how Swing looks, use a third-party look and feel (they are available; for instance there is one that closely mimics standard Windows look and feel).

      The problem is, that doesn't cut it pretty much anywhere. Yeah, it'll look kind of like a native app, but it will be lacking significant functionality that would be available to a native app.

      In OS X, it wouldn't have a menu bar at the top, and wouldn't support AppleScript and the like.

      In KDE it wouldn't integrate nearly as well into the desktop. For instance, it wouldn't be able to embed other kparts, if that was necessary. It wouldn't make use of ioslaves for transparent access of various non-disk media. Etc.

      Similar things could be said of Gnome and Windows, I'm sure.

      Yeah, you could use JNI and add all those things, or use Java bindings for all the respective toolkits. But then you're doing just as much work porting in Java as you are in any other language. Only your core logic is the same, and that won't change if you choose C, C++, (or good languages like) haskell or python. Java doesn't buy you much if you plan on making an app that actually integrates well into several different environments.

      The only place I see that flying is on Windows, because people there are used to using apps with 30 different toolkits that don't integrate together at all. Everywhere else, your application is second class.

      --

      I've come for the woman, and your head.

    50. Re:What if it were written in Java? by CarrionBird · · Score: 1
      I dispute the your last contention (the others were correct as far as I know). I have yet to see a java app that I could not tell from the UI was a java app. I don't mean that they're all bad, but they're not exactly like native.

      Limewire, for example. You can tell it's java, but it is still an attractive interface.

      --
      Free Mac Mini Yeah, it's
    51. Re:What if it were written in Java? by alienw · · Score: 1

      You don't know what you are talking about. Of course you can't use platform-specific crap if you are making a portable app. If you want to write an app in C++ that works on Windows, Linux, and Mac, you can't use any of those features, either. KDE features pretty much require that your app be KDE-only, for instance. With Java, you get out-of-the-box portability. While your app won't support AppleScript out of the box (neither will the C++ app), it should look like a normal Mac application, with a menubar on top and Aqua widgets everywhere (you are wrong with regard to the menu bar).

      As far as python and others: they do not have any advantages over Java for desktop apps. They are not portable, since they depend on external (often platform-specific) libraries for everything. They are exteremely slow (about 10x slower than java). They are hard to develop and hard to deploy due to the external libraries. Scripting languages are best left for scripting.

    52. Re:What if it were written in Java? by Mornelithe · · Score: 1

      No. The point is that "looking like" a normal application isn't enough. You'll still be beat out by any applications that actually are native, because they can use all the "platform-specific crap" that is actually useful to people.

      The ability to use AppleScript isn't crap. Kparts and kioslaves aren't crap. They're useful features of their respective desktops, and they benefit applications greatly. And they're the reasons that cross-platform programs will often be second class citizens, unless you do an amazing amount of work porting them to each environment.

      --

      I've come for the woman, and your head.

    53. Re:What if it were written in Java? by goofballs · · Score: 1

      late response, but hey- when talking about *porting* apps, supporting *additional* services like applescript isn't really in the realm of discussion. but since you brought it up- it's pretty stinkin' easy to add applescriptability to a swing app by implementing a couple classes in the com.apple.eawt package. additionally, gui scripting events are auto-magically supported via System Events. so there. =D

  13. Re:They recommend MS Office :) by Anonymous Coward · · Score: 0

    And it says long about NeoOffice/J too..

  14. Java by ahmetaa · · Score: 1

    NeoJ, the J at the end represents Java. complete GUI layer (and posibly more) is designed with Java. It is a shame poster did not mention that.

    1. Re:Java by Anonymous Coward · · Score: 0

      Why does it matter? It works.

  15. Very much a Mac Application by Ford+Prefect · · Score: 5, Informative

    Before anyone complains about the lack of Aqua widgets and the continuing Windows 95-like appearance of the program, from experience that's probably the last remaining area to be completed.

    Everything else is great, and infinitely superior to the old port of OpenOffice.org to the Mac's X11 - for instance, copy-and-paste works fully (styled text is no problem whatsoever); file associations work correctly; native printing, fonts, anti-aliased line art are just fine. Even more recent, esoteric stuff like Spotlight searches are fine - when I installed Tiger, all my documents got neatly indexed without me lifting a finger.

    It's in an application bundle, it stores its settings in ~/Library/ - apart from those grey, rectangular buttons and controls, it's a complete, modern Mac application.

    Honestly, don't judge it on first appearances or screenshots (I've found numerous Mac 'ports' of software which seem to concentrate too much on cosmetics rather than functionality) - it's truly wonderful. For anyone looking for a free office suite on their Mac, here it is!

    --
    Tedious Bloggy Stuff - hooray?
    1. Re:Very much a Mac Application by Seumas · · Score: 3, Funny

      I'd rather download Microsoft Office for OSX. They've released it for free now on BitTorrent, apparently. At least, I see it available all the time there, so it must be. You have to really appreciate that kind of gesture from Microsoft. Not only do they innovate, but they share with the competitor's customers!

      More importantly, no amount of money could be placed on the quality and reliability of a corporately-developed product like this. After all, would you rather drive a car built by Ford or a car built by some acne-riddled kid down the street?

      I for one only want expensive corporate products in my environment. Otherwise I wouldn't have spent all that money on a Mac. I suppose a program like this does have its place, though. Maybe among all of those poor people who can't afford robust Microsoft or Apple systems and have to settle for the third-rate world of open-source software and Linux operating systems.

      I'm also eagerly awaiting Avalanche, which Microsoft assures will be a revolutionary no offering that will make free programs like Bit Torrent seem childish. Just another example of how pay-for software will always rival cheap stuff made by poor people in their basement for use by other poor people who can't afford stuff like PowerBooks and iMacs and iPods and WindowsXP and bread and rent and tennis shoes.

    2. Re:Very much a Mac Application by tverbeek · · Score: 1
      As a person who switches between half a dozen boxes running OS X, Linux, and Windows (sometimes all in a single day), I decided over a year ago to switch to OOo, as something I could run on all of these (and work on the script for my Great American Graphic Novel in stolen moments at work, at the laundromat, sitting in front of the TV, and even sometimes in my study). The OS X boxes required some substantial hacks to get OOo for X11 working well enough for even a geek like me to put up with. (Don't get me started about fonts.) No real fault of the OOo folks; just the nature of the Xbeast.

      But since I switched the iBook and PowerMacs to NeoOffice, I've found it an excellent and perfectly viable option: even good enough to give to civilian Mac users. It does need a facelift (for which I apologise to the people I give it to) (Anybody know if there's a project underway to address that?), but that's the only substantial complaint I have.

      --
      http://alternatives.rzero.com/
    3. Re:Very much a Mac Application by WinterSolstice · · Score: 1

      This is a bit off-topic but...

      You have a "study", but you have to use a laundromat? I think your priorities are bit mixed up :)

      Most 2 bedroom apartments (which I presume yours is, at the least) have a washer/dryer hookup, or can easily be adapted to one. Assuming you don't live in one of those cheapass "no laundry machines allowed" complexes, you could at minimum use the ones designed to attach to the sink fixtures.

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
    4. Re:Very much a Mac Application by tverbeek · · Score: 1
      You have a "study", but you have to use a laundromat? I think your priorities are bit mixed up :)

      My priorities are nicely ordered, thanks. :)

      I don't live in a "complex" of any kind. My apartment is the ground floor of a house built in the early part of the last century, whose "washer/dryer hookup" consists of a large sink and hooks for clotheslines in the basement. Although living here sends me to the laundromat every week or two (which isn't too bad, especially if I hang out in the little park across the street), I have hardwood floors, a front porch overlooking a shaded lawn, a bus stop just a couple doors down, and... room for a study. I wouldn't trade all that for a washer/dryer set in some moern tenant-warehouse apartment complex.

      --
      http://alternatives.rzero.com/
    5. Re:Very much a Mac Application by WinterSolstice · · Score: 1

      Sounds nice. As I mentioned to the other person who responded, it all depends on your experiences with laundromats. Mine have always been extremely unpleasant. I'm glad yours are not so bad :)

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
    6. Re:Very much a Mac Application by Judge_Fire · · Score: 1

      Apperance does not a Mac user interface make.

      NeoOffice/J still has some way to go in order to get the 'feel' part right. The Mac UI experience relies on consistency and standard ways of doing things and a number of things feel or function 'wrong' in this app.

      That shouldn't stop anybody from using it, of course, but in the context of other apps it stands out as a bit.... clumsy. The 'amateurish' (and unnecessary) splash screen, the weird name and somewhat intimidating dialog boxes (such as 'Save') may be seen as signs of a non-credible application.

      Hopefully, they'll be appreciative of the bunch of critical feedback they'll get and can take a bit of time to polish this aspect of the app next. As pointed out, most things have indeed been done right in this app so far : )

      J

    7. Re:Very much a Mac Application by saltydogdesign · · Score: 1

      I get what you are saying, but let's not forget that GUI design, at its best, is about usability, not just pretty graphics. And as such, it should be part of the initial design, not something that is tacked on last. I haven't used this version yet, but the previous versions, in my opinion, fell short not because they didn't have pretty Aqua widgets, but because the GUI was clunky and counterproductive. Just saying...

      --
      // This is not a sig.
  16. Re:all kidding aside... by DenDave · · Score: 1

    Perhaps when they somehow get the money to do so. Feel free to donate:

    http://www.planamesa.com/neojava/en/donate.php

    --
    -if at first you don't succeed, stay the heck away from paragliding.
  17. Good news by Lord+Satri · · Score: 2, Informative
    This is good news (tm). I've been using the X11 version for a while. Works great. Yes, it's X11, but it truly works fine. Downloading NeoOfficeJ right now. It is a good thing to have a choice. It might not be native but hey, we'll get there eventually.

    In terms of competition, there's KOffice for MacOS X I kept my eyes on, see http://kde.opendarwin.org/. Still pre-alpha however.

    I use and love iWorks. Keynote is simply *great*. But it is not free (forget open source). And iWorks, for the moment, lacks a spreedsheet, which OOO doesn't. Thanks to OOO and NeoOfficeJ developpers! :-)

    1. Re:Good news by MsGeek · · Score: 1

      Apple is working on a spreadsheet. They have applied for a trademark for "Numbers" which will probably be the finishing part of iWork. (not iWorks...iWorks was iWaltDisney's partner back in the day. ^_^) All they need do to top MS Office for Mac is to take their FileMaker Pro engine and retool it to be their Access-killer. Oh, there's not a version of Access in MS Office for Mac? Too bad, how sad...for Microsoft. ^_^

      They might have to pull iWork together fairly quickly because I suspect that MS might just disband the MBU because of Apple's unsatisfactorily lackadaisical attitude about the prospect of Windows running as a guest OS on a future Mac OS X x86. Again, too bad, how sad...for MS.

      --
      Knowledge is power. Knowledge shared is power multiplied.
  18. Re:/.ed already by milkasing · · Score: 1

    Apparently the homepage is still up http://www.planamesa.com/neojava/en/index.php
    Could someone make a mirror before it gets /.

  19. Coralized link by harvardslacker · · Score: 3, Informative

    Here's the Coralized link:

    http://neowiki.sixthcrusade.com.nyud.net:8090/inde x.php/NeoOffice/J_1.1_Announcement#Announcement_.5 Ben.5D

    Though, frankly, there's not much there to read.

    Greg

  20. Question: by bogaboga · · Score: 1
    ["...] mouse scrolling, integration with major Mac email clients and native support for Mac fonts. The full announcement is here."

    Do current relses of OpenOffice.org and other software have native support for Linux fonts? I ask this because I find that fonts on Linux are a bit "blurry"...that is, they are not as clear/crisp as their those on their windows counterparts. Even when anti-aliasing is turned off, fonts on Linux do not look that good. This is one reason in my opinion, why some slashdotters have written to say that Linux is ugly! Is it because there is lack of the so called native support for Linux fonts?

    1. Re:Question: by Anonymous Coward · · Score: 0

      That is a patent issue. The code is implemented to fix the problem, and when you pay the patent holder for the rights to use it, you may then enable it.

    2. Re:Question: by Anonymous Coward · · Score: 1, Interesting

      You are surely trolling? My fonts on Debian are crystal clear and far better than what I get from OS X - regardless of what antialiasing setting I use on the Powerbook. In fact, the slightly fuzzy fonts on the Apple were particular disappointing having gotten used to nice sharp gliphs on Debian.

    3. Re:Question: by Anonymous Coward · · Score: 0

      I find that fonts on Linux are a bit "blurry"...

      It's called anti-aliasing, and is usually done by dropping an old 14" screen on the floor :-) but it has recently become popular to do it in software. It is possible to turn off however, and make the text readable again.

      I disliked anti-aliasing just as much as you, when some upgrade introduced it on my system. I had just gotten my work monitor replaced because it had become blurry, and then some moron decides to make fonts blurry by default.

      Windows can anti-alias fonts too, but it doesn't do it by default.

    4. Re:Question: by zborgerd · · Score: 3, Insightful
      I find Linux font rendering to be very nice; better than Windows and even on par with OS X, but a lot of it is largely due to configuration and the videocard/monitor being used. This is a pretty lengthy reply, but I'd like to help people debunk the myth that Linux has "bad" font rendering. It's just that most distributions don't provide fonts and font renderers that function in the way many users might expect.

      By default, all distributions (except for Debian, I believe) use the Autohinter instead of the Bytecode Interpreter, due to potential patent issues. They render in very different ways. The Autohinter looks pretty good on LCD displays, with its subpixel hinting (producing fonts that are better in my opinion than Windows Cleartype), but I prefer the Bytecode Interpreter on CRTs.

      I'm not sure what you mean by "native" support for Linux fonts. All of the font rendering is handled through Libfreetype. You can compile Freetype to use either rendering method, but it defaults to the Autohinter. Freetype supports more than 11 different font formats. This includes standard scalable formats such as Truetype and Type 1 fonts.

      For example...
      With the Bytecode Interpreter:
      http://www.borgerding.org/dropline/zborgerd/screen shots/2.10_1.png
      http://www.borgerding.org/dropline/zborgerd/screen shots/2.10_2.png
      http://www.dropline.net/gnome/optical/2.10_4.png
      http://dlgwiki.dot42.org/uploads/katana.jpg
      http://dlgwiki.dot42.org/uploads/katana2.jpg

      With the Autohinter:
      http://www.dropline.net/gnome/optical/dropline-11. png
      http://www.dropline.net/gnome/optical/dropline-9.p ng
      http://www.dropline.net/gnome/optical/dropline-5.p ng

      Additionally, configuration can cause fonts to look bad. Some people don't like much antialiasing. They prefer the method that Windows uses to antialias only fonts greater than 12 points in size. A combination of the Bytecode Interpreter and disabling antialiasing for small fonts can produce font rendering that is similar to the rendering that most Windows users are familiar with.

      If you disable antialiasing while using the Autohinter, you'll find that fonts look terribly uneven and jagged.... They're pretty ugly. If you want to disable antialiasing, you probably should do it only with the Bytecode Interpreter being used as the renderer. This will produce the results that you may be looking for if you prefer Windows-like font rendering.

      Lastly, OpenOffice.org's builds have typically included internal Freetype libraries that don't particularly look pretty. There are some workarounds for this. I mention it in the following FAQ:

      http://www.dropline.net/forums/viewtopic.php?t=825

      It's quite outdated, but may provide you with the information that you need to get the font rendering that you prefer. You may also want to try tracking down a package of the Microsoft Core Webfonts. They are legal to distribute as long as they are provided in the original EXE, which may be extract with cabextract. As an alternative, you may be able to find a custom build of OpenOffice.org for your favorite distribution, that links against your system's own freetype libraries instead of the internal OO.o Freetype libraries.

    5. Re:Question: by WhiteWolf666 · · Score: 1

      One of the biggest issues in Linux (x.org) is to make sure that your monitor size is setup correctly (in mm) in your xorg.conf.

      This is *very* *very* important, and makes a *huge* difference in the quality of your on-screen font rendering.

      In this section:
      Section "Monitor"
      DisplaySize 381 228
      HorizSync 15-48
      Identifier "Monitor[0]"
      ModelName "Unknown"
      Option "DPMS"
      VendorName "Unknown"
      VertRefresh 30-61
      UseModes "Modes[0]"
      EndSection

      Make sure your display size is correct, in MM. The first number is the horizontal.

      I was *amazed* at how important that was. Get a ruler, go to google, convert your inches to mm, and be amazed at the brilliant Freetype font rendering.

      With that correctly set, I find the Freetype anti-aliaser better than the bytecode renderer+Anti-aliasing.

      (Bytecode processing is avaliable for Freetype, but disabled for patent reasons).

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  21. I think this shows that by Anonymous Coward · · Score: 4, Funny

    NeoOffice isn't the one.

    and that quite possibly
    there is no server.

  22. open office fork? by lethe1001 · · Score: 1

    I know that open office once had a port to OSX, which had the goal of attaining native widgets and what-not.

    So my question is, what is this NeoOffice stuff? A fork of the open office port? why are there two projects to bring open office to OSX? What is the difference between the two projects? Why didn't the NeoOffice developers just work on the OOo port?

    1. Re:open office fork? by Anonymous Coward · · Score: 0

      The OpenOffice port to OS X only works under X11 for OS X, and does not support native widgets or look and feel. OOo has announced they have no intention of making these things work.

      NeoOffice/J does support native widgets and look and feel.

      I hope that helps.

    2. Re:open office fork? by TheRaven64 · · Score: 4, Informative
      NeoOffice was originally started as a prototype for the OpenOffice port. Ideas for porting would be tested in NeoOffice, and then ported to OpenOffice if they worked. As part of the project, NeoObject/J was created with a different approach - to use the Java interface in OpenOffice to talk to the Java interface to Cocoa, rather than implementing everything in Carbon / Cocoa.

      Over time, it appeared that NeoOffice/J was developing faster, and it would be easier to get it to a usable state than the OpenOffice OS X port, so the OpenOffice OS X port was abandoned. NeoOffice/J is the `official' OS X version of OpenOffice. Additionally, the NeoOffice/J people will be handling the official port of OpenOffice 2.0 to OS X.

      --
      I am TheRaven on Soylent News
    3. Re:open office fork? by bsharitt · · Score: 1

      I belive that the offical port has been more or less put on hold indfinitly for a non-X11, so the NeoOffice port is the only viable project to port for OS X.

    4. Re:open office fork? by Rimbo · · Score: 1

      Is that the case? Last I'd heard, NeoOffice/J and OpenOffice.org hated each other's guts.

      Or something.

    5. Re:open office fork? by Uncle+Asad · · Score: 1

      Last I'd heard, NeoOffice/J and OpenOffice.org hated each other's guts.

      Oooh, look at the hate; they haven't updated the page yet!

      Or see this post, which was featured on the OpenOffice.org homepage for a while.

    6. Re:open office fork? by Rimbo · · Score: 1

      Well, good, that's nice to see.

      A spat they had made the news, but I guess the fact they got over it wasn't going to sell papers/ad space.

  23. Re:They recommend MS Office :) by macshome · · Score: 2, Informative

    Hrm - maybe Office on the Mac is much better than the Windows version. I've been hearing that for awhile, but it's still from Microsoft,

    It's far from perfect on the Mac, but I'm always astounded at how much it is better on the Mac than on Windows.

  24. Re:They recommend MS Office :) by Hercynium · · Score: 1

    Worse yet, my experience with MS-Offixe/OS X has been terrible. Maybe it's because my mac is dreadfully under-spec, but MS Office's stability was lamentable, even for a M$ product. Luckily it was a copy I bummed off my parents. I'm quite happy with OOO (which I bought at the apple store), and will give NeoOffice a try. Heck, if the integration is good enough, and it proves to be stable enough, I'll try to convince the 'rents to switch!

    --
    I'm done with sigs. Sigs are lame.
  25. A story by Apple Computer Inc: by Anonymous Coward · · Score: 0


    Enabling Bonjour Service Discovery by Apple Computer Inc

    Bonjour service discovery is always enabled. You can't disable the use of Bonjour to discover network services.

    the end

  26. For the Mac but not Mac like. by jellomizer · · Score: 1

    While I salute the NeoOffice team for getting Open Office to work nativly on the Mac, there are still things that need to be done. Primarly clean the interface. The interface is good for Windows user and Linux users who are use to sucky interfaces and which solves the problem by adding more buttons and icons to it. Mac People are more use to the cleaner Interface and most are more willing to access the features threw the menus, and hotkeys. And having buttons for the most commonly used features. Microsoft realized this when they made Office X. While it is still Office the interface was redesigned to look good on the Mac, they still went crazy with the buttons but no where as abusive as Open Office is.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:For the Mac but not Mac like. by Dystopian+Rebel · · Score: 2, Interesting

      Mac People

      UI standards aside, it's interesting to note that this phrase "Mac People" now also means "BSD-UNIX users of Intel-based computers... ~with~ two-button mice."

      --
      Rich And Stupid is not so bad as Working For Rich And Stupid.
    2. Re:For the Mac but not Mac like. by Magic5Ball · · Score: 1

      The NeoOffice/J UI looks almost as good as interfaces for the last generation of high-end pro products such as QuarkXPress and Adobe *. Although http://upload.wikimedia.org/wikipedia/en/0/0a/S-co mp-sw-aid-work.jpg">InDesign CS isn't strictly a word processor...

      --
      There are 1.1... kinds of people.
    3. Re:For the Mac but not Mac like. by Anonymous Coward · · Score: 0
      it's interesting to note that this phrase "Mac People" now also means "BSD-UNIX users of Intel-based computers... ~with~ two-button mice."

      Really? I became a "Mac Person" when I installed FreeBSD the other week, then?

      The key points you're missing:
      1. OS X is not BSD. Some of it is derived from BSD, but it's quite possible to use OS X for years and never activate a single BSD-derived function.
      2. OS X is not UNIX(r). It has Unix-like features, but it's still about the furthest you can get from Unix without becoming Windows.
      3. For all intents and purposes, there are no Intel-based Macs around today and there won't be till 2006.
      4. Apple still do not sell two-buttoned mice.


      Incidentally, what was your point, anyway?
    4. Re:For the Mac but not Mac like. by HumanTorch · · Score: 1

      yes, and if the Mac ever gets more popular (ie gets more former Windows users) .. applications will be able to get away with being Windows-like. On second thought, perhaps more Windows-like applications are what the Mac really needs.

    5. Re:For the Mac but not Mac like. by yoxi · · Score: 1

      "Mac People are..." - I'm a mac person and I don't have any problems with NeoOffice/J's interface - it works. It's very easy to customise the buttonbars if you personally think there are too many buttons. You can even add more. Let's be subjective about this....

  27. Allegedly this is a patent issue... by argent · · Score: 3, Interesting

    fonts on Linux are a bit "blurry"...that is, they are not as clear/crisp as their those on their windows counterparts.

    According to this it's a patent issue. I think there's something deeply wrong with patents on operations required to render fonts correctly, above and beyond the already troubling issue of software patents in general. Remember that in the US fonts are explicitly not copyrightable to prevent even the potential of copyright being used to prevent free speech. Shouldn't this easement be extended to any communication or presentation technology.

    1. Re:Allegedly this is a patent issue... by timster · · Score: 3, Informative

      Whoa, you're not a lawyer for sure. Nor am I.

      Fonts -- meaning that file (or files) of computer data that represent a particular typeface -- are absolutely copyrightable. That's why Linux distributors cannot distribute the fonts from Microsoft or Apple (though an end-user can download some fonts from Microsoft's web site, or use the fonts from their own Windows installation).

      It is the typeface itself that cannot be copyrighted. But that's the way the characters look, not the data that represents them to a computer. So I'm free to clone the Arial typeface by developing my own font that represents it, but I can't just copy Microsoft's font.

      Developing a good font from a typeface is a lot of hard work, I hear.

      --
      I have seen the future, and it is inconvenient.
    2. Re:Allegedly this is a patent issue... by Anonymous Coward · · Score: 0

      That is fine, and the copyright is being applied as it should be... The patent issue however is completely different.

      The methods for anti-aliasing font edges when rendering them are patented, and this is why cleartype (or anything that looks equally good) cannot be used in OSS.

    3. Re:Allegedly this is a patent issue... by argent · · Score: 1

      You're right, current usage of these words means that I should have said "typefaces" rather than "fonts". But that's a side issue: the copyright on the font isn't relevant to the patent on Truetype rendering. I could create a true type font and release it into the public domain and it would still be necessary to use the algorithm covered by this patent to properly render the typeface embodied in the font.

      That is, this is a patent that restricts the typeface itself. You can only approximate way the characters are supposed to look - the typeface - without using the technique covered by this patent. That's why this particular software patent is more disturbing than most.

    4. Re:Allegedly this is a patent issue... by justforaday · · Score: 1

      So I'm free to clone the Arial typeface by developing my own font that represents it, but I can't just copy Microsoft's font.

      As I've pointed out before, Arial already is a ripoff of another font (Helvetica)...

      --
      I'll turn into a supernova and burn up everything. Well I'll turn into a black little hole and you'll turn into string.
    5. Re:Allegedly this is a patent issue... by Anonymous Coward · · Score: 0

      That is, this is a patent that restricts the typeface itself. You can only approximate way the characters are supposed to look - the typeface - without using the technique covered by this patent.

      Not true. There is absolutely nothing stopping you creating text that will look absolutely 100% identical, down to the very last pixel, while not making use of any patented techniques whatsoever. One method (impractical, provided only as a simple proof that it is possible) would be to draw the text by hand, pixel by pixel. If you use identical pixels, that would obviously do more than "approximate" the result.

      The ONLY THING that the TrueType hinting bytecode decoding patent has locked away from the public is one particular method of adjusting character shapes at low resolutions. There are plenty of other approaches that are not patented.

      The problem isn't that the patent prevents free fonts looking good - it's that the fonts people want to use all happen to use the patented technique. Possible solutions? Convince font authors to use an equivalent non-patented technique, or produce your own non-encumbered fonts that people want to use. The Bitstream Vera family is a great start.

      Oh, and remove all the hideous "standard" fonts from X11, okay? Half the people who complain that Linux has shitty fonts are probably using bitmapped fonts by mistake. They have no purpose on modern desktops and should be removed. Thank you.

    6. Re:Allegedly this is a patent issue... by m50d · · Score: 1

      Typefaces aren't copyrightable. However, programs which produce them (i.e. ttf files) are. Anyway, yes it's patents, compile your own freetype and ignore them.

      --
      I am trolling
    7. Re:Allegedly this is a patent issue... by Upaut · · Score: 1

      Remember that in the US fonts are explicitly not copyrightable to prevent even the potential of copyright being used to prevent free speech

      I'm afraid to say it, but your wrong on this one. The English firm Monotype bought up the copyrights to every major font line, and at the time they went broke they owned every major font class. Now one of their major font libraries - the one with Ariel, Times New Roman, Courier, etc. Was bought up by Microsoft. The rest - Including the monotype name - Was bought by the new Monotype in the USA.

      Through cross lisencing Microsoft and Monotype sell the ability to print a particular font to all those that need it: Printer developers and manufacturers, publishing houses, Film production studios, etc. Which means a chunk of the cost of your new printer was paid to one or both of these firms for the right to print a particular font. If you download a new font that is owned by either of these corperations, you will have to pay anywhere from $10 to $50.

      --
      3 degrees of separation from Vladimir Putin
    8. Re:Allegedly this is a patent issue... by IamTheRealMike · · Score: 1
      For western/Latin scripts there is no big deal, the fonts on Linux look just fine as the auto-hinter can cope well most of the time. Certain types of scripts, especially Asian scripts, currently don't work terribly well with the auto-hinter. I believe the FreeType team are working on fixing this, though you get best (and most compatible) results using the real bytecode interpreter.

      For what it's worth this patent is owned by Apple, but they are repeatedly refused to license it so it can be used by free software. It's supposed to expire in 2009 or so, I think.

  28. Screenshot by base_chakra · · Score: 4, Informative

    This 800x600 screenshot should survive a slashdot throttling.

    1. Re:Screenshot by owlstead · · Score: 1

      Although it gives the right impression, it confuses the hell out of me why someone would use a JPEG picture to show a window that is 90% unicolored. People have invented GIF and PNG for just that purpose. Yuk.

    2. Re:Screenshot by Anonymous Coward · · Score: 0

      ># man love

      Sorry dude, I'm not into that

  29. Re:They recommend MS Office :) by crawling_chaos · · Score: 1
    Worse yet, my experience with MS-Offixe/OS X has been terrible. Maybe it's because my mac is dreadfully under-spec, but MS Office's stability was lamentable, even for a M$ product.

    And OpenOffice totally blows as well. Takes over two hours to load. Maybe it's because I'm trying to run it on my Coleco Adam, but hey.

    --
    You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
    -- Colonel Adolphus Busch
  30. Linux: The bleeding edge of user interface by Anonymous Coward · · Score: 0, Funny

    The interface is good for Windows user and Linux users who are use to sucky interfaces

    What are you talking about ? Stop it ! Take Eterm and those kewl patterns man, they are just so cool and fresh. Apple doesn't stand a chance.

    Linux is the king of GUIs. After all it comes with about twelve different ones installed.

    1. Re:Linux: The bleeding edge of user interface by jellomizer · · Score: 1

      Dont confuse good graphics with good interface. Compared to Windows and Linux the Mac OS Interface is quite boring. But it is functional

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  31. First impression by mariox19 · · Score: 1

    I'm glad you beat me to my post, because I was going to say something about the appearance.

    I hope that you're right and the developer team is planning on improving the appearance. This sort of thing is important to Macintosh users. (I say this even though I know I risk the flames of Macintosh critics about "superficiality.")

    The responsiveness of the windows is impressive, and overall it does look good. The icon especially is superb. Other than a slight delay when first typing text, the application seems quick enough, and quicker than many Java apps.

    By the way, I'm using an iMac G4 at 800MHz with 512MB of RAM running Panther -- not exactly a speed demon machine.

    This is a good first release. I look forward to improvements, but it's ready to go now.

    --

    quiquid id est, timeo puellas et oscula dantes.

    1. Re:First impression by Ford+Prefect · · Score: 1
      I hope that you're right and the developer team is planning on improving the appearance. This sort of thing is important to Macintosh users.

      I gather that this is a very big issue to them - I've found the future development plans from the main developers (Patrick Luby, 'pluby', and Edward Peterlin, 'OPENSTEP'):
      Implement Aqua widgets and file dialogs - This has been our goal for a long time and I would like to get this done while the OpenOffice.org volunteers are working out all of the bugs in the OpenOffice.org 2.0 X11 code.

      There's other interesting reading in there as well, including the plans to port to MacOS X-on-Intel, which sound potentially fraught but mainly involve porting OpenOffice.org to GCC4, which will affect other platforms sooner or later too...
      --
      Tedious Bloggy Stuff - hooray?
    2. Re:First impression by Anonymous Coward · · Score: 0

      First comes stability, then beautification :)

      There's a plan underway to redo the GUI icons, and eventually we hope to force OOo to realize that the UI matters and more than just swapping icons and buttons are needed....

    3. Re:First impression by Anonymous Coward · · Score: 0

      The responsiveness of the windows is impressive, and overall it does look good. The icon especially is superb.

      Yes, that is really important, the look of the icon. Sheesh, I'll never understand MacPeople...

    4. Re:First impression by mariox19 · · Score: 1

      I took the work done on the icon as a good sign that an attractive interface mattered. The icon itself is only of little importance, but after finding out that there were plans to improve the looks of the GUI, I was willing to take the icon's appearance as an indication that there was good taste among this development team.

      Sheesh, I thought that would be obvious to anyone!

      --

      quiquid id est, timeo puellas et oscula dantes.

  32. I'd give NeoOffice/J a try but... by Anonymous Coward · · Score: 0, Funny

    Try as I might I can't seem to locate a crack anywhere on the internet.

  33. keep 'em coming by maryjanecapri · · Score: 1

    this is such a boon to Mac. when i bought my ibook (i use it for writing when i'm away from my desk) i couldn't believe how difficult it was to find a word processor that i not only liked to use but felt good about using.

    after trying and trying i finally got the X11 port of openoffice installed but it was the most amazingly slow thing. eventually i found neooffice and found it to fit the bill perfectly.

    i wish other softwares would follow their lead. sure you can try to install packages with fink but it's not terribly user friendly.

    and, after 10 years of using Linux software, i'm not about to start paying for software i can use for free on my desktop!

    --
    nature loves variety::society hates it get your variety at http://www.monkeypantz.net
    1. Re:keep 'em coming by TheRaven64 · · Score: 1
      Try Pages. For one-off documents and anything shorter than a few pages, it's a joy to use. For longer things, it isn't a patch on LaTeX, but isn't meant to be.

      As for a spreadsheet, NeoOffice/J is still the one I use.

      --
      I am TheRaven on Soylent News
  34. Define Niche by Anonymous Coward · · Score: 1, Funny

    A Java Office program (with dubious file format compatability) on a mac....

  35. It'd probably be easier by CdBee · · Score: 3, Interesting

    OpenOffice on OSX was almost cancelled several times due to the amount of x86-specific code in it, apparently.

    --
    I have been a user for about 10 years. This ends Feb 2014. The site's been ruined. I'm off. Dice, FU
    1. Re:It'd probably be easier by helixblue · · Score: 2, Informative

      Huh? OpenOffice has runs very nicely on other architectures such as SPARC and MIPS, and in fact, it's predecessor, StarOffice was sold for such platforms. I mean, the project is basically run by Sun! It was not x86-specific by any stretch of the imagination. Mac OS X has it's own set of peculiaraties that make porting the code of this particular project a bit of a pain. For more information, see Compiler and Other Technical Issues in the Mac OS X 10.0.x Platform.

    2. Re:It'd probably be easier by Princeofcups · · Score: 1

      > OpenOffice on OSX was almost cancelled several times due to the amount of x86-specific code in it,
      > apparently.

      It's written in C, not in assembly. :-) OpenOffice runs fine on my Solaris Sparc machine. I think you mean to say Windows and X11 specific code, as opposed to Cocoa specific code.

      jfs

      --
      The only thing worse than a Democrat is a Republican.
  36. The big question: Is it made using XCode? by Mr.+Cancelled · · Score: 3, Interesting

    ... And thus easy to make a universal binary from? Or will this be harder to port once the Intel switch begins?

    Good app, but I hope it can move with the Mac as Apple transitions to Intel processors. Seems like kind of a waste of effort if it's tied to a specific architecture, in light of Apples recent announcements.

    1. Re:The big question: Is it made using XCode? by Danathar · · Score: 1

      Good question...but thankfully a large percentage of the code is in java..so it should not be that much of a problem hopefully.

    2. Re:The big question: Is it made using XCode? by tverbeek · · Score: 1
      I've heard a rumor that the non-Java code that underlies NeoOffice has already been ported successfully to Intel processors. The codename for it is "OpenOffice.org for Linux". ;)

      Even if they can't pull of the "universal binary" thing, I wouldn't expect it to be especially difficult to compile a separate version of NeoOffice for the MacIntel boxes.

      --
      http://alternatives.rzero.com/
    3. Re:The big question: Is it made using XCode? by biftek · · Score: 1

      "made using XCode" is apple-speak for "compiled with GCC". Just add -arch i386 and it will likely work.

    4. Re:The big question: Is it made using XCode? by Drakonian · · Score: 1

      Wow, every Apple story now has at least a few posts like this. It's not a big deal. It's mostly a recompile. And it's a good year away. Chillax everyone.

      --
      Random is the New Order.
    5. Re:The big question: Is it made using XCode? by javaxman · · Score: 1
      Even if they can't pull of the "universal binary" thing, I wouldn't expect it to be especially difficult to compile a separate version of NeoOffice for the MacIntel boxes.

      There's this "lipo" command you can use to modify universal binaries ( I *still* want to call them 'fat', for obvious reasons ). Even if you compile the binaries separately, you can use 'lipo' to combine the two ( possibly completely different ) binaries into one executable file.

      And you make an excellent point. The OpenOffice stuff should just recompile under GCC4 and be done. If they have endian issues, there's a problem already. The difficulty of 'porting' an application from PPC to x86 is way overblown. It's not like we're writing in assembly here, folks! Well, ok, not most of us... but if you're writing assembly, you have your own issues ;-)

  37. Re:5 Years??? by Anonymous Coward · · Score: 0

    Five years refers to the period of time since the first Mac OOo code was written. OOo on the Mac didn't even launch until 2002 and OOo 1.0.3 on the Mac wasn't released until 2003. Neo/J has really only been in development for two years, mainly by one programmer in his spare time.

    http://neowiki.sixthcrusade.com/index.php/History_ of_NeoOffice_and_OpenOffice.org:_Introduction (when the wiki comes back again)

  38. Re:They recommend MS Office :) by k96822 · · Score: 3, Funny

    Microsoft Office for Mac OS X is to Microsoft Office for Windows as Chevy is to Ford. No matter which you use, you should have bought a Toyota.

  39. Great! Just in time by nurb432 · · Score: 1

    For OO 2.0 to arrive...

    Great work tho.. have to give them a lot of credit..

    --
    ---- Booth was a patriot ----
    1. Re:Great! Just in time by realkiwi · · Score: 1

      I'm running a beta of OOo 2 on my G3 B&W (X11 version of course)

      Google around

      --
      realkiwi
    2. Re:Great! Just in time by nurb432 · · Score: 1

      Yes, but the whole point of the 'j' project was to get rid of the X11 dependencies and be a true OSX application...

      --
      ---- Booth was a patriot ----
  40. Runs way slow! by Anonymous Coward · · Score: 0

    I was actually using NeoOffice yesterday, and it was painfully slow...

  41. Cars and Computers by amichalo · · Score: 1

    I don't know why people love comparing cars to computers so much. Mac users especailyl like to call Macs the BMW of Computers due to the small market share, high quality, and a heavy dose of style when compared to plane jane Dell (Chevy/Ford?) boxes.

    Well I have an analogy for NeoOffice/J - It's the PT Cruiser of Software. Sure it's all new and shinny on the inside, but it's retro styling harkens back to Office98 or something. Lots of Grey and icons I certainly don't want to lick or drink.

    Don't get me wrong, I like NeoOffice/J and have had it installed for several Beta release cycles now. But if they are gonna stay retro, I am gonna have to hold out for a Ford Mustang GT version, with retro racing stripes and an aqua GUI, before I leave the Chevy Camero that is MS Office for Mac in long term parking.

    Three Cheers for the NeoOffice team!

    --
    I only came here to do two things; kick some ass, and drink some beer...looks like we're almost out of beer.
    1. Re:Cars and Computers by yoxi · · Score: 1

      " But if they are gonna stay retro..." they're working on the rest of the UI aquification, but it's a lot of work for not many people to do. Be patient - and what wrong with being grey anyway? Are you a chromophobe?

  42. The Desktop Wars by chia_monkey · · Score: 3, Interesting

    Are the desktop wars over as many had previously assumed. "Microsoft has won". There still seem to be some coals on the fire though. You've got a couple of these open source projects (OpenOffice, NeoOffice, etc). Then you've got Apple doing their thing...starting with Safari, then Keynote, then iWork...Then you've got the whole Apple moving to x86 and everything that brings such as developers showing how easy it is to port to x86 by doing a full conversion during the WWDC and nutty statements like Michael Dell saying he'd sell OS X if Apple decided to sell it as a standalone product.

    I'm not really sure the desktop wars are over. Each announcement of stable, full-featured M$ replacement seems to solidify that assumption. Thoughts anyone?

    --

    "He uses statistics as a drunken man uses lampposts...for support rather than illumination." - Andrew Lang
  43. My Experiences by LaughingLinuxMan · · Score: 5, Informative

    I have used the last release candidate to do "real" work on personal projects. That is, I actually tried to get things done with it rather than just clicking around to see how "Mac" it is. I have both MS Office X and NeoOffice/J installed. Office X is used for school work, where I cannot take a chance of my professors not being able to read a document.


    1) In the early releases NeoOffice/J was sluggish. There were rendering delays with first word typed, pull-down menus, and switching tools, among other things. I am pleased to say that the interface speed has increased through the release candidate schedule. That said, you will find there are still delays here and there that may bother you. They bothered me until I used Office X again. That product has UI delays as well, just in different places. At this point I think it is a wash.


    2) Stability (e.g. random crashes) was an issue on the earlier releases. These have been largely successfully addressed. In fact, when using the last RC to get work done I did not experience any crashes. Very nice.


    3) The UI is somewhat confusing, since it departs from some of the standard metaphors we usually see in office software. The primary example is the tight coupling of the different suite functions. Those that are used to using one application for spreadsheets and another for presentations will need to aclimate to a monolithic application. This is not a big change per se; it just takes some getting used to. There are other minor departures, such as the lack of aqua widgets and different locations of buttons and menu items. Once I got used to these differences, I found the product usable for my project work.


    All that being said, I have decided to do all my personal project work in NeoOffice/J. Why? The data I generate in my personal projects is valuable to me personally. I would like to maximize the chances of being able to read it in the distant future. Since the Open Office file format is completely open and documented, I believe that the OO.org file format has the greatest chance of being read 15-20 years from now. If there is not any software in 15-20 years that can read the format, then due to the open licensing on the format I could write/hire someone to write a program to read the documents. Try doing that with some archaic closed format. I will deal with quirks today to enable access to the my data tomorrow.


    -LLM

    1. Re:My Experiences by Anonymous Coward · · Score: 0

      I have been using the release candidates as well and have found NeoOffice/J satisfactory in performance and features, especially its ability to read and write Microsoft Word documents. One thing the parent doesn't mention, though, is that it takes a good long time to start up. On my 800MHz G4 PowerBook, the final release takes a little over a minute to start up from the dock and open a new blank document, and that's a pretty sizable improvement over the previous release candidates.

    2. Re:My Experiences by blah-Hipo · · Score: 0

      I'm going to have to disagree with you here dude. I used one of the RC of NeoOffice/J, probably about a month ago. I found it to be sluggish and more or less unusable. I also hate Word X, which crashes all the time and is slow too. As far as the format goes...

      It seems to me that XML is more of a standard now than OO.org's file format will ever be. The only way that is incorrect is if OO.org uses XML, which I am entirely ignorant of. But either way, even open office on linux isn't very impressive; everyone just says it is because we long for a nice open source desktop, even though that is nowhere close to being achieved.

      for those of us who are /rad enough to admit that apple has come into the unix desktop market and acheived what 10+ years of competing OO standards and implementations could not, i see no reason not to admit that now. Pages is a fabulous word processor that stores documents in XML.

      In terms of usabiliity and preservation for the future, how is OO.org a better option?

    3. Re:My Experiences by Anonymous Coward · · Score: 0

      Openoffice does use XML. It won't be the OASIS XML format until 2.0, but it is still XML.

    4. Re:My Experiences by Zhe+Mappel · · Score: 1
      Helpful post, thanks.

      Regarding UI delays: running on a G3 iBook, the only word processor for OS X that has not produced the slightest hesitation in rendering or responsiveness is Mellel. Perhaps not coincidentally, it's also the one with the most intuitive and orderly UI--my word processor of choice.

      To be sure, Mellel isn't an office suite so I'm keen to give this NeoOffice/J release a try.

  44. Great for files from those 'other' computers by NardofDoom · · Score: 4, Interesting
    My wife was working on a presentation for her masters class and was getting files from her Windows-using classmates to produce the final Powerpoint. For some reason Office v.X couldn't open the files, but NeoOffice/J could.

    For that reason alone (and the price), I recommend NeoOffice. I've been using it as my sole office application for some time now with no problems.

    --
    You have two hands and one brain, so always code twice as much as you think!
    1. Re:Great for files from those 'other' computers by MrHanky · · Score: 1

      Yes, that sort of thing happens. I've had errors in Word documents that I couldn't fix in three different releases of Word (one for Mac, two for Windows), while OpenOffice.org easily repaired them. There really isn't any reason for not having OpenOffice/NeoOffice if you exchange documents in Microsoft's proprietary formats, at least as a back-up.

  45. What not do this on all versions by plazman30 · · Score: 1

    Ok, my understanding is that this is the C++ OpenOffice code with Java used solely for the GUI (or so their site says). I loaded it last night and it works just fine. It's not 100% Aqua, but it's good enough for every day use.

    My question is.... Why don't the openoffice developers take this approach? Java is available for Mac, Linux, Solaris (obviously), and Windows. And on the Mac and Windows versions the UI looks pretty good. My understanding with the Linux version is, it can use GTK widgets, so I would think a 1.5 Java on Linux should have a good look and feel also.

    Wouldn't keeping the C++ backend with a Java front end for the UI make the app much more portable among platforms, and allow OpenOffice.org to embrace the Mac right off the bat, as well as any new platforms that come along?

    1. Re:What not do this on all versions by iGN97 · · Score: 1

      Why "fix" what isn't broken? Part of the problem with the new OO.o is (according to many), the reliance on Java for the DB-functionality.

      Java still has licencing issues which makes Java code (in practice) less portable than C++.

      Also, technically, what you're suggesting is using Java as a layer on top of C++, just to make calls back out into native code (GTK and friends). Without starting a flamewar about bloat, this just seems extremely expensive for something that just doesn't provide all that much functionality. JNI is fairly slow, and adding two layers of it "just because" doesn't make much sense to me.

    2. Re:What not do this on all versions by flithm · · Score: 1

      You know, it's not all that hard to do a cross platform gui in c/c++ that has native widget support across all platforms.

      I mean there's already free toolkits out there, and even so, doing your own isn't immensely hard. It just takes knowing more than one system really well, and writing a properly abstracted widget interface.

      Having said that, that's exactly what they've done for OO 2.0.

      And no, they didn't use Java for the GUI.

    3. Re:What not do this on all versions by plazman30 · · Score: 1

      If there's really a cross platform GUI on OpenOffice, why does the Mac version still require X11? And OpenOffice has already announce no native GUI for OS X in version 2.0

      So cross platoform GUIs are not that easy. Just ask the Mozilla folks. Their project was delayed for years just getting GUI framework to work across the board.

      Personally, I'd like GTK+ ported to the Mac to run natively the way it does in Windows. And simply port apps using that.

      Sadly I am not a developer, so I can't help hack code....

    4. Re:What not do this on all versions by flithm · · Score: 1

      Did I miss something? The OOo website clearly states that it will have native theme integration. All of the screenshots of the betas already show what appears to be full integration.

      Apparently the KDE team already has OOo 2.0 native widget support ready.

      Unless you can find a reference for that, I don't believe you.

      Also cross platform GUI's definitely aren't easy, but they're not a complete nightmare. And just so you know I'm not talking out of my ass I've personally created a GUI abstraction layer that supported GTK, win32, and a custom OpenGL widget library. You just have to think about it before hand.

      Yeah it's tough, and yeah you learn a lot along the way, but just ask the Mozilla folks, it's not an impossibility by any stretch of the imagination.

      Also, especially now with toolkits like wxWidgets that suddenly becomes a whole lot easier!

      And yeah a GTK port to Mac would definitely be cool.

      Seeing as you're not a developer maybe you should leave the development talk to people who know better.

    5. Re:What not do this on all versions by plazman30 · · Score: 1

      Well, if I don't ask questions, I will never learn. So leaving the development talk to the developers doesn't really encourage anyone to take up development that hasn't done so before, does it?

    6. Re:What not do this on all versions by flithm · · Score: 1

      Yeah true enough. Sorry man I was a bit of an ass there.

      Asking questions is never a bad thing.

    7. Re:What not do this on all versions by plazman30 · · Score: 1

      Hey man, no problem. Funny part is, as I was reading that, I was in the process of writing my first perl script. While in no way as complicated as C++ coding, it is a start.... :-)

  46. NeoOffice/J Not Written in Java by auctoris · · Score: 1
    From NeoWikie:

    So...is NeoOffice/J written in Java?

    No.

    NeoOffice/J is a Mac OS X native version of OpenOffice.org that uses small amounts of Java code for graphics drawing and configuration.

    OpenOffice.org is written primarily in platform-agnostic C++. However, NeoOffice/J takes advantage of Mac OS X's advanced Java integration to tap into the OS X look-and-feel. In other words, the "J" in NeoOffice/J primarily has to do with operations that affect how the application appears to the user. The "guts" of the office suite are written in C++. (The code that makes up NeoOffice/J is 99% OpenOffice.org code shared among all OpenOffice.org platforms and 1% Mac OS X-specific code in Java, C++, C, and Objective-C.)

    Thus NeoOffice/J will only run on Macintosh computers running Mac OS X 10.2.x, 10.3.x or 10.4.x--not on Mac OS 9, Windows, Linux, Darwin, or any other form of UNIX.

  47. Troll or idiocy? by Anonymous Coward · · Score: 0
    Great comment! It's a shame you didn't take the trouble to read the whole sentence you quoted otherwise you might have said something relevent. But even so, it was a great answer to the first eight words (minus, perhaps, the sixth, if you assume context is a factor.)

    My advice: give up. Seriously. If this is the best you can do, it's probably time to move on. You obviously don't know what you're talking about and have few, if any, English comprehension skills.

  48. They Just Don't Get It: Why I'm Sticking With Word by AndrewJ-NYC · · Score: 2, Informative

    I'd love tgo switch to NeoOffice or Pages or another decednt alternative to Word on the OS X platform, but they all ignore a feature of vital importance to professional writers like myself: A halfway decent word count function. In Pages, you can do a word count on the whole document, but not on a highlighted selection. And in NeoOffice, you have to go through an enormous song-and-dance with the Tools-->Statistics dialog (before manually selecting a tab!) to get the word count (a method that also precludes getting the word count of a highlighted selection). There's tons of room for a word count box in the status bar at the bottom of document panes in NeoOffice, but is it there? Nope. In Word, I can see how much I've written by looking at the status bar or by by executing a quick keyboard commmand, and I can run it on selections as easily as the whole document. Everyone who's trying to make Word-beaters for OS X just don't get it. I don't like using MS bloatware, especially on the Mac, but for now Word is the only real option for anyone who earns his or her living as a writer.

  49. Not Completely a Mac Application by 99BottlesOfBeerInMyF · · Score: 1

    Everything else is great, and infinitely superior to the old port of OpenOffice.org to the Mac's X11.

    Disclaimer: I haven't downloaded and tried this most recent version.

    While NeoOffice/J is a usable program, I think stating that everything else is great is a bit of an overstatement. In all the versions I have used to date the startup times are very slow, and the GUI lacks the responsiveness of a native application. Scrolling for example is noticeably choppy. More importantly for me is that it has no support for native system services. My personalized spell checking library, grammar checking, translation services, thesaurus, online searching, scripts, font books, etc. are all unavailable. That right there is a lot of the added value of OS X. For me that makes it a non-starter as a production application. (I do a lot of writing, professionally.)

    On the other hand, it does a very good job of opening Word files, the spotlight plug-in is worth downloading all by itself, and you can't beat the price.

    1. Re:Not Completely a Mac Application by arodland · · Score: 1

      Well, this is certainly no special feature of NeoOffice. OpenOffice is slow, unresponsive, poorly integrated, and visually out-of-place on every platform :)

    2. Re:Not Completely a Mac Application by bcrowell · · Score: 1

      Disclaimer: I haven't downloaded and tried this most recent version. [...] In all the versions I have used to date the startup times are very slow,
      I downloaded the latest version today, and installed it on my wife's high-end Mac. The startup time was 65 seconds for the first time, and 30 seconds for the next time. To me, that's unacceptable.

    3. Re:Not Completely a Mac Application by poofyhairguy82 · · Score: 1
      I downloaded the latest version today, and installed it on my wife's high-end Mac. The startup time was 65 seconds for the first time, and 30 seconds for the next time. To me, that's unacceptable.

      Welcome to OpenOffice. It even is like that on Linux. The second edition is a little better. I would not use it, but paying $400+ for an Office suite "to me, [is] unacceptable."

  50. Uh huh... by Anonymous Coward · · Score: 0

    still no Access-like app, huh? I know several people that would do the Mac switch, except for the lack of a version of MS Access. I explain that Filemaker is much better, but there's no interest in converting between Filemaker for their home machine and Access that must be used for work. :(

  51. NeoOffice can't compare... by ignatz72 · · Score: 1

    To OO.o, at least in my experience. Heck, I'm using OO.o 1.1.2 with 10.3.9, and there's no comparison! The main reason is 10.3 comes with Apple's own X11 app that has the tightest Aqua X-win integration available. Previous versions, while packaged in a nice installer, still used OroborX or XFree86 for X-window rendering, which leaves A LOT to be desired (you know you ain't usin' no commercial product). However, with Apple's modification of XFree86, the Apple X11 env is almost transparent.

    By all means give Neo a try, I'll even try the new one, but here's my caution: YOU BETTER HAVE A FAST MACHINE. Trying to run a Java office package on a 466mhz just don't cut the mustard.

    Just my $.02 worth.

  52. speed? by Anonymous Coward · · Score: 0

    So now that it's stable, will there be any work on it's speed? (Particularly startup time). Forget native widgets, that's just eye candy. How about a useable startup time?

    On my brand new G4 Powerbook, 1.5GHz/768MB of memory, to open a small (very small) .SXC (StarOffice spreadsheet format) file takes about 22 seconds. (This is with NeoOffice not having been running, the actual file open time is minimal compared to startup).

    The direct X11 port is actually slightly quicker... startup plus opening a small file is only 20 or 21 seconds. Which is still intolerable. Really, what is it DOING? 1.5GHz * 20 seconds = 30 billion calculations to just start the application?

  53. Re:They recommend MS Office :) by kannibal_klown · · Score: 1
    Microsoft Office for Mac OS X is to Microsoft Office for Windows as Chevy is to Ford. No matter which you use, you should have bought a Toyota.


    I would say it's more like this:
    MS Office for Mac is to MS Office for Windows
    as
    Cadillac is to Geo

    The Mac and Windows versions are as different as night and day.

    However while Cadillac's are nice cars, they're not the best.
  54. Re:They recommend MS Office :) by Arker · · Score: 2, Insightful

    *cough*

    Still trying to get through to their server, but the Slashdot text certainly doesn't give me any confidence in the developers.

    Key Macintosh features include a standard Mac OS X installer

    Except that's not a standard Macintosh feature. Real Mac programs don't have installers, they have .app bundles and can be installed by simply dragging them to 'Programs' (or any other location of your choice) and uninstalled by dragging them to the trash.

    Up till now it seemed to be mostly Microsoft products that break that model. Is the NeoOffice/J team trying way too hard to follow MS?

    When their servers come back up I'll be trying it, nonetheless... with high hopes but low expectations.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  55. Umm...it *IS* written in Java by frankie · · Score: 1
    How much quicker could we have had NeoOffice on MacOS if it were written in an easily-ported language like Java?

    Wow, this thread is much Much MUCH farther into the bizarro world than usual, even by the lax non-article-reading standards for Slashdot. NeoOffice/J IS WRITTEN IN JAVA with some Carbon for native Mac goodies. What the heck do you think the "/J" stands for?

    It really freaks me out that NINE OTHER PEOPLE already responded to Santa's question and none of them mentioned this minor detail.
    1. Re:Umm...it *IS* written in Java by Anonymous Coward · · Score: 0

      It really freaks me out that NINE OTHER PEOPLE already responded to Santa's question and none of them mentioned this minor detail.

      Considering that we revel in our ignorance and paranoia on this site, is it any surprise that most people wouldn't have the slightest idea they were being had?

    2. Re:Umm...it *IS* written in Java by 2.246.1010.78 · · Score: 1

      I understood it in a different way: what if OpenOffice would have been written in Java right from the beginning - then porting would have been much easier.

      Would it be possible to back-port NO/j to windows/linux?

  56. Re:They Just Don't Get It: Why I'm Sticking With W by 99BottlesOfBeerInMyF · · Score: 1

    ...NeoOffice or Pages or another decednt[sic] alternative to Word on the OS X platform, but they all ignore a feature of vital importance to professional writers like myself: A halfway decent word count function.

    Actually, while the programmers of Pages may not "get it," because it is a native application and because the programmers of OS X do "get it," you can just install a system service that will perform a word count on a selection. In fact there is a set of services called "Wordservice" that is free and includes that functionality as well as many more (like: Reformat, Remove line attachments/endings/links/multiple spaces/multiple feeds/quotes, Trim line beginnings/line endings/lines, Sort lines ascending/descending, Shift left/right, Initial caps of words/sentences, All caps & lowercase, Mac/Windows/Unix line endings, Rotate 13, Straight/Smart Quotes, Encode/Decode tabs, Insert date/date & time/time/contents of path, Speak native/german text). You can download it from here. System services work on all cocoa applications like Word, Pages, Indesign, TextEdit, Safari, etc. They do not work on NeoOffice/J though, which is for me one of it's biggest failings.

    ...for now Word is the only real option for anyone who earns his or her living as a writer.

    OK, now you've really confused me. You're a professional writer who uses Word? I'm so very sorry. For larger, technical works Latex or Framemaker are both much, much better options. They are actually designed to create and layout books, not memos. For writing non-technical works or if you don't need to do layout there are many text editors that don't have the bugs/limitations of word and provide very useful features.

    I've worked at a place that used word for actual writing, but we had to give it up very quickly. Larger files (200+ pages with some embedded images) would regularly become corrupted and either fail to save, or save but fail to open. The layout features were incredibly weak and everyone was reduced to using carriage returns to try to place text and objects. I'll tell you right now, I have written professionally as all or a large part of my job for many years and Word is a non-starter.

  57. Have a great big cup of C++ by argent · · Score: 1

    NeoOffice/J IS WRITTEN IN JAVA with some Carbon for native Mac goodies. What the heck do you think the "/J" stands for?

    It stands for "we're using Java for the user interface". NeoOffice is based on the OpenOffice.org source code, which is written in C++.

  58. Re:all kidding aside... by canUbeleiveIT · · Score: 0

    If this project wants to be seen as credible, perhaps they should have the money before they make the announcement. Whether or not the original poster wants to donate is immaterial.

  59. Well Done NO/J devs! by benmhall · · Score: 4, Informative

    I've been using NeoOffice/J on my Macs for a couple of years now. (I have a rather dated review here.) Without a doubt, it's my favourite office suite for OSX.

    What's really amazing is that almost all of the coding work is done by Patrick Luby (pluby) with a fairly small group of very dedicated testers and contributors. Despite the complexity of the code and the magnitude of the task, Patrick and the rest of his small team of volutneers has managed to release the only viable alternateive to MS Office for Mac OSX.

    I have been installing NeoOffice/J on lab machines at work for over a year now. NO/J 1.1 is a significant improvement over the earlier versions. It now integrates with the menubar, opens and closes like a Mac app, and even uses OSX's keyboard shortcuts. Heck, they even managed to integrate it with SpotLight!

    For everyone out there using a Mac, be sure to check it out. Also, if you like the program don't forget to donate. Even $50 is much appreciated. Think of it, an entire office suite on your platform of choice with perfect interoperability with Linux, Windows and Solaris. And it's Open Source. Surely that's worth a donation.

    1. Re:Well Done NO/J devs! by anechoic · · Score: 1

      agreed 1000%...while not as spunky as OO it is a very, very good alternative to the crapware that MS Office is on the Mac.
      I also highly recommend supporting Mr. Luby by donating some cash to his efforts if you use NeoOffice.

  60. Refund by bach37 · · Score: 1

    Then why don't you go ask for a refund?

  61. Re:all kidding aside... by Macrat · · Score: 1

    You must be kidding.

    Even major corporations can't handle the cost of the bandwidth to be slashdotted.

  62. Re:They recommend MS Office :) by MsGeek · · Score: 1

    If you are beating your head against the wall trying to run Mac Office 2004 on an older machine, you might want to try the previous version, Mac Office X. v.X is happy on a 300MHz iBook...it was happy with only 160MB RAM and is positively ecstatic with 544MB.

    I intend to try this new version of NeoOffice when the dust settles, though. I try to run as much F/OSS on my machines as possible, even those running unfree OSes. There is a huge amount available for Mac OS X, and almost everything is available to Mac that is available to LinuxPPC if you run the X11 layer.

    --
    Knowledge is power. Knowledge shared is power multiplied.
  63. RE: Maybe you're the "fucking idiot" ... depends. by King_TJ · · Score: 1

    Commerical software developers aren't stupid. They don't like re-inventing the wheel any more than anyone else does.

    If they see an OSS project that parallels something they want to do, or are trying to do, they very well might want to contribute to it or work along-side of it, to achieve their own goals more quickly.

    I'm not saying Apple would just want to give out free hardware to anyone working on OSS proijects. Obviously, that wouldn't make any good business sense. But striking a deal with the NeoOffice people? Might be a sound plan for Apple, while helping them at the same time. Right now, Apple has the aging "Appleworks" product as their "all in one" suite. It's long overdue for replacement with something, but there's really nothing they've come out with that serves that purpose. I could see adopting and modifying something like NeoOffice and making it the successor to Appleworks, while still keeping Pages, Keynote, and whatever else Apple has up their sleeves as the higher-end set of solutions. (Microsoft still sells "Works", despite having Office. Apple could very well do something similar.)

  64. Great by hkb · · Score: 1

    Wow great, an office suite with a Windows GUI. Now I can harken back to the days before I "switched", back when Windows was relevant to me.

    TextEdit it still is.

    --
    /* Moderating all non-anonymous trolls up since 2004 */
  65. Study versus washer and dryer by mariox19 · · Score: 1

    That's funny that you should make that comment. (I'm not the original poster, by the way.)

    I had a one-bedroom apartment some years ago. I turned the living room into more of a studio apartment and the bedroom into a study. Having no washer and dryer I used the laudromat, which I happened to enjoy. You can get all of your wash done in one sitting, and it's a great place to people watch. (Of course, I was living in a college town, where the ratio of attractive to non-attractive people increases.)

    As for his priorities, each to his own ;-)

    I just prefer to have a room for my books, desk, and computer.

    --

    quiquid id est, timeo puellas et oscula dantes.

    1. Re:Study versus washer and dryer by WinterSolstice · · Score: 1

      I guess that does help. I have only had experince with laundromats that were ugly, uncomfortable, and unpleasant. Perhaps the one you used would change my assesment :)

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
  66. Ugliest Mac OS X app ever by Anonymous Coward · · Score: 0

    Oh my God... I got a Mac about six months ago and have abstained from the Windows world... and then I open this goliath on my Mac and I actually audibly screamed... Windows look/feel never seemed quite so ugly as when displayed acutally within a Mac... *sigh*

    -jag

  67. Why I'm Sticking With "vi" (plus, Services Menu) by argent · · Score: 1

    I'd love tgo switch to NeoOffice or Pages or another decednt alternative to Word on the OS X platform, but they all ignore a feature of vital importance to professional writers like myself: A halfway decent word count function.

    Yeh, that's why I'm sticking with "vi". Being able to go ":,'aw !wc" or "!}fmt" or "!/^From/-1sort" instead of having to write a script or cut-and-paste from a whole other document is a killer feature.

    OK, OK, I'm a retro old fogey. I won't tease you any more (but I really do prefer to work in "vi" than GUI apps)... but this isn't entirely irrelevant either... because Mac OS X has a really neat capability that many people don't fully "get", that gives you a lot of this kind of easy integration between applications that made UNIX such a revolutionary environment back in the '70s (and, goldarnit, still does today).

    In Pages, you can do a word count on the whole document, but not on a highlighted selection.

    Does the Services menu not work in Pages? I'm sure it does. In any Cocoa app and many Carbon ones you can select text and perform operations on it through "Application -> Services", and any application can publish a service in the Services menu. There's a freeware application called "WordService" that provides among other things a "statistics" dialog that gives you characters, spaces, words, and lines in the selected text.

    I don't know how well NeoOffice/J supports services, but Pages is Apple's own application so I would be positively astounded if it fell short in this area. This kind of deep integration between applications is what really makes Mac OS X a joy for me. You don't need to provide every feature over and over again in every application, you just need to provide a way for programs to work together.

  68. Eh ... am I missing something? by cobrabyte · · Score: 1
    Key Macintosh features include a standard Mac OS X installer, a native Aqua menu bar, use of the native printing system, full clipboard support, drag-and-drop, Mac "command" key shortcuts, mouse scrolling, integration with major Mac email clients and native support for Mac fonts.


    So, basically ... sorry, I have to see if I am getting this right ... it took them 5 years to get the functionality of a 'Hello World!' app? Ooops ... with email integration.

    If these are the key features, they should rethink their slot in the development world.

    Seriously.

    Nobody ever made it anywhere by reinventing 'Hello World!' apps or marketing the most basic (ie. functionality is built-in from the get-go) features as 'key features.'

    </jawdrop>


    -c
    1. Re:Eh ... am I missing something? by danigiri · · Score: 1
      "marketing the most basic (ie. functionality is built-in from the get-go) features as 'key features.'"

      You mean like true plug-and-play in Linux or seamless universal works-without-a-hitch copy-paste among X11 apps?

      They are definitely considered "basic" to any Mac user... aren't they? Remember: Basic(user) == ExtremelyDifficult(engineer)

    2. Re:Eh ... am I missing something? by Uncle+Asad · · Score: 2, Insightful

      Yes, you are missing something. If you've used (or read reviews) of the Mac (X11) version of OpenOffice.org, you'd know none of these features are present in OOo. Maybe that's not a big deal for the Slashdot crowd, but for the average Mac user who's looking for a fully-featured and/or free/Free alternative to Microsoft--especially if the person has tried to use the X11 version or has read reviews--these are important features to tout. It all depends on the audience....

      And five years is the total time since the first work on porting OOo to the Mac began. NeoOffice/J has really only been in development for two years, primarily by one developer in his spare time....

  69. Re:Why I'm Sticking With "vi" (plus, Services Menu by AndrewJ-NYC · · Score: 1

    Thanks for the info on WordService, of which I was entirely ignorant. I'll give it a whirl with Pages. I made my post from the POV of a fairly recent Windows-->OS X switcher who hasn't used Macs much since the System 9 days. While I'm obviously fairly computer-savvy (otherwise, I wouldn't be reading /.), I'm not a technical writer, but rather a pop culture journalist, and most of the people in my field are probably only going to use mass-market ultra-user friendly word processors (for compatability's sake, if nothing else), and while the other progams' ability to save as Word files makes them viable alteratives, it really all comes down to the features set. I'll definitely give WordService a try. If I can get the functionality I need from Pages, I'd be happy to make it my primary word processor.

  70. Re:They recommend MS Office :) by Mechcozmo · · Score: 2, Informative

    Office for the Mac isn't perfect, but it is far nicer than the Windows version. I don't have any real complaints about Office aside from the bloat, which if reduced, would be nice. But otherwise... it beats the Windows version by far. Waaayyy far.

  71. Neo... hmmm... by __aaclcg7560 · · Score: 0, Offtopic

    Does NeoOffice come with a Matrix screen saver? Or maybe NeoOffice isn't the One after all?

  72. Re:They recommend MS Office :) by ThomaMelas · · Score: 1

    I've only got to play with my wife's powerbook a little bit, but wouldn't that be the standard installer?

  73. get this morning's patch too by grikdog · · Score: 1

    http://www.planamesa.com/neojava/downloads/patches /NeoOfficeJ-1.1-Patch-0.dmg I'll give 'em credit for getting patches out fast, but the nearly flawless 1.1 RC Patch 6 was out for quite a while, so it would have been nice if Preferences... [splat-comma] worked out of the box.

    --
    ``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
  74. Irony is a Wonderful Thing (Sometimes) by bill_911 · · Score: 1

    OOo and NeoJ does have a simple way to dynamically display word count in any document.

    1/ Place the cursor in your document where you'd like the word count to appear ( I use the header).

    2/ Drag down at the NeoJ Insert menu label in the OS X menu bar.

    3/ You want

    Insert/Fields/Document/Statistics/Words

    While this may seem like a lot of work (ha ha) if you can put this field in your professional-writer templates.

    Also, there is a OOo macro out there that supposedly gives a more accurate word count. However installing a OOo macro is an enormous task (ha ha again).

    The parent post serves to point out there are many free OOo mannuals, tutorials and user forums available.

    For what it's worth, I get paid to write and everything I've written for the past 18 months came from NeoJ.

    When I write for fun (non-fiction) I use CopyWrite because of its organization tools and full-screen (no distraction) mode. I still use NeoJ for the editing and printing though.

  75. Swing and AWT, not Java by Craig+Ringer · · Score: 2, Informative

    The real issue isn't Java - it's javax.swing, the Java Swing toolkit, and the java.awt, the Abstract Window Toolkit . AWT looks awful, has a clumsy event model, and is low level and clunky. Swing provides higher level widgets, but an over-complex API, and it's still slow as hell.

    Ever tried SWT from Eclipse? It's the Java widget toolkit that doesn't suck! (as much).

    That said, I'm very happy with C++ and Qt. Well, except the C++ bit, but I find Java just as gag-worthy in different ways (Java 1.5 goes some way to rectifying the issues with generics and the collections framework, though. It's still WAY too verbose and static for a truly nice language, though).

    1. Re:Swing and AWT, not Java by alienw · · Score: 1

      Bah. Qt is complete, utter crap. Talk about an over-complex API -- you can't even figure out what the hell it's doing most of the time because Qt doesn't use C++ but has it's own little language extension, with it's own set of compilers, no less. If I wanted to deal with any more nightmare that is C++ I would at least use GTKmm (which has a shitty API and is poorly documented but is at least written in C++ and doesn't use 10 million macros and a meta-compiler). With that said, I'll stick to Java. At least you don't have to consult a textbook to look up some mind-numbingly complicated expression every time you need an iterator. Not to mention dealing with all the joys of allocating memory and dealing with memory leaks. And being able to run your app on just about any platform without worrying about dependencies and other random user-unfriendly crap.

    2. Re:Swing and AWT, not Java by Craig+Ringer · · Score: 1

      Aaah, Qt iterators. *sobs*. Yes, Qt definitely has some problems.

      When it comes to the macros, moc, and signals/slots though ... I'm really not convinced it's a big deal. While it is conceptually ugly, it works around the miserable limitations of C++'s reflection/introspection and its ultra-basic RTTI scheme. And, in practice, it works well and without fuss. I value things that work well and stay out of my way to let me get the real work done.

      If C++ had decent reflection and introspection (and a couple of other things) I'd agree with you that Qt should stick to being just a toolkit - not a general programming library and set of language extensions. Unfortunately, it doesn't, and Qt for me provides a way to use C++ while retaining my sanity. Just. If I didn't use Qt, I'd probably end up using similar ugly hacks with a meta-compiler, macros, or an IDL compiler to get the facilities I need, and *that* would be ugly.

      As for memory management - yep, I agree it's mind numbingly stupid and frustrating. Why the C++ committe didn't mandate a basic garbage collection implementation as part of the std lib, and some decent introspection/reflection capabilities, is beyond me. They threw in the kitchen sink and most of the rest of the pluming system when they put in templates (you know you can write functional programs with templates that are executed by compiling the file, right?), so surely, say, a property system wouldn't have gone astray?

      I've looked at GTKmm - that's what Inkscape are using. Looks interesting, but as you say it's poorly documented and the API isn't what I'd call attractive. If I hadn't joined an existing project built on Qt, I'd probably have tried it out.

      What gets me about Java is that it's not enough better, for all the fuss it gets. What pisses me off the most is that it lacks a built-in property system so you STILL have to do the archaic old "lets write simple accessors for every attribute, just in case we later need to make them do more" crap. A good property system negates that need completely - you can simply create a property that looks like a value member, but runs the accessors when you get/set it. Still, at least it does provide some reflection and introspection facilities and some (marginally) better support for functor objects etc so you don't have to use hacks like Qt's moc.

      There's also the matter of dependencies. I couldn't use Java without dependencies with any of the programs I currently work on. Not without re-implementing a number of the libraries I use. What's worse, I'd have to create and maintain Java bindings for them. LittleCMS is but one example. It's not Java's fault, but it still sucks :S

    3. Re:Swing and AWT, not Java by Craig+Ringer · · Score: 1

      That makes me sound like I don't use Java because it's "not enough better."

      I don't use Java because I can't use the libraries I need without (AFAIK) doing lots more work than I have to under C++, and because I really don't like Swing. At all. Anyway, I'm mostly working on existing projects where the language and toolkit choice isn't exactly mine to begin with.

  76. Well, given the options by Craig+Ringer · · Score: 1

    It seems to be a choice between dirty swamp water (Java), somewhat cleaner but might be radioactive swamp water (C#), and swamp water with sewerage in it (C++).

    I can't wait until PyQt4 comes out - GPL for Windows, Mac OS X, and UNIX/Linux. Python has its own faults, and PyQt more, but ... it sucks much less than the others for many tasks.

    1. Re:Well, given the options by killjoe · · Score: 1

      Python is a great language (and so is ruby while I am at it) but it seems to me if you are coding open source applications you might be better off with a stictly typed language based on contracts like smart eiffel. It seems like the safest way to ensure the new programmers can jump in to a project with some certainty of confidence that any boneheaded mistakes they might make will be caught by the compiler.

      Java is strictly typed too but it's not really free and there are restrictions on the distribution of the runtime. Eiffel also compiles to the JVM if you really want to go that way.

      --
      evil is as evil does
    2. Re:Well, given the options by Craig+Ringer · · Score: 1

      OK, small issue: Python is strongly typed too (rather more so than, say, the fairly weakly-typed language C). It's just not /statically/ typed.

      Anyway ... I personally share your desire for better static checking. I'd rather the compiler *didn't* do it though, and got on with the job of compiling. In my view static checking is the job of an additional tool (though it might use parts of the compiler to help it along, and the compiler might have a convenience "run a static check too" option) dedicated to the job.

      I wish Python had more facilites for /optional/ static typing where appropriate, and better support for things like before/after contracts. Assertions just don't cut it.

      That said ... I'm not too sure about Eiffel. It sounds like it goes a bit far in the other direction.

      Right now, my dream language would be Python with a *good* standard GUI toolkit (Tkinter doesn't count), selective static typing - perhaps by interface/protocol not just class - and the ability to transparently run Haskell procedures. That would be awesome.

    3. Re:Well, given the options by killjoe · · Score: 1

      Wow, you don't ask for much do you?

      Anyway Guido has blogged about the typing issue and basically he seems against it. He apparently feels that it will become so widely used that it will change python. Now that PHP people have implemented a similar thing perhaps Guido will change his mind.

      --
      evil is as evil does
    4. Re:Well, given the options by Craig+Ringer · · Score: 1

      Well, I did say "dream language" ;-)

      I did read Guido's comments on typing. I can see his concerns (especially when it comes to programmers from C/C++/Java backgrounds who're moving to Python), but I'm not sure it's a good reason to completely exclude the facility.

      I know you can do a lot of this with decorators now - but I also know they're sufficiently convoluted to make any sane developer want to cry and wish to go back to their nice, simple C++ templates ;-)

  77. That's just not true by Craig+Ringer · · Score: 1

    Sure, Swing is slow as molasses, but the Java language isn't. Using SWT, or the Java cocoa bindings, it'd be much less crap. You lose your GUI portability, but then you'll have to customise your GUI heavily for each platform anyway.

    I'll still stick with C++ and Qt, especially with Qt4 GPL for Windows.

    1. Re:That's just not true by m50d · · Score: 1

      You're right, of course. If there was just another implementation of swing that would probably be enough. But in order for there to be any advantage to using java, it would have to be swing, and it would have to be sun swing, so it would be incredibly slow

      --
      I am trolling
  78. Re:Just when they get it finished.... by AYeomans · · Score: 1

    Just 12 hours after I downloaded the RC version, out this comes! That's life.

    --
    Andrew Yeomans
  79. Not much by Craig+Ringer · · Score: 1

    OpenOffice.org was ported quickly to Mac OS X. Mac users went "eew, X11" and turned up their noses - and rightly so, the X11 integration on Mac OS X is shit. I should know. Scribus, an app I contribute to, has been working on Mac OS X for ages - it's a C++ app, yet all it took was a recompile and a few endianness fixes. That, however, doesn't cut it - you get nowhere unless it's been ported to all Apple's special platform specific APIs for doing everything, none of which can be neatly integrated into an X11 app - you have to move across to Aqua first. Qt made that fairly easy, but there's still all this f**ing integration work left.

    <rant>
    Apple could've made this much easier by making their X11 integration NOT SUCK and giving X11 developers some easy to use libraries for simple access to the Mac menu bar, dock, VFS, etc. They evidently felt tying developers to Mac OS X's APIs was more important.
    </rant>

    Anyway... OpenOffice's platform API abstraction didn't fit well with the "Mac way" of doing things, so they had to do some fairly major work to make it all work right. The best way ended up being the Java cocoa bindings. Note that the Java here is not portable, it relies on the Cocoa bindings for Java that only work on Mac OS X.

    Blame Mac OS X. Java deserves only some of the credit here, and I suspect many of the issues would've remained if OO.o was written in Java.

    1. Re:Not much by Brandybuck · · Score: 1

      Ditto on Qt. I too have ported an application over to OSX using their native Aqua Qt. It gets you 95% of the way there. But that last 5% of integration seems to be the only thing some users care about. Most Mac users are quite willing to accept ported software that isn't 100% perfect. But there's a few that get genuinely offended if the software isn't the poster boy for the Apple Interface Guidelines.

      --
      Don't blame me, I didn't vote for either of them!
  80. Re: humor? by Anonymous Coward · · Score: 0

    That was a pretty pathetic attempt at humor. Don't quit your day job.

  81. Re:They Just Don't Get It: Why I'm Sticking With W by Anonymous Coward · · Score: 0

    "Word is the only real option for anyone who earns his or her living as a writer."

    I've made my living as a (technical) writer for the past 25 years.

    Never had to use Word; most of my work for the past 15+ years has been with FrameMaker. Word won't do, or won't easily do, things that I have to do on a daily basis developing collections of books.

    LaTeX and other tools would work, too. Good thing, I'd hate to have to be stuck with Word.

  82. Re:get this morning's patch too by Anonymous Coward · · Score: 0

    Well, you can always go under Tools and choose "Options". It's the same thing. The Preferences menu choice was just a shortcut :)

    Ah well, nothing is perfect.

  83. There's a patch out already... by VValdo · · Score: 1

    Seems the "NeoOffice/J"->"Preferences..." menu option got disconnected in the final build.

    You can use "Tools"->"Options" if you want; it's the same thing. Or get this patch.

    W

    --
    -------------------
    This is my SIG. There are many like it, but this one is mine.
  84. Objective C is a strict superset of C; C++ is not by Apogaion · · Score: 1
    Just as with C++, regular C code can be used in an Objective C program, but still be treated the same, so you can us[e] C with Cocoa.

    To be more precise, Objective C is a strict superset of C, while C++ is not. This means that C code can be included anywhere in an Objective C project, but to use pure C in a C++ project you have to do some minor massaging. For example, in C++ you need to modify your C h-files with

    #ifdef __cplusplus
    extern "C" {
    #endif
    ...
    #ifdef __cplusplus
    }
    #endif

    See the Wikipedia for more information.

    --
    This account verified sig-free since..., uh, never mind.
  85. That's nice, but... by they_call_me_quag · · Score: 2, Insightful
    A "native Aqua menu bar" is ridiculous. Look at this Java-based abomination... the rest of the interface is lifted straight out of Windows 98. The open and save dialog boxes are totaly non-standard. This application does not support any native Mac OS X technology such as Applescript, Quartz, native UI controls (except, the menubar).

    Yuck. Who wants to see that on their Mac every day?

    And, what ever happened to the fully native Aqua interface that Sun promised for Open Office three full years ago:

    "I think you can see Open Office running solid on OS X by the end of this calendar year," said Tony Siress, Sun's senior director of desktop marketing solutions. ... The current release of Open Office for Mac OS X requires x11," Siress said. "I've got my Hamburg (Germany) team working on eliminating that requirement right now and using Java. Full text
    So, let's recap. In 2002 Sun promises to fully support the Aqua interface using Java. Like so many other Java on the desktop promises from Sun, they never make good on this promise. Has anyone ever held Sun's feet to the fire on this and the hundreds of other Java promises they've made in the past 10 years?

    Three years after Sun promises Mac OS X support another team of developers finally ship something for Mac OS X that has no Aqua interface at all... except for the MENUBAR.

    My analysis of this sad state of affairs is Java has failed on the desktop.

  86. Re:They recommend MS Office :) by Arker · · Score: 1

    Well I got the page with installation instructions to open. It's not as bad as the slashdot blurb made it sound. It's not a standard .app folder, but it's not an MS style installer either. Sounds like it's a .pkg, that's a file for the Macs built-in package management tool, similar to an .deb or an .rpm. A reasonable way to go about it - is still considered better to do a proper .app but if for some reason it's absolutely essential that the install spread files around the filesystem this is the way to do it - registers them all in the database for a clean uninstall. That's the way *nix programs for the mac are usually packaged... so nice. One of these days I'll actually get the whole package downloaded, and then we'll see how it runs. ;)

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  87. Re:get this morning's patch too by grikdog · · Score: 1

    Was it? Was it really? It was so damn convenient I mistook it for a feature. Sorry 'bout dat!

    --
    ``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
  88. Re:They recommend MS Office :) by Uncle+Asad · · Score: 1

    The final app is a standard .app package, but because of OpenOffice.org's Unix/Windows roots and build system, Neo/J can't just be dragged from the .dmg. That's why there's an Apple Installer .pkg. (OpenOffice.org for Mac (X11) does not use a standard Mac installer and many people do not like that installer.)

  89. Re:They recommend MS Office :) by bnenning · · Score: 1

    Sounds like it's a .pkg, that's a file for the Macs built-in package management tool, similar to an .deb or an .rpm. A reasonable way to go about it - is still considered better to do a proper .app but if for some reason it's absolutely essential that the install spread files around the filesystem this is the way to do it

    Yeah, although the silly thing is that the NeoOffice application *is* a single .app wrapper. There's no reason for it to be using an installer.

    registers them all in the database for a clean uninstall.

    Actually there's no built-in facility in OS X to do uninstalls. There should be, but it wouldn't be much of an issue if more developers would follow Apple's advice and use .app wrappers, which is almost always possible. (Apple itself is one of the largest offenders in this area).

    One of these days I'll actually get the whole package downloaded, and then we'll see how it runs. ;)

    Pretty well so far, based on playing with it for 15 minutes. It's handled several complex Word and Excel files with no problems except for macros.

    --
    How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
  90. Re:They Just Don't Get It: Why I'm Sticking With W by Anonymous Coward · · Score: 1, Informative

    Highlight section
    Command-C to copy
    Open terminal
    pbpaste|wc -w

  91. Re:/.ed already by Anonymous Coward · · Score: 0

    > it lasted a lot longer than 30 seconds.

    you're right. but no more than three minutes. (say timothy posted at 6:17:00 and udderly posted at 6:19:59.)

    > Posted by timothy on Wed 22 Jun 06:17AM

    > by udderly (890305) Alter Relationship on Wed 22 Jun 06:19AM (#12879788)

  92. Re:They recommend MS Office :) by lunadog · · Score: 1

    Yes I am not sure about MS office X being "absolutely perfect".

    Just got hit by a nasty bug today that made me lose 1 hours worth of work.. Try it:

    Open excel

    type the formula

    =average(

    in a cell, then hold down apple key (whatever it's called!) and click on three separate cells (not sure if they have to contain data). When you click the third, the program magically disappears along with your data, only to be replaced by a sarcastic message about reporting th bug to people who don't bother to fix bugs (okay the last bit didn't happen, but you get the idea!)

    Anyway, if anyone knows of a patch to fix this, I would be very grateful. In the meantime I think I will stick with openoffice.org

  93. Re:They recommend MS Office :) by lunadog · · Score: 1

    You aren't the only one with problems running msoffice X on the Mac.

    I was also beset by nasty crashes until I installed the MS "security"?? patch for msoffice X. Even now it still crashes sometimes (see my other post to this parent). This is on a G4 Powerbook with (now) 512MB RAM, so I don't think it is too underpowered.

    Secondly, although it isn't really a bug, I hate the way that I can slide windows under the menubars so that I can no longer click the top of the window to move it. To fix this problem I have had to change my menubars to mac-like floating boxes to the side of my workspace. Well I suppose I am using a Mac ! ;P

  94. Re:They recommend MS Office :) by Arker · · Score: 2, Interesting

    Actually there's no built-in facility in OS X to do uninstalls.

    True, it doesn't ship with the OS, but OSXPM is an easy add-on and does the job fine.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  95. Re:They recommend MS Office :) by k96822 · · Score: 1

    Well, Chevy makes better cars than Ford, IMHO, but they both suck compared to a Toyota. :-) I don't think Mac Office is Cadillac:Geo level, though; Mac Office is still one of the slowest and clunkiest Macintosh applications you pay money for (Of course, IMHO). I cannot -- will not -- put such filth on my Mac.

    On a related topic, AppleWorks 6.5 is an 8 year Yugo that has never had an oil change. Total sh*t. OpenOffice is the best thing going for Mac right now, even if the interface is X-Windows style -- but, I'll try NeoOffice now and see if it is more consistent with the rest of the system. I'd sacrifice a bit of speed for usability. I think some parts of OO are very oddly designed.

  96. AppleWorks by line.at.infinity · · Score: 2, Insightful

    I prefer AppleWorks for my office suite, which comes free with new Macs .. yes, it's an outdated office suite, but it works, it's more responsive and loads much faster than NeoOffice/J.

    iWork is $79, Mac MS Office is $399. If one was choosing between these two, I would recommend the iWork not just because of pricing but because of the vendor: Apple is more likely to care about their own users while MS has potential to drop their product quality because Mac users aren't as important to MS than they are to Apple. Microsoft has already started to pull away from Microsoft Windows Media Player for OS X (currently lacks AVI, MPEG, MP3 support, playlist, drag-n-drop support, displayal of filename during playback, doesn't stop screensavers from running during video playback, etc.). MS has also announced that they've stopped development for Internet Explorer for Mac. The few people that still use IE for Mac probably do so because they've grown accustomed to it from the times before Mozilla + Safari, or because of the Microsoft brand name. I think people need to stop thinking that the Microsoft brand is the best choice, especially on the Mac platform which competes with Windows for marketshare.

    1. Re:AppleWorks by unclethursday · · Score: 1
      I also prefer AppleWorks... however, my AppleWorks decided to stop working, completely. Trashed the preferences and everything, still won't boot up. I just get the spinning beach ball of death and have to force quit the app.

      A lot of people say this happened to them when they went to 10.3.9, but this happened to me the night before I went to 10.3.9.

  97. Abiword by Hal+XP · · Score: 1
    Abiword is a much lighter program for MacOSX. Of course it's just a word processor. But I've never yet met a person who has any real need for a spreasheet which couldn't be filled in with Abiword's table feature.

    But if you're looking for the kitchen sink, some people have apparently ported various Gnome office apps into an integrated bundle. The company behind the offering appears to have turned the traditional definition of free on its head. The software is free in the GNU sense, but you're charged $30 for a download of the (pre-built) binaries. I still need to check the site if there are patches available for free download, or if the company simply used some exotic compiler that would make it extremely difficult (or expensive) to (legally) roll out your own executables.

    --
    I'm a sci-fi vegan: I don't want the aliens to think we have as much right to live as the fried chickens we eat.
    1. Re: Abiword by Uncle+Asad · · Score: 1

      OpenOSX has a mixed reputation. There are a couple of other developers out there who have stories to tell, but the only one I could find quickly was Fink.

  98. Re:Patent claims by DickBreath · · Score: 1

    Microsoft has stated that these patents will be avilable on a "royalty free and otherwise reasonable and non-discriminatory basis", but short of an irrevocable legally-binding release worded in such a way that it's unambiguously clear these patents can not be used against open-source software, I am unwilling to trust to their good will.

    Microsoft has no good will to trust.

    If you can point to an actual statement that the patents would be available on a royalty free basis, then there is something called estopel. You can't sue someone for doing something that you publicly promised that they could do.


    Did you notice that Mono is primarily an implementation of .NET, and thus subject to patent claims by Microsoft?

    Did you notice that just about any software whatsoever, including Free software, is subject to patent claims by Microsoft, IBM, Novell, Lucent, GE, etc., etc. ?

    Specifically, did you notice that Linux very well may be subject to patent claims by Microsoft?

    Generalizing...

    Did you notice that X very well may be subject to patent claims by Y.

    Where X could be any of Linux, OpenOffice.org, Mozilla, KDE, GNOME, ReiserFS, Ext3, Bash, and a long, looooong list of others.

    Where Y could be any of Microsoft, and a long list of others.

    If you use any of X without an iron clad legally binding agreement from any of Y, then it would seem that you are hypocritical? (i.e. if you use Linux without an binding no-patent-attack statement from Microsoft)



    Who is going to start the patent nuclear war?

    Novell has promised to use their patent portfolio to defend against patent claims made against their products.

    IBM has not made a similar promise, but they still might act if an important enough high profile open-source project were attacked. Nothing would stop IBM from arbitrarily, suddenly, asserting one of their patents against some random party, that just happened to recently have attacked an open source project.


    With Mono you can hitch your wagon to Microsoft's oxen, never knowing just where they're going to go.

    I disagree.

    Mono runs on Windows as well as other platforms. No matter what directions .NET goes in, if you hitch your wagon to Mono, you go where Mono goes, not where .NET goes.

    With Mono, I could, for example, use GTK#, but not with .NET.

    --

    I'll see your senator, and I'll raise you two judges.
  99. Re:Patent claims by HiThere · · Score: 1

    You trust MS wrt NET far more than I do.

    FWIW, there was a lower level (I think) MS manager who commented WRT NET: "It's our intellectual property, and we intend to defend it." If this statement was ever clarified, I never heard it. I also never heard it denied. I don't remember who it was, and Google doesn't remember it either, but let's say I tend to be a bit skeptical about the openness of .NET...I may not know where the catch is, but this is coming from MS.

    "O oysters come and walk with us!"
    The walrus did beseach,
    "A plesant walk, a pleasant talk
    Along the briney beach.
    We cannot do with more than four
    to give a hand to each"

    Perhaps I'm feeling a bit oysterish, but I think I'll remember what happened at the end, and so:
    The eldest oyster looked at them,
    but never a word he said
    The eldest oyster winked his eye
    and shook his heavy head
    Meaning to say he did not choose
    to leave the oyster bed.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  100. Why is this marked interesting? by John+Nowak · · Score: 1

    This is just plain nonsense. There is no reason a program properly coded in ANSI C would be any more difficult to "port" than a Java app.

    1. Re:Why is this marked interesting? by FatherOfONe · · Score: 1

      Sorry, I jus finally saw your reply. To "port" Java code I generally just copy the JAR or WAR/EAR file over to the different platform.

      Now to move C code from a Linux box to a Windows box? Yes the developer can take that code in a compiler on Windows, but I am willing to bet that the they didn't limit their stuff to all STANDARD ANSI C stuff. The reality of it is that moving code written in C to a different platform is generally not a trivial task.

      --
      The more I learn about science, the more my faith in God increases.
  101. Re:Patent claims by argent · · Score: 1

    Microsoft has no good will to trust.

    No kidding.

    If you can point to an actual statement that the patents would be available on a royalty free basis, then there is something called estopel.

    Read the pages I linked to.

    Microsoft can say "these patents are available on a royalty free basis for any vendor that uses our libraries, we will license these libraries to anyone, at no cost (which is all 'royalty-free' means), to everyone under identical (thus non-discriminatory) terms, using the 'Happy Freeware' license", and then ship the libraries with a license that's incompatible with open source.

    They haven't lied. They've done what they said. But they've still got you by the short and curlies if you don't want to spend time in court or unless you don't want to ship source. AND they've tried to play basically this game with the EU. Several of us predicted this... and we got the same kind of reaction to that THEN as you're having to me NOW. THIS time we seem to have a European regulator who doesn't buy in to the idea that these are "reasonable terms", but you can't depend on that... they've gotten away with worse elsewhere.

    Did you notice that just about any software whatsoever, including Free software, is subject to patent claims

    Yes, but there's a big difference here. Here, we know ahead of time EXACTLY what the claims are, because those claims are on patents that are explicitly an essential part of what's being implemented. There's no "innocent infringement" here.

    Who is going to start the patent nuclear war?

    There doesn't need to be a "nuclear war". A patent "cold war" will serve Microsoft just as well: they have effectively fought a clandestine war on many fronts for decades, from "DOS isn't done until Lotus won't run" through the very effective file format battles that lead to Office's dominance on the desktop, and facing down the Department of Justice over IE. Patents are just another tool for them.

    Microsoft is already demanding royalties and receiving payments for embedded use of the FAT file system. They're establishing a strong presence in a relatively inconspicuous corner of the market for their patent portfolio. They have strongarmed free software they didn't approve of, like ntcrashme, out of the limelight... and hardly made a ripple. Thinking they won't continue to expand this precedent is trusting to their good will.

    With Mono, I could, for example, use GTK#, but not with .NET.

    Whatever direction .NET goes, Mono will follow, unless the Mono group are willing to abandon compatibility with Windows... something I find about as likely as Samba abandoning compatibility with Windows.

  102. OT Clarification of byte-order by kulpinator · · Score: 1

    Nitpick: All architectures I know of have the same bit order (please correct me if necessary). What you mean, I think, is little-endian versus big-endian (see http://www.cs.umass.edu/~verts/cs32/endian.html ), which is actually *byte* order.

    Sorry, sorry, I'm leaving now ...

    --
    Karma: Positive (mostly due to rash moderations)
  103. Re:They recommend MS Office :) by tverbeek · · Score: 1

    I've been running the Betas and Release Candidates of NeoOffice on my G3 iBook, and they run as well as any other substantial apps do. That is, I'm not about to start gushing about how Neo screams on a G3 (because it doesn't), but its not as if Photoshop does, either.

    --
    http://alternatives.rzero.com/
  104. Nissus Writer has excellent word count... by Anonymous Coward · · Score: 0

    Nissus Writer handles word count well. I don't use it however -- I use OO.o and LaTeX.

  105. Thanks you! by Grimster · · Score: 1

    Downloaded this and installed it on the wife's Mac-mini already and finally she can open those old Openoffice and MS Word docs she's got. She's been on me for weeks to get that working for her.

    It seems to be a bit slow to load but once it's up it seems to work OK, as long as she can open her old docs and read them all is good!

    --
    --- www.f-theocean.com
  106. Re:They Just Don't Get It: Why I'm Sticking With W by yoxi · · Score: 1

    Okay, Neo/J's functionality is restricted to OpenOffice.org's functionality, and one thing that is missing built-in is a good word counter. But as another poster pointed out, there is a great 3rd-party macro available http://sourceforge.net/project/showfiles.php?group _id=87718&package_id=98079here - which you only have to click on a button in the doc to install - just assign the Wordcount macro to cmd-K and it'll display word/letter/para count for the whole doc, plus word/letter count for selected text (plus the former less the latter for good measure).

  107. Re:They recommend MS Office :) by Anonymous Coward · · Score: 0

    Yeah, although the silly thing is that the NeoOffice application *is* a single .app wrapper. There's no reason for it to be using an installer.

    Actually, there is. Apparently OO (by design) will alter some of the installed files (example document templates, etc.) in its app wrapper if given write access to them, which interferes with patches and is considered bad practice by the authors of NeoOffice/J. Normally this behavior doesn't cause problems, because in cases such as Linux RPMs or .debs the files are all installed read-only, or at least read-only by anybody other than root.

    However, Finder copy installs will leave the files writeable by whichever user initiated the install. Since it is very common for users to have only one account, which is an admin account, this means that drag-installing NeoOffice/J would expose this problem for a large number of users. So they chose to use a .pkg install process in order to get control over the ownership and permissions of installed files.

  108. Re:They Just Don't Get It: Why I'm Sticking With W by vonFinkelstien · · Score: 1

    After install Word Services, you can count the words in highlighted text in any program with services (e.g., Safari). Just click on the name of the application, slide down to Services and select Statistics.

  109. i dont get you people by Trendkill · · Score: 1

    you all praise open source, which is a good thing, but you b!tch about the icons. the source code is there. if you DONT like the icons, make news ones and publish them, heck they might even add it to the next release if you submit it to them what im trying to say is, why complain about an open source product when you can get in there and change it yourself.