Design of software · 07
The IDE That Invented RAD
Look at any modern interface builder, Visual Studio's WinForms designer, a XAML surface, a web page editor, a no-code canvas, and you are looking at a descendant of the Visual Basic workspace.
01The workspace, room by room
The Visual Basic environment arranged itself around four dockable panes, and the arrangement was so correct that it barely changed across the product's entire classic run (a run traced in the complete history.
- The Toolbox) a palette of controls (text boxes, command buttons, timers, data grids) that you dragged onto the form. New controls arrived over the years as OCX and ActiveX components, and VB5 finally let you build your own.
- The Form Designer (the canvas itself), covered in the famous dot grid that guided alignment. This was the heart of the RAD promise: your interface was a drawing, and the drawing was the program.
- The Properties window: a two-column grid listing every property of the selected control, editable in place. Caption, colour, font, position: half of application development became data entry.
- The Project Explorer and Code window (the file tree of forms), modules and classes, and the editor where the other half of development happened, one event procedure at a time.
The gesture that tied it all together was the double-click. Double-click a button and the IDE generated Sub Command1_Click() (the empty handler), waiting for your logic. Interface first, behaviour second, boilerplate never.
02The debugger as a way of life
The workspace's less photographed half was its debugging kit, and veterans remember it fondly. The Immediate window was a command line into your running program: interrogate a variable, call a function, change a value mid-execution, no recompile required. Breakpoints paused execution on a line; F8 stepped through procedure by procedure; the Watch window tracked expressions as they changed. Set against the edit-compile-link-run purgatory of contemporary C development, this felt less like a tool and more like a teleporter.
Under it all sat the choice of build modes (compact p-code interpreted through the runtime, or true native compilation from VB5 onward) a trade-off explained alongside the rest of the compiler anatomy in the VB6 deep dive. The IDE rewarded keyboard fluency just as strongly: shortcuts, rapid edits and immediate feedback made speed visible before a project ever compiled. Modern browser typing tests measure that same physical layer of programming work without tying the exercise to one editor.
The form designer taught a generation the most important idea in modern software: that the interface is a first-class object, not an afterthought rendered by code.
03Where the design came from
The workspace descended directly from Ruby, the visual shell builder Alan Cooper brought to Microsoft, the acquisition story is told in our Cooper profile. Cooper's insight, inherited wholesale by the product, was that the properties-and-controls model beat the code-first model for everyone except professional interface programmers, and there were not many of those. Microsoft's contribution was scale: help files, wizards, sample projects, a macro recorder culture inherited from the Office side (visible to this day in VBA), and eventually an entire tools industry growing OCX controls to fill the Toolbox.
04The lineage
Follow the descendants and the family resemblance is unmistakable. Visual Studio's WinForms designer, the direct heir, palette and property grid and all, still ships today and remains a workhorse for the VB.NET applications described in the Great Split analysis. The WPF and XAML designers, web flow builders, dashboard editors, and every "drag a component onto a canvas" tool in between are repeating the grammar VB codified in 1991: a palette of controls, a design surface, an inspector of properties, and an event to write code into.
Even the modern no-code movement (website builders, automation canvases, app editors that promise programming without programmers) is, at the level of interaction design, an extended remix of the same idea, usually without the courtesy of a credit. The depot keeps the receipts: the patterns that ran through all of this are preserved and annotated in the code depot, and the whole chronology is pinned in the timeline.
This very site tips its hat: the dot grid of the form designer and the window chrome of the classic IDE are quietly woven into VB Depot's own design. Software history deserves a home furnished in its own idiom.