The wrapper project
Thu Aug 21 13:39:45 CEST 2003
----- Original Message -----
From: "Joe Armstrong" <>
> I'm back .... (been on holiday)
> I would like to propose the construction of a series of "wrappers" -
Very interesting idea.
> I am currently pursuing this idea. My first component should be a
> control wrapper round wxWindows so we can do GUI's - NOTE my view is
> that the GUI is itself a *component* which is isolated from the
> application which should be another component.
Looking forward to it :)
> NOTE the image component ONLY displays the image and has NO GUI - the
> GUI must be done by the GUI component (which I am trying to write :-)
I think I don't really understand what you mean.
If the image component can display something by itself, then it has a GUI (even
if it's a dumb one). What would be needed here is a "remote canvas" created by
the GUI component, and on which the application could draw. Alternatively, the
application would describe for the GUI what to be drawn via the protocol - and
we get the X basic setup. Or one could split into three layers, according to the
Model-View-Controller pattern: the application knows how to manipulate the
binary bitmap, the view knows how to display it, and the controller... well, it
More information about the erlang-questions