Plugin's MVC and the editor lifecycle


#1

Hi.

Trying to build a decent plugin I’ve been pondering about some design issues:

  1. How and whether to implement an MVC framework using the AudioProcessor and the AudioProcessorEditor.
    (a previous MVC thread http://www.rawmaterialsoftware.com/viewtopic.php?f=2&t=1386&hilit=mvc )

  2. Whether to keep Juce’s default behavior of deleting the editor on each close() or to keep it in memory.
    (a previous editor lifecycle thread http://www.rawmaterialsoftware.com/viewtopic.php?f=8&t=4683&hilit=delete+editor )

My decision was to keep Juce’s default behavior of deleting the editor and by that enforcing myself to create a stateless GUI.
All the state data will be stored in the processor and the MVC demarcation will be:
processor = Moder + Controller
editor = Controller + View

If you thing differently feel free to comment.