Neat. Getting some good use out of HTML2Canvas as well. But always wondering why there is no way to get a bitmap from screen... something like window.getPixels(x, y, width, height).
Webkit.js
41–50 of 106 posts
Re: Webkit.js
#42this is pretty cool but network requests and javascript support would make it even more crazier. I viewed the html source for this page and pasted it. I was quite impressed. It looks like this is supposed to be a browser engine written in Javascript? So essentially we would have a sandbox browser within a browser? That would be awesome.
There's interesting research being done in the area of meta-circular interpreters. There's techniques for speeding them up; they're not as slow as I'd expect. For example, one interpreter can do type analysis and rewrite chunks of code.
Re: Webkit.js
#43Can't wait for JS support so I can:
Re: Webkit.js
#44Neat. Getting some good use out of HTML2Canvas as well. But always wondering why there is no way to get a bitmap from screen... something like window.getPixels(x, y, width, height).
There are privacy and security concerns to address. Similar to this situation: https://hacks.mozilla.org/2010/03/privacy-related-changes-co...
Re: Webkit.js
#45Why? Not being dry/evil, simply just interesting in whether this project has practical offshoot or is pure fun (..)?
Re: Webkit.js
#46Re: Webkit.js
#47Why? Not being dry/evil, simply just interesting in whether this project has practical offshoot or is pure fun (..)?
Re: Webkit.js
#48Neat. Getting some good use out of HTML2Canvas as well. But always wondering why there is no way to get a bitmap from screen... something like window.getPixels(x, y, width, height).
https://developer.mozilla.org/en-US/docs/Web/CSS/element
I've written GUI builders that really could have used this for icons of views. Instead I had to render on the server. It'd be nice if it got more broadly adopted.
Re: Webkit.js
#49Earlier quoted context omitted.
>The browsers that are in the Apple App store are handicapped by legal limitations, which are not present on other, more open operating systems. Is FirefoxOS more or less 'open' than iOS? You can't write a competitive javascript runtime for FirefoxOS either.
You can fork the project on Github and Mercurial and write DOM bindings to whatever JavaScript engine you'd like. [0] https://github.com/mozilla-b2g/B2G [1] http://hg.mozilla.org/
Re: Webkit.js
#50Earlier quoted context omitted.
Because competition in the browser market is vital to keep the web platform progressing and to prevent a single party from controlling web standards. Do you remember the dark ages when IE ruled the web and things like HTML5, canvas, webgl, etc... couldn't happen?
>competition in the browser market is vital to keep the web platform progressing and to prevent a single party from controlling web standards I don't see much difference between a single party and a cartel of 3-4 parties. They are all mega corporations that don't share my interests and even when there are several parties any one effectively has veto power over any changes to standards. The push for browser-as-OS is o…
Doing while preserving security would mean that such a runtime would run sandboxed (in the same way we render web pages with gecko in sandboxed processes). For that to work, the sandboxed process need to delegate some functionality to the "main" trusted process, like network access. This is happening through an ipc protocol (we reused the one from chromium) but the messages exchanged are very much gecko specific currently, so a lot of work would be needed to turn that into a more generic ipc embedding interface.
I'm pretty sure that the folks working on Servo would be very happy to plug in their engine there ;)