I have two concerns: - Just looking whether a file is installed somewhere isn't going to work. That's because the installation locations aren't fixed. For example, it's possible to run multiple scopes run times side-by-side on the same machine without having them interfere with each other, by changing configuration files. Among other things, tests and the SDK rely on being able to change configurations. But, to figure out what the current configuration is requires a fair bit of heavy lifting in terms of parsing configuration files and the like.
Now, we sure can do this. But, to do it right, we'll have to spin up a client-side run time. This isn't all that cheap (about 35 ms on a Nexus 4). So, doing this would be worth it only if you could keep that run time around for multiple queries. Spinning up and shutting down a separate run time instance just to answer a single question is simply too expensive. - I'm reluctant to add knowledge about how things are packaged into the scopes run time with, really, has no business knowing about such things. Could you look through the click manifests somehow instead to figure this out? Seeing that click knows everything about packaging already, that would seem cleaner? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465675 Title: API needed to determine if App ID is a scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1465675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
