I'm reading the master versions now, thanks to those who pointed them out. I'm continuing to summarize my impressions since it should be useful in improving these guides. If I don't share these impressions now I will know too much about Symfony 2 to remember them later (:
Continuing with forms, the updated version of this page: http://docs.symfony-reloaded.org/master/guides/forms/overview.html Does not seem to make sense with regard to rendering forms. It shows this: return $this->render('HelloBundle:Hello:signup.php', array( 'form' => $form )); Passing the form object directly to the template, but then says this: "Instead of passing the form instance directly to the view, we wrap it with an object that provides methods that help to render the form with more flexibility ($this->get('templating.form')->get($form))." Huh? No we didn't. And why would we? The presented template seems happy without it: <?php $view->extend('HelloBundle::layout.php') ?> <form action="#" method="post"> <?php echo $view['form']->render($form) ?> <input type="submit" value="Send!" /> </form> Assuming this code works, there doesn't seem to be any reason to mess about with templating.form. * * * Is it possible to render a form with a Twig template? The earlier tutorials emphasize Twig, so I'm all ready to rock with Twig, and wondering how to continue with it. * * * The main problem with this guide is that it jumps right into talking about your Domain model without ever explaining what that is. I think I get it: it's the "M" in MVC. It might be Doctrine entities, but it might not be. You can have Entity classes without using Doctrine to persist them. But none of this is explained so the cart is really far out in front of the horse in this tutorial... OK, now that I look at some of the other topical guides, I'm apparently meant to have read the validation guide first: http://docs.symfony-reloaded.org/master/guides/validator/overview.html This makes sense to me in retrospect, but it's not clear to the reader - if I'm a newcomer I'm going to want to jump in and make some forms and then add some validation, almost certainly not the other way around. And the topical guides are not presented as progressive, "you must read these in order" material. If I need to read validation first to make forms work (because Symfony 2 flips things around and says a form is just a representation of a validatable class) then there needs to be a prominent "you need to read this first" link in the forms guide. Otherwise that chapter is too confusing to follow. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
