On 4-May-06, at 3:54 PM, Carter Wojcik wrote:
Hi all -I am relatively new to WebObjects and have built an app with basic functionality (list EO's, view/edit an EO). Now I would like to take this one step further and abstract out some of the functionality for displaying a list of EO's or an edit/view form, so the code can be used reused in my many code pages. The app has lots of code pages that display a list of EO's and allow the user to view/edit and EO. Instead of writing the same code for each screen I would like to create a helper class that would perform the same functions for each page. Are there any good examples or explanations that show/describe this abstraction?
You could try this:Create a Java class, make it inherit from WOComponent. Put your common logic in it and subclass all of *your* components from it.
Rinse, repeat.Or, build your app with Direct to Web, which does all of this grunt work for you :-)
-- ;david -- David LeBer Codeferous Software 'co-defer-ous' adj. producing or containing code site: http://www.codeferous.com blog: http://david.codeferous.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
