Breaking the core in multiple controllers #88
Labels
No labels
0. Imported
1. Bug
1. Clean-up
1. Feature
1. Improvement
2. Deliverable
2. Epic
3. Duplicate
3. Invalid
3. Need investigation
4. Assets
4. Birb Core
4. Debug
4. Dependencies
4. Inputs
4. Lang
4. Scenes
4. Screen
4. World
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: epervier/epervier-old#88
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current system with a "core" object that only contain submodule isn't really usefull, and is vastly redudant with the love callbacks. It could be replaced by a set of core managers/controllers and utilities that would handle different aspect of the game and work together.
Breaking the coreto Breaking the core in multiple controllersOther linked work
-> The asset manager
-> Fusing data, options and gamesave
-> core/init.lua :: fuse with framework/init.lua
-> core/datas.lua :: fuse with core/options.lua, gamesystem/init.lua
-> core/debug.lua :: logger system, available globally
-> core/input.lua :: transform into a simple input-to-event-translator (maybe not available globally ?) and dispatch on different levels
-> core/lang.lua :: TODO (maybe become a ``_t("Nom Originel")`-type API ?)
-> core/music.lua :: become part of new asset manager
-> core/scenemanager.lua :: become scenes/manager.lua ?
-> core/screen.lua :: TODO
The gamesystem should also be transformed in maybe something like
in main.lua
( or call the function "game" to remind the old gamesystem. )