🚀 go-pugleaf

In article <1991Jun19.173316.18566@alphalpha.com> nazgul@alphalpha.com (Kee Hinckley) writes:
>In article <1991Jun18.205101.28425@colorado.edu> thompsog@spot.Colorado.EDU (THOMPSON GEOFF) writes:
>>by accessing the native window sytem components of XVT objects. Hence, the
>>term "Extensible." In general, the full capabilties of the native window
>>system are available in non-portable ways, including handling all native
>>system events.
>However, manager-type widgets like forms, rowcolums, tables... are not
>accessable, unless quite a bit has changed since I last looked at XVT.
>In my mind this toss out one of the best features of Xt.
>-- 
>Alfalfa Software, Inc.          |       Poste:  The EMail for Unix
>nazgul@alfalfa.com              |       Send Anything... Anywhere
>617/646-7703 (voice/fax)        |       info@alfalfa.com
>
>I'm not sure which upsets me more: that people are so unwilling to accept
>responsibility for their own actions, or that they are so eager to regulate
>everyone else's.

In general, if you want to do something non-portably in XVT, you should
be able to do most anything the underlying toolkit, window system, and
operating system allow. You make a good point however. In fact, I will
be presenting a talk at the upcoming XVT Conference this August which
will include the topic of "How to add an arbitrary motif widget to an
XVT window."  It is my belief that any widget should be accessible,
but the real question I need to explore is, just how hard will this
be.  Now I'm not sure how much this would go to satisfy your point, but
I do intend to answer the general question of creating a widget, putting
it in an XVT window, and handling its related callbacks. I won't know the
results for a while, since I wont be doing that work until next month.

Geoff Thompson
independent software consultant