Why Safari support has become important

Posted by tkouts on 24 September 2008 | 0 Comments

Tags: quix, safari, iphone, chrome

The next version of Porcupine - hopefully to be released in October - will include the new version of QuiX that supports the Safari browser. When I started developing this new feature, I never realized how beneficial it would turn out in the mean time.

After having done some tests on iPhone, it turns out that you can run full featured QuiX based applications on mobile Safari. Ideally, you will need to write a separate QuiX based front end for your iPhone application, using Apple's guidelines. Having a desktop on a small screen is not usable and there are a lot of unsupported actions like double clicks and drag and drop.
The RPC interface of your application can be shared between both the dekstop and the mobile versions of your application.

Then Google releases Chrome, a new browser that is based on Webkit, the same rendering engine that Safari uses. With some minor tweaking I managed to run the Porcupine desktop in Chrome within a couple of hours. Therefore, the next version of Porcupine is going to support Google Chrome too.

For those who can't wait to test these new features, you can check out the latest development version.

Clicky Web Analytics