Hello,
My concern, and the effort that I would like to contribute, is to make PW more accessible to developers who haven't made that commitment. I want to provide the random WO developer with the kind of documentation (and ease of access) that will first answer his/her up front questions (what IS this thing? Do I want it? Do I need it? What impact will it have on my current environment? How do I make it happen?) to his/her more detailed questions (If I go with PW, how do I have to change my logging configuration? How do I display request/ response headers and contents for deeper debugging? If something goes wrong in my production app and the exception is thrown in a PW framework, how do I debug it?)
Don't want to jump in the long discussion, but the documentation work Jerry proposed sounds great. I think the following four documents could really make a difference ... - FAQ for WOLips/Eclipse - A Getting Started with WOLips - available, tutorials in progress - More Documentation for PW - A Getting Started with PW, eg. update this information http://wonder.sourceforge.net/start.php Marc _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to archive@mail-archive.com
