Re: [webkit-dev] Support for E4X
Hi, I'm interested work on it too. I've started reading something about E4X and WebKit, and specially looking at JavaScriptCore code. My first question was where I would start to code. On 4/3/07, Eric Seidel [EMAIL PROTECTED] wrote: The first step would be to come say hello in #webkit. http://webkit.org/contact.html That's where all the hackers hang out. You'd particularly want to chat with ggaren or othermaciej, possibly others (my information about JSC is rather dated). Yes, JSC holds all the JavaScript logic, and would be the place where E4X support would be implemented. -eric On Apr 3, 2007, at 8:45 AM, Afonso Costa wrote: Hello all, I'm a beginner in this list and in WebKit development as well, but I'd like to contribute for WebKit adding or improving its support for E4X. I've found some informations about E4X and WebKit, like this http://lists.macosforge.org/pipermail/webkit-dev/2006-September/001316.html and this http://bugs.webkit.org/show_bug.cgi?id=5381. I'd like to ask you if somebody is working on it or not. I'm trying to understand how JavaScriptCore works inside WebKit, I mean, where I can write the code (in JavaScriptCore/kjs or other dir?) and how I can test my code. Basically is this. It will be great if somebody give me some initial pointers or advices about it. Thanks in advance. Afonso ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev -- Rodrigo Melo ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Support for E4X
On Apr 4, 2007, at 6:54 AM, Rodrigo Melo wrote: Hi, I'm interested work on it too. I've started reading something about E4X and WebKit, and specially looking at JavaScriptCore code. My first question was where I would start to code. Although we've discussed E4X support, we're not entirely sure we want it. It's a big chunk of extra functionality that isn't really used on the web. And the web already provides the DOM for XML processing. So we'd want to hear some some good reasons before adding support. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Support for E4X
On Apr 4, 2007, at 12:25 PM, Maciej Stachowiak wrote: On Apr 4, 2007, at 6:54 AM, Rodrigo Melo wrote: Hi, I'm interested work on it too. I've started reading something about E4X and WebKit, and specially looking at JavaScriptCore code. My first question was where I would start to code. Although we've discussed E4X support, we're not entirely sure we want it. It's a big chunk of extra functionality that isn't really used on the web. And the web already provides the DOM for XML processing. So we'd want to hear some some good reasons before adding support. One argument in favor of it is for use outside of the web, where you don't necessarily have a DOM available. -Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Support for E4X
Hello, here are some arguments according to E4X specification: E4X applications are smaller and more intuitive to ECMAScript developers than comparable XSLT or DOM applications. They are easier to read, write and maintain requiring less developer time, skill and specialized knowledge. The net result is reduced code complexity, tighter revision cycles and shorter time to market for Internet applications. Best regards, Afonso On 4/4/07, Adam Roben [EMAIL PROTECTED] wrote: On Apr 4, 2007, at 12:25 PM, Maciej Stachowiak wrote: On Apr 4, 2007, at 6:54 AM, Rodrigo Melo wrote: Hi, I'm interested work on it too. I've started reading something about E4X and WebKit, and specially looking at JavaScriptCore code. My first question was where I would start to code. Although we've discussed E4X support, we're not entirely sure we want it. It's a big chunk of extra functionality that isn't really used on the web. And the web already provides the DOM for XML processing. So we'd want to hear some some good reasons before adding support. One argument in favor of it is for use outside of the web, where you don't necessarily have a DOM available. -Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
