You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice to paper over the fact that we run in a terminal; I don't think we can assume students are familiar with command prompts and flags and paths and such.
Not sure what the best way to do this is...
I think the obvious solution is to ship a small GUI wrapper (or really, to have the binary pop up with a file selector/board dropdown if run with no args). This lets users familiar with the command line continue as they normally do while letting other users run the program by "double clicking" on the file they download.
On Windows this would work just fine; if you "open" a terminal binary in file explorer it'll launch the default terminal emulator. Same on macOS (provided your .profile doesn't do strange things but I think we can assume that users making .profile changes can handle themselves).
I'm less sure what the story is on Linux but I also feel comfortable assuming that students choosing to use Linux have some familiarity with the command line.
steps
[[ steps ]]
[[ What steps will we need to take to implement this feature? ]]
where
branch: feat-
[[
This should be:
N/A if this feature is not currently being worked on
what
It'd be nice to paper over the fact that we run in a terminal; I don't think we can assume students are familiar with command prompts and flags and paths and such.
Not sure what the best way to do this is...
I think the obvious solution is to ship a small GUI wrapper (or really, to have the binary pop up with a file selector/board dropdown if run with no args). This lets users familiar with the command line continue as they normally do while letting other users run the program by "double clicking" on the file they download.
On Windows this would work just fine; if you "open" a terminal binary in file explorer it'll launch the default terminal emulator. Same on macOS (provided your
.profile
doesn't do strange things but I think we can assume that users making.profile
changes can handle themselves).I'm less sure what the story is on Linux but I also feel comfortable assuming that students choosing to use Linux have some familiarity with the command line.
steps
[[ What steps will we need to take to implement this feature? ]]
where
branch:
feat-
[[
This should be:
feat-<feature-name>
if this is being worked on in this repoorg/repo#<branch-name>
if this is being worked on in another repo]]
open questions
The text was updated successfully, but these errors were encountered: