Re: [racket-users] DrR compilation progress bar

2017-10-31 Thread Hendrik Boom
On Sun, Oct 29, 2017 at 06:19:41PM -0500, Robby Findler wrote: > Yes, I can see that. That said, I think that good GUI design is > probably best conducted not in brainstorming sessions on a mailing > list, however. No, but collecting ideas that might be useful in UI design can be done here. >

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread Robby Findler
Yes, I can see that. That said, I think that good GUI design is probably best conducted not in brainstorming sessions on a mailing list, however. At the risk of repeating myself, I think it makes sense to see if we can get good information first and then decide where to put it second. I still

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread Neil Van Dyke
How about a progress bar in the status bar (like some Web browsers used to have, and Thunderbird still does), accept that it will be non-monotonic and not an accurate wall-clock-time % for some compilation tasks, and overlay it with some simple metric like "Compiled 8 / 12 files..."? If you

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread 'John Clements' via Racket Users
> On Oct 29, 2017, at 15:35, Robby Findler wrote: > > On Sun, Oct 29, 2017 at 5:31 PM, John Clements > wrote: >> >>> On Oct 29, 2017, at 15:27, Robby Findler >>> wrote: >>> >>> I think it is a bad idea to

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread Robby Findler
On Sun, Oct 29, 2017 at 5:31 PM, John Clements wrote: > >> On Oct 29, 2017, at 15:27, Robby Findler wrote: >> >> I think it is a bad idea to dump output into the interactions that >> isn't being printed by the program. > > We currently

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread 'John Clements' via Racket Users
> On Oct 29, 2017, at 15:27, Robby Findler wrote: > > I think it is a bad idea to dump output into the interactions that > isn't being printed by the program. We currently print “Welcome to DrRacket” at the start of each interaction, so it’s not as if *all* of the

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread 'John Clements' via Racket Users
This is a great idea: I feel like this change would deliver 80% of what I want, and be easy to implement. It would give a concrete and recognizable visual “path” of the compilation. I would not be inclined to delete it when finished. Could it ever be long? Would it make other people unhappy to

Re: [racket-users] DrR compilation progress bar

2017-10-29 Thread Stephen De Gabrielle
What about a simple timer and an indicator of compilation time compared to the previous compilation? The reasoning is that for a small project compilation time is short so it doesn’t matter that it will be wildly inaccurate, but for longer projects where compilation time is long, the number of

Re: [racket-users] DrR compilation progress bar

2017-10-28 Thread Shu-Hung You
I think printing which file is currently being loaded can also help, like the logs given by enter! #:verbose. These logs can also be printed to the interaction window and be erased after the loading process is finished. This can let the user know that something is actually running. --Shu-Hung On

Re: [racket-users] DrR compilation progress bar

2017-10-28 Thread Ben Greenman
I like the output `raco make -v ` gives on the command-line. How about piping that into the interactions window? -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [racket-users] DrR compilation progress bar

2017-10-28 Thread Robby Findler
I would not want to see a popup window, but there are lots of other, more subtle ways to indicate progress that would totally work here. Lets see if we can find a measure of progress that makes sense first. One idea: the drracket startup progress bar counts the number of files that are passed to

[racket-users] DrR compilation progress bar

2017-10-28 Thread 'John Clements' via Racket Users
Okay, this is just what the world needs…another DrRacket GUI suggestion. If it makes sense, though, I’d love to help implement it. If there’s anything that the last 30 years of UI (oh… sorry… UX) design has taught us, it’s that people hate to wait, and they REALLY hate to wait when they have