gschema: Introduce the 'app-picker-layout' key
This is the key that will be used to store the pages and the icons in each page. The idea is that we we store an a{sv} variant for each page. This variant will contain <icon id> → array of properties, where we can store arbitrary data for each icon. The expected output of this key is: [ { 'polari.desktop': <{ 'position': 0 }>, 'epiphany.deskop': <{ 'position': 1 }>, }, { 'telegram.desktop': <{ 'position': 2 }>, 'builder.desktop': <{ 'position': 0 }>, 'gitg.desktop': <{ 'position': 1 }>, } ] The toplevel array is sorted, and pages of the grid always show in the order they are stored. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1284
This commit is contained in:
parent
8a50a8e64c
commit
8e23ff8111
@ -109,6 +109,17 @@
|
|||||||
the shell.
|
the shell.
|
||||||
</description>
|
</description>
|
||||||
</key>
|
</key>
|
||||||
|
<key name="app-picker-layout" type="aa{sv}">
|
||||||
|
<default>[]</default>
|
||||||
|
<summary>Layout of the app picker</summary>
|
||||||
|
<description>
|
||||||
|
Layout of the app picker. Each entry in the array is a page. Pages are
|
||||||
|
stored in the order they appear in GNOME Shell. Each page contains an
|
||||||
|
“application id” → 'data' pair. Currently, the following values are
|
||||||
|
stored as 'data':
|
||||||
|
• “position”: the position of the application icon in the page
|
||||||
|
</description>
|
||||||
|
</key>
|
||||||
<child name="keybindings" schema="org.gnome.shell.keybindings"/>
|
<child name="keybindings" schema="org.gnome.shell.keybindings"/>
|
||||||
</schema>
|
</schema>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user