Re: wolips / webobjects build question
Re: wolips / webobjects build question
- Subject: Re: wolips / webobjects build question
- From: Kieran Kelleher <email@hidden>
- Date: Wed, 12 Dec 2007 08:43:12 -0500
Hi Fred,
While your "new" perspective is still fresh, you should get a wiki
account (http://wiki.objectstyle.org/confluence/display/WOCOM/WOCOM)
and fill in the gaps. It is true that once you have learned this
stuff, your perspective of what a newcomer needs is not as clear as
it was when one was a newcomer themselves.
Regards, Kieran
On Dec 12, 2007, at 8:34 AM, Fred Shurtleff wrote:
Kieran,
Thanks very much for this explanation - things are now becoming
clearer.
Actually my confusion was how you were using the source (as
Imported projects) without having the binary PW frameworks. I had
forgotten all about BUILD.txt - which details the use of Ant to
build/compile the source into > /Library/Frameworks. Also I can now
relate to your blog script to automate the CVS download/build.
And yes I have read the website piece on embedding project
frameworks into a build, and 'get the drift'.
So now I just need to do the CVS download/build thing, and
hopefully I will be in business.
Thanks for the '20,000 ft up' perspective - I needed this.
Fred
PS - Its not so much that any one particular tutorial was
confusing. Rather I was getting 'lost in the trees' and couldn't
see the 'forest'. In addition to the tutorials, I think some high
level/introductory roadmap would have been nice to have.
Kieran Kelleher wrote:
Well, after you checkout the whole Wonder directory which has a
file hierarchy inside with all the various collections of Wonder
frameworks, example apps, README's, and also source code for
things other than WO apps/frameworks too, you can then follow the
instructions in BUILD.txt in the root directory (by "root", I mean
the Wonder directory itself).
Now, I can see why you are confused. The wiki instructions said
follow INSTALL.txt, which AFAIK was correct when I wrote that in
June 27th. Since then the nerd build from source instructions have
been moved to BUILD.txt.
Installing from the Wonder tree, using the Wonder ant builds
installs all the Wonder frameworks in /Library/Frameworks.
For me this is only important for deployment since I use embedded
builds (Fred, don't even think about that right now!) and the
embedding ffeature of the WOLips deployment build tasks pulls
copies of the installed Wonder frameworks from /Library/Frameworks.
During development, my app or frameworks (generall known as
"projects") refers to the Wonder projects that are in my workspace
(which really are like "alias" or "shortcut" links back to those
individual projects in the Wonder source tree that I am interested
in.
Fred, please feel free to identify a wiki page that is too
"mechanical" that needs some conceptual embellishment of the "What
THis Procedure Does" type explanation!
Regards, Kieran
On Dec 12, 2007, at 7:15 AM, Fred Shurtleff wrote:
Kieran,
Can you further expound here for the neophytes. When you say 'you
can install from the same tree'(when you do a CVS download), do
you mean when you build/deploy your app, all the imported &
referenced projects are compiled into the deployment bundle/woa/
directory or whatever?
Take for example the BugTracker tutorial where you import 21 PW
projects which are all referenced in the Build Path of BugTracker
as 'Projects' NOT 'Libraries'. How would this app get deployed?
And what would the deployment object consist of?
Or is this line of questioning off track - would it be better to
have BugTracker reference all the PW *frameworks*(and not
Projects) as added 'WO Frameworks' in the Build Path window?
This is the most confusing aspect of WO/Eclipse development - so
much is done mechanically following some tutorial without really
understanding how all the participating frameworks (WO & Local)
get used and deployed.
I know this may appear as so basic to experienced practitioners,
but is confusing as hell to me.
Thanks
Fred
Kieran Kelleher wrote:
Simon,
Downloading the whole tree and importing has the advantage that
you can install form the same tree, so the embedded frameworks
(which come from the install locations) are the same code as you
have linked to workspace.
Kieran
On Dec 11, 2007, at 5:49 PM, Simon McLean wrote:
--
MacOS: Tiger 10.4.11
Eclipse: 3.3.1.1
WOLips: 3.3.4705
WebObjects: 5.3.3
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
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