Limitations of Vuforia Studio compared to Unity
Hi,
I am currently working on getting my feet wet with Vuforia Studio and am trying to reimplement a Usecase from Unity within Vuforia Studio.
I am now curious about the limitations of Vuforia studio. The usecase is an AR app for the Microsoft Hololens augmenting a machine, showing a customized 3D UI, that allows the user to interact with 3D buttons and the machine itself. (This is currently implemented with Unity and Vuforia SDK)
As far as i have seen now, Studio has events for hololens gestures like holding, doubletap, swiping, but i cannot seem to get a normal "click" working. The JS field for "click" on a model itself doens't seem to be triggered by a hololens click ?!?
Am I missing something? Is it possible to interact with the scene and its models (colliders), buttons, etc. like it is in Unity?
Can i get REST Api calls from a Vuforia studio javascript function or do i need to have Thingworx composer running in the background for that?
(I am currently only working with the trial version, which has a composer, but I cannot create any new things etc, because of restricted permissions)
The default Home.js is the place where all javascript functions are stored. is there a possibility to create a second file to reduce the size of that single file and to tidy up things a little bit?
Can't we select multiple objects in the Editor, or group them together, so you can reposition multiple elements all at once? (also having a shared pivot point for multiple objects by grouping would be handy too)
And final question. is there a nice documentation available for all the keywords used ike $scope, $element etc. and how to use it properly?

