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

Improved UI/UX #2

Open
jo11he opened this issue Nov 22, 2024 · 0 comments
Open

Improved UI/UX #2

jo11he opened this issue Nov 22, 2024 · 0 comments

Comments

@jo11he
Copy link

jo11he commented Nov 22, 2024

This is a suggestion to rethink the user interaction with the data downloader class. As of now, there are some cases (Cassini, or flyby missions in general) for which the user has to write a short script, execute the script and then interact with the terminal to get the desired downloads. I would suggest instead to make two separate paths of interaction for the user:

  1. User gets the job done in one script (also for Cassini). Import class, create instance, call get_data function and then specify timespan or flybys (how to implement this is up to creativity of the developer)

  2. Additionally (bit more elegant) there could be an executable that can be called from terminal, where the user is prompted to give (in sequence) the inputs to obtain the desired output (mission name, time bounds, archive path). The prompts can be different based on prior inputs.

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

1 participant