6 Netsurf is divided into a series of frontends which provide a user
7 interface around common core functionality. Each frontend is a
8 distinct implementation for a specific GUI toolkit.
10 Because of this the user interface has different features in
11 each frontend allowing the browser to be a native application.
15 As GUI toolkits are often applicable to a single Operating
16 System (OS) some frontends are named for their OS instead of the
17 toolkit e.g. RISC OS WIMP frontend is named riscos and the Windows
18 win32 frontend is named windows.
22 Frontend specific to the amiga
26 Frontend specific to the atari
30 Frontend specific to the Haiku OS
34 There is a basic user guide for the [framebuffer](docs/using-framebuffer.md)
38 Frontend that uses the GTK+2 or GTK+3 toolkit
42 This is the internal unit test frontend.
44 There is a basic user guide [monkey](docs/using-monkey.md)
48 Frontend for the RISC OS WIMP toolkit.
52 Frontend which uses the Microsodt win32 GDI toolkit.
56 The behaviour of the browser can be changed from the defaults with a
57 configuration file. The [core user options](docs/netsurf-options.md)
58 of the browser are common to all versions and are augmented by each
59 frontend in a specific manner.