Am I missing something?
--Ben Doom
Dwayne Cole wrote:
> If you use 3 objects you might run into a conceptual trap. You will
> begin designing objects as if they were tables and that can be
> problem. I don't know what they are, but I do know that there are
> conflicts with OO and Relational Theory. THere has be alot written
> about incompatiblity between the two methodologies. So be careful.
>
> Dwayne Cole, MS in MIS, MBA
> Florida A&M University
> Certified Advanced ColdFusion Developer
> 850-591-0212
>
>
> "It can truly be said that nothing happens until there is vision. But it
> is equally true that a vision with no underlying sense of purpose, no
> calling, is just a good idea - all "sound and fury, signifying
> nothing." The Fifth Discipline - Peter Senge
>
> ---------- Original Message ----------------------------------
> From: Ben Doom <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Tue, 18 Nov 2003 10:36:18 -0500
>
> >First, I wouldn't use an array. If you build a big array (say, 1024)
> >you waste a lot of space if most tasks have 3 consumables. If you build
> >it too small, it's too small. :-) Linked list is the way to go here.
> >
> >As to how to break up your objects....
> >
> >If you use ConsumableLists in places other than as part of a task, it
> >should (obviously) be a separate object. Conversely, if a Comsumable is
> >never loose, but is always part of a List, then maybe you don't need it
> >to be a separate object. And if Consumables are always part of Lists
> >are always part of Tasks, then you don't *have* to break them up due to
> >logical devisions. Of course, I always use this to judge when I
> >*should* break them, not when I *shouldn't* (if that makes sense).
> >
> >Next, what's the most flexible? Obviously (well, I think it's obvious)
> >3 objects is the most flexible, since you can pull out subobject
> >separately. You could, for example, copy ConsumableLists from task to
> task.
> >
> >Finally, what's the easiest to code? Probably 3 objects, if they're
> >designed well.
> >
> >Hmm. I guess I decided you should make 3 objects. Heh. I should be a
> >manager......
> >
> >--benD
> >
> >
> >Deanna Schneider wrote:
> >
> >> That's what I'm wondering if I should do, yes. Or, if it works better to
> >> just have the two objects, with the task object having an array of
> >> consumable objects.
> >> -d
> >>
> >> ----- Original Message -----
> >> From: "Dwayne Cole" <[EMAIL PROTECTED]>
> >> To: "CF-Talk" <[EMAIL PROTECTED]>
> >> Sent: Tuesday, November 18, 2003 8:59 AM
> >> Subject: Re: SOT: OO Design
> >>
> >> > So are you thinking of creating three objects: a task object, a
> >> consumable
> >> object, consumableList object that acts like a associative entity?
> >> >
> >> >
> >> > Dwayne Cole, MS in MIS, MBA
> >> > Florida A&M University
> >> > Certified Advanced ColdFusion Developer
> >> > 850-591-0212
> >> >
> >> > "It can truly be said that nothing happens until there is vision.
> But it
> >> is equally true that a vision with no underlying sense of purpose, no
> >> calling, is just a good idea - all "sound and fury, signifying nothing."
> >> The Fifth Discipline - Peter Senge
> >> >
> >> >
> >> >
> >> > ---------- Original Message ----------------------------------
> >> > From: "Deanna Schneider" <[EMAIL PROTECTED]>
> >> > Reply-To: [EMAIL PROTECTED]
> >> > Date: Tue, 18 Nov 2003 08:28:11 -0600
> >> >
> >> > >Hi Folks,
> >> > >I'm trying to get my head around OO design for CF and I have a
> ton of
> >> > >questions, of course. I'll try to keep them limited, as they're
> sort of
> >> > >off-topic (though not entirely, because whatever I have to
> design I have
> >> to
> >> > >build in CF).
> >> > >
> >> > >Here's my first basic question:
> >> > >When you're designing an object that includes a multiple has-a type
> >> > >relationship, do you typically build the objects such that their
> is an
> >> > >intermediate "collection" type object?
> >> > >For example, I'm working on a project management system. It involves
> >> tasks.
> >> > >Tasks can have 0 to many "consumables" associated with them.
> >> > >
> >> > >Do I have one object "Task" and one object "Consumable" with the
> >> consumable
> >> > >object having both a "getOne(consumableID)" and a "getAll(taskID)"
> >> method?
> >> > >Or, do I have an intermediate "ConsumableList" object that takes a
> >> taskID
> >> > >and gets all the consumables associated with that task by calling a
> >> method
> >> > >in the Consumable object.
> >> > >
> >> > >Does that make sense?
> >> > >
> >> > >Thanks.
> >> > >-Deanna
> >> > >
> >> > >
> >> > >
> >> > >---------------------------------------------------------
> >> > >Deanna Schneider
> >> > >UWEX-Cooperative Extension
> >> > >Interactive Media Developer
> >> > >
> >> > >
> >> >
> >>
> >
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
