Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restructure Package hierachy #1298

Open
bevans2000 opened this issue May 6, 2024 · 2 comments
Open

Restructure Package hierachy #1298

bevans2000 opened this issue May 6, 2024 · 2 comments

Comments

@bevans2000
Copy link
Member

Is your feature request related to a problem? Please describe.
The source code has grown over time and the existing package structure results in hotspot of large packages.
Secondly there are cases where the separation of concerns is poor giving a high dependency.

Describe the rationale
Split the packages into a more structured approach with more top-level packages.

Describe the goal(s) you have in mind
Key changes would be:

  • structure renamed to settlement
  • structure/building moved to new top level package
  • structure/construction moved to new top level package
  • person/ai/task moved to new top level package

The Tasks classes will be moved out of the general single location into task sub-packages under the appropriate top level; this is being covered as part of #1285.

This would be a large change but relatively low risk if done in an IDE. It's important files undergo a Git rename to preserve the history.

@mokun
Copy link
Member

mokun commented May 18, 2024

Can we also consider the possibility of having remote stations, such as weather tower, communication towers, traffic hub, etc. that will be minimally manned and/or robotically operated ?

@bevans2000
Copy link
Member Author

Ok. What's the difference between a Settlement with only one Building? I think those places would just be a small settlement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants