d2d Activity Component Architecture

Rationale

The d2d Activity-Component architecture is a hybridization of the Android Activity structure as well as the Java Swing component-based GUI builder. Activities essentially function as Android Activities while components function almost exactly like Java Swing components. Activities are useful for breaking the life-cycle of the program into specific tasks or stages while components are useful for handling smaller specific sub-tasks. One way to visualize the difference would be to think of the activities as something that happens in a section of time whereas a component happens in a section of space. For example, an activity might be the game's splash screen or options screen whereas some components might be the buttons or text fields on those activities. A display can hold an activity, and an activity can hold various components. Of course, the entire Activity-Component architecture is not forced and specific parts can be avoided if not needed, but this architecture is highly recommended as it can help structure an application cleanly and is time-tested.

Using Screens

TODO

Using Components

TODO