Now CURL is high on the todolist and going back to fixing GtkLayout for staticbackground and API is on the todolist. For CURL it is a matter of improving throughput, parsing the HTTP header and setting the HTTP Header (Cookies, POST). Also redirects, etc. are to be implemented for curl. For GtkLayout I need to somehow invalidate the region before gdk_window_move is called in the Closure connected to the adjustment_changed signal to avoid the visual appearance of flickering. Well and the API is a complete other topic as this will force us to think about clipping, sharing one cairo_t* between Frames, recreating the FrameView on demand... there is a lot of todo but the port is promosing and in good shape.
Alp Tolker has battled cairo, we have clipping issues fixed, we can render SVG, the canvas element is going to be implemented as well.
14 comments:
great progress - it can render my corporate logo briefly before crashing at libfontconfig.so.1 0x00002b1138372b3a in WebCore::FontPlatformData::isFixedPitch..
why is CURL needed - seeing as the browser can already load pages, and even do XHR. just to rip out some nasty hardcoded socket code?
Well curl is needed to load pages using a protocol called HTTP. It is already doing that inside WebKit but it has some limitations that deserve fixing.
Make sure to apply the FontData Gdk patch from bugs.webkit.org and if it is still crashing please file a bug report with at least the backtrace and if valgrind works on AMD64 with valgrind output as well.
AEbPJ2 Your blog is great. Articles is interesting!
1lwCK5 Thanks to author.
Hello all!
Thanks to author.
Good job!
Wonderful blog.
actually, that's brilliant. Thank you. I'm going to pass that on to a couple of people.
Wonderful blog.
Nice Article.
Please write anything else!
RQtryA Please write anything else!
Post a Comment