From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: LablTk internals
Date: Thu, 17 Nov 2005 14:29:38 -0700 [thread overview]
Message-ID: <437CF642.8060302@gushee.net> (raw)
Hello, all--
I am working on some enhancements to LablTk, to bring it up to date with
Tk 8.4. One of the features I want to implement is validation for Entry
and Spinbox widgets (the latter being a new widget that I have added
already). It looks like this will require support module(s) in the
'builtin' directory ... the validation commands are somewhat like event
bindings, in that they use fields (with % substitutions in Tcl syntax)
and require registering callbacks; on the other hand, unlike event
bindings, but like Button and Menu commands, they are bound to the
widgets with configuration options rather than a standalone binding command.
So I need to understand more about those 'builtin' components. I'm sure
I can work out the answers myself, but it will take a lot of time, so
I'd greatly appreciate it if someone could answer at least these questions:
* How are external support modules associated with modules generated
from Widgets.src? If I introduce a new module(s), do I need to modify
a Makefile, or are the dependencies all auto-detected? In the latter
case, what do I need to do so that
option ValidationCommand
will work in a widget definition, where the ValidationCommand type is
defined in an external module?
* What do the prefixes 'builtin_', 'builtina_', 'builtinf_', and
'builtini_' mean, and why do some of the modules in 'builtin' have
these prefixes, while others have no prefix?
--
Matt Gushee
Englewood, CO, USA
next reply other threads:[~2005-11-17 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 21:29 Matt Gushee [this message]
2005-11-18 6:00 ` [Caml-list] " Jun Furuse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=437CF642.8060302@gushee.net \
--to=matt@gushee.net \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).