				The Big Overview

The whole dependency tree is supposed (in ideal world) to look somewhat like
the following. Please note that this deals only with the core parts of ELinks,
not extensions like bookmarks, cookies, globhist, mime etc.

Note also that some other parts of ie. lowlevel/ are omnipresent as well and
it's ok :-). Also some other exceptions are ok.

document/html/ is containing something which is supposed to be ELusive in the
future, so... ;-)

dialogs/ can serve as a frontend for stuff exported from the frontend all
around, its dependencies are meant rather regarding the _functionality_ (not
content) it requires/provides.

scripting/ (== browser scripting) is also expected to hook all around, perhaps
it should be better in the omnipresent box.

.---------.
| util/   | <-- This is omnipresent :)
| config/ |
| intl/   |
`---------'

                   .-------.         .---------.
                   |  bfu  | ------- | dialogs |
                   `-------' \       `---------'
                       |      `---.       |
                 .----------.      \ .--------.
                 | terminal | ------ | viewer | ------------------.
               / `----------'        `--------'                   |
           .--'        |                  |                       |
.-------. /      .----------.        .---------.        .-----NOTDONEYET-----.
| osdep | ------ | lowlevel |        | ELusive | ------ | document scripting |
`-------'        `----------'        `---------'        `--------------------'
                       |                  |
                 .----------.        .---------.        .----/scripting/----.
                 | protocol | ------ |  sched  | ------ | browser scripting |
                 `----------'        `---------'        `-------------------'

(Note that ELusive isn't there yet neither, but document/ supplies it for now.)

$Id: README,v 1.10 2003/12/31 23:19:44 pasky Exp $
