The silent agreement in the Unity lens interactions is that the URI column is very free form and mostly internal (wow, can we get more sloppy? ;-)). We've introduced another address mechanism for results which is, for now, called the "external uri" - or maybe justifiably a URL. This external URI *must* be correct and addressable from the outside (hence URL makes sense). So I think we can document our selves out of this problem?
Robert Carr committed a fix to the apps lens to support this:
revno: 227.1.1
committer: Robert Carr <email address hidden>
branch nick: unity-lens-applications
timestamp: Fri 2011-09-09 11:20:33 -0400
message:
Use the get_path method of AppInfoManager to pass full URIs for desktop files to unity. Lets us drag and drop an application to the desktop fo example
The silent agreement in the Unity lens interactions is that the URI column is very free form and mostly internal (wow, can we get more sloppy? ;-)). We've introduced another address mechanism for results which is, for now, called the "external uri" - or maybe justifiably a URL. This external URI *must* be correct and addressable from the outside (hence URL makes sense). So I think we can document our selves out of this problem?
Robert Carr committed a fix to the apps lens to support this:
revno: 227.1.1 applications
committer: Robert Carr <email address hidden>
branch nick: unity-lens-
timestamp: Fri 2011-09-09 11:20:33 -0400
message:
Use the get_path method of AppInfoManager to pass full URIs for desktop files to unity. Lets us drag and drop an application to the desktop fo example