Go to file
Daniel Silverstone 6683818c18 Makefile.config.example: Document logging options
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
2019-08-02 10:03:07 +01:00
content Window: Provide a little more info on why not EXPOSE()ing some stuff 2019-08-02 09:27:06 +01:00
desktop Browser window: Make invalidate gui callback use unsacled coordinates. 2019-08-01 22:34:13 +01:00
docs Docs: Convert GTK doc to markdown. 2019-08-01 16:57:44 +01:00
frontends RISCOS: change invalidate to cope with unscaled rectangles 2019-08-01 22:34:13 +01:00
include/netsurf split browser and browser_window operations 2019-08-01 19:51:19 +01:00
resources update copyright years for release 2019-07-17 11:19:06 +01:00
test ensure monkey farmer copes with recv returnint EAGAIN 2019-07-06 10:08:10 +01:00
utils Logging: Also log the level and category 2019-08-02 09:58:41 +01:00
.clang-format add a clang format that roughly conforms to the netsurf style 2017-09-24 18:19:58 +01:00
.gitattributes add attributes file to stop .gitignore being exported 2013-04-19 21:27:45 +01:00
.gitignore make framebuffer use the language environment for the UI resources 2019-02-17 00:11:27 +00:00
COPYING Clarify licensing arrangements 2007-08-09 15:32:39 +00:00
Makefile add webp image handler 2019-02-17 12:09:17 +00:00
Makefile.config.example Makefile.config.example: Document logging options 2019-08-02 10:03:07 +01:00
Makefile.defaults add webp image handler 2019-02-17 12:09:17 +00:00
README Fix to point at current build documentaion. 2014-07-22 15:36:36 +01:00

--------------------------------------------------------------------------------
  NetSurf README
--------------------------------------------------------------------------------

  This document should help point you at various useful bits of information.


  Building NetSurf
==================
  
  Read the QUICK-START document in the Docs/ directory for instructions.


  Creating a new port
=====================

  Look at the existing front ends for example implementations.  The framebuffer
  front end is simplest and most self-contained.  Also, you can contact the
  developers for help:

      http://www.netsurf-browser.org/contact/

  Check out the developer documentation sources listed below too.


  Further documentation
=======================

  The Developer section of the web site has loads of info to get you started:

      http://www.netsurf-browser.org/developers/

  General documentation on how NetSurf's code works can be found on the
  development wiki:

      http://wiki.netsurf-browser.org/Documentation/

  The code style guide is here:

      http://www.netsurf-browser.org/developers/StyleGuide.pdf