I have come across this thought from my fellow monks in the past, yet I still can't seem to see how, possibly not seeing the woods through the trees.
In my example, a My::Customer may work in a My::Industry. They'll need to select a My::Industry on a form.
This all leads me to needing to get a list of possible industries, and tying the two together through their IDs.
Somewhere else I may need to get all My::Customer objects that registered last month, last year, 2 weeks ago, etc, hence the need for some sort of...
My::Customer->get( registered => [ DateTime->new( year => 2011, month +=> 4, day => 1 ), '>' ] );
...approach.
I'd love to sit down and talk this idea of modelling processes more than the objects themselves with a fellow monk, but unfortunately I currently work pretty much alone, while training up 2 others.
I presume my original approach to be "ok", I think I've asked a similar question before and it usually goes on this same tangent of the modelling rather than the interface.
In reply to Re^2: Design Question - I've gone object mad!
by Cagao
in thread Design Question - I've gone object mad!
by Cagao
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |