Does node-webkit enable native-level GFX support?

[kthros...@gmail.com]

Excuse me if this is a foolish question, but does the Chromium instance node-webkit creates have access to all the native OS gfx enhancments that a normal browser doesn't? For instance, an OSX .app is generally "faster" than an app in the browser because it works with the native gfx APIs. 

In other words, is running a "native" node-webkit app literally just the same thing as running it in the Chrome browser ( your app will have same speed, etc ), or are there bonuses it gets from not being web content?

I have an app I'm doing with Paperjs/canvas, and when I open it in the browser with 250 shape objects, it can take a long time to load and it lags with use. I was under the impression that node-webkit might magically make it possible to have way more shapes in the program, but I am seeing the same lag, if not worse lag, when running it through node-webkit in a .app program.

Thanks!

[Roger WANG]

<kthros...@gmail.com> writes:

> Excuse me if this is a foolish question, but does the Chromium instance
> node-webkit creates have access to all the native OS gfx enhancments that a
> normal browser doesn't? For instance, an OSX .app is generally "faster"
> than an app in the browser because it works with the native gfx APIs.

Hello,

It's a good question. Regarding GFX support we are the same as
Chromium. The only native enhancement we've done is the native UI
library, which limits to native UI widgets only (e.g. menu).

> In other words, is running a "native" node-webkit app literally just the
> same thing as running it in the Chrome browser ( your app will have same
> speed, etc ), or are there bonuses it gets from not being web content?

It's almost the same with Chrome. The benefit is the Node platform
brought in. We tent to support everything runs on Node.

> I have an app I'm doing with Paperjs/canvas, and when I open it in the
> browser with 250 shape objects, it can take a long time to load and it lags
> with use. I was under the impression that node-webkit might magically make
> it possible to have way more shapes in the program, but I am seeing the
> same lag, if not worse lag, when running it through node-webkit in a .app
> program.

Does it lag in Chrome browser?

--
Roger WANG Intel Open Source Technology Center