Go to file
Michael Drake b6be869f19 Hotlist: Allow hotlist initilialisation without hotlist corewindow.
Now, hotlist_init can be called without a corewindow.  This allows the
hotlist backend to be up and running, before any hostlist manager is
opened.  Calling hotlist_manager_init attaches the hotlist to a corewindow.
2016-12-29 14:44:48 +00:00
!NetSurf local pages should not have a favicon 2016-11-20 13:32:28 +00:00
content Duktape: Prevent clang static analysis. 2016-12-28 15:06:08 +00:00
desktop Hotlist: Allow hotlist initilialisation without hotlist corewindow. 2016-12-29 14:44:48 +00:00
Docs fix spelling in backing store documentation 2016-11-20 15:12:46 +00:00
frontends Revert "RISC OS: Squash unused variable." 2016-12-29 12:56:38 +00:00
include/netsurf improve corewindow API documentation 2016-12-24 23:31:47 +00:00
render complete transition to locale independant core operation 2016-09-29 22:37:10 +01:00
resources haiku: add some menu accelerators to FatMessages 2016-11-21 17:26:58 +00:00
test Test: Add trailing whitespace and garbage datetime string parse tests. 2016-08-17 09:11:02 +01:00
utils move test script into utils 2016-12-16 14:45:16 +00:00
.gitattributes
.gitignore remove unused extraneous windows file 2016-10-19 11:08:45 +01:00
COPYING
Makefile fix haiku target selection from commandline 2016-12-22 16:04:59 +00:00
Makefile.config.example remove junk references to old javascript implementations 2016-09-19 22:02:51 +01:00
Makefile.defaults enable use of netsurf public suffix library to prevent supercookies 2016-09-20 21:45:35 +01:00
README

--------------------------------------------------------------------------------
  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