Path: utzoo!attcan!uunet!snorkelwacker!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!+ From: Christian.Molick@CS.CMU.EDU Newsgroups: comp.windows.x Subject: Random toolkit issues Message-ID: Date: 26 Jul 90 18:51:05 GMT Organization: Carnegie Mellon, Pittsburgh, PA Lines: 44 In the Athaena and Motif toolkits, buttons that perform some simple action when pressed and widgets that maintain a state and toggle when pressed are two very different widgets. Is this really such a good idea, though? The only really big difference between these seems to be that toggle widgets have radio group code included with them, but this seems like more than people need for their toggle widgets. Personally, it seems like a better choice to make a button widget that has the option of toggling and a radio button widget that can be radio grouped with others. Comments? I have had only very limited contact with the Motif toolkit, but the use of managers and gadgets seems to be a very usefull. Is there any chance that future Athaena toolkit releases might include similiar options? Finally, "3D" look and feel seems to be really popular in toolkits these days, but do these toolkits really support a 3D analogy? The Motif style guide, if I remember, said something about pressable objects being differentiated from nonpressable objects by a raised edge. If this is the case, then how come Motif menus show raised edges only when individual items are selected? Wouldn't it make more sense to have all selectable/pressable items throughout the interface be indicated by a raised edge, then use a highlighting mechanism to call attention to armed/highlighted buttons. Furthermore, if 3D is the thing, then wouldn't it be nicer to highlight buttons with a lowered surrounding area, as the default buttons in Motif dialog boxes? This would give even the highlighting a 3D look without having to start buttons and menu objects flush like unselectable labels. Items could then become unselectable by not having raised edges, and the default selections could be differentiated by having borders of varying thickness, making them appear as larger buttons. Come to think of it, aren't most look and feel issues independant enough from code that you could start of with a simple/primitive widget that knows how to draw itself given foreground and background colors and a border width. This widget would have highlighting and selection actions built in so that you could use different versions depending on your own look and feel preferences. Hmm. Anyway, I was just having some general thoughts on toolkit issues and thought I'd throw them into the fray for consideration. (Please don't flame me or anything!) ChristianM