"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
Paul Clapham wrote:The whole idea of objects "firing" and being "later" or "prior" objects just sounds wrong to me.
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
S.D. MADHAN
Not many get the right opportunity !
Madhan Sundararajan Devaki wrote:You may use the "Builder" pattern.
OCUP UML fundamental and ITIL foundation
Paul Clapham wrote:Sure, the "controller" is a pretty common pattern. A lot of frameworks in the Java world are built on the "MVC" ("Model, View, Controller") pattern.
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
Cory Hartford wrote:
1) Why does the idea of creating objects in a definitive order and referring to them as "later" and "prior" sound wrong in these examples? We have to have a cake before we can frost and frost before we can check the frosting and correct frosting in order to start again. I don't understand how else we could do that.
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
Paul Clapham wrote:
Cory Hartford wrote:
1) Why does the idea of creating objects in a definitive order and referring to them as "later" and "prior" sound wrong in these examples? We have to have a cake before we can frost and frost before we can check the frosting and correct frosting in order to start again. I don't understand how else we could do that.
As for the two pictures you posted, I'm sorry, I couldn't make any sense out of either of them. Normally in object-oriented design you provide a description of an object in terms of what attributes it has and what actions it can perform. I didn't see anything like that.
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
Paul Clapham wrote:
Cory Hartford wrote:
1) Why does the idea of creating objects in a definitive order and referring to them as "later" and "prior" sound wrong in these examples? We have to have a cake before we can frost and frost before we can check the frosting and correct frosting in order to start again. I don't understand how else we could do that.
In my mental model of that process there's only one object. The cake. Its state changes as time goes on, but there's only a cake. If your model has "unfrosted cake" and then "frosted cake" as two separate objects then I think that's the source of most of your problems.
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
"The greatest of all weaknesses is the fear of appearing weak." - JB Bossuet
Cory Hartford wrote:So would those steps reside inside of an object?
Or be behaviors of one of the objects that you listed?
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |