• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa Java vs Swing Java classes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa Java vs Swing Java classes


  • Subject: Re: Cocoa Java vs Swing Java classes
  • From: Andreas Monitzer <email@hidden>
  • Date: Sun, 14 Oct 2001 16:21:09 +0200

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.


  • Follow-Ups:
    • Re: Cocoa Java vs Swing Java classes
      • From: David Findley <email@hidden>
References: 
 >Re: Cocoa Java vs Swing Java classes (From: David Findley <email@hidden>)

  • Prev by Date: Re: Cocoa Java vs Swing Java classes
  • Next by Date: Re: Cocoa Java vs Swing Java classes
  • Previous by thread: Re: Cocoa Java vs Swing Java classes
  • Next by thread: Re: Cocoa Java vs Swing Java classes
  • Index(es):
    • Date
    • Thread