frontend packaging: discussing the details.

[PBJI]

---

We divide the front-end into two variety.

1. User mode: Only keeps the current state of the game and general options.
2. Research mode: Have full access and special panel to run simulations on back-end. This UI will be more dynamic in nature.

---

---

Specification for user frontend:

1. It will not contain the game logic but will only reflect the game state.
2. It cannot directly update the game state. but rather have controlled user inputs which will trigger API requests to update the game state in the backend.

That is it.

Game state:

• currentPlayer,
• currentMove,
• movesArray, etc.

Controlled user inputs:

• clickable cells,
• non-clickable cells,
• start game,
• undo, etc.

API request:

• send move for currentPlayer,
• read reply,
• undo move, etc.

---

---

ROUTINE for frontend development:

1. Specify the general options for user on game setup changes in backend.
2. Track bot experimental features and update the special panel for researchers to interact with these newly designed features.

---

---

UI DESIGNs for frontend:
Figma file for user and researcher interface design

---

---

TODOs (based on routines defined):

1. Setup boards and cells that can be clicked. (Game setup)
2. Setup api requests that sends user inputs like cell location and other metadata (player, name, etc.)
3. When receiving an update, accordingly change user interface.

---

[NitkarshChourasia]

I want to make it for, all levels.
Should I be assigned for packaging of this product?
For, Android, Webapp, and Pc builds?

[PBJI]

@NitkarshChourasia You are free to do that, as this is an open-source project, although it would be grateful if you do give due credits to the author in some way. Thank you.

[PBJI]

But one thing is, make sure the packaging part do take into account the dynamic nature of the backend. Backend will surely be developed with NodeJS and express. And it will be an API based application so you can be assured that no game logic will run on client side, so if you feel you can create frontend for various platforms then surely this would be great addition to the original scope of the project.

[NitkarshChourasia]

@NitkarshChourasia You are free to do that, as this is an open-source project, although it would be grateful if you do give due credits to the author in some way. Thank you.

I will just create and not publish it.
The author if want should take care of this.

[NitkarshChourasia]

But one thing is, make sure the packaging part do take into account the dynamic nature of the backend. Backend will surely be developed with NodeJS and express. And it will be an API based application so you can be assured that no game logic will run on client side, so if you feel you can create frontend for various platforms then surely this would be great addition to the original scope of the project.

I will start after the project here is like logically okay.

[PBJI]

Sure

But one thing is, make sure the packaging part do take into account the dynamic nature of the backend. Backend will surely be developed with NodeJS and express. And it will be an API based application so you can be assured that no game logic will run on client side, so if you feel you can create frontend for various platforms then surely this would be great addition to the original scope of the project.

I will start after the project here is like logically okay.

[NitkarshChourasia]

Ok, thanks for the clarification.

…

On Sat, 7 Oct 2023 at 17:43, Purshotam Bohra ***@***.***> wrote: Sure But one thing is, make sure the packaging part do take into account the dynamic nature of the backend. Backend will surely be developed with NodeJS and express. And it will be an API based application so you can be assured that no game logic will run on client side, so if you feel you can create frontend for various platforms then surely this would be great addition to the original scope of the project. I will start after the project here is like logically okay. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVTTXYBAYLC3U4L3PGDOOPTX6FBNTAVCNFSM6AAAAAA5WZ5RTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGY4TMMZRGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Nitkarsh Chourasia