Community
Participate
Working Groups
AW (23.03.00 20:10:27) SWT 0.39: While trying to "beautify" VAME for Motif I've got the impression that the Motif implementation (for obvious reasons) lacks some "coordination" between the visual elements. "Coordination" means: It should be possible to compose larger controls from single controls without having to know how a specific control looks on every platform. This requires careful upfront tuning of sizes, borders, gaps so that things line up nicely, double borders are avoided etc. and this all without too many tweaks in client code. A classical example is how to align a label and a button so that the text baselines line up independent of the size of both controls and the fonts used. I'm not asking for all that right now, but it would be nice if we can state some basic invariants, which are independent from a platform. AW (27.03.00 10:59:33) See first: 1FSA2CS: SWT:DCR - Visual coordination of SWT controls! (Tree w/o Border) inside (Composite w Border) == (Tree w Border) A borderless Tree (or Text, Table, etc.) as the single child of a Composite with border has identical appearance as a Tree with border. True on all platforms? (If not then I'm in trouble because I cannot write an adorned viewer whose visual appearance matches the native one; right now this seems to be true on Windows but not on Motif) KH (4/11/00 9:36:42 AM) Added AW's comments from March 23 and moved 1FSA2CS to ZZ-Trash. McQ (27/11/2000 12:56:44 PM) - To some extent, appearance differences between platforms are simply a *direct* outcome of our decision to use platform widgets with as little "playing with defaults" as possible. We still strongly believe that as soon as you (actually, we) start changing the defaults which the platform is providing for the widgets, we get in to trouble. The perfect example of this is the well known "widgets don't change colour when you change the Appearance control panel values" problem, where if you explicitely set window colors, then the o/s won't update them for you when users request it. In all honestly, we don't have time to deal with these issues in this cycle anyway. Moving to inactive.
We have done all that we can for the Motif L&F issue (turned on "thin thickness" flags, etc.)
