Screens In the 2deg.net File Manager
------------------------------------

There will be screens in the 2deg.net editor. Different functionality results in different parts of the file needing to be implemented. We have some functionality from the past. I have written my BM paper. I have specifically hand-written it, although it was also typed.

Frames are one thing that the editor should implement. The file type name used for the graphic goes on the end of the file as .egg, and when referred to it should be capitalized. That's the case with PNG, too.
This might not be an official file type commonly seen in systems. It's just the type of file we're using for our editor.


I'm writing this in different files so you can read it sequentially with the order of files decided by the website when it outputs files in the directory. It could be typed as a book, all in one document. Thus, I've given names to different parts, based on what subject I might want to get into. But, these individual pages are not necessarily stand-alone.


Different screens and different frames within a BM will be used.
The screens in the editor allow different functionality.
The frames in a -- newly named -- EGG will show different frames sequentially on the screen when they are being placed.

The old term for placing a Bit Map was map (verb). Perhaps for Egg, we will want to use the word place.

When an Egg is placed, the previous Egg is saved in it's structure. When it is removed, the previous save information is written to that location on the map.
The map is the image on which others are placed.

The Egg is saved in system memory. It's read into memory from a file.


Screens
-------
Controls will be used to access the screens of the 2deg.net editor. All controls will be accessible using a controller.


Connecting a Controller
-----------------------
A controller can be used on an Android device, or a computer. If the controller is recognized by the system it should be able to be recognized by the web browser, so that it can be used with the JavaScript Gamepad API. Linux operating systems might only be able to recognize the Xbox 360 controller out of the box, while Windows PCs handle the task much better. There are peripherals you can buy for your phone, which is probably going to be my chosen method of using the editor. Although, I'm not entirely sure. I might like it once I try it out with my PC. It could be like using a TV.


4 to 3 Aspect Ratio Screen Area, and 4 to 9 Menu
------------------------------------------------
The screen area will be placed in the center of the screen. Mobile displays might be wider than 16 by 9, but the size of the screen when the menu is open along with the screen area will be 16 by 9. The screen area will not be offset by the opening of the menu if there is room for it to be opened without moving the screen area to the left. The menu opens on the right.
The menu can be opened over top of the screen area if the screen area is not wide enough to show them both. The menu cannot be open while the screen area is functioning. That is the case with that implementation. It would be possible to have the menu open if the screen area was shrunk, if you needed to have the menu open on a smaller device AND have screen functionality with it open.
At first, we will try to be able to use the editor without having the menu open, but if it is needed we can implement it later.


What Type of Screens Will There Be?