Idea: use a prefix character on classes to distinguish Widgets, Views, Components, Systems

[ras0219]

So we would have something like
WItemList
VItem (currently ItemView)
VMain (currently MainView)
WUnitListing
CFoodStuff
CFurniture
CPosition
SAI (currently AISystem)
SNeeds
SMovement
SStorage
SHydroponics
CRoom
CItem

A lot of classes have suffixes such as "System" or "View" to distinguish the type from a similarly named component (AISystem vs AI, NeedsSystem vs Needs, ItemView vs Item, etc). Also, in the case of certain components, they clash with the underlying struct providing their data (Position vs position, Clearance vs clearance).

A prefix system would fix all of these cases in a concise and forward-proof way.

pros: Fix class name conflicts. Concise. Reasonably intelligible?

cons: Not intuitive if you don't know the overall codebase architecture (not really a big deal). Copies inheritance information into the naming scheme (DRY!). Approaching Hungarian and all it's +/-s.

Thoughts?

[ras0219]

Oh, we also have conflicts between component class names and their corresponding enum values in the components list.