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

Add editing tools #1

Open
egor045 opened this issue Jul 13, 2017 · 2 comments
Open

Add editing tools #1

egor045 opened this issue Jul 13, 2017 · 2 comments

Comments

@egor045
Copy link
Collaborator

egor045 commented Jul 13, 2017

Move from a collection of classes to an actual sector/subsector/collection of systems editor.

  • Use a web front-end (maybe Flask)?
  • Use some Python GUI?
@LeamHall
Copy link
Member

I've had to face that question a few times. The answer devolves down to the expected use case; will the user download the code and have all the tools to run it or would it be better on a website where they just point and click?

GUI requires the libraries and you have to assume nothing is present on the users machine. Web means a different skill set and lots of input filtering. And a platform like Linode or Digital Ocean. I lean towards web but haven't gotten to the "have to decide" point yet.

For now I stick with CLI.

@egor045
Copy link
Collaborator Author

egor045 commented Jul 14, 2017

CLI or web (probably Flask - I've looked at it for some other stuff) is likely the way to go.

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