| Portions of this tutorial are incomplete and/or very out of date as of the 1.0 release. While some may find useful information in this tutorial useful, please check any code listings against the current version of the manual before seeking assistance on Zend Framework forums such as the mailing lists. |
The tutorial sections generally build on top of each other in a constructive style, trying to delay complexity until after demonstrating prerequisite concepts.
I understand from Bill Karwin this tutorial will receive some attention as soon as time permits.
I'd like to offer some suggestions.
1. Make it a project with a team assigned to it like the MVC and DB teams etc. I think it's important enough personally.
2. Make it installable as "working out of the box" as much as possible. eg. self contained DB with SQLite. .htaccess file instead of the albeit faster central config.
3. Make it track the current stable ZF release.
4. De-mystify the complexity of the controller by building in CLI access for some maintenance task as well as Web access and illustrate action helpers and plugins.
5. Build in a security strategy to bring the demo up to "real world" standards.
6. Show the use of table references (with DRI in native or ZF)
7. Add unit testing to it if not already in.
8. The Demo should showcase ZF as people's first experience of it and earn itself the right to a nice big button in the Download page. Theory is great but there's nothing like seeing the cogs whirring in action for a newbie to get that instant "gratification" and "buy in" to how ZF's stated Goals under the Roadmap look in concrete deployable form.
ZF Home Page
Code Browser
Wiki Dashboard
Gavin
Is there someplace where we might download the tutorial code as a working tutorial chapter Package? ... so we can see how it fits together? ... including the required directory structure.
I'm finding it hard to distinguish between tutorial ZF class explanations vs. the code to be used vs. where specifics fit within files and the directory structure.
MVC examples on various (other) sites, written using specific (earlier) beta versions (usually unspecified as to either version or date written) are getting ocnfusing.
For me, it's much easier to see a working chapter/"Stage" example at some static point in the explanation ... than to imagine "Stages" accumulating throughout a tutorial.
Thanks - for understanding ...