pladams9 / okolina Goto Github PK

• What should be logged?
  • What level of detail?
  • What different categories (tables)?
• Clean up?
  • Scheduled or based on volume?
  • Delete records or archive in some way?

Create a clean, consistent way to access the database from the server-side scripts (primarily ajax.php and admin.php).

Current thinking is:

Use gulp

1. rollup to combine es6 modules
2. babel to transpile to es5
3. uglify to minify the final script

I believe gulp will need vinyl-source-stream and vinyl-buffer to work directly with these packages instead of resorting to gulp plugins.

Tile engine for displaying levels in the client. Fed an array of tile info, display tiles.

May need information such as:

• Solid/not solid
• Tile image
• Tile animation
• Layers?

• Button on the login screen
• Username, password, e-mail

To the controls area

• Username/password inputs
• Login button
• Welcome to Okolina message

Currently admin.php has the power to wipe everything away and start fresh. Although I like the idea of an auto setup, how should this be handled?

• How to keep the setup open initially, but closed/password protected after install?
• Should other admin settings be here as well?

Look into PHP installer tools: https://stackoverflow.com/questions/4388513/how-i-can-create-installer-for-website-php-mysql

Generate room based on biome (or other) data and size. Generated on server at request (a caching system would be important too).

There should be a simple and consistent way of making AJAX requests to the server.

Thoughts:

• Client should send something like { request_string, { data } }
• Server should send back { { result_code, result_string }, { data } }