incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lorin Beer <>
Subject Re: Project Pender for inclusion in Cordova-labs
Date Fri, 15 Jun 2012 15:52:51 GMT
1. Well, there is no canvas element per se, it's actually an opengl view. So anything the view
system of the platform can do, Pender can do. Early testing on Android proved that we can
still render efficiently with a PhoneGap web view overlaid on to a Pender gl view. With transparency
set, and the PhoneGap app written with a dynamic background in mind, they cooperate quite
nicely overlaid on one another, or in split screen.

A little wizardry would be necessary, but we could pull a similar trick and make the Pender
GL view look as though it was an element on a page. 


On 2012-06-14, at 7:01 PM, Michael Brooks wrote:

> Cool stuff Lorin!
> One question:
> 1) Can you use Pender with embedded canvas elements or must the canvas
> element be fullscreen?
> Long ago, I remember Jesse MacFadyen played around with embedding UIKit
> elements inside of the iOS UIWebView. Using of the offset and dimensions of
> the <div/> placeholder, he could overlay the UIKit component in the correct
> position. The result was that you can scroll the webview and the native
> component looked as though it was embedded inside the webpage.
> Michael
> On Thu, Jun 14, 2012 at 6:38 PM, Patrick Mueller <> wrote:
>> On Thu, Jun 14, 2012 at 5:25 PM, Lorin Beer <> wrote:
>>> Project Pender provides a hardware accelerated 2D graphics api wit JS
>>> hooks for mobile devices. This provides a fast drawing context for
>>> platforms that lack hardware accelerated Canvas drawing in the native
>>> browser.  Currently supported are Android, iOS, Blackberry and Desktop
>>> Browser.
>> Sounds very cool, but ... questions.
>> 1) any other links to the Pender goo beyond your Github project (thx for
>> providing that, btw)?
>> 2) the latency to get from native to the web view, or vice versa, is not
>> fantastic.  What are the impacts for the Pender APIs?
>> 3) embedded JS engine.  Kinda weird using SpiderMonkey for iOS instead of
>> JSC, but ... who am I to judge.  Of course, Apple may judge.  Has this
>> shipped on the App Store yet?  I'm wondering though if we embedded JSC,
>> could we make use of the JIT where maybe we can't with UIWebView (seems
>> unlikely, JIT may need "mark this data as code" which maybe you can't do
>> from user-land code).
>> 4) With the embedded JS engine, I guess you have to split your code between
>> the Pender stuff and your normal app stuff.  Seems like potentially a
>> confusing aspect for users, but obviously means you get to avoid the native
>> bridge latency (point 2).  I'm curious to see how
>> --
>> Patrick Mueller

View raw message