Description:
Update README and TODOs.
Commit status:
[Not Reviewed]
References:
Diff options:
Comments:
0 Commit comments
0 Inline Comments
Unresolved TODOs:
There are no unresolved TODOs
Author
-
| @@ -107,6 +107,8 | |||||
|
|
107 | └── **TODO.taskpaper** Tasks, feature requests, and bugs. |
|
107 | └── **TODO.taskpaper** Tasks, feature requests, and bugs. |
|
|
108 | ``` |
|
108 | ``` |
|
|
109 |
|
109 | ||
|
|
|
110 | Right now, the largest parts of the code are `UI/`, `Engines/`, `FNAGame.cs` (which | ||
|
|
|
111 | still contains a lot of drawing code), and `Simulation.cs`. | ||
|
|
110 |
|
112 | ||
|
|
111 |
|
113 | ||
|
|
112 | ## Acknowledgements ## |
|
114 | ## Acknowledgements ## |
| @@ -101,6 +101,7 | |||||
|
|
101 | Structure: |
|
101 | Structure: |
|
|
102 | - Add modes @milestone(5: Events) |
|
102 | - Add modes @milestone(5: Events) |
|
|
103 | - Refactor stuff out of FNAGame |
|
103 | - Refactor stuff out of FNAGame |
|
|
|
104 | At this point, virtually everything in FNAGame is setting up key Engines or doing drawing | ||
|
|
104 | - Saving @prototyped @milestone(4: Beginning) |
|
105 | - Saving @prototyped @milestone(4: Beginning) |
|
|
105 | - Encompass @maybe @done(2021-04-03) |
|
106 | - Encompass @maybe @done(2021-04-03) |
|
|
106 | Currently thinking about a hybrid model where the Simulation class receives a lot of the events from Encompass. so things like Events, Contracts, and Research agreements are handled by Encompass. Perhaps Input, too? |
|
107 | Currently thinking about a hybrid model where the Simulation class receives a lot of the events from Encompass. so things like Events, Contracts, and Research agreements are handled by Encompass. Perhaps Input, too? |
| @@ -111,7 +112,19 | |||||
|
|
111 | Technically done |
|
112 | Technically done |
|
|
112 | - Decide how to handle ImGUI ref parameters |
|
113 | - Decide how to handle ImGUI ref parameters |
|
|
113 | Basically have to decide whether to embrace its style or go toward a more functional approach |
|
114 | Basically have to decide whether to embrace its style or go toward a more functional approach |
|
|
114 | - Change conversation to use ImGui @milestone(5: events) |
|
115 | - Add Ink @maybe |
|
|
|
116 | - Add NuGet package | ||
|
|
|
117 | - Load .Ink files | ||
|
|
|
118 | - Rewrite Dialog to show Ink | ||
|
|
|
119 | - SetTextVariable also sets variables within Ink | ||
|
|
|
120 | Technically doesn't have to be done this way, but having what would essentially be separate namespaces for Tracery variables and Ink ones seems confusing. | ||
|
|
|
121 | - Integrate with Tracery | ||
|
|
|
122 | COuld run everything through Tracery or could create an Ink function that calls Tracery | ||
|
|
|
123 | - Change conversation to use Encompass @milestone(5: events) | ||
|
|
|
124 | - Refactor out common ImGUI patterns | ||
|
|
|
125 | - Tooltips | ||
|
|
|
126 | - Status indicators (not yet implemented) | ||
|
|
|
127 | By status indicators, I mean putting an icon on, say, the Contracts button to indicate a contract is about to expire. | ||
|
|
115 | - Rearchitect to avoid giving everything access to Simulation |
|
128 | - Rearchitect to avoid giving everything access to Simulation |
|
|
116 | - Add a start screen @milestone(4: Beginning) @done(2021-06-08) |
|
129 | - Add a start screen @milestone(4: Beginning) @done(2021-06-08) |
|
|
117 | - Add a create park dialog @milestone(4: Beginning) |
|
130 | - Add a create park dialog @milestone(4: Beginning) |
You need to be logged in to leave comments.
Login now