01-30-2011 10:06 PM
I have been working with some my colleague on projects related to WebWorks application, but there are some technical concerns which our developers really wish to know and ask for some professional advice.
2) SQLite on HTML5
HTML5 provides SQLite standard to let us store data in a SQLite database format. But the SQLite file seems only restricted to be used within the WebWorks Application. I wonder if there are any ways we can read these SQLite file from other application (Other WebWorks Application, or Java Application) ?
In fact, what I want to know is the feasibility to have a WebWorks Application that manipulate a SQLite file which is received from server side on-the-fly, then send it back the whole SQLite file to server.
It would be appreciate if some of you can give some advices on this, thank you.
Solved! Go to Solution.
01-31-2011 08:39 AM
1) i didn't start to play with playbook simulator, but i the webwork extension provided are implemented with action script/adobe air, so i think, we have to program with adobe air to create our own extensions. You have to know that playbook has not a java vm yet.
2)I think the answer is no. Webwork apps use sqlite encrypted files, so only webworks application could access to the database.
01-31-2011 10:18 AM
lasterra is correct on both points...
We have not yet released details on creating extensions in AIR for WebWorks on PlayBook. We are currently working on putting the final open source touches on the WebWorks for PlayBook SDK so that we can upload it to github. The full source code to the platform will be available on github so that you can see everything that is going on under the hood.
This new architecture will be a preview of the WebWorks platform architecture moving forward.
Details on creating extensions in AIR will be coming.. but currently the main underlying API platform on the BlackBerry PlayBook is AIR and the functionality of an extension will be limited to what is possible on the AIR platform and its extensions.
As the PlayBook's development options evolve, so too will the architecture of the WebWorks platform... I can't really say much more than that right now