BaseGame naming

[spydon]

Since Game and BaseGame will be components (after #906) and Game now has some more features than it used to have @st-pasha suggested that its maybe time to change the name of BaseGame to something more representative.

[spydon]

@flame-engine/flame-colab @st-pasha for visibility

[st-pasha]

My suggestion was FlameGame, similar to how we now have OxygenGame

[spydon]

It is now named FlameGame (and Game is a mixin instead of a class) after #906 was merged.

[erickzanardo]

Before, Game and BaseGame differ as BaseGame as a component based game, now both are components, what are their difference now? Asking so I can think better about this haha

[spydon]

BaseGame is still a bit more opionated, it has:

• the Camera
• you can handle priority changes for the components in there
• prepares the components by checking a lot of asserts and resizes it for the first time

Maybe they could be merged to one, I'm not sure if that would cause any problems for Oxygen.

[wolfenrain]

I am mostly concerned that it will add more code at runtime when "everything" moves to Game, especially if some people don't use it. Not sure how the Dart tree shaking handles methods on class instances that are not used.

But apart from that, anything that "forces" people to use FCS and related functionality will be breaking for Oxygen I guess, so to prevent that I would opt for having it still separate where possible :-)

Another good reason to keep it separated would be what @spydon said about BaseGame, it is opinionated and that has the pro that people can still do other "fancy" stuff on Game itself.