On Wed, 19 Mar 1997, Kenneth H. Cox wrote:
> On Mon, 17 Mar 1997 [EMAIL PROTECTED] wrote:
> > I looked at specTcl and hate it. Now vtcl looks like a
> > good clean sensible GUI builder and I like it's look and feel.
> >
> > Has anyone got vt working with the tix widget set?
>
> Hello,
>
> I also tried, and I failed to get Tix working with VTCL. I asked Stewart,
> the developer, for help, and got nothing. When he's less busy, he may
> get around to it. Anyway, I would be interested to hear your status
> with respect to Tix integration.
You may have missed my mail to the list on this depending on when you
joined. Tix support is the next widget support that I intend to add. The
hooks are in 1.08 for adding dynamic widget libraries, though it is
incomplete. Hints may be found in the lib_core.tcl file in the lib
directory of vtcl. Any file in that directory starting with "lib_"
will be autoloaded as a widget library.
This has mostly been hampered by two things:
1) time
2) I've never used Tix before. From what I've seen, it is different
enough from the core set that I'll have to make changes to accomodate.
> Also, I thought you might like to hear why I gave up on VTCL. Mostly it
> was one feature that killed me: the Tcl code that VTCL generates
> specifies every option on every widget. That is, every widget will have
> a `-background xxxx' option specified. This makes it very unweildy to
> try to change the defaults universally. It made it basically impossible
> for me to integrate VTCL windows with an existing app, which already had
> an options-based mechanism to customize colors and fonts.
Ken,
This was only true in early versions of vtcl. Now, it compares a widgets
option with the default. If it is different, it is saved. This makes the
generated code much smaller and more portable. You may want to look at
the most recent version.
-stewart-
