Re: PAC (presentation-abstraction-control) question


"craig" <craigwharris@xxxxxxxxxxx> wrote in message
news:1143061653.290656.145620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for posting this on comp.object,.. thats where I intended to
post.
Phlip,

By a "triangle" of observers, do you mean M and V and C should each be
observers?

The simplest form is they just call each other. (Escallate an interface to
break the dependency cycle.)

The next step in complexity is this:

http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch2.html

The Model calls functions on the View to query state, and the View observes
the Model. The Model calls functions on the Controller to query state, and
the View calls functions on the Controller to query state, and the
Controller observes the View to receive fully cooked user events.

At the next step in complexity, objects within the Controller observe
objects within the View, and objects within the View observe objects within
the Model.

By "complexity" I mean "simpler than the alternatives, for the existing
requirements".

Now what is PAC and who wrote it up? All I ever heard of are MVC (and MVP
which might be different).

--
Phlip
http://www.greencheese.org/ZeekLand <-- NOT a blog!!!


.