Go to file
Michael Drake 8332bf6b2a Plotters: Remove width param from path plotter.
We now use the stroke_width in the plot_style.
2018-05-23 13:48:17 +01:00
content Plotters: Remove width param from path plotter. 2018-05-23 13:48:17 +01:00
desktop Plotters: Remove width param from path plotter. 2018-05-23 13:48:17 +01:00
docs fixup doxygen directory list to cope with html content handler move 2018-05-10 22:47:46 +01:00
frontends Plotters: Remove width param from path plotter. 2018-05-23 13:48:17 +01:00
include/netsurf Plotters: Remove width param from path plotter. 2018-05-23 13:48:17 +01:00
resources Initial conversion of GTK accelerators to separate config file 2018-04-22 14:03:18 +01:00
test Update urldb test data for format 107 2018-04-22 14:22:21 +00:00
utils Resolve resource leak on error (coverity issue 1390560) 2018-05-18 10:02:03 +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 Move !NetSurf into frontends/riscos and fix up 2018-04-22 11:15:23 +01:00
COPYING Clarify licensing arrangements 2007-08-09 15:32:39 +00:00
Makefile move html and text content handlers where they belong 2018-05-10 13:37:02 +01:00
Makefile.config.example remove junk references to old javascript implementations 2016-09-19 22:02:51 +01:00
Makefile.defaults Sort out the logging so that -v etc do the right thing 2017-09-08 21:15:54 +01: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