kyroschow / basementsandandroids Goto Github PK

New plan: GameState on the server, JSONObject in the client. This is much more efficient, and plus we only have to store json strings in the database.
Also, when we render the game we just need to read off the JSONObject. There's no point in serializing and de-serializing @hedgey579. We don't even need Klaxon.
Refer to #3 for details.

If the model classes are located in core, then how would we do the Room database instead? The major problem is about the annotations on the instance variables.

The current structure of the Game class limits us to a single screen app. By isolating the logic components and refactoring the Game class to be a KtxScreen rather than a KtxGame<Screen> while simultaneously relegating the view code to the Application class, which will become the new KtxGame<Screen> we can improve readability and actually run the app.

I have migrated the server to a new project: https://github.com/TheCompSciNoob/BnaServer
We need to remove the server module and all the Kotlin/JS dependencies.
This might even be related to #1

https://github.com/TheCompSciNoob/BasementsandAndroids/blob/58618a014ee8052e178d663c7489fe4aaefd068e/app/src/main/java/com/example/chichow25/basementsandandroids/repo/retrofit/DndApi.kt#L13

We need to move the android specific backend code (i.e. retrofit, room) from master_deprecated to libktx_master

Nuke it from orbit

possibly introduced by 893b5b8

now git workin'

Everything is in a JSONObject now, so we don't need to parse JSONs to model classes anymore.
https://github.com/TheCompSciNoob/BasementsandAndroids/tree/libktx_master/core/src/com/bna/game/model

My university technical writing course has an assignment which involves editing documentation on GitHub repositories as practice in real world settings. Edits may involve aspects like style, structure, and concision. Existing style guidelines would be taken into account. The following is one of the resources I would be using:

https://jacobian.org/writing/technical-style/

Would anyone mind if I add or propose edits to documentation in this repository? It would really help me out!