[webkit-dev] Multitouch support for QtWebKit on gitorious experimental branch
FYI, we have just released experimental branch of multitouch support of QtWebKit for Windows7 on gitorious. More information: demo videos, source code and binaries, and a small developer guide how to use Touch & Manipulate API's(draft versions) and CSS transforms, animations and transitions are available here: http://opensource.nokia.com/Starlight We are currently cleaning up the code in gitorious and are hoping to submit patches to webkit.org in the near future. Regards, Jonni and the rest of the Starlight team ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] errors in Carbide but not on command line
Have you tried instructions from: http://wiki.forum.nokia.com/index.php/Building_S60Webkit And yes, using CodeWarrior might also solve those bld.inf problems, as most likely initial port was done before Carbide was taken into use. Regards, Jonni >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of ext >Zalan Bujtas >Sent: 17 July, 2008 13:35 >To: Jack Wootton >Cc: webkit-dev@lists.webkit.org >Subject: Re: [webkit-dev] errors in Carbide but not on command line > This seems simple enough and, I can just remove the line '#include '. However, in the JavaScriptCore bld.inf it looks likes this: >The targeted sdk (s60 3rd edition) cannot resolve >MW_LAYER_SDK_EXPORT_PATH, so the export paths are hardcoded. >That's the major difference between the #ifndef and the #else >branch. I think you need to clean up the .inf files by >removing the #ifndef __BROWSER_SDK' branch. > >>> How can Nokia port the webkit so that it doesn't build in >their own IDE? >I guess, Webkit was ported to S60 before, Carbide was taken >into use and not been updated since. > >Zalan. > >On Thu, Jul 17, 2008 at 11:58 AM, Jack Wootton ><[EMAIL PROTECTED]> wrote: >> Does anyone have a solution other than just commenting out all the >> files that shouldn't be included? This doesn't seem practical since >> there are around 60 errors reported from files not being found, it >> seems these files are meant to be conditionally included in >the build >> process but that the '#ifndef __BROWSER_SDK' preprocessor >commands are >> not working. >> >> On Thu, Jul 17, 2008 at 10:38 AM, Jack Wootton ><[EMAIL PROTECTED]> wrote: >>> OK, So from reading this >>> >>> http://discussion.forum.nokia.com/forum/showthread.php?t=69737 >>> >>> I understand the situation better. One question: >>> >>> How can Nokia port the webkit so that it doesn't build in >their own IDE? >>> >>> People moan about Google this and Google that, but this is >something >>> Google would never do. >>> >>> On Thu, Jul 17, 2008 at 9:50 AM, Jack Wootton ><[EMAIL PROTECTED]> wrote: Hi, The WebKit bld.inf contains the following lines: #ifndef __BROWSER_SDK #include #endif This seems simple enough and, I can just remove the line '#include '. However, in the JavaScriptCore bld.inf it looks likes this: /** Start horrible code extract */ #ifndef __BROWSER_SDK #include ..\kjs\internal.h >MW_LAYER_SDK_EXPORT_PATH(javascriptcore\internal.h) ..\kjs\interpreter.h >MW_LAYER_SDK_EXPORT_PATH(javascriptcore\interpreter.h) ..\kjs\object.h >MW_LAYER_SDK_EXPORT_PATH(javascriptcore\object.h) ..\kjs\protect.h >MW_LAYER_SDK_EXPORT_PATH(javascriptcore\protect.h) ..\kjs\stdint.h >MW_LAYER_SDK_EXPORT_PATH(javascriptcore\stdint.h) ..\bindings\npruntime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime.h) ..\bindings\npruntime_impl.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_impl.h) ..\bindings\npruntime_priv.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_priv.h) ..\bindings\runtime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime.h) ..\bindings\runtime_object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_object.h) ..\bindings\runtime_root.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_root.h) ..\bindings\NP_jsobject.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\NP_jsobject.h) ..\bindings\c\c_utility.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\c_utility.h) #else ..\kjs\internal.h >\epoc32\include\oem\javascriptcore\internal.h ..\kjs\interpreter.h >\epoc32\include\oem\javascriptcore\interpreter.h ..\kjs\object.h >\epoc32\include\oem\javascriptcore\object.h ..\kjs\protect.h >\epoc32\include\oem\javascriptcore\protect.h ..\kjs\stdint.h >\epoc32\include\oem\javascriptcore\stdint.h ..\bindings\npruntime.h \epoc32\include\oem\javascriptcore\npruntime.h ..\bindings\npruntime_impl.h \epoc32\include\oem\javascriptcore\npruntime_impl.h ..\bindings\npruntime_priv.h \epoc32\include\oem\javascriptcore\npruntime_priv.h ..\bindings\runtime.h >\epoc32\include\oem\javascriptcore\runtime.h ..\bindings\runtime_object.h \epoc32\include\oem\javascriptcore\runtime_object.h ..\bindings\runtime_root.h \epoc32\include\oem\javascriptcore\runtime_root.h ..\bindings\NP_jsobject.h \epoc32\include\oem\javascriptcore\NP_jsobject.h ..\bindings\c\c_utility.h \epoc32\include\oem\javascriptcore\c_utility.h #endif //#ifndef __BROWSER_SDK /** End horrible code extract >*/ So, presumably it's the first section that needs to go, >but can all of
Re: [webkit-dev] Request for comments
Hello, Yes, my organization is more familiar with QT-WebKit side, but I do have some contacts on S60 WebKit people and have digged out some info regarding S60WebKit. And I can comment on Jack's complaint that Nokia IS aware of current problems of the S60WebKit port, and there is actions started to rectify the situation on S60WebKit port. 1. I know that updated version of the S60WebKit port will be released after the phone which uses newer version of the WebKit is released, this will happen in this year. 2&3. Will be corrected at the same time, and S60WebKit team will have couple fulltime people maintaining released code line for the community. 4&5. As I'm not member of S60WebKit team, I cannot officially communicate that much on behalf of their team because I don't have that clear picture of S60 side activities, but hopefully this email atleast clears some of the rumours and misinformation that might be going around. But I can say that we are aware of the situation, and hopefully you will see better support in the future. Regards, Jonni >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of ext Mark Rowe >Sent: 14 August, 2008 12:23 >To: Jack Wootton >Cc: webkit-dev@lists.webkit.org; Rainisto Jonni (Nokia-D/Tampere) >Subject: Re: [webkit-dev] Request for comments > > >On 2008-08-14, at 21:07, Jack Wootton wrote: > >> I hope this signals a better start for Nokia. Before Nokia >can submit >> anything back to the WebKit community they'll have to: > >[snip] > >Speaking as developer of WebKit, if Nokia wishes to resume >contributing code to the WebKit project then they are free to >do so, as are any other developers. I understand that you may >be frustrated with how the S60 port has been handled, but I >don't think that it helps the situation to claim that Nokia >must do the things you list in order to continue contributing >to WebKit. The work that Jonni is presenting appears to be >based on the Qt WebKit port, which is completely distinct from >the S60 code base, and has an active community maintaining it. > >Kind regards, > >Mark Rowe > > ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Request for comments
Yes, we are well aware of WebKit Teams proposals: http://www.nabble.com/Apple's-Proposal-for-CSS-Transformations-p13615345 .html http://lists.w3.org/Archives/Public/www-style/2008Mar/0313.html http://webkit.org/specs/CSSVisualEffects/CSSTransitions.html http://webkit.org/specs/CSSVisualEffects/CSSTransforms.html http://webkit.org/specs/CSSVisualEffects/CSSAnimation.html And animation examples: http://www.the-art-of-web.com/css/css-animation/ We also want to make sure that WebKit API's would remain consistent between platforms. And it would be nice to see all those features in the public trunk, and not only in desktop/iPhone WebKit. It is the best interest of all parties, that all manufacturers devices would have the same advanced API set, when there are large number of devices with the same API's deployed in the world, then the web devolopers would be more interested of using the API's, as there is no point for devolopers to make custom web pages for each manufacturers device. We are not trying to make competing API, but rather cooperate and maybe extend the functionality of the possibly missing features that we had in mind, and we are more than happy to talk about the ideas on technical side and make needed modifications. Currently there might be some overlapping with our work and Apples work especially on 2.5D/3D transformations as we haven't seen that code in WebKit nightly build yet, or haven't been able to find it ;-) We have studied iPhone Safari a bit (what a surprise :-D), but maybe I have missed something, does it already support for web developers to receive touch and accelerometer events, like our implementation of JS API's provide? regards, Jonni From: ext Maciej Stachowiak [mailto:[EMAIL PROTECTED] Sent: 14 August, 2008 21:19 To: Rainisto Jonni (Nokia-D/Tampere) Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] Request for comments On Aug 13, 2008, at 6:37 AM, [EMAIL PROTECTED] wrote: Hello, I've been following the webkit-dev list for a while now, and I though that it might be good time to introduce myself and the project that we have been working on with a small team. First some general high level introduction jargon for managers or such ;)... Motivation: Finger-touchable direct manipulation of 2.5D visual objects with gestures is the new emerging UI paradigm with personal navigation devices. However, the new paradigm has not reached the web yet -- there is no way a web developer can embrace the new interaction. In this project we will look into bringing finger touch and gestures to the web framework in order to accelerate easy web usage with mobile devices, with the goal of mobile devices becoming the primary web access method instead of laptops. This project is about: * To create innovative web representation platform * Multi-touch, accelerometer (rotation, shaking) and haptics based interaction mechanisms * Enriching the mobile web content with 2.5D graphics with hardware accelerated rendering * New JavaScript interaction APIs, Haptics CSS extensions Have you looked at the WebKit team's proposal for 2.5D graphics and transitions? http://webkit.org/specs/CSSVisualEffects/CSSTransforms.html http://webkit.org/specs/CSSVisualEffects/CSSTransitions.html These are now on track to become W3C standards and are already implemented on iPhone (2D portions only on desktop WebKit currently). Also, have you looked at how touch and accelerometer events work on Safari on iPhone? I am excited to see contributions from Nokia, but we would want to make sure that advanced WebKit features remain consistent in API between platforms. Regards, Maciej High Level Architecture: (disclaimer: this is only high level architecture and some aspects might change during the project) <> What we have already up and running: - Prototype implementation OpenGL ES 1.1 accelerated QT-WebKit running on ARM based Internet Tablet device (such as N810), reference implementations of the draft JS API's are somewhat working (no haptics yet tough). JavaScript test pages receives touch gesture DOM and accelerometer events quite nicely. I'm wondering if people in this mailing list would be interested to look and give feedback/comments to our JS API draft versions and general feedback for us to see if this would be beneficial for end users. More detailed draft architecture specifications
