Subj : Re: Objects in library, tables in application
To   : comp.programming
From : Phlip
Date : Mon Jul 11 2005 04:14 pm

rhedin wrote:

> We are working on an interface with a lot of elements the user can
> manipulate.  Most of the user interface objects reside in a library
> that is used by several applications.  It is natural to keep the
> results of the users' manipulations in tables in the applications, to
> control the running of our model.
>
> The problem is this straddling between the library and the
> applications, and between objects and tables.  The natural solution is
> to maintain both, and refresh one from the other as needed.  However,
> that strikes us as, um, inelegant.
>
> This doesn't seem to be something that was covered by the Gang of Four.
>  Has someone else encountered this, and have they discovered a clean,
> codeable solution?

You are asking about "Model View Controller". Look up one of several of its
definitions.

The GOF pattern here is Observer. Instead of A hard-codes a link to B, B
should observe A and respond to A's events.

-- 
  Phlip
  http://www.c2.com/cgi/wiki?ZeekLand

.