🚀 go-pugleaf

There has lately been a heated discussion pro and contra Basic in this
conference.  It all started (if I remember correctly) with a question
about Visiual Basic, and if it was any good.

I was at a presentation of Visual Basic (VB) some days ago, and I have 
worked with a product (Winix Toolkit (WTK), mail me if you want more info)
very much like it for over a year. The main difference is that WTK uses
a pascal like language and needs SDK.

When discussing if a product is any good it is necessary to view it in
the context of the problem that is to be solved.  Both products simplifies
the user interface part of Windows programming to a level of painting
and writing some simple statements in Basic or Pascal.

As a tool for handelig the user interface both VB and WTK performs quite
good.  You can quickly make a prototype and you can take most of the work
with you to the final product.

If you make a product that has much code that isn't user interface related,
you can put this code in a DLL and have it called from VB or WTK.  This
works very vell and results in code that has a clearly seperated interface
and engine.

After the presentation of Visual Basic and with my experience with 
Winix Toolkit I don't belive that I would use either product to much
besides handeling the user interface.  There is however a lot of work 
spared with this use of VB and WTK.

My conclusion is: Product like VB and WTK saves a lot of work in the user
interface part of a Windows program, but is not for the complete 
implementation of programs with a lot of non interface code.  For this use
a DLL made from C(++) code.

I hope this will turn the discussion back from a flame war between Basic
ant the others, and to a more interesting discussion of what tools to
use to simplify Windows development.

Ole