You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently everything still kinda assumes everything is a piece of tuig, but a few don't. I should pick one:
Start treating each sub-project as its own thing with its own tags. (Probably ew: they're not separate projects; but if they were gonna be I should split them into their own repos)
Treat each sub-project as a sub-project of tuig (so tuig-ui, despite being a separate crate, gets treated like it's tuig::ui -- a system, whose "systems" are components)
Treat each sub-project as the "starting point", so e.g. there'd be p: tuig and p: tuig-iosys, then s: ge-runner and s: io-render
Or the labels might just not be that helpful: Maybe they should be saved for when there's more than one person working on the project. Or used for tracking status/kind/project only, not system/component/whatever.
The text was updated successfully, but these errors were encountered:
Currently everything still kinda assumes everything is a piece of tuig, but a few don't. I should pick one:
tuig
(sotuig-ui
, despite being a separate crate, gets treated like it'stuig::ui
-- a system, whose "systems" are components)p: tuig
andp: tuig-iosys
, thens: ge-runner
ands: io-render
Or the labels might just not be that helpful: Maybe they should be saved for when there's more than one person working on the project. Or used for tracking status/kind/project only, not system/component/whatever.
The text was updated successfully, but these errors were encountered: