Re: source control best practice with wonder
Re: source control best practice with wonder
- Subject: Re: source control best practice with wonder
- From: Chuck Hill <email@hidden>
- Date: Mon, 17 Mar 2008 10:46:39 -0700
On Mar 17, 2008, at 10:38 AM, Simon McLean wrote:
I'm not being rude about it, just wondering if it's one of those
things that everyone tolerates because "that's the way it is". I'd
put it quite high on the list of "confusing-things-to-get-your-
head-around-when-moving-to-eclipse". It just doesn't feel
intuitive. Whereas putting your components in the "components"
directory, and your resources in the "resources" directory is more
my cup of tea.
I think it made sense to someone way back when this all got
started. There was (in my interpretation) a strong "don't force
things on the user" intention in how the woproject stuff was
written. The flexibility can be useful. In retrospect, a little
force in terms of having a convention for project layout makes life
better for everyone.
Yeah, I agree. Flexibility is good as an advanced option, but stick
the shackles on to begin with - If anything you avoid questions from
dummies like me :-)
I'm sure this must have been suggested before, but how about fluffy
being the default for a new WOnder app in eclipse ?
If you are using a recent WOLips version, it IS the default for all
new projects.
Cuddle the Fluffy Bunny!
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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