Re: Integrate AppMenu into Workspace 4.9
Le jeudi 9 février 2012 23:40:07 Weng Xuetian a écrit : I would say give it a blacklist for some special application It'd already possible: http://www.tuxgarage.com/2011/05/disable-enable-global-menu-natty.html -- Cédric ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Integrate AppMenu into Workspace 4.9
Le vendredi 10 février 2012 00:22:21 Weng Xuetian a écrit : By the way GNOME is also doing something similar, though not knowing the implementation detail. http://live.gnome.org/ThreePointThree/Features/ApplicationMenu This is dbusmenu2, there is a qt branch but not active for now :-/ -- Cédric ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Integrate AppMenu into Workspace 4.9
Le vendredi 10 février 2012 12:12:04 Alex Fiestas a écrit : I take that the KDED won't register a com.canonical.Registrar until somebody is registered to it, right? Right. QMenu* menu = mRegistrarClient-menuForWinId(windowId()); Remember that we are going QML, QMenu is perfect for QWidgets but is really inconvinient either for QML or for stuff running in a thread (happened to me in the Runner). Is there any chance this library can return a Model? Hmm, this part is in appmenu-qt, not in kded lib... That's why i think appmenu should be merged as this... For an alternative presentation, we will have to wait for libdbusmenu2 and appmenu2-qt. Regards, -- Cédric ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Integrate AppMenu into Workspace 4.9
On Friday, February 10, 2012 12:41:34 PM Cedric Bellegarde wrote: Hmm, this part is in appmenu-qt, not in kded lib... That's why i think appmenu should be merged as this... For an alternative presentation, we will have to wait for libdbusmenu2 and appmenu2-qt. I don't see why we should wait for it, depending on dbusmenu2 timeline we may want to add Models to the current lib and then port'em (if possible) to dbusmenu2. For the Runner I end up talking directly to DBus because I needed Data so it is possible. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Integrate AppMenu into Workspace 4.9
Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Integrate AppMenu into Workspace 4.9
On Thursday 09 February 2012 16:07:13 Alex Fiestas wrote: Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? I'm all for it and would even say we go for default menu in windeco. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Integrate AppMenu into Workspace 4.9
On Thu, Feb 9, 2012 at 4:24 PM, Martin Gräßlin mgraess...@kde.org wrote: If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) Oh didn't know that, because the QML decoration thing? I'm all for it and would even say we go for default menu in windeco. In that case I would really love to see something like this: http://www.afiestas.org/improving-kde-applications-help-menu-actions-lookup/ But in this case I'd put the textbox at the bottom, what do you think? I can take some time today to try to do a PoC if you like the idea. BTW remember to reply to all, I'm not sure if gnumdk is in plasma-devel. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Integrate AppMenu into Workspace 4.9
On Thu, Feb 9, 2012 at 11:24 PM, Martin Gräßlin mgraess...@kde.org wrote: On Thursday 09 February 2012 16:07:13 Alex Fiestas wrote: Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? I'm all for it and would even say we go for default menu in windeco. Cheers Martin I would say give it a blacklist for some special application, such as gimp / inkscape. Current win deco menu button is not a good solution for those. For other menu-is-rarely-used-application (Maybe that's the most case), my two cents for putting it in windeco. By the way, is there anyway for people to implement some special appmenu only case like compact menu of firefox? I currently don't see it is possible with dbus menu. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Integrate AppMenu into Workspace 4.9
On 09.02.2012 17:31, Alex Fiestas wrote: I'm all for it and would even say we go for default menu in windeco. In that case I would really love to see something like this: http://www.afiestas.org/improving-kde-applications-help-menu-actions-lookup/ But in this case I'd put the textbox at the bottom, what do you think? I can take some time today to try to do a PoC if you like the idea. This looks a lot like Ubuntu's HUD [0]. I'd love to see that in KDE, maybe integrated with KRunner? [0] http://www.youtube.com/watch?v=w_WW-DHqR3c -- Andrei ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Integrate AppMenu into Workspace 4.9
On Thursday 09 February 2012 16:31:27 Alex Fiestas wrote: On Thu, Feb 9, 2012 at 4:24 PM, Martin Gräßlin mgraess...@kde.org wrote: If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) Oh didn't know that, because the QML decoration thing? no, because window tabbing is broken beyond any repair and Thomas is currently rewriting it and because of that we need adjustments to the API. We use this as an excuse to clean up a little bit and given that there are no 3rd party decorations except for skulpture, dekorator, bespin and QtCurve which are all developed by developers close to us it's not a big issue. I'm all for it and would even say we go for default menu in windeco. In that case I would really love to see something like this: http://www.afiestas.org/improving-kde-applications-help-menu-actions-lookup/ But in this case I'd put the textbox at the bottom, what do you think? I can take some time today to try to do a PoC if you like the idea. sounds like an awesome idea. I had seen this today for the first time in your linked video and really liked it. BTW remember to reply to all, I'm not sure if gnumdk is in plasma-devel. ups, but even in your mail only agateau was included... Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Integrate AppMenu into Workspace 4.9
On Thursday 09 February 2012 23:40:07 Weng Xuetian wrote: On Thu, Feb 9, 2012 at 11:24 PM, Martin Gräßlin mgraess...@kde.org wrote: On Thursday 09 February 2012 16:07:13 Alex Fiestas wrote: Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? I'm all for it and would even say we go for default menu in windeco. Cheers Martin I would say give it a blacklist for some special application, such as gimp / inkscape. Current win deco menu button is not a good solution for those. For other menu-is-rarely-used-application (Maybe that's the most case), my two cents for putting it in windeco. By the way, is there anyway for people to implement some special appmenu only case like compact menu of firefox? I currently don't see it is possible with dbus menu. No I think this is not yet possible. But it is something we should do in Frameworks 5. Just turning the menu from horizontal to vertical is not a perfect solution and I really like what Dolphin did to the collapsed menu. Firefox btw did a bad implementation: just try to navigate with keyboard only :-) Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Integrate AppMenu into Workspace 4.9
On Thu, Feb 9, 2012 at 4:50 PM, Martin Gräßlin mgraess...@kde.org wrote: On Thursday 09 February 2012 23:40:07 Weng Xuetian wrote: On Thu, Feb 9, 2012 at 11:24 PM, Martin Gräßlin mgraess...@kde.org wrote: On Thursday 09 February 2012 16:07:13 Alex Fiestas wrote: Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? I'm all for it and would even say we go for default menu in windeco. Cheers Martin I would say give it a blacklist for some special application, such as gimp / inkscape. Current win deco menu button is not a good solution for those. For other menu-is-rarely-used-application (Maybe that's the most case), my two cents for putting it in windeco. By the way, is there anyway for people to implement some special appmenu only case like compact menu of firefox? I currently don't see it is possible with dbus menu. No I think this is not yet possible. But it is something we should do in Frameworks 5. Why not? The new decorations are going to be QML based anyway so why not make the menu button a qml element that gets filled from a model or something.. That way it's perfectly themable, right? Or am i missing a point here? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
R: Integrate AppMenu into Workspace 4.9
Hi, I really like this idea, expecially because I'm dreaming of a KRunner version that uses voice recognition, so the user could do the main operations (and have access to applications menus) using the voice. But I don't know if there are problems in integrating AppMenu in the next version of Plasma. Luca Tringali Messaggio originale Da: afies...@kde.org Data: 09/02/2012 16.07 A: plasma-devel@kde.org Cc: agat...@kde.org Ogg: Integrate AppMenu into Workspace 4.9 Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Integrate AppMenu into Workspace 4.9
On Thu, Feb 9, 2012 at 11:50 PM, Martin Gräßlin mgraess...@kde.org wrote: On Thursday 09 February 2012 23:40:07 Weng Xuetian wrote: On Thu, Feb 9, 2012 at 11:24 PM, Martin Gräßlin mgraess...@kde.org wrote: On Thursday 09 February 2012 16:07:13 Alex Fiestas wrote: Hey there! It seems that people really likes AppMenu, we have fans of everything we have done with it so far: -oxygen-appmenu -plasmoid -runner So it seems clear to me that we should integrate this technology into Workspace 4.9, but before we do it would be good to hear opinions about these questions: -Is there any way of integrating oxygen-appmenu without breaking api-abi? Maybe a second version of the API? If that refers to KWin decoration API: no problem as we are going to break deco API in 4.9 anyway :-) -How the KDED works? -Is there any plans to extend libdbusmenu-qt to make it export the menu as a model? -Do we need something else to complete our support? documentation maybe? -What is the status of it being merged into GTK ? Personally I think that AppMenu is a powerful technology that will allow us to decide how and when show the menubars which sure will be handy in the future. So, what do you think of AppMenu? I'm all for it and would even say we go for default menu in windeco. Cheers Martin I would say give it a blacklist for some special application, such as gimp / inkscape. Current win deco menu button is not a good solution for those. For other menu-is-rarely-used-application (Maybe that's the most case), my two cents for putting it in windeco. By the way, is there anyway for people to implement some special appmenu only case like compact menu of firefox? I currently don't see it is possible with dbus menu. No I think this is not yet possible. But it is something we should do in Frameworks 5. Just turning the menu from horizontal to vertical is not a perfect solution and I really like what Dolphin did to the collapsed menu. Firefox btw did a bad implementation: just try to navigate with keyboard only :-) Yes keyboard navigate is simply broken for firefox.. By the way, is it possible to make win deco use another menu right now? For example, can dolphin use its collapsed menu if windeco menu is used, or if it's not possible automatically, can dolphin manually do it? By the way GNOME is also doing something similar, though not knowing the implementation detail. http://live.gnome.org/ThreePointThree/Features/ApplicationMenu Seems they try to give application a global hint via a daemon for what kind of menu they can make use of, in order to choose different kinds of menu to meet the specific environment. Traditional menu is not a good idea for all application, but putting existing traditional menu directly into windeco is also not a good idea for me (this can be done later, but if windeco is pushed by default, might break some sort of user experience for specific application). ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Re: Integrate AppMenu into Workspace 4.9
On Friday 10 February 2012 00:22:21 Weng Xuetian wrote: By the way, is it possible to make win deco use another menu right now? For example, can dolphin use its collapsed menu if windeco menu is used, or if it's not possible automatically, can dolphin manually do it? yes, that's what I meant with needs support in Frameworks 5. We need to add an API to allow applications to export a specific menu. By the way GNOME is also doing something similar, though not knowing the implementation detail. http://live.gnome.org/ThreePointThree/Features/ApplicationMenu Seems they try to give application a global hint via a daemon for what kind of menu they can make use of, in order to choose different kinds of menu to meet the specific environment. Traditional menu is not a good idea for all application, but putting existing traditional menu directly into windeco is also not a good idea for me (this can be done later, but if windeco is pushed by default, might break some sort of user experience for specific application). interesting, that sounds like a good opportunity to collaborate. signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
