Rick Macdonald wrote:
> There are some features missing for me in vTcl that I don't think are
> easily added:
This first one might not be so hard.
> - multi source file development.
The biggest deal here is that all the code that is sourced into
vtcl becomes part of the vtcl project. By that I mean when you
save your work everything, including all the sourced code, is saved.
There is a set of code that is not saved, that is the vtcl code it's
self. from what I can tell is that all the code that is prefixed with
'vTcl' is not saved. One solution might be to turn this around and
define a prefix unique to each vtcl project ( or file ). Now use that
prefix to mark procs in the vtcl project. This set of prefixed procs
could be the only ones saved that way an external set of procs
could be used.
> - calling one vTcl project from another.
tcl was meant to be process glue from the start.
I think that should be done in software.
open a pipe or something.
Or am I missing something.
Is this different from multi source file development?
> - multiple instances of a toplevel, including some sort of
> dynamic widget alias scheme.
vtcl does not do dynamic widget creation.
What I do is let vtcl make a prototype.
than I include that in a proc and a loop.
(ie. I do my self)
---------------------------------------------------------------------------
To unsubscribe from the Visual Tcl mailing list, please send a message
to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the
message body (where [EMAIL PROTECTED] is your e-mail address).
