 |
 |
|
|
| Changed: |
<
< |
This layer is the GUI as would typically be defined. Representations of data classes from the Pjre Engine are displayed to the user, and opportunities are given to the user to view and change parameters. Any changes are made by updating data classes in the Pjre Engine?. File IO is performed by making the appropriate call to the Pjre Engine layer, which is then responsible for making the appropriate IO call(s). Tabular, 2D and 3D views of arbitrary table sizes would be nice. A web/html oriented GUI might be a neat idea too. The Pjre UI? class is the container class for this layer. (blundar)
| >
> |
This layer is the GUI as would typically be defined. Representations of data classes from the Pjre Engine are displayed to the user, and opportunities are given to the user to view and change parameters. Any changes are made by updating data classes in the Pjre Engine?. File IO is performed by making the appropriate call to the Pjre Engine layer, which is then responsible for making the appropriate IO call(s). Tabular, 2D and 3D views of arbitrary table sizes would be nice. A web/html oriented GUI might be a neat idea too. (blundar)
|
| Changed: |
<
< |
The Pjre Engine is composed of the classes responsible for representing data and the methods for identifying, interpreting and manipulating it. It also is responsible for abstracting Load/Save/Update type IO calls based on the method used to acquire the current working data. Pjre ROM? class is the container class for this layer. (blundar)
| >
> |
The Pjre Engine is composed of the classes responsible for representing data and the methods for identifying, interpreting and manipulating it. It also is responsible for abstracting Load/Save/Update type IO calls based on the method used to acquire the current working data. (blundar)
|
| Changed: |
<
< |
The Pjre IO layer is responsible for opening ROM files from disk, retrieving ROM information via RTP connection, and/or any other method of ROM storage. Any and all low-level IO manipulation belongs here. Pjre IO? class is the container class for this layer. (blundar)
| >
> |
The Pjre IO layer is responsible for opening ROM files from disk, retrieving ROM information via RTP connection, and/or any other method of ROM storage. Any and all low-level IO manipulation belongs here. (blundar) |
|
|
| Added: |
>
> |
%META:TOPICINFO{author="ROM" date="1081966320" format="1.0" version="1.1"}%
%META:TOPICPARENT{name="JavaRomEditor"}%
I see layers as being key to this project working, both from a development and functional perspective.
(blundar)
What I mean by this is that there are various units of code (layers) that can communicate only with the layers immediately above and below. Interfaces between layers are well defined and documented. The top "layer" will be input - usually user input(potentially automated) This "layer" then interacts with the top layer of the software. Below the bottom layer of the software lies the actual permanent manifestation of the data itself, which initially will be a file on the user's computer (but could also be a PGMFI RTP connection or a ROMulator). (blundar)
Proposed Layers:
User Input (pseudolayer)
Input represents the top layer. As this is initially intended to be a ROM editor, user input will probably be the case. Any automated input could potentially talk directly to the Pjre Engine. (blundar)
Pyre Gui Layer
This layer is the GUI as would typically be defined. Representations of data classes from the Pjre Engine are displayed to the user, and opportunities are given to the user to view and change parameters. Any changes are made by updating data classes in the Pjre Engine?. File IO is performed by making the appropriate call to the Pjre Engine layer, which is then responsible for making the appropriate IO call(s). Tabular, 2D and 3D views of arbitrary table sizes would be nice. A web/html oriented GUI might be a neat idea too. The Pjre UI? class is the container class for this layer. (blundar)
Pjre Engine Layer
The Pjre Engine is composed of the classes responsible for representing data and the methods for identifying, interpreting and manipulating it. It also is responsible for abstracting Load/Save/Update type IO calls based on the method used to acquire the current working data. Pjre ROM? class is the container class for this layer. (blundar)
Pjre IO Layer
The Pjre IO layer is responsible for opening ROM files from disk, retrieving ROM information via RTP connection, and/or any other method of ROM storage. Any and all low-level IO manipulation belongs here. Pjre IO? class is the container class for this layer. (blundar)
Representation layer (pseudolayer)
In this psudolayer, representations of ROMs exist. These include but are not necessarily limited to files on disk, running images in a car accessed via RTP, running images in a car accessed via ROMulator and portions of a ROM as present in import/export files or hevaily modified ROMs |
|
Copyright © 2002-present by the contributing authors. All material on this collaboration platform is the property of the
contributing authors, and is covered by the Non-Commercial Share-Alike License unless explicitly stated otherwise. |
|