Re: Java Client Desktop app WO 5.3 APIs
Re: Java Client Desktop app WO 5.3 APIs
- Subject: Re: Java Client Desktop app WO 5.3 APIs
- From: Ian Joyner <email@hidden>
- Date: Fri, 3 Feb 2006 09:50:51 +1100
Perhaps someone from Apple could clarify, but between Cocoa and WO,
you are talking two very different things (as I'm sure you
appreciate), so I don't think there is any reason to change how you
develop Java-client apps with IB (I have a large project in it).
The statement does say 'release to end users', which I interpret as
sell to customers (which is what we are doing), but your work sounds
internal.
However, there is another cause for concern in the Apple statement
which seems aggressive against third party languages – the blanket
you "must use Obj-C to develop Cocoa", which undermines efforts such
as http://www.maceiffel.com. Perhaps they should recommend not to use
Java, but not to go on and say must use Obj-C that's just not accurate.
Ian
On 03/02/2006, at 4:44 AM, Ken Tabb wrote:
Hi folks,
it's noddy question time and I may well be barking up the wrong
tree here but...
I'm about to embark upon some new Java Client Desktop WO 5.3 apps
(that also have a web interface for other aspects of the same app).
All the desktop apps will be run on macs (10.4 or later). While
neck high in the AppKit Obj-C Cocoa documentation the other day
(for another project) I accidentally ended up in the Java Cocoa
currency converter tutorial:
http://developer.apple.com/documentation/Cocoa/Conceptual/
JavaTutorial/index.html
Although I'd heard Apple had ceased adding features to Cocoa-Java,
I had not before heard them say "don't use Java for end user Cocoa
apps" (2nd para at above link):
To develop Cocoa applications that you intend to release to end
users, you must use Objective-C. No Java interfaces for new Cocoa
features will be added to Mac OS X versions after 10.4. Therefore,
features added to Cocoa in subsequent versions Mac OS X will not
be available to Cocoa applications developed using Java.
So my question is: does this change the way you build GUIs for Java
Client Desktop apps? In order to use IB to make the GUIs for my WO
Desktop apps, do I continue to use Cocoa/Java with it doing the
automatic Swing translation of supported Cocoa widgets, or do I use
Cocoa EOF (which seems to be stuck in a beta state and I'm not even
sure where to get hold of it, despite this link saying it comes
with 5.1):
http://developer.apple.com/softwarelicensing/agreements/cocoa.html
... or is there now a better way of developing Java Client Desktop
app GUIs than using IB?
And also, do I use Direct to Java (and then customise) or start
with non-direct?
I'm after the route that is most (officially) supported and has a
longer lifespan (eg. into future OS releases / WO releases).
Any advice gratefully received! Thanks in advance,
Ken
- - - - - - - - - -
Dr. Ken Tabb
Mac & UNIX Developer - Health & Human Sciences
Machine Vision & Neural Network researcher - School of Computer
Science
University of Hertfordshire, UK
http://www.health.herts.ac.uk/ken/
Certified non-Microsoft Solution Provider
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden