Re: Ada 95 Windows GUI Classes

[tmoran@bix.com (Tom Moran)]

> Choice 1 could be *CLAW* (commercial) or *Windex* (in progres).  If
> designed in a OO fashion, one can imagine inheriting from the base
> application class, modifying it and decorating it with
> other objects.
  Slight correction:  Claw does not have an *application* object
to modify/decorate.  It instead has system objects which your app
can use/extend as needed.  Thus there is a Basic_Window_Type which
will call, for instance, procedure When_Mousemove when the mouse
moves.  If you need to actually use the mouse, you would declare
your own "type Window_Type is new ..."  and supply your own
When_Mousemove, which gets called whenever the mouse moves.
Similarly there is a (class of) Socket_Type, Menu_Type, etc etc.

> 2. Use a UI designer that generator the code implementing the UI
>...  Choice 2 is my ideal solution. ...
> The Knoware tools are an example. Alas, there are no such tools
> yet for Ada.  The closest thing is currently *RAPID*.
  Actually, Claw comes nowadays with CBuild, a visual GUI
designer that will generate code using Claw plus your own code.
  It may not fit everyone's idea of an "ideal solution", but it
certainly goes a long way. ;)