Hello Rob,

rob wrote:

> Yes, I'd go for the second version too. I'm just thinking that what the

OK, now I'll finalize the exact division and names for chapters.

> reader wants and what we want to get across is
> 1) Why use EH and
> 2) How to use EH.

I wolud be very happy if you wrote some paragraphs about what you or
anyone else colud benefit from using EH. I'm always coding and trying to
add new features to it, and finally I'm just too tired to translate my
jumbled thoughts about why this and that would be useful and especially
in what cases.

> The section I) copyright etc goes first just so it gets read ;-)
Similar to
> what is in the original manual?

Yes. Though, IMHO, it is a matter of taste, and in other hand, it
doesn't matter where to put, if someone is interested, he will look for
it, but if not, just skip it.

> In II) Features, I would be concentrating on Why use EH. A short
description.
> Like some of what is in try.php

Yes, but I need to write a more convincing, demonstrative test page. It
is key point whether the chapter "Why use EH?" should explain what one
can see while testing the demo page (try.php). What do you think about it?

> A more in-depth discussion could follow.

OK.


> My immediate and selfish interest is in 2) How to use EH.

> I like the PHP installation instructions which have a very brief
step-by-step
> installation and test instructions - really useful the second time
around as
> a reminder - followed by a more detailed version.
> I'd like to include the obvious - put the ErrorHandler.inc file in your
> include directory - reported by phpinfo(). Put try.php in directory
your
> webserver serves.

You are welcome :))

> Put the .ini file in the same directory as ErrorHandler.inc (I just
found
> this out ! )

You are free to change the default ini path in ErrorHandler.inc to
assign new value to ERRORHANDLER_DEFAULT_INI contants at beginning of
the file or to supply the file location to constructor in the 1st argument.


> Do you have some preference as to what tools to use to put together this
> document? Are we aiming for HTML?

Yes we are aiming for HTML, but from DocBook XML source through an
automatic transformation with XSLT or DSSSL. I've been working on PHP
Manual in the past, I've some experience about those products. If you
are unfamiliar with those, it is not a problem.

It is totally enough for me, if you write it text/plain (maybe with mose
special markup for linking, etc. -- we'll discuss it), or .rtf.

The main thing is not to waste time to design the resulting pages, it is
up to the automatic transformation process (like PHP manual.) I'm
thinking about to use a stylesheet like used in the Postgres Manual.

--
Your turn,

Gerzson