AW: [ooc-compiler] OOC GUI development for Windows (was: Problems with OOC under Cygwin 1.1.2)

[<Tim...@ma...>]

Hallo!

> > How's the GUI interface to Windows
> > coming along?

> I'm afraid I can't take much credit for that as Tim has done all the
> work of porting Visual Oberon to Windows.

I once did a first port of VO to windows. However because of lack of
time I did not finished it and I'm sure, that because some interfaces
slighly changed, it would not compile out of the box anymore. However
it should be easy to get it running again. Also the port lacked the 
implementation of some less important methods (some drawing pattern
were not supported), the line drawing was still bug etc... a number
of small problmes that could be easyly fixed but a good windows
programmer.

> For those of us interested in doing GUI work with OOC/Win32 there are
> probably three options:

> 2) Use Visual Oberon / Windows. I don't yet have much experience with VO
> but what I've seen looks very promising.

There are some widget missing in VO, however it is written in Oberon,
it design is much slicker than that of Gtk, and thus may be a valuable
option for doing plattform independant GUI design for people.

> - GTK has its own object model which is based on C. I'm not sure how
> well Oberon-2 objects can be fitted into their object/callback system. I
> imagine that coding new widgets would be far cleaner under VO. GTK
> probably has a more complete set of its own widgets. 

The overall design of Gtk is a mess. VO is not bleeding edge (a lot of
minor stuff to fix and redesign) but still it is better than Gtk.
Exspecially
the Model/Viewer concept of VO is very nice to have.

> - The GTK DLLs are rather large: about 2 megabytes in total. Its
> probably no worse than MFC, but its still big.

I don't know the size of VO, but fear that it plays in the same liga.

> - GTK is also fairly unstable in that it is developing fast (on all

VO is in flux. Small changes and even some bigger changes may happen
and the developer still has to exspect to activly maintain it
application to make it compileable under future versions of VO.
However the developers are with you and will help you.

-- 
Gruß...
       Tim.