Luka I don't think it makes a difference if your running a lot of thumbnails you would want to use gpu's some sort of render farm arrangement. My port does it as a result of the design not because of a strong desire to render with the cpu. Also for real world web pages your going to have problems with plugins which depend on X11 and native widget libraries.
So although its possible with my port I can't see a single real problem that can be solved with this approach. Gtk/DirectFB will work for most pages if you have a flash port. Thats the number one stumbling block. I did my headless version of DirectFB for example to use the DirectFB video provider for the media tags. You can take other approaches but you would need to consider at a minimum flash and the media tags. For complete font support your going to have to use pango or go with the QT port but the QT port gets you back to the plugin issues if you don't use X11 and a lot of plugins use GTK so.... As far as releasing I'm not in control of the release cycle except for creating delays as I work on stuff :( It should be released however some time this year. I obviously don't disagree with your idea in fact I worked hard to ensure my approach was adaptable so it could be used for these types of use cases so someday we will have what your looking for if things go well. I actually designed it to work with all the legacy use cases I mentioned but be flexible enough to transparently drop them when replacements without the legacy X11/Gtk dependencies become available. So soon a framework will be available to allow you to reverse software bloat but I've got no idea if software developers will accept it. I built it to deal with the problems that occur with our new embedded devices that have capabilities rivaling desktops where bloat is a huge problem. The fact it can do what your asking makes me confident the design is correct in fact it solves problems your not considering. On Thu, May 22, 2008 at 8:41 AM, Luka Napotnik <[EMAIL PROTECTED]> wrote: > Wow really? Could you share the port please. I've been looking for such > a port to save the cairo painting to a PNG image. > > Greets, > Luka > > Dne 22.05.2008 (čet) ob 07:41 -0700 je Mike Emmel zapisal(a): >> I actually have a WebKit port with no dependencies but Cairo. >> >> >> >> On Thu, May 22, 2008 at 7:02 AM, Luka Napotnik <[EMAIL PROTECTED]> wrote: >> > Hello Mike. >> > >> > What I need is a WebKit port that is independent of any display server >> > (X or a framebuffer). I only want to render the page to an image. And >> > since cairo is a great graphics library I think It's a good start. >> > >> > Greets, >> > Luka >> > >> > Dne 22.05.2008 (čet) ob 06:49 -0700 je Mike Emmel zapisal(a): >> >> Use the GTK DirectFB backend. >> >> >> >> I have a memory only system that I really need to get into the trunk. >> >> But if you have a graphics card in the system the fb0 will work. >> >> >> >> Its on my TODO to get the mem only system checked in and I can give >> >> you a patch in the mean time if its a issue. Also you can use the vnc >> >> driver >> >> as a virtual framebuffer. >> >> >> >> Also some of the XServers should work in a similar way so you can probably >> >> play the same trick with the right X11 server. >> >> >> >> >> >> On Thu, May 22, 2008 at 4:21 AM, Luka Napotnik <[EMAIL PROTECTED]> wrote: >> >> > Hello. >> >> > >> >> > I am interested in porting webkit to cairo for off-screen rendering >> >> > without a X server. As I cannot find any documents about porting to >> >> > other platform I would really appreciate if you could help me with some >> >> > hints about porting webkit. >> >> > >> >> > Greets, >> >> > Luka >> >> > >> >> > _______________________________________________ >> >> > webkit-dev mailing list >> >> > [email protected] >> >> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> >> > >> >> > >> > > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
