Bug 413733 - GLOBAL MENU CROOSPLATFORM HELP DEMAND
Summary: GLOBAL MENU CROOSPLATFORM HELP DEMAND
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Global Menu widget (other bugs)
Version First Reported In: master
Platform: Debian stable Linux
: NOR normal
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-02 10:18 UTC by n1coc4cola
Modified: 2019-11-21 10:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description n1coc4cola 2019-11-02 10:18:54 UTC
Hello, I know that this isn't the place to but I haven't find another way...
So, I'm writing this today because I'm a (very) young developer who want to globalize... the Global Appmenu. I watched a long time source codes from different projects but I cannot understand how it works. I understood that org.canonical.DBusMenu is used in com.gnome.AppMenu.Registrar (I'm not sure of the interface name's beginning, it's 00:08 now...) are a technology used together. But can you help me to understand how you make the apps registering their menu at one place and not another or if it's a path that is a standard. So can you tell me, give me some tracks on how to make this service in C++ (I have some bases) to make it available in cross platform?


EXPECTED RESULT
Have some help and make my project real and not leave it as some lost hours.
Comment 1 David Edmundson 2019-11-02 11:42:21 UTC
Please don't type in capitals.

Can you clarify what you mean by "globalize" the menu.
Comment 2 n1coc4cola 2019-11-02 18:25:36 UTC
Sorry, now it's 8:05, I'll can explain it better.
So, with "globalize" I mean that I want to make an app which handles these services, but, without having any dependencies in relation to the environment where the app is currently running. With that, the different distributions (OS and env.) will be able to install just one DBus service and have access to a Global Menu that is currently exclusive to KDE Plasma 5.9+ and Gnome (with the Vala Panel). I hope that is more clear for you now. Thank you for your replies.
Comment 3 David Edmundson 2019-11-03 15:44:37 UTC
At most you can proxy from one client spec to another, then a daemon can read that. 

See   plasma-workspace gmenu-dbusmenu-proxy which is a daemon that proxies from GTK menu spec to our version of the spec.
Comment 4 Bug Janitor Service 2019-11-18 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!