It would be nice to be able to support progress monitoring in the console when Juno is not available. I think the proper way to handle this will be to actually implement this as a standard feature for Juno.jl's progress API, so then any implementation of progress monitoring in Juno will automatically carry over to such an implementation in the console.
Also noted at SciML/DifferentialEquations.jl#121
It would not be too hard if Juno.jl accepts the dependency of ProgressMeter.jl, in which case a Progress type could get a new field of whether to print to the console or use the Juno progress bar (default determined by whether Juno is loaded, but make this a keyword arg on construction so one can switch this around as needed), and a few methods could have a separate branch depending on this boolean which calls the appropriate ProgressMeter.jl commands. It can display variables, so the msg string can probably be displayed as well, so it should be a feature-complete fallback.
It would be nice to be able to support progress monitoring in the console when Juno is not available. I think the proper way to handle this will be to actually implement this as a standard feature for Juno.jl's progress API, so then any implementation of progress monitoring in Juno will automatically carry over to such an implementation in the console.
Also noted at SciML/DifferentialEquations.jl#121
It would not be too hard if Juno.jl accepts the dependency of ProgressMeter.jl, in which case a
Progresstype could get a new field of whether to print to the console or use the Juno progress bar (default determined by whether Juno is loaded, but make this a keyword arg on construction so one can switch this around as needed), and a few methods could have a separate branch depending on this boolean which calls the appropriate ProgressMeter.jl commands. It can display variables, so the msg string can probably be displayed as well, so it should be a feature-complete fallback.