In the 20 minute QuickTime movie below, Mark Smit demonstrates how MasterStudio allows us to build complex windows in minutes. Without using wizards and with no code duplication, applications become incredibly easy to maintain. At the same time, MasterStudio's controllers and managers add unprecedented user interface power.

The first half of the movie shows the steps required to create a window from scratch, starting with an empty library. In 10 minutes, you can build a completely functional window that manages employees, including dynamic context menus and printing. The single-point-of-definition concept allows you to fix mistakes in seconds, even after you create an application.

This Sneak Preview assumes Omnis Studio knowledge. MasterStudio consists of 100% Omnis classes. MasterStudio development is Omnis Studio development; although MasterStudio uses advanced design patterns and "pure" OO, there's nothing stopping developers from combining MasterStudio functionality with (possibly existing) code.

The movie may take some time before it starts automatically. Total file size is 13.6 MB. The movie can also be downloaded. Users of older QuickTime versions may receive a message during playback saying that new authoring components need to be downloaded.

The movie consists of real-time screen recordings, from which we have removed frames belonging to typos, stray mouse movements, and interlacing artifacts. Backgrounds appear white as a result of the heavy video compression we used. Voice-overs were added later. The first half of the movie includes all steps required to create the actual windows. The last half of the movie includes examples that were previously created. The movie otherwise gives an accurate impression of performance using MasterStudio 1.0 beta 9 on a 450 MHz PowerMac G4, comparable to a Pentium III at 500 MHz in real-life tests.

During the movie, Mark refers to "not requiring any code in window classes". This is because MasterStudio cleanly separates business logic (in table classes and associated list managers) from application logic (in contexts and controllers) and interface (in window classes and menus). This means that UI-specific enhancements could (and often should) still be coded in the window classes or fields themselves. Application logic is programmed in the "application context". Window-specific code is added to the "entity frameset delegates". Of course, any of MasterStudio's controllers can also be subclassed for the ultimate in development power, especially because MasterStudio uses the factory design pattern for most things that developers may want to change in the future.