[ooc-compiler] VisualOberon or not VisualOberon?

[Frank H. <fh...@ph...>]

I am starting to use oo2c on Win32/MinGW.

Why not POW? Because IMHO oo2c is (i) more portable, because it (ii) 
offers more functionality (libraries) and it (iii) is easier to use in a 
multilingual project (use of library and program source code written in C).

I certainly will need GUIs, so should I use VisualOberon or another 
framework (Glade/Gtk, Qt, ...)?

I know the Oberon look-and-feel from System 3 and I like it. And using 
the language Oberon for the GUI would make programming more comfortable 
using VisualOberon. On the other hand: VO (i) would have to be 
statically linked to my programs or be installed on the target 
platforms, whereas Gtk already might be there. (ii) More people are 
familiar with C and Gtk. And finally: (iii) for Gtk an interface builder 
is available (Glade). So I tend towards the latter solution.

I am curious about your ideas out there, and especially about the 
objective opinion of Tim ;-)
-----------------------------------------------------------
Frank Hrebabetzky		Tel.:  +55/48/239-2258
Photonita Ltda			Fax:   +55/48/239-2200
Parque Tec. Alfa - Ed. CELTA
Florianopolis, SC		
88030-000
Brasil