-
Notifications
You must be signed in to change notification settings - Fork 0
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
500+ hits error should link to Focus Mode, not docs about Focus Mode #25
Comments
@jonbell-lot23 here is an example of a hot print statement today. I like the idea of an button that launches focus mode with a "best guess" window. I also wonder if it is time to begin discussing some other frontend improvements we could do as well The biggest one that we could do which we can discuss in #36 is adding the ability to progressively evaluate more expressions. How would this work
|
Yeah, even in cases where we have thousands of analysis points, we often get back usable results from the backend, and a thing that would be nice is to say "I only ever want to see a window of ten of these in the console, and let's start by using the ten that are closest to my current timestamp". This would actually be really handy for all print statements, even the print statements that are only 200 hits - often the analysis takes a long time because there are so many points to evaluate, when in truth you might not care about 99% of those evaluations. |
If I had an interface to say "I want to see X neighboring hits, centered around Y time or the Zth hit" I think that would be 🤌 |
Here's my short term proposal before we get to Focus Mode 1.1 and #36 : Right now the page links to docs -> I think clicking on the words "Focus Mode" should instead trigger our actual Focus Mode. That's a quick win that sets up our broader ideas. Thoughts? |
Marking as design complete and tapping @jcmorrow and @jasonLaster on the shoulder for:
|
Yeah I'm happy to knock this out as a bandaid pre #36 |
Right now this happens:
This should be replaced with two things:
The text was updated successfully, but these errors were encountered: