On Wed, Sep 25, 2013 at 10:41:15AM -0000, Sebastien Bacher wrote: > > Handle in what way? I guess a message will be delivered to u-s-s > somehow? > > My understanding is that it's going to go through the normal mimetype > handling mechanism, which means clicking on "settings://...." is going > to call the default handle for settings: (which is u-s-s) "system- > settings settings://system/sound" for example ... we should parse the > "settings://system/<name>" argument as a request to open "<name>"
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. Not sure how it interacts with the single instance stuff though. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
