The main method calls the Dynamite class functions, which will eventually own all data needed to run the app, from the application state to the UI setup. Currently we are just initializing the UI with a new editor context on each run (later we will want to load a context), so Dynamite only needs to set up the UI. The UI class owns the menu bar, central canvas, palette (which is where we will integrate Kevin's code) and the multi-purpose panel (also Kevin).
To test:
The edited CMake file reconfigures the build-release folder that will allow you to run the app.
The main method calls the Dynamite class functions, which will eventually own all data needed to run the app, from the application state to the UI setup. Currently we are just initializing the UI with a new editor context on each run (later we will want to load a context), so Dynamite only needs to set up the UI. The UI class owns the menu bar, central canvas, palette (which is where we will integrate Kevin's code) and the multi-purpose panel (also Kevin).
To test: The edited CMake file reconfigures the build-release folder that will allow you to run the app.