On Wed, 2013-09-25 at 10:59 +0000, Iain Lane wrote: > Why does it have to pass the whole string? The settings://system/ part > is only interesting to the URL dispatcher so it can find out what to > launch. It'd make the application code nicer if we only had to take the > information which is interesting to us - the name of the panel. As a > bonus we already handle this.
Because the activation mechanisms only work with URIs, they don't pass parameters. Parameters are only added on the Desktop File Exec line. For most applications they need the full URI as it's a file or website. System Settings really is the exception here. In the future we could implement something like this with desktop actions, but we're not going to support those in the 13.10 timeframe. They are on my desired list for 14.04 though. On Wed, 2013-09-25 at 10:59 +0000, Iain Lane wrote: > Not sure how it interacts with the single instance stuff though. They will work together. We expect a QML plugin to land tomorrow that'll provide a signal of a new URL if the application is already running. Upstart App Launch will also take care of discussing with Unity to unsuspend any suspended applications as well and making sure they get focus. On Wed, 2013-09-25 at 11:53 +0000, Alberto Mardegan wrote: > I think that the value is in that using URLs is easier than an array > of strings. > However Seb raised a very valid point, about the risks of exposing > System Settings via those URLs. Will the url-dispatcher implement some > kind of ACL, to make sure that only whitelisted apps can request > certain URLs? The URLs are only used to start a new application under confinement. So that application would be brought to focus and shown to the user. There's no way to do operations that return values or otherwise allow for interaction with the application. Ubuntu Security is aware of this and has signed off on the architecture. It is important that application ensures that it handles the URL well. Since it is a regular expression we can provide more protection to system settings if that'd be useful. For instance only allowing characters after the final "/". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227690 Title: should support settings://system/<...> urls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1227690/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
