Re: [ooc-compiler] VisualOberon or not VisualOberon?

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

Thanks for your detailed answer, Tim.

The point which let me think most, is about the size of the development 
groups. I knew that they are small, but I didn't expect thus few people 
in the case of oo2c.

The language decision is a hard one, once you are addicted to elegance 
(which according to Saint Exupery is reached not when there remains 
nothing to be added, but when there remains nothing to be left out), you 
have found it, and the tool for writing executables for the two 
dominating OSs worldwide depends on a single man.

With respect to GUI building, I'll try to postpone the decision as much 
as possible, following the MVC (model-viewer-controller) paradigm as 
long as possible, using the following strategy: writing programs which 
allow full control through command line parameters/options, compile them 
into an executables, and call them later from the GUI. It may still take 
some time, but you made me curious about VO, so I'll have a look at it.

-----------------------------------------------------------
Frank Hrebabetzky		Tel.:  +55/48/239-2258
Photonita Ltda			Fax:   +55/48/239-2200
Parque Tec. Alfa - Ed. CELTA
Florianopolis, SC
88030-000
Brasil