The new documentation is already underway (though it hasn't been updated 2 weeks and so will be a little out of date). It covers the basics and I've got an outline for the rest of the topics that I want to cover in the initial chapter (though I'm sure I'll miss a few things):
https://github.com/weaverryan/symfony-docs/tree/forms I can update this and complete it before Monday (pending any further changes that still need to be made). Having the symfony/form branch will help me know where I should be looking for the latest+greatest. Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Wed, Apr 13, 2011 at 4:52 PM, Lukas Kahwe Smith <[email protected]>wrote: > > On 13.04.2011, at 23:48, Fabien Potencier wrote: > > > > > On 4/13/11 11:26 PM, Bernhard Schussek wrote: > >> 2011/4/13 Lukas Kahwe Smith<[email protected]>: > >>> is there some sort of updated information on where we are at with the > form rewrite? > >> > >> I'm currently going through Fabien's changes and adding functional > >> tests for the rendering code. If I don't hit major problems, I can > >> merge his changes tomorrow. > >> > >> The plan after that is to create a symfony/form branch ASAP and to > >> update the documentation, so that we can gain more public testers. And > >> bug fixing, of course. I'm not sure whether we have a lot to discuss > >> though, honestly. > > > > The plan I've discussed with Bernhard is the following: > > > > * Create a symfony/form branch. Creating this branch means that the new > version will be merged into master eventually but that the current state is > not stable enough to replace the current form framework. So, I expect more > people will port their code to the new version. > > > > * Gather more feedback about the new code to check that all the > "problems" we have with the current code are "fixed" and that everything > that is possible today is still possible with the new version. > > > > * Check that the new API is at least as simple as the current one (and > simpler if possible of course). > > > > * Work on this branch to stabilize things until we are confident that we > are at least as stable as the current form framework in master (mainly > phpdoc, tests, class/method naming, and documentation). > > > > * Merge into master. > > > sounds good to me. > > i guess bundles like FOS\UserBundle and Sonata\AdminBundle should then > create "form" branches as well. > > i have one question about documentation. it would be good if we start > updating the documentation as well and then it would be nice to have a > rendered version of these docs somewhere. > > regards, > Lukas Kahwe Smith > [email protected] > > > > -- > 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 developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- 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 developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
