Re: Cocoa Java vs Swing Java classes
Re: Cocoa Java vs Swing Java classes
- Subject: Re: Cocoa Java vs Swing Java classes
- From: David Findley <email@hidden>
- Date: Sun, 14 Oct 2001 10:12:10 -0500
Not that I've found. I've found bits and pieces of sample code, of
course, here and there; but no comprehensive library. If you look at
Sun's site, you'll think Swing is the end-all and be-all of application
interface development. I don't wish to denigrate the work that they've
done, as it is remarkably cross platform if you treat it right, and they
are allowing me to code using Mac tools for a primarily Windows target,
but I guess I'm just spoiled after working with Cocoa.
I think it boils down to the fact that as a Mac user and developer I
have higher expectations of how an application is supposed to behave,
not just look. I've don't believe that philosophy drives development on
any other platform than the Mac. If it had, I think Apple wouldn't have
needed to expose the Cocoa Appkit to Java on the Mac in the first
place... we could just use Swing.
David Findley
On Sunday, October 14, 2001, at 09:21 AM, Andreas Monitzer wrote:
On Sunday, October 14, 2001, at 04:06 , David Findley wrote:
True, an application written with Swing looks a lot like a Cocoa
application (when run on the Mac), but with Swing you have to write a
_lot_ more code to get it to act the same.
Anyway, you'll notice that there's no Cut, Copy or Paste, or Undo, or
Redo, or Save (yet). This is because Swing is an "appearance" layer,
not a "behavior" layer, and does not provide a foundation for those
items. There's no "appkit" in Swing. You really are on your own
there. The menus don't enable properly yet (for the most part).
Hey, that reminds me of Classic Mac OS/Carbon, it's exactly the same
there.
Luckily, there are frameworks like Powerplant that give you that
functionality. Nothing like that for Java/Swing?
andy
--
God created the universe in 6 days because He didn't have to worry
about an installed base.