Hello Rob,

this is far the best news I've heard since the first release :))
Please let me know what you need and what you want to do or what you
have done.

I already sketched the structure of the documentation very similar to
the PHP or Smarty manuals. Comment it! I was thinking a lot about what
would be the most appropiate:

a) telling everything about every feature and aspect of EH one by one
(going into details immediately chapter by chapter), which results
something like this:

I. CONTEXT (an sample chapter)
1. What it is?
2. INI settings
3. API (methods and properties)
4. changelog

_OR_

b) first give an outline, then show how to use it, and last but not
least reveal how it works, what the proper syntax is, what internals
must taken into consideration.

I. Acknowledgments - Copyright - Short Intro

II.Features Part
1... (you know :) CUSTOM, CONTEXT, SOURCE, LOGGING, ALTDLOG, etc ...
each one with a short example.

III.Usage Part
(How-tos, describing the most common and advanced use cases)
1. installation
2. upgrading - from now on, this chapter would comprize the
information about how to replace an earlier version with the new one
strongly considering what should be rewritten in your application (if
required).
3. common practise - debug and silent mode mainly
4. advanced tips
4.1 working with non-textual MIME outputs
(using while creating images, pdf-s, etc.)
4.2 per-session debugging
4.3
5. contributions - if any

IV.Reference Part
1. Ini file - complete reference of ini directives
(mainly copy from ini file)
2. Constants
3. Methods
4. Summary about EH parts with versioning
5. changelog (copy from readme.1st)


I vote for the last one. And you?

Please let me thank you again your kindness to help me improve the
documentation.