Re: Official Rubicode Statement Regarding EOGenerator and Leopard
Re: Official Rubicode Statement Regarding EOGenerator and Leopard
- Subject: Re: Official Rubicode Statement Regarding EOGenerator and Leopard
- From: David LeBer <email@hidden>
- Date: Tue, 30 Oct 2007 15:34:53 -0400
On 30-Oct-07, at 12:51 PM, Chuck Hill wrote:
What Mike said. EOGenerator has been a vital part of our
development process for many years now. I never understood why more
people did not use dbEdit. I shall miss that.
Chuck
On Oct 30, 2007, at 5:43 AM, Mike Schrag wrote:
I just want to thank you guys for EOGenerator. That tool made a
huge percentage of the WebObjects development community's lives
substantially easier. As I mentioned in my private email, it's a
testament to how great your apps were that I believe the #1 reason
WebObjects people can't move to Leopard is because eogenerator is
broken.
Yes, ditto and "Me too" on both.
When I think of the sheer volume of code I would have had to have
written myself that EOGenerator took care of for free, or the sense of
freedom I got from knowing that a change in my model would result in
new attribute accessors or fetch methods or factories in my Java
classes automagically. Why it almost makes me get teary eyed...*
And I was really annoyed at myself when I realized that naming all of
my PKs "id" in a recent model made it not open in DBEdit. Do'h!
(*Well not really, but it was for effect.)
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
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