Article:		Macworld Wish List for Steve
Subject:		iOffice
Date:		2003-12-30 23:45:37
From:		kollivier
Response to: iOffice
The problem with OpenOffice, and actually the reason we have not seen a native Aqua port already, is that the GUI is emulated, not native. OOo's GUI toolkit is not really designed to give users the native look and feel that Mac users expect - it is designed to provide the same look and feel on every platform. (In fact, the OOo developers are currently trying to create Aqua-looking controls to emulate an Aqua interface, but whether or not the controls will ever behave 100% like native Mac controls is anyone's guess...) Apple would be better off writing the app from scratch using Cocoa instead of trying to massage OOo's VCL to work with Aqua. They could of course incorporate some of the particularly useful bits of code.

Showing messages 1 through 2 of 2.

• iOffice
  2003-12-31 01:41:50  anonymous2 [Reply | View]
  
  
  If cost is the larger issue, and speaking for myself, it usually is, what is the big deal about having the existing OpenOffice GUI less the native Aqua controls? Other than looks, is there that much difference to the average consumer in the bottom line usefulness of this program given its free price? Mabye it's a matter of education, and people understanding there is something for free, with a hidden cost, i.e. things don't look "pretty". OpenOffice may look a bit generic, but it's not that bad.
• iOffice
  2003-12-31 20:49:30  anonymous2 [Reply | View]
  
  
  The problem I see with Open Office for the Mac is its size, load time, and the fact that some of it's dialog boxes (such as save )don't always have the buttons labelled (intermittently). Also, on a single Mac with mutltiple user accounts it is necessary to configure .rc files for each account -- not something the average user will want to do.
  Also, last I checked the Aqua Dev track was essentially moribund with a target of 2006 (yes, six) for the first Aqua release.
  
  rjv