February 2, 2010
Cross Platform Hybrid Communication
For those who wish to develop their own hybrid library or framework here is a table that may be of help. It also explains how QuickConnect communicates back and forth with the native device code on multiple platforms.
Key:
- URL data transfer – Information must be passed as if the view was being updated with a new page to display or, in the Case of Android, and HTML “JavaScript:” URL is used.
- Direct Call – JavaScript objects are available from the underlying language or underlying objects are available from within JavaScript depending on the direction of the call.
- Built In – The native development environment is HTML, CSS, and JavaScript.
Device | To Native | From Native |
---|---|---|
iPhone/touch/iPad | URL data transfer | Direct Call |
Android | Direct Call | URL data transfer |
Blackberry | Direct Call | Direct Call |
Palm WebOS | Built In | Built In |
Nokia/Symbian with QT | Direct Call | Direct Call |
February 1, 2010
Milestone Passed!
Today QuickConnect passed the 12,000 downloads mark. Thank you!
It looks like the rate for the last few days is between 50 and 100 downloads per day.
The development blog will pass 90,000 hits today.
Thanks again for your support.
Lee
QuickConnect Always Open
Apparently the PhoneGap team, a competitor to QuickConnect, has run into a storm. Initially they stated that any contributors of code are required to sign a legally binding document essentially turning over rights to the code being submitted. Contributors and potential contributors were understandably upset and asking for clarifications.
Nitobe has now changed their statement and are now saying that they are only proposing this requirement due to talks with their lawer. It looks like contributors are still having a strong, negative reactions.
I can’t help but put this action together with the rumors I’m hearing from multiple independent sources that the Nitobe company, owner of PhoneGap, is actively or passively (depending on the source) seeking someone to buy PhoneGap. I guess, and it is only a guess, that they aren’t making the money they had hoped.
QuickConnect comes from a very different direction.
I’ve been doing the preliminaries to create a non-profit organization for QuickConnect so as to avoid these kinds of problems. This non-profit would run the conferences, manage user groups, and all of those other types of things that you are used to when you think of an open source project.
I’ve never planned on making money on QC. I’ve worked on QC since March 2008 for enjoyment and to help you. Helping you and talking with you is what makes this fun and is my payback.
I love it when you send me questions via the QC Google group or when I’ve been able to talk with you via twitter, email or phone.
I also love getting your feedback and working toward what you need.
Thank you.
Update: I just got off the Nitobe phone call with their users. They say that they are doing this at the request of Symbian and that Symbian is interested in putting it on their phones as a development environment. That is all Symbian needs. One more development environment. They already have FOUR. Do they really need another? How does a developer know which Symbian environment to pick? I feel for anyone developing for that platform.