How forexample/testapp works
Main Components
• Application Entry Point – Represent the “main.mm” file as the starting point. This initializes the app.
• App Delegate – Add a node for the AppDelegate (AppDelegate.mm and AppDelegate.hpp), which manages the application lifecycle.
• View Controllers – Include a node for the main ViewController (ViewController.mm and ViewController.hpp), which acts as the primary controller for handling user interactions.
• Storyboards – Clearly illustrate the two UI definitions as separate components:
• iPad Interface (MainStoryboard_iPad.storyboard)
• iPhone Interface (MainStoryboard_iPhone.storyboard)
• Build & Configuration – Represent build configurations and scripts (build.sh, CMakeLists.txt, plist.in) as part of the development and deployment support system.
Relationship and Interactions
• A connection from the AppDelegate to the appropriate View Controller(s), indicating that the app delegate is responsible for initializing and transitioning to the View Controllers.
• Link the View Controllers with the respective Storyboard files, showing that the UI layouts and transitions are defined in those files.
• A connection from the source code and configuration files (CMakeLists.txt, build.sh) to the overall build process, highlighting the integration of development tools.
Architectural Patterns and Design Principles
• Standard iOS Model-View-Controller (MVC) pattern:
• The Controller (ViewController) mediates between the UI and the underlying logic.
• The AppDelegate acts as the coordinator of the application lifecycle.
• Idea that the build scripts and configuration files support a continuous integration/continuous deployment (CI/CD) pipeline (as indicated by the presence of .travis.yml).