Re: [webkit-dev] webkit core need to be cleanly separated from ports, behind a vector table
On Tue, Oct 14, 2008 at 9:47 PM, David Hyatt [EMAIL PROTECTED] wrote: The term webkit core in your subject is very confusing. Do you mean WebKit or WebCore? There is platform-specific code in both. apologies. i mean whichever bit that you link webkit link against to produce a gtk port, or a qt port, or a wx port. l. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] webkit core need to be cleanly separated from ports, behind a vector table
On Wed, 2008-10-15 at 08:04 +, Luke Kenneth Casson Leighton wrote: On Tue, Oct 14, 2008 at 9:47 PM, David Hyatt [EMAIL PROTECTED] wrote: The term webkit core in your subject is very confusing. Do you mean WebKit or WebCore? There is platform-specific code in both. apologies. i mean whichever bit that you link webkit link against to produce a gtk port, or a qt port, or a wx port. While I agree that it would be nice to have a separate library to which both the GTK+ and Qt ports could link, for instance, I believe this model would somewhat remove the agility the project has of refactoring and redesigning big parts of the code. API stability would be something to worry not only for the most outern layer (the port), and that would complicate matters. See you, -- Gustavo Noronha Silva [EMAIL PROTECTED] GNOME contributor: http://www.gnome.org/ ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Kompilierungshilfe
Hallo an Alle, ich brauch eine unbedingte Hilfe um Javacorescript und Webcore zu kompilieren. Ich habe ¨make¨ gegeben und sagt ../Makefile.shared ist nicht gefunden. wo kann ich die komplette Datei herunterladen? Ich habe Linux - Ubuntu und Mac Os 10.5.1 ich warte auf eure Rueckmeldung, gruesse, Sherif ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] produce a new version of webkit
Hi , thank you very much for the link , Hiba , -- View this message in context: http://www.nabble.com/produce-a-new-version-of-webkit-tp19854660p19996404.html Sent from the Webkit mailing list archive at Nabble.com. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Kompilierungshilfe
Am Wed, 15 Oct 2008 14:47:55 + (GMT) schrieb Ehrenmann [EMAIL PROTECTED]: Hallo an Alle, ich brauch eine unbedingte Hilfe um Javacorescript und Webcore zu kompilieren. Ich habe ¨make¨ gegeben und sagt ../Makefile.shared ist nicht gefunden. wo kann ich die komplette Datei herunterladen? Ich habe Linux - Ubuntu und Mac Os 10.5.1 ich warte auf eure Rueckmeldung, Hey, schau mal hier, http://trac.webkit.org/wiki/BuildingGtk, das sollte weiterhelfen. Bedenke, dies ist vorzugsweise ein englischsprachiger Verteiler. have a look at this, http://trac.webkit.org/wiki/BuildingGtk, that should get you started. Note that this list is English only. ciao, Christian ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] webkit core need to be cleanly separated from ports, behind a vector table
Gustavo Noronha Silva-5 wrote: On Wed, 2008-10-15 at 08:04 +, Luke Kenneth Casson Leighton wrote: While I agree that it would be nice to have a separate library to which both the GTK+ and Qt ports could link, for instance, I believe this model would somewhat remove the agility the project has of refactoring and redesigning big parts of the code. API stability would be something to worry not only for the most outern layer (the port), and that would complicate matters. gustavo, thanks for responding. question: how so? [would it remove agility for refactoring and redesigning]? what is there about, for example, the apache2 vector table system, where you fill in 28 or so functions in a vector table and hand it back to the apache runtime, that makes refactoring and redesign difficult? extensions to the table can be done by having a union of structs, with an int at the beginning of the table saying i'm a version 1 or i'm a version 2. then, if you have a version 1-using-port that connects to a version 2 library, the extra functions that differ from version 1 and 2 will be NULL; the version 2 webkit library will go oh, these are NULL, so we're not providing version 2 functionality. far from making it _more_ difficult to do a redesign, such techniques would make it _easier_ i believe. you could add in refactored functions into the version 2, support both for a while, then, when sufficient time has passed, drop the version 1 functions. and, during the transition period, users would be able to mix-and-match version-1-using apps with version-2 of the webkit library, and not care in the slightest. ... am i missing something? l. -- View this message in context: http://www.nabble.com/webkit-core-need-to-be-cleanly-separated-from-%22ports%22%2C-behind-a-vector-table-tp19982522p19996413.html Sent from the Webkit mailing list archive at Nabble.com. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] performing a single click on a frame
Hello. I'm interested in performing a single mouse click on a frame with given coordinates. I've looked into the handleMousePressEvent() function in WebCore/page/EventHandler.cpp but don't understand how to use that. Is it even possible to perform programmable clicks due to the fact that the engine gets the events from X? Please help. Greets, Luka signature.asc Description: To je digitalno podpisan del sporočila ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Manipulate / gesture events
Hi, My name is Kari Hiitola and I work for the same project in Nokia as Jonni Rainisto, who also was emailing about our project about a month ago. As he said, we are working towards enabling a lot more compelling web experience on the small screen touch/gesture devices. We are eager moving the the technology introduced by Apple to the WebKit forward for wider acceptance and have worked with the software and hardware stacks used in Nokia and tried to figure out general solutions that would be building on top of existing implementations but also be general enough to use by the whole industry that could be moved forward in the W3C standardisation. And for the record, all we do is or will be open source, the limiting factors being only some of the legal hurdles imposed to us externally. So, as we already have done some test implementations, I would like to ask your comments on some change proposals we have, so that we would be able to make a general enough implementation to the WebKit, and if there is agreement, we will be happy to provide the final implementation to the WebKit. I'll start by elaborating more on the gesture events. We looked at iPhones http://www.opensource.apple.com/darwinsource/iPhone2.1/WebCore-351.9/dom/Ge stureEvent.idl, but we¹d like to see a bit more generic event, more suitable for becoming a standard. I'd like to hear your feedback on this proposal, and if there would be interested parties to participate in standardization of the events. 1. Name the event manipulate Different name would help in keeping the Apple proprietary gesture event in the devices alongside with the potentially standards-track version. The gesture event really is all about manipulating an object on the web page. On different device types there might be different methods for doing that. E.g. zooming could be pointroll instead of pinch, and rotate could be pointjoystick (just random picks not related to any real existing or coming product). These are methods that you wouldn¹t call gestures, but in any case they will be manipulation. 2. Enable panning with the same event as zoom and rotate Take for example a map that you can pan, zoom and rotate using one event handler. Or the classical multi-touch demo of photo organizer (where pan would be roughly equal to drag). The JS code would be simplified a lot when you don¹t separately receive the pan (or raw touch) and the zoom/rotate events. The events are most of the time used together, and naturally you can just ignore the parameters you don¹t need. In its simplest form you'd just need to actually use the X/Y coordinates that there already are in the iPhone¹s GestureEvent, but there is an additional need that would change the logic a bit: 3. Allow starting the pan manipulate event with one finger iPhone's GestureEvent requires two fingers to be down to trigger the event, so the pan would not be possible with one finger. Admitted, starting pan with one finger would bring the problem: what is then the correct coordinate to be used in the scenario where you first start panning with finger 1, then zoom/rotate with two fingers, release finger 1, and continue pan with finger 2? 3.1 First option: Use relative coordinates for the pan, with the start of the gesture as 0,0. Page/client/screen X/Y are then in the place of the only finger, or in the middle of two fingers if present. This would result in jumpy non-continuous coordinates for page/client/screen when fingers enter and exit the screen, but there would be no lying about the coordinates, and the pan coordinates would still be continuous. Having all fingers separately modeled in the manipulation event wouldn¹t be such a good idea either because of the added complexity, and if you want raw touch events, you should use raw touch events. 3.2 Second option: Use absolute coordinates for the page/client/screen X/Y so that they are continuous. This requires a bit of lying about the coordinates in the case of multi-touch. Instead of reporting the actual position of one of the fingers, you apply the movement delta to the original coordinates of the first finger. When you put the second finger down, the coordinates remain constant at the place of the first finger. When both fingers move, the delta movement of their center point is applied to the original coordinate. If the first finger is lifted, the coordinates are not in the place of the remaining finger, and can even be outside the screen, but those events can be filtered out if found necessary. With this trick the coordinates are not necessarily the center of rotation, or center of scaling, which is also the case with device types different from iPhone's. Thus, the rotation and scale center should be added as attributes. I don't see a need to have separate rotation and scale centers, but a combined centerX/Y with client coordinates should suffice. 3.3 A combination: Add new panX/Y attribute, which would be the same as X/Y from option 3.2 but the page/client/screen
Re: [webkit-dev] webkit core need to be cleanly separated from ports, behind a vector table
On Wed, Oct 15, 2008 at 12:04 PM, lkcl [EMAIL PROTECTED] wrote: what is there about, for example, the apache2 vector table system, where you fill in 28 or so functions in a vector table and hand it back to the apache runtime, that makes refactoring and redesign difficult? extensions to the table can be done by having a union of structs, with an int at the beginning of the table saying i'm a version 1 or i'm a version 2. then, if you have a version 1-using-port that connects to a version 2 library, the extra functions that differ from version 1 and 2 will be NULL; the version 2 webkit library will go oh, these are NULL, so we're not providing version 2 functionality. You seem to be reinventing COM. While there are certainly parts of WebCore and WebKit as a whole where some well-chosen interfaces would indeed make it easier to develop and maintain additional platforms and extensions (example: dave hyatt's recent refactoring of ScrollView and friends), I'm not sure that a large C-style vector of function pointers for all of WebKit is an effective way to accomplish this. far from making it _more_ difficult to do a redesign, such techniques would make it _easier_ i believe. Do you have a proof of concept? Comparing approaches is always easier with a concrete example than with abstract descriptions. If nothing else, that would help validate your assertion that it would be easy to implement this way :-). Amanda Walker [EMAIL PROTECTED] ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] produce a new version of webkit
https://lists.webkit.org/pipermail/webkit-dev/2008-May/003965.html Greets, Luka Dne 13.10.2008 (pon) ob 14:01 +0100 je houda hocine zapisal(a): Hi , Thanks for the answer , Please I search the discussion for a long time, but I don't find any thing. Can you send me the link of discussion please. Thanks in advance. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev signature.asc Description: To je digitalno podpisan del sporočila ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Unable to compile the webkit on the Redhat enterprise linux 9
Hi, On Tue, Oct 14, 2008 at 8:02 PM, Gustavo Noronha Silva [EMAIL PROTECTED] wrote: Hello, Disclaimer: I'm more of a GTK+/Debian guy =). On Tue, 2008-10-14 at 10:31 -0400, Ramesh Satyavaram wrote: I am new to webkit. Yester day I downloaded the sources on to my Red hat enterprise linux 9. I tried to compile with the following command. There is no such thing as Red Hat Enterprise 9. Either you are using Red Hat 9, or Fedora 9. If you're using the former it is already way old, and you probably have a too old version of qmake. Do check if qmake's version is current. Just chiming in. This is line: ***Unknown option –r indicates that you are using a too old version of qmake (as Gustavo pointed out). You need at least qmake 4.3. I would advice you to have a look at http://trac.webkit.org/wiki/BuildingQtOnLinux and check you meet all the requirements. Regards, Julien ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] HTML5 Application Cache
I've been using this feature on the iPod Touch. It works, but under some circumstances during a cache-manifest change, Safari will crash and will from then on always crash when loading that page, until I reset the iPod's software. I had what looks like the same problem on Safari 4 preview 2. David Kilzer wrote: This feature shipped with iPhone OS 2.1. When you use Add to Home Screen from the + button on Safari for iPhone, a web application with a manifest defined (per the HTML5 spec) will be saved with any cached resources. Note that the manifest file *must* be served with the correct MIME type for this to work. There is no shipping version of Safari for Mac OS X or Windows that supports this feature yet. -- View this message in context: http://www.nabble.com/HTML5-Application-Cache-tp19398643p2223.html Sent from the Webkit mailing list archive at Nabble.com. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] HTML5 Application Cache
On Oct 15, 2008, at 12:11 PM, VictorM wrote: It works, but under some circumstances during a cache-manifest change, Safari will crash and will from then on always crash when loading that page, until I reset the iPod's software. Would you be willing to file a bug report with some details and steps to reproduce? http://webkit.org/quality/reporting.html -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Webkit (Mobile Safari) issues in the iPhone
Hi, I am aware that this mailing list is not specifically oriented to the Apple's iphone mobile safari implementation, but I am confident that some people on this list can give me some hints on how to solve this issue. In a nutshell I have issues updating the DOM. I have a rich text edit and to simulate the text selection I have enclosed the text in a tag with a background colour. All this is done in javascript but if i do not send (after it in Objective-C) a setSelectionToStart message to the text view It comes back with something like this (the same issue can occur in some few places but always ends in the same place): #0 0x3272e30f in std::__push_heapWebCore::TimerHeapIterator, int, WebCore::TimerHeapElement () #1 0x327389d6 in std::__adjust_heapWebCore::TimerHeapIterator, int, WebCore::TimerHeapElement () #2 0x32738978 in WebCore::TimerBase::heapPopMin () #3 0x326b5acc in WebCore::TimerBase::setNextFireTime () #4 0x326b58c1 in WebCore::TimerBase::stop () #5 0x32739fde in WebCore::FrameView::layout () #6 0x3275cea7 in WebCore::Frame::forceLayout () #7 0x3275ce4c in -[WebCoreFrameBridge forceLayoutAdjustingViewSize:] () #8 0x32de6cbd in -[WebHTMLView layoutToMinimumPageWidth:maximumPageWidth:adjustingViewSize:] () #9 0x32de6b34 in -[WebHTMLView layout] () #10 0x32a7caae in WKViewLayout () #11 0x30bc16d0 in -[UIWebDocumentView layoutBeforeDraw] () #12 0x30ae23e9 in -[UITiledView layoutSubviews] () #13 0x30bbb66c in -[UIWebDocumentView layoutSubviews] () #14 0x31e87278 in -[CALayer layoutSublayers] () #15 0x31e871a8 in CALayerLayoutIfNeeded () #16 0x31e9f639 in -[CALayer layoutIfNeeded] () #17 0x31e9e92d in -[CALayer renderInContext:] () #18 0x30b6ff5c in -[UITextLoupe drawRect:] () #19 0x30a82df1 in -[UIView(CALayerDelegate) drawLayer:inContext:] () #20 0x31e951fe in -[CALayer drawInContext:] () #21 0x31e951a7 in backing_callback () #22 0x31e94db7 in CABackingStoreUpdate () #23 0x31e9442e in -[CALayer _display] () #24 0x31e887d1 in CALayerDisplayIfNeeded () #25 0x31e86b3f in CAContextCommitTransaction () #26 0x31e86853 in CATransactionCommit () #27 0x95aea9c2 in __CFRunLoopDoObservers () #28 0x95aec424 in CFRunLoopRunSpecific () #29 0x95aeccf8 in CFRunLoopRunInMode () #30 0x31699d38 in GSEventRunModal () #31 0x31699dfd in GSEventRun () #32 0x30a5dadb in -[UIApplication _run] () #33 0x30a68ce4 in UIApplicationMain () Since I am using DOMRange's and selection(s), the issue seems to be related to this, but I thought the issue was solved, and with more complex DOM manipulations it is happening again. It's worth adding that I am doing these changes while some UI events are happenning (e.g: touches), but if I simulate the same process steps in another way (pressing a button for each DOM manipulation) it doesn't happen. IMHO it may be related with some sync/event/layout issue but don't know yet the WebKit internals. If somebody can shed me some light on it, I would be very grateful. Thank you, Diego ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Webkit (Mobile Safari) issues in the iPhone
Hi David, On Thu, Oct 16, 2008 at 2:09 AM, David Kilzer [EMAIL PROTECTED] wrote: The WebKit framework is not public API on iPhone OS at this time, so any direct calls you make to WebKit are not supported and may have unintended consequences (like crashes or hangs). Yes, I am aware that the WebKit is not public for the iPhone OS. Having said that, if you're seeing an issue with -[UIWebView stringByEvaluatingJavaScriptFromString:], please file a bug on http://developer.apple.com/bugreporter/. A reproducible test case (or attaching your entire project as a zip archive) with steps to reproduce is greatly appreciated. Thanks! But I am now mainly lookin for a (even little) hint from most experienced developers, since I feel (from weeks of debugging) that the issue is related with DOMRange(s), surroundContents(), normalize() and events in the UI. But may be is not happening on Safari/Chrome (I can't do the exact test with these browsers). The crash doesn't happen when I call javascript, it happens later and I can force this crashes calling a layout function inside the webview. Thank You, Diego ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
