On Tue, 20 May 1997, Troy Monaghen wrote:
> Because of the particular configuration of my system I end up with a
> super-tiny font in many vtcl windows. I can live with most of these except
> for the function editing window. Somtimes I can't even tell what a
> particular character is... for example it is almost impossible to
> distinguish parenthesis () from curly braces {}.
>
> So... until Stewart adds a font preferences option I am looking for an
> alternative for coding most of the procedures within the vtcl application. I
> have two ideas and I was wondering if anyone could comment on what some of
> the pitfalls that I might run into would be... I'd also be open to hearing
> any other suggested solutions.
1.10 has the font preference in it.
> Here are my two ideas:
>
> 1) Put the procedures in an separate "procedures" file and then have this
> file source the vtcl-generated file. I could then use any editor I want to
> edit the "procedures" file. The one problem that comes to mind is that
> vtcl's test mode will probably not work.
>
> 2) Edit the vtcl-generated file with another editor. If I just stick to
> editing the bodies of the user defined procedures will I be ok? I would
> need to be able to read this file back in to vtcl... is there anything that
> vtcl requires about the format of the source? I tried this once but vtcl
> would no longer see most of the functions or any of the windows... I think
> this might have been caused by an extra close-brace in the body of one
> function.
This is one of the greatest weakness of the current Visual Tcl
environment and will be the basis of significant changes after 1.10
is released. I would prefer that apps be broken up into multiple source
files that could either be edited with a tcl-specific (highlighting)
editor built into vtcl or an external one. This would also allow for
integration into source control systems and possible expansion to
other Tk language support (python, perl, inferno, etc)..
I've been holding off on 1.10 in order to get better documentation
into place. Rick Macdonald and Larry Virden have put together a basics
tutorial and I've been trying to find the time to put together a FAQ.
Given the long weekend, I'm targeting Monday or Tuesday next week.
-stewart-
