update 23 Nov 2011: doesn't work in 2.0.0-4867 (RIM blocks the port for local connection)
update 8 Dec 2011: if you have rooted your playbook, reenable localbar by:
Code:
cat /etc/pf.conf | grep -v '443'| pfctl -f-
Put it in startup.sh to make it automatic.
update 3 Feb 2012: by startup.sh, i meant the one in /accounts/devuser/
Hi,
I just quickly developed an app that will allow you to install signed BAR files directly from your PlayBook. This app is called LocalBar. To install it for the first time, you will need to sideload the app using some methods that you can find in this forum.
You can download the app, and see the guide from my website:
Edit I was in a hurry when I posted the original message. Here are some additional details:
- I am using https://localhost method. To put it simply: it works like other desktop installers that connect via network or USB, it sends commands to an HTTP service in the playbook. The only difference is that it works through the playbook itself.
- It is possible that in the future RIM may block requests from localhost
- I don't have time to develop nice GUI for this, so I just use the basic GUI API that is accessible using NDK. For example: in the NDK there is a "login dialog" but no "password dialog", so for the password dialog I use the "login dialog" that shows the "user" field (which I don't need).
- This works on OS 1.0.7 and on 2.0
- With this you can sort of OTA install through the playbook. From your PlayBook Just go to a website that has some bar files (for example this forum) , download it using the built in playbook browser, then run LocalBar to install the downloaded bar files.
Nice job! I'm going to take a stab in the dark here, but are you using bps_event_create() to push an install request into the queue?
EDIT:
Nevermind, looks like you're installing it through the https://localhost/ method. Still great work! I'm sure now that the method has been uncovered, there is bound to be some new life breathed into the PB before next year.
Nice job! I'm going to take a stab in the dark here, but are you using bps_event_create() to push an install request into the queue?
EDIT:
Nevermind, looks like you're installing it through the https://localhost/ method. Still great work! I'm sure now that the method has been uncovered, there is bound to be some new life breathed into the PB before next year.
all the technicalities of the playbook really interest me; can you explain how this method works, even if in short?
Nice job! I'm going to take a stab in the dark here, but are you using bps_event_create() to push an install request into the queue?
EDIT:
Nevermind, looks like you're installing it through the https://localhost/ method. Still great work! I'm sure now that the method has been uncovered, there is bound to be some new life breathed into the PB before next year.
Yes, you are correct, I am using the https://localhost method. I was wondering why one one implemented this idea before.
It is quite obvious that in development mode we can Install apps through the network, so using the same protocol we can install apps directly from the playbook.
all the technicalities of the playbook really interest me; can you explain how this method works, even if in short?
I have edited my original post to explain this. This is how it works:
When you use the desktop sideloader, you enter an IP address, then connect through the network to that IP address.
LocalBar uses the same protocol, but since it knows that it connect to the same IP address as itself, it can just use "localhost" as the connection address.