Re: JavaClient Common classes
Re: JavaClient Common classes
- Subject: Re: JavaClient Common classes
- From: Stamenkovic Florijan <email@hidden>
- Date: Wed, 25 Mar 2009 13:10:40 -0400
One more thing... As a further motivation for doing WOJC and Swing,
take a look at some screenshots of an app made in Swing:
http://explodingpixels.wordpress.com/2009/03/23/swing-can-be-oh-so-sweet/
There's cool stuff going on with Swing on OSX, and you can make close
to native-looking apps that are WOJC driven. A *very* powerful combo.
My best,
F
On Mar 25, 2009, at 13:07, Stamenkovic Florijan wrote:
Hey John,
On Mar 25, 2009, at 12:46, John Huss wrote:
This is mainly aimed at David, but anyone is welcome to share.
How are you using the common class functionality in WOLips? From
what I gather there is a common class for the each Entity and then
two subclasses (parallel), one for the Server and one for the
Client. Do you have three sets of templates then? Would you be
willing to share? I see the client templates on the wiki, but
nothing for the common ones.
I am also wondering about this... I do lots of JC, but haven no idea
about how the common class stuff works. Guess I have a tendency to
get behind on this sort of thing :) Anyway, Dave, speak up!
Then, on a different note: are you using Wonder on the client as
well? There isn't a jar in WebServerResources, but there's really
no reason why you couldn't use it is there?
There are reasons why you can't use Wonder on the client. There are
many differences between server and client side libraries. There
might be *some* functionalities from Wonder that could be used on
the client, but the bulk of it: nope.
Have you thought about adding project templates to WOLips for
JavaClient apps (server and client)?
Or a built-in library that would add all the standard
WebServerResources jars to the classpath like the "WebObjects
Frameworks" one does for the server?
I isolate client side libs as Eclipse classpath variables. However,
I believe there is room for improvement. Not sure if it can be
standardized... Might be possible. Something like a "WOJC classpath
container" becoming a part of WOLips.
I'm still on the older WOLips, but are there any ant tasks for
JavaClient now too?
Client side apps can be many different things. For example, IIRC
Dave is deploying using WebStart, has his server and client stuff in
the same project, relies on WOLips JC stuff to build his client side
apps and does lots of D2JC. As a different example, I am not using
WebStart, have separate projects for client and server stuff, don't
rely on WOLips JC capabilities, and do pure JBND+Swing WOJC apps. My
point: there are many different ways one can approach WOJC. In that
sense I believe making standard project templates would be difficult.
Sorry, lots of questions. I'm exploring the possibility of using
JavaClient.
Go for it! The few of us that use it will be there for you...
Best regards, and hope we can hook you to the JC hook :D
F
don't want to self-advertise, but if you are new to JC, and
interested in your options, I suggest you also take a look at:
http://web.mac.com/flor385/eSwamp/software/wojc_tutorial.html
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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