Re: Java/Cocoa vs Java/ObjC/Cocoa vs Java/Swing
Re: Java/Cocoa vs Java/ObjC/Cocoa vs Java/Swing
- Subject: Re: Java/Cocoa vs Java/ObjC/Cocoa vs Java/Swing
- From: Eric Czarny <email@hidden>
- Date: Fri, 7 Feb 2003 19:00:49 -0500
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?
I was in a very similar situation you are in regards to using Java for
use of a specific API. I needed to utilize the Apache XML-RPC API since
I wasn't able to find a decent enough one written in Objective-C. So, I
figured I would utilize the Java Bridge and write the necessary code in
Java and write the GUI and Controller components in Objective-C.
After spending a few hours of research I quickly found that using Java
in this manner would have numerous issues in regards to performance and
memory efficiency. If you must use Java your best path to take would
just be using swing. Even though it's not nearly as wonderful as Cocoa,
it will make your application load faster and use less system
resources. I'm not particularly sure what API you intend on using, but
I suggest spending some time looking for a similar API written in
Objective-C.
However, if you end up using Java and Cocoa I suggest writing the Cocoa
counterparts in Objective-C and bridging your Java classes. It won't
nearly be as fast as pure Objective-C, but it will be much better than
Java/Cocoa.
Best Regards,
Eric Czarny
http://www.laterus.net
_______________________________________________
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.