wiki:HackingGtk

Hacker's guide to WebKit/GTK+

Code layout

The GTK+ port targets the cross-platform GLib and GTK+ APIs as well as related libraries. This means that it can be built against any of the windowing systems supported by GTK+ and Cairo without modification -- those tested so far are X11 and DirectFB. Windows should work too.

Code specific to any one backend should be conditionally compiled only when that windowing system is available. One examples of this kind of feature might be direct X11/Win32 use for plugin support. This can be done at configure time or with a switch passed to the build system, or even just using the definitions provided by the gdk headers.

Main port components

Shared code modules

While the GTK+ port is the primary consumer of these backends, we aim to keep them portable, avoiding even ifdef'd sections specific to the Gtk+ port:

Bundled code modules

Bundled code is code checked into WebKit SVN that is developed and maintained primarily in some other source code repository.

  • Don't change the coding style of bundled code to match the WebKit guidelines
  • Avoid making needless changes to bundled code
  • Don't change the copyright headers without permission
  • Contribute modifications back to the originating project promptly where relevant

These files are bundled from other projects:

Last modified 10 years ago Last modified on Jan 20, 2014 6:42:22 AM