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

Define use cases and useful commands #10

Open
13 of 18 tasks
Sebobo opened this issue Jan 19, 2023 · 3 comments
Open
13 of 18 tasks

Define use cases and useful commands #10

Sebobo opened this issue Jan 19, 2023 · 3 comments
Labels
question Further information is requested

Comments

@Sebobo
Copy link
Owner

Sebobo commented Jan 19, 2023

Use cases and ideas

@Sebobo Sebobo added the question Further information is requested label Jan 19, 2023
@PRGfx
Copy link
Contributor

PRGfx commented Mar 14, 2023

Some additional ideas:

  • switch workspace
  • reload guest-frame (I know there is a shortcut for that, but I like fuzzy finding a command by typing rather than remembering hotkeys)
  • (reload node-trees)
  • set filter for document-tree (node-type and search-term)
  • open frontend-preview
  • go to node-property/reveal property(/view) in inspector (a bit like Inspector search neos/neos-ui#675 and/or Make inspector tabs/groups focusable from the outside neos/neos-ui#3350; as the UI is lacking focus behavior, this probably wouldn't be very practical for the time being)

@Sebobo
Copy link
Owner Author

Sebobo commented Mar 15, 2023

Hi @PRGfx, thx for the ideas. Some notes:

  • "Reload guest frame" is already available with the Reload ContentCanvas as I load all hotkeys as commands (and filter a lot out which don't work).
    If it doesn't seem to be a big benefit to load the hotkeys as commands, we could of course choose the useful ones and implement the in the plugin itself as command to improve UX. ContentCanvas is probably not a useful term for most users.

  • "Reload node-trees", why would this be helpful? Shouldn't it be rare for the tree to get out-of-sync, or is the use case rather that more people work in parallel and one wants to see the newly added or removed elements by the other?

@Sebobo Sebobo changed the title Define use cases Define use cases and useful commands Mar 15, 2023
Sebobo added a commit that referenced this issue Mar 15, 2023
@PRGfx
Copy link
Contributor

PRGfx commented Mar 15, 2023

Oh I didn't notice the hotkey actions are already available, cool.
Some naming could probably improved, yes (for example "Live" for the preview mode isn't really descriptive imo, but thats off topic).

As for the node-trees: true, I mostly used this after migrations etc when I don't want to reload the whole backend ^^ But good point with updating changes from editors.
It was more a thought about how most actions should probably also be available to fuzzy search and the ones without context (i.e. not depending on the selected node etc) are probably lower hanging fruits, but in fact the usefulness is probably limited – as long as the overall tabbability of the backend is a bit difficult, I feel like I would still need to click buttons a lot anyways.

@Sebobo Sebobo pinned this issue Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants