How samuelasherrivello/rmc-umvcs works
Main components
– Controller (with further subdivisions for Commands, Events, and a base controller)
– Model (including data types, configuration data, and model locator)
– View (with base view implementations)
– Service (with base service classes)
– Context (the layer that glues actors together; includes BaseActor, BaseApp, etc.)
• Editor Extensions – Found under “RMC UMVCS/Editor”, these components provide Unity Editor-specific functionality. They mirror parts of the runtime structure but are meant for tooling and configuration within the Unity Editor.
• Core Utilities – Additionally, there are supporting directories for Components, Attributes, Design Patterns (like Singleton), and PropertyDrawers that are used throughout the framework.
• Samples & Tests – Although not “core” to the architecture, the Samples (especially the MyBouncyBallExample) demonstrate the practical implementation of the MVCS pattern. The Tests confirm that the architecture adheres to expected behaviors.
Out the relationships and interactions
• That the Context layer acts as an orchestrator between different modules, with the ability to coordinate or route messages/commands.
Architectural patterns and design principles
• Also, incorporate a section for “Utilities” (attributes, components, design patterns) which serve across multiple modules.
• If needed, add a note on external integration: although this package is self-contained, it is installed via npm or Git URL into Unity’s Package Manager. You might add a small “Package Manager” or “External Package” label to indicate this.