nmagerko / inertia Goto Github PK

The system layers of a simulator like this will be somewhat complex. We will need to account for multiple layers, threads, and the like in order to ensure that the simulations are, at the very least, functional.

A considerable amount of research will need to be completed in order to begin designing the "boilerplate" code. Outside libraries will be noted here, along with any special dependencies. The practicality of each will then be debated.

A final design will need to be posted and agreed upon here before this issue may be closed.

Before we get any code written, we should make sure that we have a solid understanding of what we want our user interface to look like. This includes all of the components that a user sees on the UI, and probably small blurbs about what should happen in response to specific actions as well.

This may include using libraries outside of the JavaX Swing libraries, such as the OpenGL libraries. Research will be required to figure out whether these extra libraries are practical to use, and/or any special dependencies that come along with them (e.g., other libraries or the incorporation of different languages).

We can discuss any uploaded wireframes here, and close this issue once a design has been decided upon.

Create the UI, based on the agreed-upon wireframe (see issue #1). To keep the implementation manageable, we will try to modularize the UI setup into two parts; this will be the first part.

During implementation, a discussion of obstacles should be held here. Additionally, before this issue is closed, there should be a mutual agreement that the UI (with or without any deviations from the wireframe) will do what we need it to do.

Regardless of whether or not it is completed in conjunction with issue #2, the UI should have event listeners attached to it. These will (probably) not have any service-layer methods to call by the time of this issue's completion, which is fine; we are only looking to complete a "dummy" interface at this point.

Any service-layer calls that need to be made to ensure successful completion should be stated in a separate issue, which references this one. Note that multiple service-layer calls can (and should) be listed in this single, new issue, if needed.