🚀 go-pugleaf

In article <1991Jun21.183405.26015@colorado.edu> thompsog@spot.Colorado.EDU (THOMPSON GEOFF) writes:
>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
XVT Conference?  When, where?

>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.

My problem with XVT in this respect (I have other problems in other
respects :-) is not adding arbitrary widget children - but adding
widget parents.  XVT, like the PC toolkits it started on, has no
concept of geometry management.  Everything is based on an X/Y
coordinate system (many IDTs also have this flaw).  One of the
great thing about Motif (and most other Xt-based toolkits) is that
I can specify a very complex interface without ever once caring about
the size of fonts or other objects.  Everything can be layed out
in a relative manner.  If the user changes the font (or language!)
it doesn't matter - it just works.  However I am not aware of any
virtual toolkits which allow you to take one of those manager widgets
(Table comes to mind) and put their "virtual" widgets inside of it.

-- 
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.