David,
Come to think of it, maybe it's just the Xcode Project templates that
will no exist in future versions of Xcode. Maybe the underlying
technologies will still work, but they are not being actively
developed. Which, I guess, is no huge deal since they haven't been
enhanced in years anyway. This means that you will no longer be able
to select "New Project" from the menu in Xcode and ask for a Java
Client application of any type.
But, I am quite sure that new versions of Interface Builder will have
no facility to build user interfaces for Java Client. That facility
relies heavily on the Java-Cocoa bridge. So you'll be stuck with the
XML custom interfaces, which may be fine in some cases, but I know I
never enjoyed working with them.
We are actually using several Non-direct Java Client applications
using IB. We are in the process of migrating these applications to
other alternatives.
Like I said before, I may have my wires crossed on some of this, but
I know I'm not counting on Java Client being available in the future
at all.
On May 9, 2007, at 9:36 AM, David Avendasora wrote:
I can't find anywhere where anything talks about Direct-To or Non-
Direct Java Client being depreciated. But I can't find anything
that says otherwise either.
I don't believe that the Java-Cocoa bridge (which, if I understand
correctly, is what was depreciated and therefore all of the Apple
WO Dev tools that used it were too) is in anyway involved in WO
Java Client (Direct or otherwise) development or deployment.
Out-of-the-box D2JC apps Xcode builds are using a Swing interface,
not a Cocoa one that makes calls to underlying Java code. I am
somewhat unclear on the use of Interface Bulder for Non-Direct Java
Client as this page: http://developer.apple.com/documentation/
WebObjects/DesktopApplications/index.html#//apple_ref/doc/uid/
TP30001017 states that the nib files are translated directly to
Swing by WO. So it sounds to me like WO parses the nib file and
determines how to build the Swing interface. Since you aren't
building a Cocoa UI, I don't think the bridge is involved. But you
aren't dependent upon using IB to build your client interface
anyway. It's just the Apple way of doing it.
But, with all that said, note I said "quickly mock-up and
prototype". D2JC is a great tool to make sure my model is valid and
that the entities and relationships, delete-rules, and optionality
I thought were proper on paper, actually work in practice. If they
don't work (generate exceptions or are just "clunky"), I can make a
change to the EOModel, rebuild and have a new app based on the new
structure _literally_ within seconds without writing/rewriting/
refactoring ANY code. The only thing better than Eclipse's
refactoring tools, is not needing to refactor at all. Once I have
tested and proved the model, it makes web development so much
easier because I can simply concentrate on the logic and the UI.
I think that even if D2JC is dead from the perspective of making
deployable applications, it is an incredibly powerful prototyping/
proof-of-concept tool that will keep me using Xcode for the initial
stages of a project, until at least I can create a new D2JC project
in WOLips, point it at a EOModel and click build-and-go.
I just wish it weren't dead. (I know, wish in one hand...)
Dave
On May 8, 2007, at 8:14 PM, Robert Walker wrote:
David,
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).
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.
On May 8, 2007, at 12:42 PM, David Avendasora wrote:
The whole point of _my_ use of Xcode and especially D2JC is that
it is nearly zero work to quickly mock-up and prototype object
model and have it as a running application (D2JC) in a mater of
seconds with no configuration of the development environment. It
either Just Works™ or I have a problem in my model somewhere. I
don't ever have to question if the problem is somewhere in the
configuration of the IDE or the numerous third-party plugins.
To me the reason WO-newbies would shy-away from WOLips is that
they are already trying to learn WO and Xcode does an excellent
job of just getting out of the way and letting you get an initial
project up and running quickly. With WOLips, you likely have to
learn not only WO, but you have to learn Eclipse's interface and
jump through all sorts of hoops like figuring out how to download
and install plugins and such before you can even start a project,
and I don't think anyone can say that the Eclipse UI is not
intimidating when you first get started. Xcode is not
intimidating, it holds your hand and asks you some questions and
gives you a running WO Application.
There is a much higher barrier to entry with WOLips (to my
perception) even if in the long run it is a far superior set of
tools.
On May 8, 2007, at 1:33 AM, Simon McLean wrote:
but I can click a button and get either a Direct-To-Java-Client
app, or a running web-application that just works.
You can do this with Eclipse too. I can safely say I have never
tinkered with the build scripts in either XCode or Eclipse.
Simon
_______________________________________________
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/
robertwalker1%40mac.com
This email sent to [EMAIL PROTECTED]
--
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/webobjects%
40avendasora.com
This email sent to [EMAIL PROTECTED]
--
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]
