Stylistically, TblDonorPhone and TblDonor are freaking ugly names. There are no Windows untyped resource handles here that need to be hacked around with naming conventions. DonorPhone and Donor would be the customary names in WO.
Or in some case prepending entity names with two capital letters as a sort-of "namespace." This is in case you want to provide your classes to other developers in a framework. Something similar to the NSArray, NSDictionary classes provided by the WO Foundation. This is necessary in some cases because entity names must remain unique within your application and all included frameworks.On Apr 11, 2006, at 5:46 PM, Chuck Hill wrote: I’m only prototyping my code here – as you can see it’s not elegant and lots of exception handling needs to be added – but for testing I want to let the exceptions jump right out.
I DO have Chuck’s book, but must admit it’s a bit over my head since I still don’t have my black-belt in Java. http://www.global-village.net/wointro will be my next investment. :)
Thanks in advance for pointing out all my elementary flaws,
Stylistically, TblDonorPhone and TblDonor are freaking ugly names. There are no Windows untyped resource handles here that need to be hacked around with naming conventions. DonorPhone and Donor would be the customary names in WO.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
