-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
Improve source heading buttons and interactions. #3202
Conversation
Let's just keep the solution local for today :D no need for a special class in other places yet. thx Luka |
Will review ASAP! |
3d0e117
to
525f7ce
Compare
I made a PR in the prompter library to add |
525f7ce
to
99a1719
Compare
99a1719
to
bb6cde5
Compare
@hgluka I've bumped the submodule. To conclude this PR:
I'll merge it when the patch to Guix has been accepted. |
Here's a screenshot, by the way: @lansingthomas Let me know what you think. When you approve, I'll add a changelog entry and it will be ready to merge. |
Can you send me a video? -- alternatively we can screen share tomorrow (or today if you are willing). |
I'll share my screen with you tomorrow. That way, we can work out any issues in real time. On another note, I'm not sure why these builds are failing. There are a lot of |
@hgluka no idea. But I don't think we should care either, because CI is mostly useless. All it does can be trivially replicated locally. My intuition tells me that it will start magically to work again for no apparent reason. If it doesn't, we'll get to that. |
The patch has been accepted on Guix meaning that we can move forward. What's the status here? We should have this one ready by the end of the week so that it lands on the next release. Thanks. |
Sorry I am the bottleneck for this at the moment. -- we are scheduled for tomorrow for another interaction review.
|
had a nice convo with Luka -- we agreed on styling for the arrows. he is reporting an observed bug with the +/- I approve of these changes. Thx @hgluka |
0459e44
to
e01203a
Compare
Yep, this is ready to review/merge @aadcg. |
I will review when #3231 is fixed in this PR. Please let me know. #3231 could have been spotted without @lansingthomas's intervention. That's part of the self-reviewing process expected from PRs. The work the team outputs can be as good as its ability to self-criticism. |
e01203a
to
44d6074
Compare
@aadcg This PR is ready for a final review/merge. |
44d6074
to
c00f7f3
Compare
There's a UI glitch in this PR. Sometimes, both arrows are inactive. I need to investigate. |
c00f7f3
to
2bef781
Compare
Unfortunately, there's no easy way around it. Commit 28179e7 provides a detailed explanation. Therefore, this PR no longer closes #3139. @jmercouris please review. |
2bef781
to
7aac381
Compare
@jmercouris friendly ping. |
yes, sorry for the delay! |
Change button glyphs for `next-source`, `previous-source` and `toggle-attributes-display`. Show keybinding on hover. Not all added glyphs are being used, but they may be useful in the future. Move `toggle-attributes-source` button to the right. Mute next/previous source arrow when next/previous source is unavailable. Review CSS.
The previous commit introduces a UI glitch where the left arrow down button is drawn as inactive by a brief moment. The root cause isn't related to the implementation of the feature itself, but due to the poor architecture design of update-prompt-input. Steps to reproduce: - Invoke execute-command - Run `(update-prompt-input (current-prompt-buffer) "fo")` The issue can be understood by inspecting the calls to `(prompt-render-suggestions prompt-buffer)` in `update-prompt-input`.
7aac381
to
6450b4a
Compare
Description
Change next and previous source glyphs, mute the color when there is no next or previous source and show keybinding on hover.
Depends on atlas-engineer/prompter#24.
Fixes #2852.
Fixes #2556.
Discussion
It might be useful in general to have an
inactive
style class predefined.cc @aartaka @lansingthomas
Checklist:
Everything in this checklist is required for each PR. Please do not approve a PR that does not have all of these items.
cd /path/to/nyxt/checkout git submodule add https://gitlab.common-lisp.net/nyxt/py-configparser _build/py-configparser
:documentation
s written in the aforementioned style. (It's OK to skip the docstring for really trivial parts.)changelog.lisp
with my changes if it's anything user-facing (new features, important bug fix, compatibility breakage).migration.lisp
entry for all compatibility-breaking changes.(asdf:test-system :nyxt)
and(asdf:test-system :nyxt/gi-gtk)
) and they pass.