Gaia.fs is currently over 4600 lines of code. And like a typical ImGui program, each of those lines has access to a significant number of mutable state variables. If left in a single file, I could see it growing up to 8, 12, or even 20 klocs as Nu is applied to the large commercial software titles.
I have recently done some nice refactoring on the file in preparation for splitting it up. However, I'm not 100% sure of what the ideal methods are for splitting a larger ImGui program like Gaia.
It might make sense to look at other project's approaches to splitting large ImGui programs for guidance.
Gaia.fs is currently over 4600 lines of code. And like a typical ImGui program, each of those lines has access to a significant number of mutable state variables. If left in a single file, I could see it growing up to 8, 12, or even 20 klocs as Nu is applied to the large commercial software titles.
I have recently done some nice refactoring on the file in preparation for splitting it up. However, I'm not 100% sure of what the ideal methods are for splitting a larger ImGui program like Gaia.
It might make sense to look at other project's approaches to splitting large ImGui programs for guidance.