-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathTODO_Architecture.txt
More file actions
43 lines (23 loc) · 1.52 KB
/
TODO_Architecture.txt
File metadata and controls
43 lines (23 loc) · 1.52 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
============== Present Tasks =============
TODO:
Click listener on the map layer to close the infoWindow if it is open
buildings can only be placed on certain terrain types
Tech tree
--buildings required to unlock upgrades
--buildings will need a concept of requirements for being built --done, maybe with a refactor to use a config object rather than a callback?
--non-linear tech-tree for citizen upgrades
--side effect is that this will push for incorporating even more territory
Incorporate art assets
=========== Ideas / Future ==========
Need to move on toward enabling the upgrading of citizens
daily/random events
hint/advice feature on announcements page
Consider migrating to an actual build system (webpack/babel w/ Grunt?) -- thus, an npm background, which will need to come eventually anyway if we're going to have persistence
AMD To ES5/6 npm plugin would be very helpful.
Build UI components --- I suppose I should wait on Barry before I bother with that, though? yes. everything can look like crap for now.
but down the road, I should definitely abstract UI into reusable/atomic classes
============= Saving ============
-- want to minimize the amount of data needed to regenerate the exact game state.
-- need not pass any logic
-- if we want to consider saving a possibility, then we will need the game object to be able to track which events have triggered / how many times.
--Wire up with firebase or using cookies?