5 ms·

Did you want the MS job? I mean, I could figure out how to make things overlap without repainting, and I'm a 4-year-old child.

• DanBC 12y ago
  Could you draw overlapping things without repainting using 1985 technology? That is, an IBM PC running at 4.77 MHz; with 128 KB of ram (or 640 KB if you're lucky). The OS would have been dos at something like version 2.x Some people[1] used Wordstar as their text editor. You had limited multitasking -- TSRs maybe. I'm not sure what programming language they used but possibly Microsoft C and assembly. [1] http://www.charlespetzold.com/etc/windows1/ http://www.charlespetzold.com/etc/windows1/
  • csixty4 12y ago
    To add a little more color to this, you had to be able to quickly repaint just a region of a window. And you don't have a bitmap of the window's current contents because that takes up RAM and you'd need CPU time to update a copy every time the window updates (slowing down any animations). I don't know how it's handled these days, but when I was first playing around with Win32, you'd receive events telling you a region of your window was invalidated. You were expected to figure out what controls and images belonged in that region and just repaint those items because of the CPU load.
    • lilred 12y ago
      I'm pretty sure Java's Swing uses a similar approach.
      • wmf 12y ago
        Sure, because that was the obvious standard technique in 1996. But for it to become the standard, someone first had to invent it. (And Swing in 1996 probably ran slower than Mac OS in 1986, despite Moore's Law.)
  • zw123456 12y ago
    Yes, and it was trivial to do. http://en.wikipedia.org/wiki/Graphical_Environment_Manager http://en.wikipedia.org/wiki/Graphical_Environment_Manager pre-dated windows on the same HW !
    • deleted 12y ago
      [deleted]