Skip to Content
Last modified by Klaus Berkling on 2012/06/20 12:13
From version 22.1
edited by Klaus Berkling
on 2012/06/20 12:13
Change comment: There is no comment for this version
To version 20.1
edited by kiberkli
on 2011/10/11 20:46
Change comment: Added "Add ERPrototypes if your EO model uses/will use prototypes"

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kberkling@dyned_com
1 +XWiki.kiberkli
Content
... ... @@ -34,7 +34,7 @@
34 34  If you got the minimum Wonder integration done and your app is working, then adding these extra fundamental useful frameworks are definitely worthwhile from the start:
35 35  
36 36  * Ajax - Just what it says - easy Ajax in your WO apps
37 -* ERPrototypes - save yourself lots of manhours fiddling with EOModel attributes by using convenient prototypes. This is considered best practice. (Don't forget to select a prototype in your database config in Entity Modeler, otherwise the prototype won't show up when adding/editing an attribute.)
37 +* ERPrototypes - save yourself lots of manhours fiddling with EOModel attributes by using convenient prototypes. This is considered best practice.
38 38  * ERJavaMail - send all kinds of emails - plain text, html, multi-part, attachments, etc. HTML can be generated from a WOComponent or be set using a HTML String.
39 39  * ERSelenium - functional testing that simulates user interaction with your app's web pages.
40 40  
... ... @@ -45,6 +45,6 @@
45 45  
46 46  {{info value="Start Your Next Project on the Right Foot"}}
47 47  For your next project, simply select the WOnderApplication project template instead of the WOApplication template and all the minimum integration tasks itemized above are already done for you. Besides, the WOnder Application project template is so neatly organized that some have commented on how it is a better overall project template for WebObjects projects even if you are not using Wonder.
48 -\\ !Picture 9.jpg!
48 +\\ !Picture 9.jpg!
49 49  
50 50  {{/info}}