Skip to content
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 search UI/UX #167

Open
EmmanuelMess opened this issue Feb 4, 2025 · 1 comment
Open

Improve search UI/UX #167

EmmanuelMess opened this issue Feb 4, 2025 · 1 comment

Comments

@EmmanuelMess
Copy link

EmmanuelMess commented Feb 4, 2025

As part of the effort to make breathe/exhale comparable to Doxygen, I would recommend improving the UI/UX of the search interface.

For a simple comparison see:

Image

From http://docs.ros.org/en/jazzy/p/rclcpp/search.html?q=transform&check_keywords=yes&area=default

And compare to:

Image

From https://docs.ros2.org/foxy/api/rclcpp/index.html

I would recommend:

  1. Automatically search in place (without navigating to a new page)
  2. Show only relevant snippets, in our case it would be python files, cpp files and some docs
  3. Better management of space
  4. Better sorting and grouping of entries into classes files and docs
@tfoote
Copy link
Member

tfoote commented Feb 21, 2025

Automatically search in place (without navigating to a new page)

This sounds like a good enhancement ticket for exhale or sphinx more than for rosdoc2. We don't implement the search UI, so things like the instance floating responses are not something that we're likely to work on.

Show only relevant snippets, in our case it would be python files, cpp files and some docs

Are there search responses that you consider irrelevant in the search results?

When I search the equivalent to your doxygen query I see generally pretty good coverage and relevancy: https://docs.ros.org/en/jazzy/p/rclcpp/search.html?q=create_publisher&check_keywords=yes&area=default#

Better management of space
Better sorting and grouping of entries into classes files and docs

These are generally pretty subjective. If there are settings for our instance that we can tweak, maybe layouts for the better spacing etc. We can look at that. And if there's ways to provide more information to the search for ranking that would be great. To make an improvement to the tool we'll need an understanding of what's better or worse versus necessarily personal preference. We generally follow what are best practices and use the defaults which are maintained and optimized by others. And to diverge from the best practices for these tools we'll want to have a pretty compelling case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants