You are right, but sometimes it's simply not possible.
For example:
I would have take care about the CHM documentation but it's not possible.
We developers do not have all needed informations or they are simply not
documented.
Actually I would have to build the sources manually per language and then
process chm conversion one per language.
And then I would not know if they are added to the homepage because who
should we inform without "blocking" a Zend employee ? ;-)
There is no information HOW the build process for the manual is processed by
you.
So we would have to clear the prerequisits but as you mentioned we are all
focused to 1.5 and actually noone really has time for such things.
Related to documentation.
In my opinion the best solution would be to have documentation related to
version... this way someone could download the documentation for his version
and he could also view it online. But we would have to take care that the
version is displayed usable and not somewhere hidden. :-)
Just my 2 cents
Greetings
Thomas Weidner, I18N Team Leader
http://www.thomasweidner.com
----- Original Message -----
From: "Wil Sinclair" <[EMAIL PROTECTED]>
To: "Simon Mundy" <[EMAIL PROTECTED]>
Cc: "Zend Mailing List" <[email protected]>
Sent: Wednesday, February 06, 2008 4:00 AM
Subject: [fw-general] RE: Documentation on framework site
To be honest, IMO the documentation situation is far from ideal right
now, and I can definitely see your point. On the other hand, 1.5. ;)
Have you considered putting together a proposal and reviewing what
changes would be required to our release process and build scripts? As
I'm sure you've noticed, Simon, the best way to get something done in
framework is to do as much as you can yourself without blocking on any
Zend involvement. :D Let me know what I can do to help you here, and
keep in mind that you might get more traction after 1.5 drops.
Thanks.
,Wil
-----Original Message-----
From: Simon Mundy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 05, 2008 6:39 PM
To: Wil Sinclair
Cc: Zend Mailing List
Subject: Documentation on framework site
Hi Wil
I'm not sure if this has been requested before, but would it be
possible to make it slightly clearer on the documentation pages that
the manual refers to the current trunk release of the framework?
If not that then perhaps hold back updates on the website until a
minor/major version has been released. I've seen a few cases where
people are confused as the new documentation refers to functionality
or changes that haven't yet been released to a stable version.
Or perhaps a-la MySQL's site there could be a browseable-by-version
page on the site? I'm not sure how automated the current process is so
hope I'm not asking for a biggy here :)
--
Simon Mundy | Director | PEPTOLAB
""" " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" "
202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000
Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654
4124
http://www.peptolab.com
