[webkit-dev] Pepper and NaCl supporting (prototype)

[Kapade, Mrunal]

>Neither NaCl nor Pepper are trivial pieces of code, they would require maintenance if they were in trunk.  If they're not in trunk then the entire discussion on webkit-dev is moot as they would (by definition) not be present in WebKit.

I agree that neither NaCl nor Pepper are trivial pieces of code and this project doesn't intend to be in the webkit.org trunk. I was part of this project at Intel where we explored porting Pepper and NaCl to WebKit2. This was the result of that effort. The purpose of announcing this on webkit-dev was to those who may be interested in working on this either upstream or as a side project can have a look at it and if useful reuse it.

>
>You also haven't said _why_ they're a "cool and useful technology", which was my point.  What do they provide that is not already provided by the standardized_ web platform?
>
>Taking a large pile of code, to support a platform with no obvious signs of standardization reeks of the "science experiment" concept we don't want in the tree.  I have not seen any evidence of a specification document anywhere, and without a spec document how can anyone else write their own implementation?

As I said, we don't intend to push it upstream so no question of maintenance or landing it in the tree. It's hosted on github.com and not webkit.org.

Mrunal
On Jul 11, 2013, at 5:46 AM, Jake <jake at jakeonthenet.com<mailto:jake at jakeonthenet.com>> wrote:

I would suggest you re-read the original post - Halton's work adds no maintenance burden to the webkit project whatsoever. It does, however, make some very cool and useful technology available to those who choose to use webkit2. I believe that would qualify as obvious benefit.


On Tue, Jul 9, 2013 at 12:49 PM, Oliver Hunt <oliver at apple.com<mailto:oliver at apple.com>> wrote:
Aside from any other issues, my recollection was that there had not been any work to formally specify NaCl or Pepper, has that changed?

I'm also concerned as this adds a significant maintenance burden to the project for no obvious benefit.

--Oliver

On Jun 30, 2013, at 11:41 PM, halton huo <halton.huo at gmail.com<mailto:halton.huo at gmail.com>> wrote:

Dear WebKit developers and users,

I’m pleased to announce the initial contribution of Pepper[1] and NaCl[2] support for WebKit2. The home page is located at https://github.com/nacl-webkit/native_client/wiki.
The initial code include supporting of:
* Partial pepper api supporting includes: 2d, scripting, url_loader, file chooser, audio, mouse and keyboard events, websockets.
* Basic NaCl support with post message api (HelloWorld from nacl_sdk)

There are some sceenshots on https://github.com/nacl-webkit/native_client/wiki/Screenshots

Q&A
=======
Q: Why this project?
A: We enjoy working with the WebKit projects. We also enjoy technologies like NaCl, and wanted to lower the barrier to letting people integrate NaCl into their WebKit2 based projects. We prototyped this work and now want to make it available for others to use if they want.

Q: Can I modify and re-use the project?
A: Yes. The code is inherited from the Chromium, WebKit2 and native_client projects. As such, this project follows the same licenses.

Q: Why not upstream?
A: There are two main reasons. First, the current code is only a prototype to support NaCl in the Linux EFL port of WebKit2. There still remains work to be done before the patches would be appropriate to try and take upstream. Second, the WebKit community has stated in the past that they did not want NaCl upstream.

Q: How to contribute?
A: Fork the repo on github and submit the pull request, committers will review the patches. For the time being, the initial contributors are committers, we're welcome to anyone who can show his ability to be as committer. Follow the https://github.com/nacl-webkit/native_client/wiki/Code to get code and build.

Q: Any next plan?
A: We don't have any formal plans for the project moving forward; it is being developed as a part-time effort by a few engineers. As such, there is no guarantee for future work. Again, anyone is welcome to contribute! Or fork the project and run with it.

[1] http://code.google.com/p/ppapi/
[2] http://code.google.com/p/nativeclient/
_______________________________________________
webkit-dev mailing list
webkit-dev at lists.webkit.org<mailto:webkit-dev at lists.webkit.org>
https://lists.webkit.org/mailman/listinfo/webkit-dev


_______________________________________________
webkit-dev mailing list
webkit-dev at lists.webkit.org<mailto:webkit-dev at lists.webkit.org>
https://lists.webkit.org/mailman/listinfo/webkit-dev