GTK Shell: implement global menu get-set properties
Open
Nobody has claimed this yet.
enhancement
low-priority
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 237
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 1
Description
/**
* In gnome-shell/mutter/meta windows/views keep track of the properties
* specified as arguments here.
* Currently only the app_id is implemented / required.
*/
static void handle_gtk_surface_set_dbus_properties(wl_client *client,
wl_resource *resource,
const char *application_id, const char *app_menu_path, const char *menubar_path,
const char *window_object_path, const char *application_object_path,
const char *unique_bus_name)
{
auto surface = static_cast<wf_gtk_surface*>(wl_resource_get_user_data(resource));
if (application_id)
{
wf::get_core().get_data_safe<wf_gtk_shell>()->surface_app_id[surface->wl_surface] = application_id;
}
}
I think it will be good if it will be possible to query and set other properties, because it will open Global Menu to work. Maybe it is worth to make it separate plugin along with KDE global menu protocol.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at handle_gtk_surface_set_dbus_properties and compare the properties tracked by gnome-shell/mutter with the GTK Shell and KDE global menu protocols mentioned in the issue. Define which properties must be queryable and settable, then verify that the resulting protocol support enables Global Menu integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100