Okay, I have the same question as John and Flor, and I don't think
it's been answered yet. For those of you NOT doing regular Java
Client (I guess there a few ;) there have been THREE ways of doing WO
JC development in the past:
1) D2JC
2) NIB-Based using Interface Builder
3) Straight Swing (not using NIBs, rules files, or any other cool,
but depreciated tech)
1 and 2 have be obviously depreciated, even if they can be tricked
into working. That's not the question.
The question is, is #3 still a viable option? Saying either 1 or 2
still work with some hacking only confuses the question. Are the
libraries that maintains the editing contexts on the client side and
their communication back to the server-side UNdepreciated, or is it
included in the libraries depreciated as part of D2JC and Nib-Based JC?
Does anyone have a definitive answer to this? (please don't invoke
curses such as "AJAX" in your answer!)
Thanks!
Dave
On Oct 31, 2007, at 8:53 AM, Anjo Krank wrote:
All I'm saying is that you can get D2JC to still work by fixing up
the package to a plain WO app. However, my uneducated guess is that
there won't be much development going on with the Java client stuff.
Cheers, Anjo
Am 31.10.2007 um 13:38 schrieb John Pollard:
I am not quite clear on what you are saying. I am not concerned
about the Java interface for which we happen to use JFormDesigner
at present. I really want to know whether the EOF / distribution
jars are deprecated - the ones that let me write code on the
client side, almost as if I were coding on the server side. Here
is the list of jars that I currently load onto the client via jnlp:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40avendasora.com
