On Mon, 14 Apr 1997, Dan St.Andre' wrote:
> 1) When I select 'new', there are a few things that I'm planning to do.
> (a) Make a free standing application. (b) Make an add-in subsystem
> or screen for an existing application. (c) Make a tclette.
> WHAT IF 'NEW' GAVE ME THESE OR SIMILAR CHOICES.
sort of like a wizard, right? I can start to look at this around 1.1x
since it will introduce a proper project model.
> 2) There are lots of events out there. COULD VTCL HAVE WIDGET TOOLS TO
> HELP ME DECLARE, MANIPULATE AND MANAGE THE MAJOR SORTS OF EVENTS?
The bind editor is currently very weak. I will spend some time on
this starting in 1.1x.
> 3) We all know the advantage of using callback routines. COULD VTCL
> AUTO-MAGICALLY PASS WINDOW AND WIDGET PATH NAMES AS ARGUMENTS TO BUTTON,
> LIST, ENTRY AND RELATED COMMAND ROUTINES AND BINDINGS?
Can you send a code example of how you would like to have this happen?
It might be a good user preference.
> BTW -- Could someone who has really worked out a good way to do this, PLEASE
> post example code? [... and could VTCL use that or similar uniform style...]
>
> 4) I have legacy TCL/TK code that I'd like to enhance with vtcl.
> IS THERE ANY HOPE THAT I CAN READ THIS IN AS A PROJECT? WHAT ARE THE
> MINIMUM REQUIREMENTS TO READ LEGACY CODE?
There are currently some problems managing legacy tcl code. Visual Tcl
likes to source it and this causes some things to be interpreted and
substituted which should remain dynamic. Sorry to repeat, but 1.1x will
begin to address this properly. It will also allow for custom code
editors.
-stewart-
