Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refactor: should Client and ClientGame become one? #58

Open
Razish opened this issue May 21, 2017 · 0 comments
Open

Refactor: should Client and ClientGame become one? #58

Razish opened this issue May 21, 2017 · 0 comments
Labels
Category: Meta Priority: Low Type: Question

Comments

@Razish
Copy link
Owner

Razish commented May 21, 2017

Or should a ClientGame [naming] be instantiated, used and destroyed as logically makes sense.
There are benefits of isolating the state of an active game and reducing dependencies.
There are drawbacks too; accessing necessary data/functions becomes more obtuse/indirect
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Category: Meta Priority: Low Type: Question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Razish