Visual BASIC?
CanDo can also distribute 'bound' modules, which do not require the user to
own CanDo. It adds about 100K to the size (the binding process).
On the other hand, if you have the CanDo library in your LIBS:, then any
number of CanDo programs can use it simultaneously, so that each app is
only as large as need be.
CanDo also allows binding the resources of the app (images, text, etc)
right in the app, rather than having a bunch of disk files. Increases the
size of the app though (naturally). Or you can still have the resources on
disk, and load as needed.
CanDo is very much like HyperCard, in that you 1) design interfaces stuff
interactively (buttons, documents, menus, etc) and then 2) write text
scripts ('handlers' in HyperCard) that are activated by clicking, double
clicking, dragging, releasing buttons; selecting menus; scrolling
documents, etc.
CanDo can also use outside 'functions', via ARexx. You can access ARexx
programs, or applications supporting ARexx (ie. ADPro can be the image
processing module of CanDo – silly, but you get the point). As a matter of
fact, I do use ADPro to support the FireCracker24 board in my CanDo
appls…. CanDo sends messages to ADPro, which loads/writes to the
FireCracker and is then seen on the screen. The lack of a direct data xfer
from one app to another is sad, since it does mean that you usually have to
save/load via disk, rather than just sending the data over from another
prog. Oh well.
–jp–seattle–