Need strategy for dealing with URIs in the run time
Bug #1343891 reported by
Michi Henning
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-scopes-api (Ubuntu) |
New
|
Wishlist
|
Unassigned | ||
Bug Description
We currently have a custom URI parser kicking around, which is sub-optimal.
We also have the issue of normalizing things that can show in config files, such as the URL for a scope logo and, potentially, things such as icon and art (which could conceivably be remote).
Post-RTM, we need to make a decision of how to deal with URIs in the run time and hopefully replace the custom parser with something else. Only available options at the moment appear to be Qt or liburiparser-dev (C API).
Revision history for this message
| Michi Henning (michihenning) wrote | #1 |
| affects: | unity-scopes-api → unity-scopes-api (Ubuntu) |
| Changed in unity-scopes-api (Ubuntu): | |
| importance: | Medium → Wishlist |
To post a comment you must log in.
Another one seems to be https:/