[Touch-packages] [Bug 1436927] Re: Scopes - (web)App communication really clunky
** Changed in: unity8 (Ubuntu) Status: Incomplete = Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436927 Title: Scopes - (web)App communication really clunky Status in Ubuntu UX: Opinion Status in unity8 package in Ubuntu: Opinion Bug description: This is a bug for scopes in general. Please move it if this is not the correct package. There is a lot of potential in the scopes concept, but I think the current implementation leaves much to be desired. Take the music app/scope as an example. If you want to play a local song you have two options: Either play it in the scope, or open the real music app and play it there. I think there should not be a distinction between these to. Playing a song in the music scope should have the same behaviour as the rhytmbox intigration in Unity7. Clicking play opens the music app in the background and starts playing the song. Music controls are still available in the scope itself. There is a lot of potential here. If you embrace this concept a bit more, the music scope can become your everythingplayer. Playing local music and soundcloud music as if they were all in the same app.. The scope is only the aggregate of data, the actual playback is handled by the underlying (web)apps. There is currently a clear distinction between what information and actions are app-related and which are not. I thing the scope concept really suffers from this. Scope should be aggregates of data and functions, not a portal to different apps. The music scope is not the only one suffering from this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436927] Re: Scopes - (web)App communication really clunky
unity8 waiting for design - Incomplete ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436927 Title: Scopes - (web)App communication really clunky Status in Ubuntu UX: Opinion Status in unity8 package in Ubuntu: Incomplete Bug description: This is a bug for scopes in general. Please move it if this is not the correct package. There is a lot of potential in the scopes concept, but I think the current implementation leaves much to be desired. Take the music app/scope as an example. If you want to play a local song you have two options: Either play it in the scope, or open the real music app and play it there. I think there should not be a distinction between these to. Playing a song in the music scope should have the same behaviour as the rhytmbox intigration in Unity7. Clicking play opens the music app in the background and starts playing the song. Music controls are still available in the scope itself. There is a lot of potential here. If you embrace this concept a bit more, the music scope can become your everythingplayer. Playing local music and soundcloud music as if they were all in the same app.. The scope is only the aggregate of data, the actual playback is handled by the underlying (web)apps. There is currently a clear distinction between what information and actions are app-related and which are not. I thing the scope concept really suffers from this. Scope should be aggregates of data and functions, not a portal to different apps. The music scope is not the only one suffering from this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436927] Re: Scopes - (web)App communication really clunky
** Changed in: ubuntu-ux Status: New = Opinion ** Changed in: ubuntu-ux Assignee: (unassigned) = Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436927 Title: Scopes - (web)App communication really clunky Status in Ubuntu UX bugs: Opinion Status in unity8 package in Ubuntu: New Bug description: This is a bug for scopes in general. Please move it if this is not the correct package. There is a lot of potential in the scopes concept, but I think the current implementation leaves much to be desired. Take the music app/scope as an example. If you want to play a local song you have two options: Either play it in the scope, or open the real music app and play it there. I think there should not be a distinction between these to. Playing a song in the music scope should have the same behaviour as the rhytmbox intigration in Unity7. Clicking play opens the music app in the background and starts playing the song. Music controls are still available in the scope itself. There is a lot of potential here. If you embrace this concept a bit more, the music scope can become your everythingplayer. Playing local music and soundcloud music as if they were all in the same app.. The scope is only the aggregate of data, the actual playback is handled by the underlying (web)apps. There is currently a clear distinction between what information and actions are app-related and which are not. I thing the scope concept really suffers from this. Scope should be aggregates of data and functions, not a portal to different apps. The music scope is not the only one suffering from this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436927] Re: Scopes - (web)App communication really clunky
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436927 Title: Scopes - (web)App communication really clunky Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: New Bug description: This is a bug for scopes in general. Please move it if this is not the correct package. There is a lot of potential in the scopes concept, but I think the current implementation leaves much to be desired. Take the music app/scope as an example. If you want to play a local song you have two options: Either play it in the scope, or open the real music app and play it there. I think there should not be a distinction between these to. Playing a song in the music scope should have the same behaviour as the rhytmbox intigration in Unity7. Clicking play opens the music app in the background and starts playing the song. Music controls are still available in the scope itself. There is a lot of potential here. If you embrace this concept a bit more, the music scope can become your everythingplayer. Playing local music and soundcloud music as if they were all in the same app.. The scope is only the aggregate of data, the actual playback is handled by the underlying (web)apps. There is currently a clear distinction between what information and actions are app-related and which are not. I thing the scope concept really suffers from this. Scope should be aggregates of data and functions, not a portal to different apps. The music scope is not the only one suffering from this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436927] Re: Scopes - (web)App communication really clunky
This is on our request list from our Product Management team already so there is a plan to work on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436927 Title: Scopes - (web)App communication really clunky Status in unity8 package in Ubuntu: New Bug description: This is a bug for scopes in general. Please move it if this is not the correct package. There is a lot of potential in the scopes concept, but I think the current implementation leaves much to be desired. Take the music app/scope as an example. If you want to play a local song you have two options: Either play it in the scope, or open the real music app and play it there. I think there should not be a distinction between these to. Playing a song in the music scope should have the same behaviour as the rhytmbox intigration in Unity7. Clicking play opens the music app in the background and starts playing the song. Music controls are still available in the scope itself. There is a lot of potential here. If you embrace this concept a bit more, the music scope can become your everythingplayer. Playing local music and soundcloud music as if they were all in the same app.. The scope is only the aggregate of data, the actual playback is handled by the underlying (web)apps. There is currently a clear distinction between what information and actions are app-related and which are not. I thing the scope concept really suffers from this. Scope should be aggregates of data and functions, not a portal to different apps. The music scope is not the only one suffering from this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
