• 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: Class Generation in Xcode 2.2.1 using Modeler plugin
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Class Generation in Xcode 2.2.1 using Modeler plugin


  • Subject: Re: Class Generation in Xcode 2.2.1 using Modeler plugin
  • From: David LeBer <email@hidden>
  • Date: Wed, 10 May 2006 09:03:02 -0400


On 10-May-06, at 8:00 AM, Philippe Lafoucrière wrote:


On 10 mai 06, at 13:49, Mark Morris wrote:

Just a comment, I've never had the problem with EOModeler overwriting the .java files. When you make changes to the model, click the ".java" button, then choose the "merge" option. This will open FileMerge, and you can get the new changes while keeping your existing modifications.

I just tried it : it works very well, the conflicts are shown by FileMerge, and it's quite easy to solve merging problems with this tool.


What can be the pros and cons of using it against eomodeler only ?
(I'll find the ml for some archives about that kind of discussion too)

I don't quite understand, "eomodeler only"? Do you mean eogenerator?

Anyway, FileMerge is a neat tool (and it'll compare directories if you ask it to not just files - thanks to Mark Ritchie for that tidbit). But the generation gap pattern used by eogenerator is much nicer:

1. There is no merge step - and although FileMerge does a decent job, sometimes you can confuse it, or miss something during the merge.

2. The eogenerator templates use the MiscMerge language. You can extend the templates to add all sorts of your own logic to the base classes (as per the wikibook: <http://en.wikibooks.org/wiki/ Programming:WebObjects/EOF/Using_EOF/EOGenerator>).

3. Uh... all the cool kids use it - and we all know looking cool is the *most* important criteria :-).

So, standalone EOModeler.app with eogenerator is the way to go.

--
;david

--
David LeBer
Codeferous Software
'co-defer-ous' adj. producing or containing code
site:   http://www.codeferous.com
blog: http://david.codeferous.com




Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

References: 
 >Re: Class Generation in Xcode 2.2.1 using Modeler plugin (From: David Avendasora <email@hidden>)
 >Re: Class Generation in Xcode 2.2.1 using Modeler plugin (From: Mark Morris <email@hidden>)
 >Re: Class Generation in Xcode 2.2.1 using Modeler plugin (From: Philippe Lafoucrière <email@hidden>)

  • Prev by Date: Re: Class Generation in Xcode 2.2.1 using Modeler plugin
  • Next by Date: Re: problem while connecting to application via webserver
  • Previous by thread: Re: Class Generation in Xcode 2.2.1 using Modeler plugin
  • Next by thread: Re: Class Generation in Xcode 2.2.1 using Modeler plugin
  • Index(es):
    • Date
    • Thread