Slashdot Mirror

← Back to Stories (view on slashdot.org)

Nokia Engineers on KHTML

Posted by ScuttleMonkey on from the embedded-devices-strong-with-the-force dept.

Rich writes "KDE could soon be making its way into your mobile phone. At aKademy in August David Carson and Deepika Chauhan from Nokia presented the work they've done in integrating KDE components into the latest version of the company's mobile phone software. Philip Rodrigues discusses this work with them on dot.kde.org."

6 of 98 comments (clear)

  1. Re:KHTML? by biehl · · Score: 5, Informative

    Yes, WebCore is Apples fork of KHTML. Read here for an explanation on how the collaboration between the projects works.

  2. Re:Warning by mattjb0010 · · Score: 5, Funny

    Seriously, they need to stop naming everything K-something, it's so incredibly lame.

    iAgree.

  3. Re:Cool... BUT (there's always a BUT) by TheRaven64 · · Score: 5, Informative
    WebCore is not dependent on X. It uses a small Qt-like backend. On OS X, this translates drawing calls into Quatrz (PDF-like) drawing commands. On X11, they can be translated into X11 drawing calls. On a Series 60 phone they will be translated into the native GUI's API.

    WebCore is LGPL. They have to make their changes available to people who buy their 'phones (they also have to allow their customers to use a different version of WebCore, which could be interesting). They do not have to contribute their changes directly back to Apple, but they probably will since it is usually much easier to contribute patches than maintain a fork (note that this didn't apply to Apple when they forked KHTML, since they were throwing more developer time at the codebase than KHTML had in total, so it was easier to fork).

    --
    I am TheRaven on Soylent News
  4. Re:Warning by imsabbel · · Score: 5, Insightful

    iDont.

    Seriously. When new to linux, and browsing through the huge garbage pile that is the "available list" of the package manager, finding something with the destinctinve "K" is really helpful, because they usually work and at least partly follow the same usability conventions.

    Case in point: i couldnt even EXIT that damn vi before reading 5 minutes into the damn man file without kill-9ing the PID, but luckily a "Kedit" in the corresponding cathegory was available, completely usable

    --
    HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
  5. Re: KHTML by g2devi · · Score: 5, Informative

    There are two ports, one from Apple and one based off the work from Apple by Nokia. Here's the link I think you're referring to:
                http://gtk-webcore.sourceforge.net/

    From the page: "Gtk+ WebCore is a Linux/Gtk+ port of Apple Computer Inc.'s WebCore KHTML html rendering engine including a web component. A reference browser implementation is included in the project. Gtk+ WebCore is a standards compliant (X)HTML rendering engine, javascript interpreter and an embeddable web component. The purpose of the web component is to be a light-weight, easy-to-compile and embed, open source rendering component.

    The project work is done at Nokia Research Center (NRC) as part of ongoing internet browser-related research activities. By releasing the source we hope to support in open source communities interested in using KHTML rendering engine component."

  6. Re:KHTML? by fdobbie · · Score: 5, Informative

    Since that was written, the world has moved on. Apple launched the WebKit open-source project as part of OpenDarwin. This means that WebKit bugs are now being tracked in bugzilla (in addition to Apple's internal bug tracking system), and WebKit, WebCore and JavaScriptCore have moved to a publicly accessible CVS server.