Re: [Elementary-dev-community] [Merge] lp:~elementary-dev-community/wingpanel/bug-fix-1007630 into lp:wingpanel
How, o how many times shall I tell you to use elementary-test-merge for reproducible builds and testing, instead of doing everything manually? Are you not bored to do the download-compile-run cycles manually yet? sudo apt-get install elementary-testing-scripts elementary-test-merge https://code.launchpad.net/~elementary-dev-community/wingpanel/bug-fix-1007630/+merge/181999 And it compiles and installs. Please don't bother doing all this manually. -- https://code.launchpad.net/~elementary-dev-community/wingpanel/bug-fix-1007630/+merge/181999 Your team elementary Developer Community is subscribed to branch lp:~elementary-dev-community/wingpanel/bug-fix-1007630. -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] [Merge] lp:~elementary-dev-community/wingpanel/bug-fix-1007630 into lp:wingpanel
It does fix the bug for me. -- https://code.launchpad.net/~elementary-dev-community/wingpanel/bug-fix-1007630/+merge/181999 Your team elementary Developer Community is subscribed to branch lp:~elementary-dev-community/wingpanel/bug-fix-1007630. -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] Future of Wingpanel
Sergey, What do you mean by 'embedding indictors into apps'? Does it mean one installs for example Noise and the soundindicator is installed as well but not as a separate package? If that's the case, what if a user wants to install another music player which makes use of the sound indicator? Additionally, how difficult will it be/ what effort will it take to backport upstream changes made to for example the sound indicator to the particular apps? Regards Kurt On 26-08-13 11:04, Sergey Shnatsel Davidoff wrote: [...] Voldyman showed off a cool proof of concept for libpeas-based plugs yesterday, but it's not necessarily the best architecture if we choose to embed indicators into apps (e.g. sound indicator in Audience). I'd like to talk to designers first and see what are the use cases for this feature, and if there's a sufficient number of indicators that should be embedded. Otherwise we could use the libpeas-based architecture and simply provide minimal D-bus interfaces to indicators like Sound. -- Sergey Shnatsel Davidoff OS architect @ elementary -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] Future of Wingpanel
Kurt, What Sergey means is having apps, like Audience (and I think Pantheon-Greeter as well), which have a fullscreen mode (which hides wingpanel), which can still display indicators that are essential to them. So for the video-player Audience it is handy to still provide access to the sound indicator such that it can be used for adjusting the volume. Kind regards, Pim Vullers On 08/26/2013 01:22 PM, Kurt Smolderen wrote: Sergey, What do you mean by 'embedding indictors into apps'? Does it mean one installs for example Noise and the soundindicator is installed as well but not as a separate package? If that's the case, what if a user wants to install another music player which makes use of the sound indicator? Additionally, how difficult will it be/ what effort will it take to backport upstream changes made to for example the sound indicator to the particular apps? Regards Kurt On 26-08-13 11:04, Sergey Shnatsel Davidoff wrote: [...] Voldyman showed off a cool proof of concept for libpeas-based plugs yesterday, but it's not necessarily the best architecture if we choose to embed indicators into apps (e.g. sound indicator in Audience). I'd like to talk to designers first and see what are the use cases for this feature, and if there's a sufficient number of indicators that should be embedded. Otherwise we could use the libpeas-based architecture and simply provide minimal D-bus interfaces to indicators like Sound. -- Sergey Shnatsel Davidoff OS architect @ elementary -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] Future of Wingpanel
Thanks for the clarification! On 26-08-13 13:33, Pim Vullers wrote: Kurt, What Sergey means is having apps, like Audience (and I think Pantheon-Greeter as well), which have a fullscreen mode (which hides wingpanel), which can still display indicators that are essential to them. So for the video-player Audience it is handy to still provide access to the sound indicator such that it can be used for adjusting the volume. Kind regards, Pim Vullers On 08/26/2013 01:22 PM, Kurt Smolderen wrote: Sergey, What do you mean by 'embedding indictors into apps'? Does it mean one installs for example Noise and the soundindicator is installed as well but not as a separate package? If that's the case, what if a user wants to install another music player which makes use of the sound indicator? Additionally, how difficult will it be/ what effort will it take to backport upstream changes made to for example the sound indicator to the particular apps? Regards Kurt On 26-08-13 11:04, Sergey Shnatsel Davidoff wrote: [...] Voldyman showed off a cool proof of concept for libpeas-based plugs yesterday, but it's not necessarily the best architecture if we choose to embed indicators into apps (e.g. sound indicator in Audience). I'd like to talk to designers first and see what are the use cases for this feature, and if there's a sufficient number of indicators that should be embedded. Otherwise we could use the libpeas-based architecture and simply provide minimal D-bus interfaces to indicators like Sound. -- Sergey Shnatsel Davidoff OS architect @ elementary -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] [Merge] lp:~elementary-dev-community/wingpanel/bug-fix-1007630 into lp:wingpanel
Review: Approve So, tigrang's branch was Needs Fixing because designers don't want the arrows on the edge of the indicators. Therefore, this branch needs ~elementary-design input too. Personally, I think it's better to have them there than to have a buggy indicators experience. Still, it's up to them, since I approve the code (had already approved tigrang's). -- https://code.launchpad.net/~elementary-dev-community/wingpanel/bug-fix-1007630/+merge/181999 Your team elementary Developer Community is subscribed to branch lp:~elementary-dev-community/wingpanel/bug-fix-1007630. -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] [Merge] lp:~elementary-dev-community/wingpanel/bug-fix-1007630 into lp:wingpanel
bazaar.launchpad.net/~elementary-dev-community/wingpanel/bug-fix-1007630/revision/150 I mean, I approved what tigrang did and now I also approve that. -- https://code.launchpad.net/~elementary-dev-community/wingpanel/bug-fix-1007630/+merge/181999 Your team elementary Developer Community is subscribed to branch lp:~elementary-dev-community/wingpanel/bug-fix-1007630. -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
[Elementary-dev-community] Luna on ARM
Hey guys, Just a heads-up regarding ARM support in Luna: our stable PPA got armhf enablement recently and everything (except Pantheon Greeter, see https://bugs.launchpad.net/pantheon-greeter/+bug/1214833) should run fine on ARM, at least in theory. You'd need decent GPU drivers though, because Gala requires hardware acceleration, and software rendering on ARM is in a pitiful state. However, our OS-specific patches repository did not get ARM enablement, and it's unlikely to get it anytime soon because we patched some really heavyweight things like Qt, which take way more time to build than Canonical's armhf enablement conditions require. This means we can't make OS images for ARM, but you can still install the apps on an existing Ubuntu installation. You'll miss out on the leaner and faster core, which is a pity (and doubly so on a resource-constrained system), but at least there's a chance of finding an OS image that works for your ARM hardware in case of Ubuntu and almost no chance for any other distro. Enthusiasts can still build ARM images by themselves if they have the hardware to run the build process or if they know their way around QEMU chroots (along the lines of https://wiki.debian.org/ArmHardFloatChroot and https://wiki.debian.org/QemuUserEmulation but for Ubuntu). They'd have to use something like apt-build to update to later versions of our patched packages, but such updates will probably be rare and all in all it should work. -- Sergey Shnatsel Davidoff OS architect @ elementary -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
Re: [Elementary-dev-community] Future of Wingpanel
Personally, I think there's no need to be complicated with the Audience stuff. When Audience is fullscreen wingpanel will just fade out, and when the user moves their mouse near wingpanel it fades back in. On Aug 26, 2013 11:33 AM, Pim Vullers p...@vullersmail.nl wrote: Kurt, What Sergey means is having apps, like Audience (and I think Pantheon-Greeter as well), which have a fullscreen mode (which hides wingpanel), which can still display indicators that are essential to them. So for the video-player Audience it is handy to still provide access to the sound indicator such that it can be used for adjusting the volume. Kind regards, Pim Vullers On 08/26/2013 01:22 PM, Kurt Smolderen wrote: Sergey, What do you mean by 'embedding indictors into apps'? Does it mean one installs for example Noise and the soundindicator is installed as well but not as a separate package? If that's the case, what if a user wants to install another music player which makes use of the sound indicator? Additionally, how difficult will it be/ what effort will it take to backport upstream changes made to for example the sound indicator to the particular apps? Regards Kurt On 26-08-13 11:04, Sergey Shnatsel Davidoff wrote: [...] Voldyman showed off a cool proof of concept for libpeas-based plugs yesterday, but it's not necessarily the best architecture if we choose to embed indicators into apps (e.g. sound indicator in Audience). I'd like to talk to designers first and see what are the use cases for this feature, and if there's a sufficient number of indicators that should be embedded. Otherwise we could use the libpeas-based architecture and simply provide minimal D-bus interfaces to indicators like Sound. -- Sergey Shnatsel Davidoff OS architect @ elementary -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
