Re: Better start with Wonder than WO
Re: Better start with Wonder than WO
- Subject: Re: Better start with Wonder than WO
- From: "Mr. Pierre Frisch" <email@hidden>
- Date: Thu, 20 Mar 2008 13:20:44 -0700
I would totally disagree with that. Wonder introduce another layer of
complexity and patching on top of WO. I think you should only use
Wonder if you have a good reason for it.
Pierre
--
Pierre Frisch
email@hidden
On Mar 20, 2008, at 11:56, David LeBer wrote:
On 20-Mar-08, at 2:45 PM, Gustavo Pizano wrote:
aha ok...
This is what I decided something what I posted in a previous
thread. I will develop my Software Engineering class final project
in parallel with WO, so at the end I will show the teacher what are
the differences between EO, Hibernate and WO. SO ok I will start
doing it in wonder. SO be prepare for a lot of questions I already
have in my mind, hehe, but of course I will make some tutorial
first, I will watch again the screen-cast :P. if for some reason I
see I can't achive the goal I will go to normal WO development..
hopefully i will not do that.
well what do you think?
Building on top of Wonder needn't impact your development at all
unless you want it to.
You will benefit without even knowing it.
However, there is the danger that you could get so caught up
investigating all of the cool toys in Wonder that you didn't get any
real work done. :-) But then that's not Wonder's fault now is it.
On Mar 20, 2008, at 1:26 PM, David LeBer wrote:
On 20-Mar-08, at 2:15 PM, Gustavo Pizano wrote:
Im just "wondering" what's better for me, you know guys im really
newbie. To keep learning concepts of WO or learn them and develop
in Wonder?
For a new WO developer, I think there are amazing benefits for
starting with Wonder.
Is wonder big? Yes.
Is it hard to fully understand? Definitely.
Do you need to understand all of it to benefit from it? Absolutely
not.
If you:
1. Use the WOLips WOnder Application template
2. Generate your EOs with the WonderEntity.java/
_WonderEntity.java templates
3. Always user ERXEC.newEditingContext() to obtain a new
EOEditingContext
You will benefit from a ton of bug fixes and helpful code that fix
things that are hard to fix otherwise without having to change
much else.
Let the debate commence :-)
;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
_______________________________________________
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