Dashamir Hoxha - 2003-07-30

Improve the structure of the framework and the application so
that two independent applications can comunicate easily with
each other. E.g. one of the  applications can include the other
(like a webbox that can include another webbox) and both of them
work independently in the same window. One of the applications
can check or modify the state of the other application, can
modify its behaviour, can use its resources (images, templates,
etc.), etc.

Such a capability would be useful for applications like "browse",
which browses and displays the templates of another application
(actually 'browse' is implemented like a tool, or a webbox that
is not totally independent from the application that it browses).
It may also be useful for "tidy", an application that rewrites
the templates of an egzisting application in XHTML format, with
good indentation etc.
It will also be useful for the WADE (Web Application Development
Environment), so that it is an independent application and
doesn't have to be mixed with the framework or with the application
that is being built.

In order to achieve this:
* Path constants, Option constants, Debug constants etc
  should not be constants, because the value of the constants
  cannot be changed.
* An event should tell (either implicitly or explicitly) to
  which application belongs, so that the framework can dispatch
  it to the correct webbox.
* etc.