mirror of
https://github.com/netsurf-browser/netsurf
synced 2024-11-30 02:03:14 +03:00
94ab63319f
Returning an error instead of simply calling die allows more robust error handling. Secondly initialisation may continue even if the messages have not been loaded which is more friendly than simply dropping dead with no communication to the user. |
||
---|---|---|
!NetSurf | ||
amiga | ||
atari | ||
beos | ||
cocoa | ||
content | ||
css | ||
desktop | ||
Docs | ||
framebuffer | ||
gtk | ||
image | ||
javascript | ||
monkey | ||
render | ||
resources | ||
riscos | ||
test | ||
utils | ||
windows | ||
.gitattributes | ||
.gitignore | ||
COPYING | ||
Makefile | ||
Makefile.config.example | ||
Makefile.defaults | ||
README | ||
test-netsurf |
-------------------------------------------------------------------------------- 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