Skip to Content
Last modified by Klaus Berkling on 2011/09/06 00:31
From version 43.1
edited by arroz
on 2007/12/16 21:09
Change comment: There is no comment for this version
To version 42.1
edited by arroz
on 2007/12/16 20:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,9 +41,3 @@
41 41  By now, you must be thinking why would you make the learning curve even worse by learning WONDER and WO at the same time. After all, it's a lot of frameworks, a lot of information and, unfortunately, not a lot of documentation.
42 42  
43 43  The point is: **using WONDER will actually make it easier to learn WebObjects**. WONDER fixes a lot of bugs and provides a lot of easier solutions, like EOEditingContext automatically locking, that would otherwise drive you mad if you use pure WO. So, the best option for you to learn WO easily is to use WONDER, at least ERExtensions. Although it seems you are complicating your life, you are really making it (a little) easier.
44 -
45 -=== What version should you use? ===
46 -
47 -Many of us, WebObjects developers, are very conservative about upgrading and living on the bleeding edge of the technologies. WebObjects is used for real business, where many millions of Euros are involved. So, normally the advice would be: use the stable version.
48 -
49 -Well, WONDER is different. WONDER is updated very fast, and at the same time the WONDER team makes a big effort to keep it stable. There are many small fixes every week, that will improve WONDER reliability, and new big features are usually included as optional, off by default. So, my advice on this is, use the [[nightly build>>http://webobjects.mdimension.com/wonder/]], or, even better, [[the CVS head source code>>http://sourceforge.net/cvs/?group_id=45176]]. Keeping the source code on disk will make it easier if you want to fix a bug and submit a patch.