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

re-organize files #571

Open
camthesaxman opened this issue Feb 15, 2018 · 1 comment
Open

re-organize files #571

camthesaxman opened this issue Feb 15, 2018 · 1 comment

Comments

@camthesaxman
Copy link
Contributor

A lot of the source code files are in directories that don't really make sense, especially field, and this makes it kind of a pain to find some given piece of code. I initially agreed to the idea of using subdirectories, but now it makes it harder to navigate. Currently, emerald doesn't use them, and it's not a problem. We need to either come up with a directory structure that makes sense or get rid of the subdirectories. What are your thoughts on organizing the files?

@RevoSucks
Copy link
Collaborator

RevoSucks commented Feb 15, 2018

At this stage i think I would get rid of scene/ and pokemon/. field/ would be refactored into being more of a fieldsys/ folder while everything else that doesnt immediately relate itself to how the field system works would be moved up 1 folder. battle/ can stay

libs -> gflib

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

No branches or pull requests

2 participants