Ashley,
I hate to break it to you, but along with the deprecation of the
Xcode based tools, comes the deprecation of D2JC (and also non-
direct to Java Client as well).
Again as mentioned in some previous posts, this was pure conjecture.
It's really unclear whether or not this is true, and I don't believe
any public statement exists to clarify this. Maybe we'll know more
after WWDC this year. I'm not "in the know" on this issue. I
apologize for the poor wording in my original post.
InterfaceBuilder was never a good tool for building Java GUIs, and
it amazed me (in a weird way) that they could even, or would want
to, do it. There are plenty of other tools for building GUIs in
Java that would work with JavaClient.
Here I was referring to JavaClient as implemented in WO/EOF. That is
to say by distributing objects between the server and client though
the EO distribution channel, and using IB to create Swing interfaces
by translating Cocoa UI components. This includes the binding
technology used in IB to build these interfaces. This was, sort of,
a leftover from before WO was converted to Java. IB was the tool to
write client-side applications that were written in Obj-C using a
form of binding technology. The only way to make this work in Java
was to translate some portion of the Cocoa controls to Swing using
the Cocoa-Java bridge. I did not intend to refer to pure Java Swing
development.
On May 9, 2007, at 11:30 PM, Ashley Aitken wrote:
Hi All,
On 09/05/2007, at 9:14 AM, Robert Walker wrote:
At least that's my understanding. I could be wrong about that.
But, I'm pretty certain that being able to create Java Client
applications with custom interfaces using Interface Builder has no
future.
I believe David (correct me if I am wrong) was not referring to
using InterfaceBuilder but the ability for D2JC to automagically
build an entire Java thick client without any coding - this still
blows my mind!
InterfaceBuilder was never a good tool for building Java GUIs, and
it amazed me (in a weird way) that they could even, or would want
to, do it. There are plenty of other tools for building GUIs in
Java that would work with JavaClient.
I hate to break it to you, but along with the deprecation of the
Xcode based tools, comes the deprecation of D2JC (and also non-
direct to Java Client as well).
Now with regards to the underlying technologies, that may be true,
can someone confirm this? JavaClient and D2JC never really took
off, I believe, mostly because it was way ahead of its time (like
WO was too).
Just wait though, rich clients are the hot topic at the moment in
the Enterprise world, and soon they will realise its a bonus to be
able to do real client-side business processing (a la JavaClient).
It seems, Apple innovates and tries to lead developers who
(generally speaking) have a hard time keeping up. Whereas,
Microsoft only goes where it gets pulled by the market (although
things are changing with .Net).
Cheers,
Ashley.
--
Ashley Aitken
Perth, Western Australia
mrhatken at mac dot com
Skype Name: MrHatken (GMT + 8 Hours!)
--
Robert Walker
[EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
