Re: 5th manual notes
| From: | Gabor Hojtsy | Date: | Sun, 19 May 2002 17:39:22 +0000 |
| Subject: | Re: 5th manual notes | ||
| References: | 1 2 3 4 | Groups: | php.doc.chm |
| Request: | Send a blank email to php-doc-chm+get-210@lists.php.net to get a copy of this message | ||
> Just for curiosity ... how many machines and/or different installed OSs
did
> you test it?
Two machines, with different OSes, Win2k and XP.
> About fresh install ... i agree that any clean install will get rid of ANY
> problems .. but lets be serious .. no one wants to reinstall his OS every
> time a problem arrives.
My intention was not to advice you to reinstall your machine. I have
tries with a fresh install because that was available and that was
to mean that an installed program (eg. IE addon) can break that thing
on some machines, as a fresh XP works well.
> Problems should be identified then worked-around or bugfixed.
We still do not know what is the real problem.
> If it can't be reproduced .. then, well, you gotta try harder, use
> more machines, stuff windows untill it cries for help and you can reach
the
> error in its guts.
I know how bug fixes work. Please note that this is not a business
project. I work on it when I have the time and I feel like working
with it.
As all the HTML/JS/image files are in the CHM, anyone can
help debug the files and not just submitting a screenshot with a
unotes error, and asking for correction. Users of this manual have
so much machines, OSes and much more time summarized then me. One of
the benefits of open coding communities is the distributed testing
capability.
Do you think that PHP is tested by one person on his
ten machines with 5 different OS'es with at least 3 different setups
per OS? No. PHP is itself tested by many guys on the globe, and many
of them help to identify the problem, especially if the developer
of a specific code does not have the time, or cannot reproduce the
problem on his machine.
I've asked for help from the users of this
version of the manual. Till now, I have received tips, like turn off
error reporting in WinXP, or detect if that object is there. None
of these tips solve the problem, these are just workarounds not to
display that error message...
That object should be there on every
page as there is a <div id="unotes"></div> in every page hardcoded
into the HTML code, so there should be no error message stating that
this object is not there. BTW to make you happy I have added a check
now for this object (which is quite redundant) and so the error
message should not show up anymore.
The problem is still not solved, I still cannot reproduce it, and
I won't buy any more computers, OSes, etc. to debug...
Goba