4 March 2010
Development, Project Management, Consulting, Appeon, SAP, Whitepapers
Most of us don’t remember much about Windows Version 1 or 2. They were fairly basic windowing systems, and the primary issue was the lack of a multi-threaded, multi-tasking operating system to support a multi-tasking windowing desktop. To compensate for this, Windows developed a queuing mechanism that simulated multi-tasking in a single-tasking OS.
Windows really took off with Windows 3.0 in the 1990 timeframe. Still bootstrapped from MS-DOS, the primary user interface mechanism was a series of child windows with icons nested inside them (remember Program Manager, the forerunner to Explorer?) Clicking on an icon in a child window would either open a nested child window or launch a program. Programs were differentiated from Program Groups in this manner, and hierarchical menu systems developed in this way. One of the primary uses of Child Windows in PowerBuilder at that time was to mimic Program Manager.
Full Article: Updating Your PowerBuilder Applications for Today's World