It made whole nice thing impossible to use without clicking frame and closing so on the whole KickOff. There were even a one version of KickOff what added a few pixel frame around KickOff and it rendered the “swing and click” feature unusable. But when me and others wanted to really locate KickOff other part of panel or even to resize panels, it came clear that it is impossible because the KickOff.
It would take one location space but it is already taken by breadcrumb so it would not change (much).
Even that I would cladly take a always top located single big “Back” button whats size is like any other menu object.Īnd when scrolling, you would only need to move mouse up to get back. Currently those features are more or less non-working because KickOff back button gets broken if done so.īreadcrumb is much better. The only reason why back button works, is when it is on left side of the screen, the user can go back just by swinging mouse to left without aiming and clicking to get back.īut we need to have possibility to locate the KickOff to other locations or even have panels resized and moved. As people learn to use mouse wheel to scroll, without need to aim a small target. The scrollbar size and back button size does not matter. Categories KDE, planetkde Tags Kickoff, QMLĮven that it is default now, it has been because the KickOff back button has demanded it. But of course there is still lots of time till master opens up. Drag’n’Drop support is missing, context menus are missing. Of course there is still lots of work left for me to train my QML skills. So there is no delay any more when clicking the Kickoff button in the panel 🙂 Kickoff is much faster, all Models are lazy loaded, that is they get only loaded if the tab is selected. The results of the work look really promising. Thanks Ivan for the great job of providing a working Model without having to first fix it. Exported the Model to QML, connected the search field and there were search results. After the experience with the Systems Model it was clear to me that I have to rewrite it as well.Īfter that the last remaining task was to integrate the search and finally a Model which worked exactly the way I expected it to be. Like all the other Models it has a tree structure. Last but not least I had to face the recently used Model. All my work on the tree view in QML was in vain *sigh*. Now the Model correctly proxies the underlying Model and I can use the standard views in Kickoff as it is also no longer a tree structure. So I had to fix the Model and was back doing C++ programming. This I could not copy in QML as the row count of the Model would not match the count of shown entries resulting in wrong height calculations. The proxying was not done correctly and the view so far filtered out entries not relevant to the current section – ouch. It took me quite some time to figure out the problem: the Model is buggy.
#Tabview qml code
Finally I had the QML code to play around with to improve my skills.Īfter I succeeded in rendering a tree view I noticed a new problem: both places and removable devices showed the same entries and too many entries. So I started to implement a Tree view in QML for the system tab.
Changing this to no longer being a tree structure seemed non-trivial and I did not want to touch the C++ code. It uses a QProxyModel instead of QStandardItemModels and merges the applications and places into one Model again in a tree structure. The systems model (applications, places and removable devices) turned out to be more challenging. For the Applications Model this was to be expected, but why are the Favorites in a tree structure? As QML is still rather limited for Tree Views I changed the favorites and leave model to be a plain list model which makes it easy to use. All the tabs have an underlying Model, but what was really surpising is that all Models have a tree like structure. The Kickoff code is let’s call it interesting. The actual idea was to just do some QML training, but it turned out to be more a training on Qt Models. It does not overwrite the existing applet, but adds a second one called “kickoff” instead of “Application launcher”.Īs we can see in the screenshot Kickoff got connected to all the Models, so we can browse all the tabs, the applications and perform search. If you want to give it a try, just checkout the kickoff-qml branch in kde-workspace and rebuild the kickoff applet. Now I am happy to announce that Kickoff with QML is functional and can already be used. 10 color: lected ? " #dcdada " : " white " 11 lor: " steelblue " 12 implicitWidth: Math.max(text1.As mentioned last week I started to port Kickoff to QML as a training project.
0 kommentar(er)
