June 2005 - webkit-dev - lists.webkit.org

Avoiding unstable versions?
by Matt Gough 14 Jun '05

14 Jun '05

I just did my daily update, build and run-safari on WebKit and it seems to have some layout issues and debugging code left in (lots of blue outlines around things): e.g: www.apple.com currently looks like this: http://www.softchaos.com/wkissues/01.jpg 1. Is there a way to avoid updating to incomplete/unstable checkins. i.e are there any tags that are applied to the cvs repository when it is in a known 'good' state. 2. For future reference, what is responsible for turning those blue outlines on/off. They would be useful at times. Matt Gough Softchaos Limited

2 1

clean build dies
by dp 14 Jun '05

14 Jun '05

I can't get a clean checkout and build to work. Manually compiling the first project (JavaScriptCore) by cd'ing into it and cc'ing seems to work. ideas? -dp % WebKitTools/Scripts/build-webkit Updating /Users/dp/applewebkit/WebKitBuild/Deployment/ libWebKitSystemInterface.a Updating /Users/dp/applewebkit/WebKitBuild/Deployment/usr/local/ include/WebKitSystemInterface.h deprecated option: -buildstyle is no longer supported in xcodebuild. Use -configuration instead. (NOTE: project JavaScriptCore was written by an older version of Xcode (39) -- temporarily upgrading it to version 42 (without modifying project file)) === BUILDING NATIVE TARGET dftables WITH CONFIGURATION Deployment === CompileC /Users/dp/applewebkit/WebKitBuild/JavaScriptCore.build/ Deployment/dftables.build/Objects-normal/ppc/dftables.o pcre/ dftables.c normal ppc c com.apple.compilers.gcc.4_0 mkdir /Users/dp/applewebkit/WebKitBuild/JavaScriptCore.build/ Deployment/dftables.build/Objects-normal/ppc cd /Users/dp/applewebkit/JavaScriptCore setenv MACOSX_DEPLOYMENT_TARGET 10.3 cc -x c -arch ppc -pipe -Wno-trigraphs -fpascal-strings -fasm- blocks -g -Os -fmessage-length=0 -mtune=G4 -fvisibility=hidden -I/ Users/dp/applewebkit/WebKitBuild/JavaScriptCore.build/Deployment/ dftables.build/dftables.hmap -mdynamic-no-pic -F/Users/dp/applewebkit/ WebKitBuild/Deployment -I/Users/dp/applewebkit/WebKitBuild/Deployment/ include -I/Users/dp/applewebkit/WebKitBuild/JavaScriptCore.build/ Deployment/dftables.build/DerivedSources -c /Users/dp/applewebkit/ JavaScriptCore/pcre/dftables.c -o /Users/dp/applewebkit/WebKitBuild/ JavaScriptCore.build/Deployment/dftables.build/Objects-normal/ppc/ dftables.o error: couldn't exec cc: No such file or directory ** BUILD FAILED **

1 0

JavaScript Extension for XML (E4X) Additon to KSJ - Any Plans? Any Comments?
by Gerald Bauer 14 Jun '05

14 Jun '05

Hello, I was wondering if there are any plans or if there's anyone interested in adding support for E4X to WebKit's JavaScript engine. What is E4X? E4X stands for JavaScript Extension for XML or ECMAScript for XML. E4X is a simple extension for Javascript that adds direct support for XML to JavaScript. E4X is a international ECMA standard and the next version of Mozilla's Firefox browser (that is, v1.1) will include E4X support. Here are some links about E4X: o Introduction to E4X by Jon Udell @ http://weblog.infoworld.com/udell/2004/09/29.html o Objectifying XML - E4X for Firefox 1.1 by Kurt Cagle @ http://www.understandingxml.com/archives/2005/06/objectifying_xm.html o Standard ECMA-357: ECMAScript for XML (E4X) Specification @ http://www.ecma-international.org/publications/standards/Ecma-357.htm - Gerald

1 0

Greetings from the Series 60 mobile browser team at Nokia
by roland.geisler＠nokia.com 14 Jun '05

14 Jun '05

RE: Recent press release: http://press.nokia.com/PR/200506/998214_5.html Hi, I'm heading marketing and strategy at Nokia for Series 60's new mobile browser that will be built upon WebCore/KHTML and JavaScriptCore/KJS. I am writing you this email to thank you for having built the Konqueror and Safari browser with the two components WebCore/KHTML and JavaScriptCore/KJS. I would like to introduce myself and some members from our core development team, and explain why we at Nokia have selected your code base for our future Series 60 mobile browser. I also hope that this will start a mutual dialogue among us that will support all of our projects in the future. Not all of you might be familiar with Series 60. Series 60 is a smart phone software platform developed by Nokia, which enables feature rich applications on mobile devices. Series 60 is based on the Symbian OS and is written in C++. More information can be found from http://www.forum.nokia.com and http://www.series60.com/. I copied some of our core development team members on this email so you have their names and contact information. Antti Koivisto, whom you might know already, is one of the co-authors of KHTML and has been working for Nokia Research Center for the past few years and recently joined our mobile browser development team in Boston. David Carson and Deepika Chauhan are two of the original developers of the Nokia mobile browser. Zalan Bujtas, Prabhakar Marnadi, Yongjun Zhang and Sachin Padma have been working with mobile browsers for some years at Nokia in Helsinki and Boston. Keith Hollis has several years experience working with mobile browsers and has recently joined our team in Boston, earlier he was the principal person leading the port of the Opera web browser to the Symbian OS at Opera Software. Guido Grassel, Kimmo Kinnunen and Andrei Popescu are working at our Nokia Research Center in Helsinki (http://www.nokia.com/research/) where we have built the GTK port of Apple's WebCore that we released last year - http://gtk-webcore.sourceforge.net/. The high performance, low memory consumption and small code footprint of KHTML and KJS make these components ideal for resource-constrained mobile devices. Clean architecture and good design create a good base for future development of mobile features. In addition, Web compliance was another important criteria for us. Congratulations to the KDE Konqueror developer team for building such a great browser. Big thanks at this point also go to the Apple Safari team that has tremendously improved KHTML and KJS in many areas, in particular in Web compliance and performance. WebCore and JavaScriptCore also offer a cleaner separation to the underlying operating system. For these reasons we at Nokia chose WebCore and JavaScriptCore as the code base for our Series 60 mobile browser. Our plan is that the new Series 60 mobile browser will be available as a standard Series 60 application during the first half of 2006. We at Nokia are excited to use WebCore/KHTML and JavaScriptCore/KJS for our future Series 60 mobile browser. I hope that we can start a dialogue with your community and the Apple Safari team on how to "mobilize" WebCore/KHTML and JavaScriptCore/KJS to create the best Web browser based on open-source components for mobile devices. Best regards, Roland Geisler Head of Marketing & Strategy, Series 60 Browser Nokia PS: Please forward this email to any contributor whom I may have missed.

2 1

Greetings from the Series 60 mobile browser team at Nokia
by roland.geisler＠nokia.com 13 Jun '05

13 Jun '05

This email contains email addresses in the cc of the Nokia browser developers as mentioned below. RE: Recent press release: http://press.nokia.com/PR/200506/998214_5.html Hi, I'm heading marketing and strategy at Nokia for Series 60's new mobile browser that will be built upon WebCore/KHTML and JavaScriptCore/KJS. I am writing you this email to thank you for having built the Konqueror and Safari browser with the two components WebCore/KHTML and JavaScriptCore/KJS. I would like to introduce myself and some members from our core development team, and explain why we at Nokia have selected your code base for our future Series 60 mobile browser. I also hope that this will start a mutual dialogue among us that will support all of our projects in the future. Not all of you might be familiar with Series 60. Series 60 is a smart phone software platform developed by Nokia, which enables feature rich applications on mobile devices. Series 60 is based on the Symbian OS and is written in C++. More information can be found from http://www.forum.nokia.com and http://www.series60.com/. I copied some of our core development team members on this email so you have their names and contact information. Antti Koivisto, whom you might know already, is one of the co-authors of KHTML and has been working for Nokia Research Center for the past few years and recently joined our mobile browser development team in Boston. David Carson and Deepika Chauhan are two of the original developers of the Nokia mobile browser. Zalan Bujtas, Prabhakar Marnadi, Yongjun Zhang and Sachin Padma have been working with mobile browsers for some years at Nokia in Helsinki and Boston. Keith Hollis has several years experience working with mobile browsers and has recently joined our team in Boston, earlier he was the principal person leading the port of the Opera web browser to the Symbian OS at Opera Software. Guido Grassel, Kimmo Kinnunen and Andrei Popescu are working at our Nokia Research Center in Helsinki (http://www.nokia.com/research/) where we have built the GTK port of Apple's WebCore that we released last year - http://gtk-webcore.sourceforge.net/. The high performance, low memory consumption and small code footprint of KHTML and KJS make these components ideal for resource-constrained mobile devices. Clean architecture and good design create a good base for future development of mobile features. In addition, Web compliance was another important criteria for us. Congratulations to the KDE Konqueror developer team for building such a great browser. Big thanks at this point also go to the Apple Safari team that has tremendously improved KHTML and KJS in many areas, in particular in Web compliance and performance. WebCore and JavaScriptCore also offer a cleaner separation to the underlying operating system. For these reasons we at Nokia chose WebCore and JavaScriptCore as the code base for our Series 60 mobile browser. Our plan is that the new Series 60 mobile browser will be available as a standard Series 60 application during the first half of 2006. We at Nokia are excited to use WebCore/KHTML and JavaScriptCore/KJS for our future Series 60 mobile browser. I hope that we can start a dialogue with your community and the Apple Safari team on how to "mobilize" WebCore/KHTML and JavaScriptCore/KJS to create the best Web browser based on open-source components for mobile devices. Best regards, Roland Geisler Head of Marketing & Strategy, Series 60 Browser Nokia PS: Please forward this email to any contributor whom I may have missed.

1 0

No line-number debug symbols in WebCore
by Mitz Pettel 13 Jun '05

13 Jun '05

It looks like WebCore is built with almost no SLINE symbols (don't have that problem with WebKit). Is there a separate symbols file to load into gdb to enable source-level debugging for WebCore, or a build setting that can be changed in order to generate line numbers in WebCore? Thanks, -- Mitz Pettel

2 2

"review" flag now enabled in Bugzilla
by Darin Adler 13 Jun '05

13 Jun '05

There's now a "review" flag enabled in Bugzilla for attachments. This lets you set a flag "review?" on an attachment to a bug, and optionally choose a preferred reviewer. Later a reviewer can set the flag "review+" or "review-" on the attachment. I'll eventually put some notes about how to use this on the website. It's a good idea to attach a patch to a bug and set the "review?" flag on the attachment before sending a patch to webkit-reviews. In fact, we might eventually require things be done that way so that we can easily keep track of all the patches that still need review. -- Darin

1 0

Suggestion: Bonsai
by Justin Haygood 11 Jun '05

11 Jun '05

Is it possible to have a Bonsai server setup somewhere so that its easy to see CVS changes? http://www.mozilla.org/bonsai.html is the URL for bonsai.

2 1

w00t, regression tests from testkjs on Win32
by Justin Haygood 11 Jun '05

11 Jun '05

For a very quick port of KJS to Win32 from JavaScriptCore, here's the results: Test List: All tests Skip List: ecma/Date 967 test(s) selected, 962 test(s) completed, 319 failures reported (33.16% failed) Engine command line: testkjs.exe OS type: Testcase execution time: 7 minutes, 13 seconds. Tests completed on Fri Jun 10 21:17:47 2005. Most of that time was spent clicking Don't Send in the Watson error reporter. 131 regressions failed, so the rest (188) are crashes. When and where they crash, I don't know. But its my job to find out and bring Win32 JavaScriptCore in sync with OS X JavaScriptCore in stability.

1 0

PCRE 6.0 in JavaScriptCore
by Justin Haygood 11 Jun '05

11 Jun '05

I'm going to undertake getting PCRE 6.0 merged into JavaScriptCore, and merging the UTF-16 support improvements from JSCore PCRE to PCRE 6.0. This would be mutual for both projects: 1. JSCore gets newer/better PCRE 2. PCRE gets better support. In fact, my local Win32 build already builds against it, so no code needs to be changed on the KJS side of JSCore.

1 0