Re: source control best practice with wonder
Re: source control best practice with wonder
- Subject: Re: source control best practice with wonder
- From: Simon McLean <email@hidden>
- Date: Mon, 17 Mar 2008 17:38:48 +0000
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 ?
Simon |
_______________________________________________
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