Code Monkey home page Code Monkey logo

Comments (8)

xqms avatar xqms commented on July 23, 2024 1

Alternative (let's call this variant B):

  1. User types '/' to initiate search
  2. User starts to type a regular expression / prefix
  3. rosmon displays all matching nodes, with the first one "selected" (highlighted). Pressing tab selects the next node from the result list.
  4. The user can type further or select a node using enter. Pressing escape aborts the process.

I guess that's more in line with how other tools do it.

from rosmon.

xqms avatar xqms commented on July 23, 2024 1

I implemented a draft solution in #97. Let's continue the discussion there. Beta-testers welcome!

from rosmon.

xqms avatar xqms commented on July 23, 2024

I've been thinking about a search mode for a while now (like less/vi, triggered with '/'), which would reduce the list of nodes to a number that is manageable using the current shortcut system.

Do you have a better/different idea?

from rosmon.

matawed avatar matawed commented on July 23, 2024

I like the idea with the search mode similar to vim.

from rosmon.

clungzta avatar clungzta commented on July 23, 2024

Search would be great! Another benefit of the search is less time and difficulty to perform actions on a node.

For example: as a new user, if I wish to perform an action to the move_base node, I instinctively type 'm', when in fact it is assigned node key 'a', then I have to look at the list and correct my entry.

from rosmon.

xqms avatar xqms commented on July 23, 2024

Since there is interest in this, let's try to brainstorm. What do you think about the following UI flow:

  1. User types '/' to initiate search
  2. User starts to type a regular expression / prefix (needs to be decided)
  3. rosmon displays only the matching nodes, but in the same UI as before.
  4. At any point, the user can press enter to "fix" the search and use the usual node keybindings (a-z) to access the search results.
  5. Another enter or escape exits the search mode.

The drawback that I see is that we change node keybindings, i.e. your move_base node would be accessible using 'g' in the normal mode, but then using 'a' if you search for move_base.

What do you think? Can you imagine a better alternative?

from rosmon.

clungzta avatar clungzta commented on July 23, 2024

Variant b sounds quite nice! 👍

from rosmon.

xqms avatar xqms commented on July 23, 2024

Fixed in #97.

from rosmon.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.