jhd@donuts0.bellcore.com (John D'Elia) (06/01/91)
Does anyone have experience converting character-based forms (e.g. 3270) into Motif forms. I have a series of 24x80 form definitions where each field is described in terms of x-y location, length, initial value, label, etc. I need to convert these into widget-based definitions. I assume the XmForm with XmLabel and XmText children would be the way to go, but it is not obvious how the Position/Attachment resources should be specified. Any help would be appreciated -- thanks in advance. John D'Elia
nazgul@alfalfa.com (Kee Hinckley) (06/01/91)
> Does anyone have experience converting character-based forms (e.g. 3270) > into Motif forms. I have a series of 24x80 form definitions where each > field is described in terms of x-y location, length, initial value, label, > etc. I need to convert these into widget-based definitions. I assume the > XmForm with XmLabel and XmText children would be the way to go, but it is > not obvious how the Position/Attachment resources should be specified. > Any help would be appreciated -- thanks in advance. I would use the Table widget or (if you don't mind wiring the font sizes) a bulletin board. Theoretically a bulletin board with the units in fontUnits instead of pixels would be perfect, but I'm not sure it works. 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.
kdg@world.std.com (Keith D Gregory) (06/03/91)
In article <910601114316.2440@sony> nazgul@alfalfa.com (Kee Hinckley) writes: >I would use the Table widget or (if you don't mind wiring the font sizes) >a bulletin board. Theoretically a bulletin board with the units in fontUnits >instead of pixels would be perfect, but I'm not sure it works. A question that has been buggong me for months (well, maybe I can say year(s) now): "Why does the Xm100TH_FONT_UNITS unitType act the way it does?" I don't want to say that it's brain-dead without knowing the reasons behind its implementation, but the decision to use the font size of an arbitrary resource -- which may bear no relation to any of the fonts actually used by the program -- seems a bit, ah, strange. It would seem to me that setting units in terms of the size of the font actually used by the widget could be quite nice. Especially by an application such as xfd (never mind that xfd already exists -- it's a good example). If correspondance between levels of the instance tree is a concern, put fontList into XmManager and XmPrimitive, and have children accept their parent's value by default (maybe XmPrimitive is stretching things a bit, but XmManager fer shure). Comments ... please? -kdg