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
Clean up log console api a bit #7379
Conversation
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
@mbektasbbg - if these look good to you, I'll merge and release a 1.2 release candidate. |
…ily. This also lets us set up keyboard shortcuts for the buttons, etc.
77354b5
to
177f20f
Compare
We also threaded the limit through the constructors so that the extension has sole control over the limit.
@mbektasbbg - I think the functionality is the same now from the user's perspective. Can you review these changes? I'm happy to hop on a call to go over these together if you'd like. |
49667fb
to
75f66d1
Compare
@jasongrout lets have a call to go over the changes as you suggested |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasongrout these changes look good to me. leaner and cleaner, thanks! I built and tested, haven't seen any issues except new flash color making text not so legible in dark theme.
Yeah, I tried to make things consistent with how we are using that info color elsewhere, but it doesn't look so good in a dark theme. |
The info color does not match well with the hardcoded status bar colors, especially in dark mode.
Thanks @mbektasbbg! Would you mind looking at the last two commits as well? I simplified the status bar components, and switched the highlight colors to the brand colors. It seems that it is really hard to highlight something in the status bar because the status bar does not use straight CSS, so you don't get good CSS inheritance. |
…idget for inactive logs.
…ary code. There are some subtle issues fixed here. 1. LogConsolePanel is now more careful and complete in emitting sourceDisplayed signal so that we don’t have to have a message hook anymore. 2. Because we more carefully account for displayed messages, we remove the flashEnabled checks in the status bar updates, which makes the flashing work more correctly. For example, with flashing enabled, now we will see the indicator flash when the console is open but not visible (for example, it may be hidden behind another tab).
* reorder class methods/attributes to public/protected/private * alphabetically sort imports and some other lists of attributes
Okay, I think this is good to go now. I left in the notebook output logging so it is easy to test, but we can remove that before merging. @blink1073 - Would you rather we added a setting somewhere for the notebook to log all output to the log console (default to off)? I think we don't need it for now, but you feel it is really needed, we can add it. |
ping @mbektasbbg for review. My plan is once this is merged, backport it and release another 1.2 alpha, so we can try the ipywidgets changes needed to use it. |
@jasongrout I just pulled the latest, rebuilt and tested. Previous issue I reported is gone and I haven't seen any other issues, everything is working great! and with better behavior. |
I just noticed that log console tab doesn't have an icon anymore. is that intentional or did I miss a build step? |
Argh, this probably happened when I moved to the new icon system so we'd have better-themed icons. I'll check into it. |
@telamonian - f34ca0d makes it so that the log console icon shows up in the tab. However, it's always the same color in every theme, which doesn't look very good. Is there a way to get the icon for the tab to change colors in the different themes? |
Let's address the icon color issue in a different PR. This is getting be enough as-is. I'll remove the nb output logging and merge. Thanks @mbektasbbg! @blink1073 - still would love your thoughts about including the nb output logging. |
Notebook output logging made it easier to test the logging console extension. I think it is too much noise for production, though, unless it is behind a option and turned off by default. See jupyterlab#7386
@meeseeksdev backport to 1.x |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon! If these instruction are inaccurate, feel free to suggest an improvement. |
Backport PR #7379: Clean up log console api a bit
References
CC @mbektasbbg
Code changes
This cleans up the api for the log console a bit to conform to conventions we've used elsewhere in the code, such as:
activeSource
to simplysource
and many more.
User-facing changes
None
Backwards-incompatible changes
Only in an unreleased package