<cimi> [15:37] kenvandine, hey ken!! :)
<cimi> [15:38] kenvandine, so your https://code.launchpad.net/~ken-vandine/unity8/share_data_uri_string/+merge/286676 - you sure we are supposed to support just a single string and not more than one?
<kenvandine> [15:42] cimi, well in a preview you are generally only working with a single item right?
<kenvandine> [15:42] cimi, and... the API sounds singular to me, shareData[uri]
<kenvandine> [15:42] not uris
<kenvandine> [15:42] sure we could make it handle multiples there, but the scope side needs to know it's an array
<kenvandine> [15:43] cimi, is it possible for the preview to be showing multiple images?
<pstolowski> [15:45] kenvandine, yes, see apps previews in Apps scope
<pstolowski> [15:45] cimi, I think we agreed on supporting VariantArray there as well for multiple uris?
<kenvandine> [15:45] ok, then the share-data API should be clear that it takes an array
<kenvandine> [15:46] so rename uri to uris
<cimi> [16:03] pstolowski, oh yeah answer is yes
<pstolowski> [16:05] cimi, afair we wanted to allow a single string or array, up to scope author
<pstolowski> [16:06] not sure about renaming to 'uris' though
<pstolowski> [16:07] most scopes will be interested in a single uri
<kenvandine> [16:07] i think if it expects and array, it should be uris
<kenvandine> [16:07] if you can determine it's an array or string in QML, then cool
<pstolowski> [16:10] the point is it should accept a single string (expected for 99% of scopes), but then also deal with array of strings
<cimi> [16:13] pstolowski, or nor creating an array with a single string inside?
<pstolowski> [16:13] cimi, yeah, the idea was we don't require scope to create an array with single string if it only wants a single strin
<pstolowski> [16:13] g
<kenvandine> [16:14] ok, well the code that was there always assume it was an array