Re: Some gui cleanups
Andy Piper wrote:
At 07:17 PM 4/15/00 -0700, Ben Wing wrote:
>I did offer to fax you all the documentation.
I don't have a fax machine.
not at your work? not at a copy service like kinko's?
>Don't you have access to the sources? The Athena widgets are open source.
Somewhere maybe.
"i don't feel like making the effort" isn't a very good excuse.
>I seriously doubt I made this suggestion, since it's so unclean.
At 04:36 AM 4/7/00 -0700, Ben Wing wrote:
>(2) [Better] Provide a way for callbacks to determine where they were invoked
>at. This is much more general and is what you should really do. For
example,
>have the code that calls the callbacks bind some global variables such as
>widget-callback-current-glyph and widget-callback-current-channel, which
>contain the glyph
>whose callback is being invoked, and the window or frame of the glyph
>(depending on where the glyph is) where the invocation actually happened.
>That way, the callbacks can easily figure out the dialog box and
>its parent, and not have to worry about embedding it in at creation time.
Obviously transatlantic differences in English meaning are larger than I
thought.
>I don't understand when you say "the various types of callback". Are
you
using
>the callback for various different purposes?
No. Callbacks are allowed to be many different things - some functions,
others just forms or symbols.
it's very simple -- you defined the glyph widget api, including the :callback
keyword, so you can change it. none of your api is set in stone. you yourself
suggested "design should be gradual, and evolve as necessary" in response to my
suggestion to try to get things right the first time, rather than creating
hacked-up implementations; so you can hardly argue that you can't change what
you've already implemented.
the only difference is that instead of calling "Feval", call "call2".
>Your widget callbacks should work just like any other callback: they take two
>arguments, one indicating the object to which the callback was attached
(an image
>instance, i think), and the event that caused the callback to be invoked.
I'm obviously misunderstanding something here.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also http://www.666.com/ben/typing.html.