• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: source control best practice with wonder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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:24:10 -0700


On Mar 17, 2008, at 10:04 AM, Simon McLean wrote:

What does everyone else do with the woproject files when it comes to source control ?

For years, I just swore at them.

I've done a bit of that too!

The best practice is probably to migrate your project structure to the Fluffy Bunny Layout (I really should make a Wiki page for that) and have your source control ignore woproject/.

Am i right in thinking that the FBL completely ignores the pattern- set stuff and instead relies on the physical folder structure of the project ? If so, then that a page on it would be superb.

I think so. Fuzzy Bunny is the work of Anjo (hence the name ;-).

I'm intrigued...

Who makes you think of a cuddly, fluffy bunny more than Anjo?


I am using a slightly perverted form of it, due mostly to my own peculiar tastes, so I am not 100% sure.

Does anyone actually like the pattern set stuff ?

If someone does like it, they need medication.


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.


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


  • Follow-Ups:
    • Re: source control best practice with wonder
      • From: Simon McLean <email@hidden>
References: 
 >source control best practice with wonder (From: Simon McLean <email@hidden>)
 >Re: source control best practice with wonder (From: Chuck Hill <email@hidden>)
 >Re: source control best practice with wonder (From: Simon McLean <email@hidden>)
 >Re: source control best practice with wonder (From: Chuck Hill <email@hidden>)
 >Re: source control best practice with wonder (From: Simon McLean <email@hidden>)

  • Prev by Date: Re: Qualifier Format String truncates on error?
  • Next by Date: Re: source control best practice with wonder
  • Previous by thread: Re: source control best practice with wonder
  • Next by thread: Re: source control best practice with wonder
  • Index(es):
    • Date
    • Thread