On Feb 6, 2007, at 5:29 PM, Jonathon -- Improov wrote:
Personally, being lazy and too used to the "quick and dirty, get it up and running" approach, I would do the form/screen widget method first, spot repeated processes as I go along, then abstract those into use cases (aka services). I can't stand sitting back for hours trying to foresee what services or use cases I might need. :P
This is a powerful and important concept... very in-line with agile processes that consistently lead to good results.
Just don't do services for really trivial stuff that you won't repeat elsewhere in the application, or you'll end up with zillions of services. Esp don't do services for trivial lookups; updates will need services more since they're not as varied/variable as lookups and views.
This is a good point to. Using services, especially for complex or commonly used stuff that can be parameterized effectively, is a good idea but what you describe here Jonathon is exactly why the entity-* and other such operations exist in screen widget actions.
-David
smime.p7s
Description: S/MIME cryptographic signature
