Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!gatech!bloom-beacon!eru!hagbard!sunic!dkuug!resam!andrew
From: andrew@resam.dk (Leif Andrew Rump)
Newsgroups: comp.windows.open-look
Subject: Re: XView Programming Style
Keywords: XView
Message-ID: <1991Apr10.133100.15044@resam.dk>
Date: 10 Apr 91 13:31:00 GMT
References: <1991Mar13.193948.16328@sol.UVic.CA> <7207@ecs.soton.ac.uk> <1552@west.West.Sun.COM> <1991Apr1.200322.12740@cshl.org> <1573@west.West.Sun.COM>
Organization: RESAM Project Office, SAS, CPHML-V
Lines: 29

The problem with not having created the popup windows when the base window
is created is that the programmer must keep track on the states (inactive/
changed labels/...) on all the buttons/text fields/... It is manageable
but I'm quite sure that a OOP (C++ (God forbid)) could solve the problem.
- but why should we keep track on something the window system is fully
capable of handling? OK, OpenWindows is currently implemented in C using
OOP techniques so even the smallest instance use the full scale structure
(I haven't checked this but that is what I have been told) so the memory
usage is rather heavy but keeping the information twice sure doesn't help!

I'm interested in knowing if anybody out there has a description form that
keeps tracks on: which buttons/text fields/... change state on what action
and do changes to all the windows created even though they may be hidden!

I'll rather sacrifice some memory & speed for easy programming!


Leif Andrew


Leif Andrew Rump, AmbraSoft A/S, Stroedamvej 50, DK-2100 Copenhagen OE, Denmark
UUCP: andrew@ambra.dk, phone: +45 39 27 11 77                /
Currently at Scandinavian Airline Systems                =======/
UUCP: andrew@resam.dk, phone: +45 32 32 51 54                \
SAS, RESAM Project Office, CPHML-V, P.O.BOX 150, DK-2770 Kastrup, Denmark

		If it's broke, fix it (The MS-DOS way)
	    If it aint broke, don't touch it (The Unix way)
	     If you can't fix it, fuck it (The U-boat way)