-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
搜索页签改为上下布局 #3538
Comments
Hello, thanks for your reply! Yes, I can see a use case here and know about that functionality. Still I think the occasions for this use case are probably more rare comparing it to the feature request. The long list of search results tells barely a thing about the single items it is pointing at and it's hard to find something from that list. When we put a more specific search the list is getting a lot shorter with a lot of unused space on the left side of the split pane. Another thing is that for using the search function like this, the right side of the dock has to be closed else the preview gets too narrow to be usable. At least on most used screens and resolutions that are being used today. That I get used to it and learn to love it is of course also a possibility. |
Also, I really want to put some honoring words next to my critiques. |
Thanks for the discussion. In fact, regarding the search interface, there is also discussion on the SiYuan Chinese forum https://ld246.com/article/1637045994739, some users think that the left-right layout is reasonable. At the moment, what you said also makes sense because the tab panel can already be displayed in a tree form, and it may be more reasonable to press the top-bottom layout of the search tab. We will adjust the layout of the search tab in the near future, thank you. |
Thanks for the rapid work! Insane speed. Seeing the Ambition for the left/right approach in the Chinese forums and feeling like my initial issue wasn't communicated that well I want to leave a quick annotation to this request. I actually didn't wanted to push changing the search to a top/bottom approach. It was more about splitting the results list and the preview. Then like on the screenshot the results-list can be displayed in a widget in the toolbar / dock (That's why i called it docklet.) The preview then gets a full tab / pane in the main workspace. In a way you could see it as keeping it in left/right. I'll try to make a full mock up to visualize how it was ment. |
Sorry for the errors with spelling and semantic. I needed to edit the recent comment after posting it. In case you're checking the comments just via mail: to read it in a way that makes more sense I recommend checking it directly on GitHub to see the most up-to-date version. Haha sorry for this again. |
Oh, I understand, we need a search panel, not just a tab. We may need to spend time to consider and implement this. In the recent releases, we will keep the design of the search tab, for the time being. The new change we can continue discussing in #3564, thank you. |
Feature suggestion Quicksearch Docklet
There are at least two use cases that come to my mind for this.
It would also solve problems with displaying the tag-search results in a split pane.
(Without wanting to generalize too much) Handling it in a split pane comes with workflow distractions. General Overview is compromised and it's probably an overkill. In many cases, there will be lots of empty space on the left search results side and the preview side will be too narrow on most screens to make good use of it.
Displaying the results in the docklet with a small contextual preview one above the other instead of a horizontal split would solve this problem.
I also think this feature would just add to the project without taking something. The advanced search feature is still good and usable as a launcher and for searching with full attention.
Reading the "Origin" article I could imagine that it could fit in the spirit and principles of the project.
I'm adding a screenshot from a fellow PKM Application as inspiration for how it can be handled.
The text was updated successfully, but these errors were encountered: