groundh0g / gamedevutils.com Goto Github PK

It's been quite a while since I've worked on this project. But life has settled down a bit and I'd like to pick up where I left off. I want to share my goals for the next version, and solicit your feedback on what you'd like to see today, and tomorrow.

The current version of the sprite packing application is v0.2.0. The new version will be 0.3.0 and will have the following goals:

1. Replace vanilla JavaScript and jQuery static webpage logic with ReactJS.
2. In addition to the static page, include cross-platform desktop apps using ElectronJS and cross-platform command line apps using NodeJS.
3. Optimize the sprite packing logic by reducing the number of times the logic executes.
4. Maintain project file compatibility with the original version of the static webpage.
5. Implement rudimentary linting and automated testing, with a stronger focus on the same in future versions.
6. Identify missing features and/or unimplemented placeholder features (e.g. sprite aliasing?).
7. Properly configure HTTPS support for the GameDevUtils.com website.

So. What do you have in mind for the app(s)? Have I laid out a decent roadmap, or have I made some glaring omissions? Leave a comment to share your thoughts!

— groundh0g

Open Project for Web:

• User clicks Open on main toolbar.
• User is prompted to save changes, if any.
• User selects Project to load.
• Serialized project data loaded as blob.
• Blob, callback method, and app constants are passed to Core Lib.

Open Project for App:

• User clicks Open on main toolbar.
• User is prompted to save changes, if any.
• User selects Project to load.
• Serialized project data loaded as blob.
• Blob, callback method, and app constants are passed to Core Lib.

Open Project for CLI:

• User specifies Project file on command line.
• Serialized project data loaded as blob.
• Blob, app constants, and do-nothing callback method are passed to Core Lib.

Common code in Core Lib for all platforms:

• Blob converted to js object.
• New Project instance created.
• Images array is stored separately, replaced in Project with empty array ([ ]).
• Js object analyzed, then loaded into the Project instance based on app version.
• Images array is moved back into project.
• Images populated with metadata.
• App callback is invoked when Project is ready to render.