Wow, it's fun to hear people talking about Catalysis!
Catalysis is an analysis and design methodology that focuses on
components and frameworks. It stresses being able to specify component
interactions with invariants, pre/post conditions, and supporting graphics.
The book, "Objects, Componen
Johan Carlsson wrote:
>
>> Also, the Catalysis method puts an emphasis on defining interactions and
>> collaborations between objects in terms of roles. You might want to take
>> a look at that.
>
> Is Catalysis method a pattern in Coads book?
No. Catalysis is an object oriented analysis and d
> ...
> When you're thinking about a system, it is often helpful to think about
> just a part of the system rather than the system as a whole. To do this,
> you define a limited "scope" around a particular subsystem.
> In this case, an Actor represents the role something from outside your
> subsy
Johan Carlsson wrote:
>> A Specialist manages objects that play a particular role in your application.
>> You will usually have one Specialist for each role in your application; try
>> listing all the roles, and what they do, and that's a good start for thinking
>> about what specialists you need
> A Specialist manages objects that play a particular role in your application.
> You will usually have one Specialist for each role in your application; try
> listing all the roles, and what they do, and that's a good start for thinking
> about what specialists you need.
Hi Steve,
I'm a bit conf
Phillip J. Eby wrote:
> At 08:38 AM 2/4/01 -0800, Michael Bernstein wrote:
>
>> On that subject, does anyone know why SkinScripts don't
>> support cut-n-paste or copy-n-paste?
>>
> 'cause I never thought of implementing it, probably because I've never yet
> needed to move a SkinScript. Patche
Phillip J. Eby wrote:
> At 08:38 AM 2/4/01 -0800, Michael Bernstein wrote:
>
>> On that subject, does anyone know why SkinScripts don't
>> support cut-n-paste or copy-n-paste?
>
> 'cause I never thought of implementing it, probably because I've never yet
> needed to move a SkinScript. Patches
At 08:38 AM 2/4/01 -0800, Michael Bernstein wrote:
>
>On that subject, does anyone know why SkinScripts don't
>support cut-n-paste or copy-n-paste?
>
'cause I never thought of implementing it, probably because I've never yet
needed to move a SkinScript. Patches cheerfully accepted. :)
___
Steve Alexander wrote:
>
> Michael Bernstein wrote:
> >
> > If the SkinScript
> > has functionality that should be shared by more than one
> > Rack, it should go in the Specialist,
>
> Not quite. If the SkinScript has functionality that is shared by
> all the Specialist's Racks, then it should g
Michael Bernstein wrote:
>
> Thanks, Steve. That was very helpful. To summarize your
> explanation, if I understood correctly:
>
> This is strictly an implementation issue.
You could say that. I would agree some of the time :-)
> If the SkinScript
> has functionality that should be shared by
Steve Alexander wrote:
>
> Michael Bernstein wrote:
>
> >
> > Thanks, Steve. I'll try this a little later today. What are
> > your thoughts on placing this in the Specialist's 'Plug-ins'
> > tab vs. the Rack's?
[snip excellent explanation]
Thanks, Steve. That was very helpful. To summarize you
Michael Bernstein wrote:
>
> Thanks, Steve. I'll try this a little later today. What are
> your thoughts on placing this in the Specialist's 'Plug-ins'
> tab vs. the Rack's?
A Specialist manages objects that play a particular role in your application.
You will usually have one Specialist for eac
Steve Alexander wrote:
>
> Michael Bernstein wrote:
> >
> > 'BookProduct' product
> > *'BookClass' ZClass (inherits from
> > _ZClass_for_CatalogAware, _ZClass_for_DataSkin)
>
> Don't derive from CatalogAware when you're also deriving from DataSkin.
Ok.
> Rather than use the CatalogAwareness
Michael Bernstein wrote:
>
> 'BookProduct' product
> *'BookClass' ZClass (inherits from
> _ZClass_for_CatalogAware, _ZClass_for_DataSkin)
Don't derive from CatalogAware when you're also deriving from DataSkin.
Rather than use the CatalogAwareness mechanism to
manually call reindex() when yo
14 matches
Mail list logo