At 03:22 PM 9/18/97 +0100, J.R.Suckling wrote:
>
>I wrote Stewart a private letter about the emacs bindings
>that are the default bindings for the text widget where
>lost in the editing windows in vTcl. It was my hope to
>get them back. Stewart answer was the splitting out of
>the functions. so that users could edit them with there
>own selection of editor. Where I think that is a great
>thing, I would like to see some sort of middle ground
>there vTcl can store more then one function in a file at
>the same time present the user with a single function to
>edit. What I am thinking about is level of origination.
I must admit that the number of edit sessions that I normally
have running, using emacs would seem like huge overkill.
>There are trade offs in app design having to do with the
>number of files in an app. and the ablity to use things
>like auto loaders to make apps start up fast. Thies trade
>offs need to be in the hands of the developer.
One ablility I really need is the ablility to source files
that do not the create functions in my project. I have a
set of standard library finctions that I reuse. I either need to
be able to have a new source command that keeps things hidden
from vTcl, or the ability to assign functions to files.
While the later is nice, I feel that head-aches about execution order
of individual main and init files in each file would be a nightmare.
Much though it wrangles, something liles and classes in VC++ might work.
Hope this is of some help.
Chris
