Public bug reported:
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...
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436927
Title:
Scopes -> (web)App communication really clunky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436927/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
