<GitHub>
[solvespace] marthinwurer commented on issue #359: Ok, just got back into development. Some classes 100% need to be broken out into their own files for ease of navigation. Having SolveSpaceUI and Sketch in the same header makes using a C++ IDE (I use CLion) to try to navigate the codebase painful, so I'll be breaking those out into separate headers no matter what. As a new developer to this project, I have no clue whe
<GitHub>
[solvespace] whitequark commented on issue #359: > As a new developer to this project, I have no clue where any code components are, and because there's little documentation, it's hard to tell what I need to change or what things do without reading all the code, which is hard when everything is in one massive header.... https://github.com/solvespace/solvespace/pull/359#issuecomment-428419466
<GitHub>
[solvespace] marthinwurer commented on issue #359: > Please consider that after you move all of the headers around, it will be even harder to understand, because right now you can use git blame to see what commit introduced the code and why, but after that all the lines will just be attributed to you. This is the reason I haven't refactored anything "just to make the code slightly nicer" so far, and stuck to refactori
_whitelogger_ has joined #solvespace
_whitelogger has quit [Remote host closed the connection]