Plasma/SAL QML: Difference between revisions
< Plasma
| Line 19: | Line 19: | ||
* Hide the salviewer popup when an executable/item is launched. That would require some kind of signal from the qml side, connected from the C++ applet side, which would then send a dbus command. A cleaner route would be nice, but I believe that's the only way. | * Hide the salviewer popup when an executable/item is launched. That would require some kind of signal from the qml side, connected from the C++ applet side, which would then send a dbus command. A cleaner route would be nice, but I believe that's the only way. | ||
* Create a "Close" button rendered on top of sal. That code would have to be written *inside* salviewer itself. | * Create a "Close" button rendered on top of sal. That code would have to be written *inside* salviewer itself. | ||
* Install sal-qml as not only an applet, but a containment as well. So as to replace the current broken C++ one in master. | |||
= Questions = | = Questions = | ||
What is the difference between "Categories" and "Apps"? | What is the difference between "Categories" and "Apps"? | ||
Revision as of 23:03, 4 May 2012
TODO
- Add a shortcut to open/close launcher
- Add arrow-key navigation within results
Appearance
- Make texts easier to read (more opaque background?)
- Only show tooltip when text is truncated
- Hide "highlight" frame when cursor is not over any item
- When search results are incrementally added, opacity of result items which are already there should not change. Right now opacity of all existing result items goes to 0 and back to 1.
Behavior
- After entering a category there is no obvious way to go back, add a "Back" button or breadcrumbs?
- Clicking a folder from the "Files" runner opens the folder in Dolphin, it should list the folder content IMO, just like one can enter a category
- Tabs on the top seems to be hardcoded, should they be customizable or at least extensible?
- Typing a search term in the search box searches in all runners by default, instead of the current one
- Favorites should save to the config. Currently having issues getting it to save *anything*.
- Hide the salviewer popup when an executable/item is launched. That would require some kind of signal from the qml side, connected from the C++ applet side, which would then send a dbus command. A cleaner route would be nice, but I believe that's the only way.
- Create a "Close" button rendered on top of sal. That code would have to be written *inside* salviewer itself.
- Install sal-qml as not only an applet, but a containment as well. So as to replace the current broken C++ one in master.
Questions
What is the difference between "Categories" and "Apps"?