Could somebody outline how to set up a JUCE application that follows MVC?
I have watched a video from Vlad Voina in which he strongly advises to adopt an MVC approach for building the UI. The link is here : https://www.youtube.com/watch?v=YW1HS-hQY78&t=1656s
Unfortunately, the presentation offers no insight into how to wire controllers and views together or how to implement the boilerplate code that would be necessary to separate the code into views and controllers. The small examples of code he shows have been reduced for the sake of brevity and don’t provide any insight into how they fit together.
I would really like to follow an MVC architecture and I have good experience with it when building .NET applications - but then most of the plumbing is already done for you.
It seems to me that the
Main Window that inherits from
DocumentWindow appears somewhat like a typical controller - it resolves the
setContentOwned and houses the logic for
MainComponent houses much of what I would consider belongs to a view - layout logic,
resize. However, it also includes aspects that I consider should be part of the controller such as
Does anyone follow a conventional MVC design with JUCE? If so, how are you doing it? How do you route between different views and controllers?