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.

Sign up for GitHub

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

Jump to bottom

Project Folder Structure & Naming #119

Open

Ghabry opened this issue Dec 17, 2018 · 0 comments

Labels

Member

Ghabry commented Dec 17, 2018

We are basicly just starting development again, so lets finish the organisational part :D

Some files don't use CamelCase and are completely lower, e.g.
dialogfacepicker

Many classes are prefixed with Q for no real reason, imo the Q can be removed.

Put license on top of all source files

There could be also some logical grouping in folders. Most for the UI files, no idea, something like:

database
events (this is currently commands)
map (all dialogs related to the map and the map tree)
common (for commonly used stuff like Switch/Variable picker)
[drop everything else in the src root for now]

Only with database and events in sub folders this would reduce the clutter in the src directory alot.

Ghabry added the Building label

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