Java/Cocoa vs Java/ObjC/Cocoa vs Java/Swing
Java/Cocoa vs Java/ObjC/Cocoa vs Java/Swing
- Subject: Java/Cocoa vs Java/ObjC/Cocoa vs Java/Swing
- From: James Eitzmann <email@hidden>
- Date: Fri, 7 Feb 2003 08:43:36 -0800 (PST)
I am currently evaluating the options for building a
client appication that must use java for
sending/receiving data through a java api. Therefore a
pure objective-C application is out. The client
application is being built for OS X exclusively so
cross-platform support is not a concern. Given those
requirements, I see 3 viable options for building the
UI: Java/Swing, Java/Cocoa, or Objective C/Cocoa as
View and Controller and Java as Model using the MVC
design pattern.
I do not want to limit the application's UI so I am
assuming Java/Swing is out. My assumption is that
there is no way to implement some Cocoa features like
window drawers.
I have seen quite a few people discouraging Java/Cocoa
and have seen no ringing endorsements of it. The
reasons seem to be a lack of documentation and
concerns of performance. Does anyone think the
performance of a Java/Cocoa UI would be worse than
Java/Swing? Are there other issues with Java/Cocoa UI
development?
Given that the application must use Java, does it make
more sense to build the UI using the Java Cocoa API or
to build the UI using Objective C and use the
java/objC bridge to tranfer the data for the UI
between the UI and the Model/backend layer that
manages the data in Java?
Any feedback would be appreciated.
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.