Programmer's Reference Guide


Guide de référence du programmeur

Sommaire Zend Framework

Guide de référence de Zend Framework destiné au programmeur


Comments

Wow this is a good feature like php.net . This will really help to get great documentation .

( Already logged in and when trying to add comments asking for name and email . Seems like a bug :( . Also its showing logged in as () null value . )
This comment is addressed to the ones that made the downloadable version of the documentation:

a) thank you for writing a documentation.
b) the downloaded documentation/manual/core/en is full of HTML-Bugs
c) it doesn't contain an index-page
d) none of the html pages validates on http://validator.w3.org/
e) adding a stylesheet instead of putting an invalid STYLE tag in the middle of the code would have been an alternative that is not-so-unusual today

I assume the makers of the Zend Framework made great efforts to produce a high quality framework. The downloadable documentation will need some quality-check too.

best regards
I am really appreciating the effort zend framework development team.
do you have a pdf version of this framework manual ???

regards

Oliver
Downloadable version: No index? No table of contents?
Overall this Programmers' Reference Guide is quite average and even very poor in places.

There is a lot of content which is good but huge parts aren't written very well. Very little cross-referencing too which makes the long page formats tough to navigate. Better indexes (already mentioned above) and "jump to section" links are desperately needed.

The search is awful. It always has been and it frustrates me to no end by bringing back either no results or barely relevant results. I've put up with it for months but clearly it isn't something that's being worked on as there haven't been any perceived improvements in that time so I have finally snapped and am giving you some feedback!

For example I get no results if I search for "action helper" or "url". Really? No results? At least let me get some bad results so I can adjust my search terms appropriately.

Instead I must always use Google to search your documentation. Not ideal.


I quite like the new documentation format, but I would really prefer a .pdf version. So, here's another vote for .pdf.

Thanks!

Mark
Here, here for the .pdf version!!!
I'm aware that online documentation is a better and easier way to provide up-to-date accurate documentation but, i would love to see also a pdf version of the stable release available for those, who like me, like to do some offline( see before bedtime) reading...
examples given is not good as detailed one with folder example .please change this & give the view
PDF !!!!
Alex G.'s comments are completely on target: search is basically worthless, not enough cross-referencing, and system needs jump navigation because some of the pages are very long. The old system was superior, minus the ability to comment.

The quickstarts are good, but the main documentation is a big turn off. I'm sure your driving aware newbies.
I vote for PDF Version for impress.
i vote for PDF version +1 for impress in paper.
Pdf version will be very helpful. please make a pdf version. This is a vote for the pdf version.
I definitely need a PDF version!
I think that every title in each chapter should have a index too. It's really hard to find what I need on the page. And it's better to have an overview on each page!
There seems to be some improvement in search functionality, but still the index seems "off." For example, if I search for "progress" I should get at least one hit out of the page on File_Transfer, which has a heading that reads "Progress for file uploads." But no. Only something on pubsubhub....

Maybe incorporating Google Search via API would be a stop gap until search can be improved?

How come there's no pdf of the document?
For a newbee like me, most documentation is not very helpful.

For most components I tried to understand (Layout, Navigation, Auth, Acl) there was two to five examples on how to do exactly the same thing - this is really confusing. And for none of the components, there was really working code.

Examples:
From just the information you get here, try to build a sample app which does:
- Have a website with 3-4 different basic layouts (2-3 frontand and one backend)
- Session handling with user authorization
- Authentication
- Navigation
- MVC with proper sub-view (or partials) encapsulation

The quick start example answered at least some of my questions, but even that was far from enough.

Next Vote For PDF Version ...
Hope this will be the last Vote !

Select a Version

Languages Available

Components

Search the Manual