In box we have been playing with LocalBar on your PlayBook all weekend we might be meddlesome in this. Yohan, a developer of LocalBar, posted on his blog charity a bit of discernment into how LocalBar works and what it does. In hint he is replicating a sideloading routine from a PC by behaving it regulating a PlayBook NDK to bucket apps from Localhost. This is a penetrate RIM could substantially simply retard by restraint sideloading from Localhost though we unequivocally wish they DO NOT confirm to do that. If anything RIM should be compelling OTA downloads given that is a usually approach for Beta Testing and even their possess Beta Zone judgment to work on a PlayBook.
Here is how Yohan describes LocalBar:
- I am regulating https://localhost method. To put it simply: it works like other desktop installers that bond around network or USB, it sends commands to an HTTP use in a playbook. The usually disproportion is that it works by a playbook itself.
- It is probable that in a destiny RIM might retard requests from localhost
- I don’t have time to rise good GUI for this, so we only use a simple GUI API that is permitted regulating NDK. For example: in a NDK there is a “login dialog” though no “password dialog”, so for a cue dialog we use a “login dialog” that shows a “user” margin (which we don’t need).
- This works on OS 1.0.7 and on 2.0 (developer beta)
- With this we can arrange of OTA implement by a playbook. From your PlayBook Just go to a website that has some bar files (for instance this forum) , download it regulating a built in playbook browser, afterwards run LocalBar to implement a downloaded bar files.