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

Taal: Rethink file/folder structure #236

Closed
sloede opened this issue Oct 19, 2020 · 1 comment · Fixed by #200
Closed

Taal: Rethink file/folder structure #236

sloede opened this issue Oct 19, 2020 · 1 comment · Fixed by #200
Labels
question Further information is requested taal

Comments

@sloede
Copy link
Member

sloede commented Oct 19, 2020

After Taal is feature complete and we have deleted "the old Trixi", but before we merge it to master, we should rethink the file and folder structure to make sure that

  • existing stuff is "easy" to find and
  • new stuff has a "natural" place where it should be added to.
@sloede sloede added question Further information is requested taal labels Oct 19, 2020
@sloede sloede mentioned this issue Oct 20, 2020
45 tasks
@ranocha
Copy link
Member

ranocha commented Oct 25, 2020

I totally agree. Something to think about: Many (some?) editors display the file name without path in a more prominent position than the rest of the path. In that case, it can be much more convenient to include some important information in the file name itself instead of the path, e.g. dg_1d.jl and dg_2d.jl instead of 1d/dg.jl and 2d/dg.jl. In particular, this makes working on 1D and 2D versions in VS Code more convenient for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested taal
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants