• 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: Framework EOModel Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework EOModel Question


  • Subject: Re: Framework EOModel Question
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 5 Aug 2005 11:46:34 -0700

On Aug 4, 2005, at 10:35 PM, Anjo Krank wrote:

Am 05.08.2005 um 07:14 schrieb Chuck Hill:
Point taken. I'll get around to utilising PW... just getting as comfortable as I can with WO first.
Although Project Wonder is, erm, wonderful, there is no need to use it to reap the benefits of prototypes. EOPrototypes are part of EOF.

Well... we have neat code that allows you to switch then based on properties and not on the mumbo-jumbo that normally gets used. And we allow you to actually support multiple types of DBs, which is not possible with the EOJDBCPrototypes.

Yes, but there are other options for this than the entirety of Project Wonder. Practical WebObjects also has this functionality and there are code examples on WOCode and WODev. I was just trying to make it clear that prototypes existed outside of Project Wonder.



However, I'd advice prototypes only when you have either only one model or are very disciplined:

I'd always use them, but that's me.


- I don't know if that's still the case, but they get deleted when you open the model from the Finder and then save. You *must* open it from XCode

Or from WOLips/Eclipse. The same thing goes for multiple models with cross model relationships or inheritance.


- Terrible things happen if you don't change the load order so that the model with the prototyp gets loaded first. So basically - if you have more than one model - you should have a framework just for prototypes (no code) and drag it in the load order at the top.

I've never noticed a problem with that, but that is probably because I have code that runs at model load time.

Chuck

--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development 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


References: 
 >Re: Framework EOModel Question (From: LD <email@hidden>)
 >Re: Framework EOModel Question (From: Chuck Hill <email@hidden>)
 >Re: Framework EOModel Question (From: LD <email@hidden>)
 >Re: Framework EOModel Question (From: Chuck Hill <email@hidden>)
 >Re: Framework EOModel Question (From: LD <email@hidden>)
 >Re: Framework EOModel Question (From: Chuck Hill <email@hidden>)
 >Re: Framework EOModel Question (From: Anjo Krank <email@hidden>)

  • Prev by Date: Re: EO + SQL Errors
  • Next by Date: Re: EOModeler insanity
  • Previous by thread: Re: Framework EOModel Question
  • Next by thread: Re: Framework EOModel Question
  • Index(es):
    • Date
    • Thread