• 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: user obstacles to WOLips adoption (was: Apple's Support of WebObjects)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: user obstacles to WOLips adoption (was: Apple's Support of WebObjects)


  • Subject: Re: user obstacles to WOLips adoption (was: Apple's Support of WebObjects)
  • From: Ashley Aitken <email@hidden>
  • Date: Thu, 10 May 2007 11:30:50 +0800


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!)



_______________________________________________
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


  • Follow-Ups:
    • Re: user obstacles to WOLips adoption (was: Apple's Support of WebObjects)
      • From: Robert Walker <email@hidden>
References: 
 >Apple's Support of WebObjects (From: Don Lindsay <email@hidden>)
 >Re: Apple's Support of WebObjects (From: Kieran Kelleher <email@hidden>)
 >Re: Apple's Support of WebObjects (From: Mike Schrag <email@hidden>)
 >Re: Apple's Support of WebObjects (From: Guido Neitzer <email@hidden>)
 >Re: Apple's Support of WebObjects (From: David Avendasora <email@hidden>)
 >Re: Apple's Support of WebObjects (From: Simon McLean <email@hidden>)
 >Re: user obstacles to WOLips adoption (was: Apple's Support of WebObjects) (From: David Avendasora <email@hidden>)
 >Re: user obstacles to WOLips adoption (was: Apple's Support of WebObjects) (From: Robert Walker <email@hidden>)

  • Prev by Date: Re: NSTimer replacement?
  • Next by Date: Re: Getting a project started right
  • Previous by thread: Re: Merits of D2JC (was: user obstacles to WOLips adoption (was: Apple's Support of WebObjects))
  • Next by thread: Re: user obstacles to WOLips adoption (was: Apple's Support of WebObjects)
  • Index(es):
    • Date
    • Thread