1User Interface
2==============
3
4[TOC]
5
6Netsurf is divided into a series of frontends which provide a user
7interface around common core functionality. Each frontend is a
8distinct implementation for a specific GUI toolkit.
9
10Because of this the user interface has different features in
11each frontend allowing the browser to be a native application.
12
13# Frontends
14
15As GUI toolkits are often applicable to a single Operating
16System (OS) some frontends are named for their OS instead of the
17toolkit e.g. RISC OS WIMP frontend is named riscos and the Windows
18win32 frontend is named windows.
19
20## amiga
21
22Frontend specific to the amiga
23
24## atari
25
26Frontend specific to the atari
27
28## beos
29
30Frontend specific to the Haiku OS
31
32## framebuffer
33
34There is a basic user guide for the[framebuffer](docs/using-framebuffer.md)
35
36## gtk
37
38Frontend that uses the GTK+2 or GTK+3 toolkit
39
40## monkey
41
42This is the internal unit test frontend.
43
44There is a basic user guide [monkey](docs/using-monkey.md)
45
46## riscos
47
48Frontend for the RISC OS WIMP toolkit.
49
50## windows
51
52Frontend which uses the Microsodt win32 GDI toolkit.
53
54# User configuration
55
56The behaviour of the browser can be changed from the defaults with a
57configuration file. The [core user options](docs/netsurf-options.md)
58of the browser are common to all versions and are augmented by each
59frontend in a specific manner.
60
61
62