symfony Forms Book update

February 24, 2009 Fabien Potencier

Today, I have added more than 40 pages in two new appendices to the symfony forms book: one about form widgets and the other about validators. These appendices describe all built-in widgets and validators, and also widgets and validators from sfPropelPlugin, sfDoctrinePlugin and sfFormExtraPlugin.

For each widget or validator, you will find a full description, all available options and configuration settings, and useful examples to illustrate the usage when needed.

You can already read these appendices online. But as they are also meant to act as a day-to-day reference, feel free to also download them as a PDF file.

Comments

BjÃ¶rn Ahlers said on Feb 24, 2009 at 11:44 #1

Great! Thanks!

Dreur said on Feb 24, 2009 at 11:51 #2

Now you are talking :)
Thanks

Massimiliano Arione said on Feb 24, 2009 at 13:13 #3

Nice job! We (Italian community) are already working for translation.
Just a little bug I noticed: in appendix A, there's a render bug in sfWidgetFormSchema "caution" box.

saganxis said on Feb 24, 2009 at 13:34 #4

Really great news!thanks for your work

Markus.Staab said on Feb 24, 2009 at 14:27 #5

would be nice to see a prefix like "Appendix A" and "Appendix B" on http://www.symfony-project.org/book/forms/1_2/en/

Kardie said on Feb 24, 2009 at 15:36 #6

That's great, I really appreciate the hard work you guys put into documenting the framework.

Maybe it's a good time then to ask, whether or not there are plans to complete the missing chapters of the Forms Book in the nearest future?

phpleo said on Feb 24, 2009 at 16:12 #7

Awesome, Thanks!

Fabian said on Feb 24, 2009 at 17:39 #8

Kardie, well i would say its a bad moment to ask for more when you just recieved a lot. Chapters will be added. If they wouldnt be numbered as they are people wouldnt ask so much.

Fabien said on Feb 24, 2009 at 17:42 #9

@Massimiliano Arione: fixed (this is a bug in the Markdown converter - the fix is to uppercase the first letter of the table tag, not nice, but it works)

@Markus.Staab: fixed

Scott said on Feb 24, 2009 at 18:43 #10

Thank you Fabien. We truly appreciate all of your time and effort, the documentation for symfony is the best of it's kind and keeps getting better!

Tomasz Ignatiuk said on Feb 24, 2009 at 20:28 #11

This is great!!!
Thank you very much. This is something that was missing. It is very nice that you answer for users requests. Thank you again. God job!!!

dereck said on Feb 24, 2009 at 21:08 #12

thank you, guys

Kardie said on Feb 25, 2009 at 11:41 #13

@Fabian

Please take a note of the difference between asking, whether or not there are plans to complete the chapters anytime soon (I would take "yes, they will be completed next year" for an aswer) and demanding attitude like "GIMME THAT DOCS NOW!! MOAR!!" ;)

Fabien said on Feb 25, 2009 at 12:06 #14

@Kardie: The only missing chapter is the one about nested forms. It will take a bit more time to write, but be reassured that we are working on it.

Kardie said on Feb 25, 2009 at 12:48 #15

That's good to hear. Thank you, Fabien.

John said on Feb 26, 2009 at 02:34 #16

Great work on the book. However I still face the same problem that I have reported in bug #4993.

Although the sfValidatorPropelUnique works fine when inserting new records, it will have problems in updating existing records if there is more than one unique column.

I am using symfony 1.2.2 and the problem still persists and there is no mention this is fixed elsewhere.

Is there anyone else here who is encountering the same issue?

halfer said on Feb 26, 2009 at 14:32 #17

@John - this isn't the best place for bug discussion. If there is no action on the ticket for a while, but it is a confirmed bug, then raise it on the devs list and, if you can, offer to create a test case if necessary.

Hope that helps :)

jL said on Mar 24, 2009 at 16:55 #18

Are there plans to publish the forms book via Lulu, as well, when the last of the chapters have been added?

If not, please allow me to +1 the idea ;-)

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.