In a mere two days, I've managed to design the visuals and implement basic functionality for Interface3. Perhaps this indicates that, at long last, I have crafted a balanced interface - one that looks good but isn't high-maintenance. Already I3 has full rendering capabilities, bar post-processing. With the features of I3 expanding rapidly, I3 could well overtake I2 in functionality by the end of the week.

Here's a screenshot of the early GUI.

Much of the interface will probably remain unchanged since I like this design. The simplicity of the interface adds to the feeling of speed and ease-of-use. As in Interface2, a tile-button scheme allows the user to easily load plugins into module slots. The plugin selection window (not shown) in I3 improves on that of I2, which could only display four plugin thumbnails at a time. I3 can display twenty-five. I've also doubled the number of generative tiles in the interface for extra power.

Perhaps the most remarkable thing about this screenshot is the "renderer" tile. Indeed, no previous interfaces have treated the renderer as a module, but I think it's time to make a shift. There's simply no reason not to treat a renderer like a plugin since the same basic principles of configuration, execution, and interchangeability all apply to renderers just as they do to core and generative plugins. Furthermore, this will solve the problem of having to find space in the main interface for all the rendering configuration options.

If the first two days of Interface3's existence provide any indication of how things will pan out in the long run with this new interface, mGen has a lot to look forward to.