-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
Athena #126
Comments
hi @prabhath6 thanks for this. I actually was just about to merge in some changes. I removed the cache, and added key down functionality (up, down, enter, shift-enter). This will likely affect how you implemented |
Hi @tangjeff0, you can find my changes below. We have modified the same functions so i expect merge conflicts. |
Awesome code @prabhath6 ! I just merged in #201, which removes the |
thanks @tangjeff0 🙂! I will pull in your changes, resolve the conflicts and move the recent-item to re-frame db.
All the search results or just the ones that the user clicked on. |
The vector is an (exact match OR nil), 20 page matches, and 20 block matches. If what you mean by |
It might also be easier to start with a fresh branch than to try to resolve the conflicts @prabhath6 . |
Hey @tangjeff0, i pulled in your changes and built the save and show feature on top of them. Now the state is stored in re-frame db instead of an atom. I have opened a pull request. |
Mani and Adrien, please comment here so I can assign you this task. Thanks 💚 |
👋 hi @nthd3gr33
Probably a detail but may I also suggest Ctrl+j and Ctrl+k, like on Roam? |
hi @nthd3gr33 🚀 |
All keybindings will be configurable @alaq don't worry :) |
This seems to be working again (tested in Firefox and Safari). However, we may have found another issue: with the test data loaded, if you type one character only in athena, the page freezes and you have to close it (tested in Chromium and Firefox). @tangjeff0 let me know if you feel like this needs a separate issue. |
Quick update: We (Team Seneca) made some progress on this today. We have implemented a solution so that the the arrow keys do scroll vertically through the menu items. That said, the animation is far from ideal. We also need to implement the following additional changes:
Here is the code that we used today: (this goes in (= key KeyCodes.UP)
(do
(swap! state update :index dec)
(let [cur-sel (first (array-seq (. js/document getElementsByClassName "selected")))]
(.. cur-sel (scrollIntoView false {:behavior "smooth" :block "center"}))))
(= key KeyCodes.DOWN)
(do
(swap! state update :index inc)
(let [cur-sel (first (array-seq (. js/document getElementsByClassName "selected")))]
(.. cur-sel (scrollIntoView true {:behavior "smooth" :block "center"})))) (code author: @itsrainingmani) This issue of focus management turned out to be harder than we expected. My gut told me that we should do more research before hacking away further. Results of our research:
We will be working more on this issue tomorrow. |
It might be best to make two new issues: one for this typing bug and one for arrow-keys. @alaq @nthd3gr33 @itsrainingmani |
Just opened #269 for the typing bug |
Can you make a separate issue for arrow keys and copy this comment ? |
Opened issue for arrow keys #271 |
The hover issue still remains. We implemented parity with Roam (aside from the flickering) as can be seen in the Loom, but the three of us are thinking that the Dynalist functionality is probably more ideal. Any thoughts on which direction is best? |
Tasks
up
anddown
to go through listenter
- create new page or go to pageshift-enter
- open in right sidebarcmd-k
)Design
The text was updated successfully, but these errors were encountered: