Oh, I misunderstood. I thought you were getting a URL from Thingworx, but it sounds like the actual image data itself is in Thingworx.
That's a little trickier. You can certainly point a VS image object to a remote URL. But I don't think Thingworx exposes image properties on Things as simple URLs. (If you were storing the images in a FileRepository thing, then you could use that approach.)
In this case, you'll probably have to use the GetImagePropertyValue service, which should return the image as a data object. So you'd have to use Javascript to create an data URL and assign it to the image widget, something like this:
$scope.test = function() {
$rootScope.$broadcast('app.mdl.VuforiaChatThing.svc.GetImagePropertyValue');
}
$rootScope.$on("GetImagePropertyValue-complete", function(evt, data) {
var imagedata = data.data[0].result;
$scope.setWidgetProp("image-1", "imgsrc", "data:image/png;base64," + imagedata);
});
For this to work, you'll need to add the GetImagePropertyValue service from your Thing in VS, and you'll need to set the "name" parameter, either as static or via scripting or Application Parameter binding. You may also need to tweak the data URL header so the MIME type is correct for your image type (PNG, JPG, GIF, etc.).
