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

Wish: group autocompletion pop-up #402

Open
uliska opened this issue Mar 26, 2014 · 2 comments
Open

Wish: group autocompletion pop-up #402

uliska opened this issue Mar 26, 2014 · 2 comments
Assignees
Labels

Comments

@uliska
Copy link
Collaborator

uliska commented Mar 26, 2014

As expressed in PR #401 I think it would be a good thing to pimp the autocompletion pop-up window.

Currently I have two independent ideas for that:

Grouping

Group the items and add graphically highlighted, non-clickable group headers.

  • include:
    • group by source: relative-to-document/include-path/LilyPond
    • within include-path: for each include-path
  • commands:
    • LilyPond built-in syntax
    • from includes, differentiating between local/include-path/LilyPond as for include

Tooltip

Show a tooltip window when hovering or highlighting an item when there is any information about the element that can be retrieved from somewhere (documentation, Grob properties, ly-music or whatever).

This basic idea of showing Tooltips with more information could later be extended to different parts of Frescobaldi. For example when hovering over an element in the Music view (e.g. try to determine if there are overrides and show their values).

@wbsoft wbsoft added the wish label Mar 27, 2014
@wbsoft
Copy link
Collaborator

wbsoft commented Mar 27, 2014

The completion (using QCompleter) is already model-driven and that should make it fairly easy to support tree- or otherwise grouped structures. It would even be possible to add a column in the completion popup that displays other useful information.

@uliska uliska self-assigned this Oct 2, 2019
@uliska
Copy link
Collaborator Author

uliska commented Oct 2, 2019

Just stumbled over this and self-assigned without a concrete commitment to work on this. But other than in 2014 I now have an idea about the model-view approach and would probably find my way through it by now.

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

No branches or pull requests

2 participants