Ajout d'actions
Récapitulatif
Jusqu'à présent, nous avons réussi à construire une application simple pouvant afficher des cartes. Cependant, nous n'avons pas encore trouvé le moyen d'ajouter de nouvelles cartes à notre affichage en cartes.
Dans ce tutoriel, nous allons étudier les actions de Kirigami. Celles-ci nous aideront à ajouter de l'interactivité à notre application d'une manière cohérente, rapide et accessible.
Actions
A Kirigami.Action encapsulates a user interface action. We can use these to provide our applications with easy-to-reach actions that are essential to their functionality.

Actions de page pour le bureau

Page actions on mobile
Si vous avez déjà utilisé des applications sous Kirigami, vous avez certainement déjà interagi avec des objets « actions » de Kirigami. Dans cette image, nous pouvons voir des actions à droite de la page de titre avec diverses icônes. Les actions de Kirigami peuvent être affichées de plusieurs façons et peuvent réaliser une large variété de choses.
Ajout de compteurs
Une application de compte à rebours est plutôt inutile sans la possibilité d'ajouter des comptes à rebours. Créons une action nous permettant de le faire.
pageStack.initialPage: Kirigami.ScrollablePage {
...
actions.main: Kirigami.Action {
id: addAction
icon.name: "list-add"
text: i18nc("@action:button", "Add kountdown")
onTriggered: kountdownModel.append({
name: "Kirigami Action added card!",
description: "Congratulations, your Kirigami Action works!",
date: 1000
})
}
...
}
We are placing our Kirigami Action within our main page from our previous tutorials. If we wanted to, we could add more actions to our page (and even nest actions within actions!).
Kirigami.Action
components are used as contextual actions within Kirigami pages. We are setting it specifically to the
actions.main
property of our
Kirigami.Page
: the actions
object has properties that let us set different actions in different positions, but since our "Add kountdown" action is central to our UI we are setting it as the main action of this page.
The id
and text
properties should be familiar from previous tutorials. However, the inherited Action.icon property should be interesting: it is an object with several properties letting you display certain icons for your actions. Fortunately, to use KDE icons all we need to do is provide the name property for the icon property, icon.name
.
Note
Cuttlefish est une application de KDE vous permettant d'afficher toutes les icônes que vous pouvez utiliser pour votre application. Elle offre un certain nombre de fonctionnalités utiles telles que des aperçus de leur apparence à travers les différents thèmes installés, des aperçus selon différentes tailles et plus encore. Cet outil peut s'avérer très utile pour choisir les icônes à utiliser dans votre application.
Many of KDE's icons follow the FreeDesktop Icon Naming specification. Therefore, you might also find it useful to consult The FreeDesktop project's website, which lists all cross-desktop compatible icon names.
The
onTriggered
signal handler is the most important. This is what our action will do when it is used. You'll notice that in our example we're using the method kountdownModel.append of the kountdownModel
we created in our previous tutorial. This method lets us append a new element to our list model. We are providing it with an object (indicated by curly braces {}
) that has the relevant properties for our countdowns (name
, description
, and a placeholder date
).

Each time we click our "Add kountdown" button on the top right, our custom countdown is added

Mobile version
Tiroir global
Did you notice those three lines next to the page title on the previous screenshot? That's a hamburger menu that opens a Kirigami.GlobalDrawer . Global drawers are useful for global navigation and actions: in other words, those things you might need to use throughout your application. We are going to create a simple global drawer that includes a "quit" button.
Kirigami.ApplicationWindow {
id: root
...
globalDrawer: Kirigami.GlobalDrawer {
isMenu: true
actions: [
Kirigami.Action {
text: i18n("Quit")
icon.name: "gtk-quit"
shortcut: StandardKey.Quit
onTriggered: Qt.quit()
}
]
}
...
}
Here, we put our global drawer inside our application window. The main property we need to pay attention to is GlobalDrawer.actions , which takes the form of an array of Kirigami.Action components. This action has an appropriate icon and executes the Qt.quit() function when triggered, closing the application.
Since we are keeping our global drawer simple for now, we are setting the
GlobalDrawer.isMenu
property to true
. This displays our global drawer as a normal application menu, taking up less space than the default global drawer pane.

Tiroir global

Global drawer as a menu
Note
The Actions based components page of these docs provides further detail on Kirigami Actions and how they can be used.Notre application jusqu'à présent
|
|