Package Details: vala-panel-appmenu-budgie-git 24.02.r1.gced6ce3-1

Git Clone URL: https://aur.archlinux.org/vala-panel-appmenu-xfce-git.git (read-only, click to copy)
Package Base: vala-panel-appmenu-xfce-git
Description: AppMenu (Global Menu) plugin for budgie-panel
Upstream URL: https://gitlab.com/vala-panel-project/vala-panel-appmenu
Licenses: LGPL3
Conflicts: vala-panel-appmenu-budgie
Provides: vala-panel-appmenu-budgie
Submitter: rilian
Maintainer: rilian
Last Packager: rilian
Votes: 37
Popularity: 0.52
First Submitted: 2015-04-01 21:00 (UTC)
Last Updated: 2024-02-27 21:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 24 Next › Last »

<deleted-account> commented on 2018-04-30 16:33 (UTC)

appmenu-qt is a missing optional dependency, now it's appmenu-qt4. Also appmenu-qt5 is not needed anymore if vala-panel-appmenu-registrar is installed since qt5 exports the menu bar to DBus by itself.

Vanilla GTK2 hides the menus natively, so gtk2-ubuntu isn't needed as well. However, appmenu-gtk-module-git doesn't work on flatpak'ed gtk2 apps. In flatpak'ed gtk3 apps the menu bar doesn't hide.

Just some feedback so the PKGBUILD dep list is fixed.

zhangkaizhao commented on 2018-04-24 02:22 (UTC)

@rilian gobject-introspection is needed as one of the makedepends here.

rilian commented on 2018-04-08 20:58 (UTC)

No, it should not, because you can use different Registrar provider like kwin.

dwellingsoul commented on 2018-04-08 19:23 (UTC)

I installed this and had duplicated menus (panel + menubar in applications). Enabling ShellShowsAppMenu and ShellShowsMenuBar with xfconf didn't work.

I fixed it by installing vala-panel-appmenu-registrar-git. IMO it should be a dependency so that users won't have to be looking for fixes.

rilian commented on 2018-03-11 18:03 (UTC)

Can you write this to issues with a full log? And you should not set Java agent before building finished, or it will be broken.

andreyorst commented on 2018-03-11 15:50 (UTC)

Understood. But can't quite get how to build it with Jayatana. I've installed OpenJDK7, and tryed to build your Git package according to your instructions from readme, and got this error: https://pastebin.com/2Vp0jsSc. And I'm not quite sure what I've done wrong.

rilian commented on 2018-03-10 20:01 (UTC) (edited on 2018-03-10 20:05 (UTC) by rilian)

It is make dependencies, you can just build appmenu-gtk-module, and then remove rest of panels. All panels needed just because I do not want to build applet four times (it will builds four times, if I split pkgbase to seven packages). For KDE you will need only appmenu-gtk-module and jayatana (Jayatana is disabled, because I do not want openjdk in make dependencies).

Why are you needed to install all panels to make this: just because it builds one time to rule them all: it build GTK-only dependent static library (it will not be installed) and then actual plugins for all panels (XFCE, MATE, vala-panel and budgie-panel). If I split a package, it will build static library and Registrar four times, which I do not want, because I have vala-panel, MATE and budgie).

andreyorst commented on 2018-03-10 19:21 (UTC)

Whoa.. I've just read a post in Kai Uwe's Blog http://blog.broulik.de/2018/03/gtk-global-menu, about GTK global menus in plasma 5.13, and was curious to install this package just in case so I don't forget about it when 5.13 is released. And.. Do I really need xfce4-panel, vala-panel-git, budgie-desktop (OMG why you even need a desktop as dependency?) and all the rest of 63 dependencies just to have appmenu-gtk-module-git in my plasma setup?.. Or I can install it with -Sdd? I don't want unused packages in my system, espeshially if it is anothed DE packages which I wont use anyway.

Why pull all kind of panels with appmenu package? I think it makes no sence in any DE, not only in KDE Plasma. Is there a some kind of mistake?