mirror of
https://github.com/netsurf-browser/netsurf
synced 2025-02-10 03:24:21 +03:00
6bced73998
Scheduled events are now in event time order, so schedule_run simply takes the top event off the heap and runs it (if we're polling, rather than having received a signal that the next event is due to be run, we check first that we have passed the scheduled time). This should provide performance benefits as we are no longer trawling the entire list of scheduled events (potentially hundreds) every time an event is signalled or the schedule list is polled. svn path=/trunk/netsurf/; revision=11703
--------------------------------------------------------------------------------
NetSurf README
--------------------------------------------------------------------------------
This document should help point you at various useful bits of information.
Building NetSurf
==================
Read the appropriate BUILDING-* 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