Hello Ryan,
i really like your style of writing docs.
Regarding proof-read: Form framework never "just accesses" the
properties if there are no getters and setters defined. You have to have
either get*, is* and set*, or public (!) properties or implement
ArrayAccess. Reflection is never used to get the values.
greetings,
Benjamin
On Sun, 17 Apr 2011 20:54:32 -0500, ryan weaver wrote:
The work-in-progress form component documentation (corresponding to
the symfony/symfony form branch) can be found here:
source: https://github.com/symfony/symfony-docs/tree/forms [11]
rendered: http://www.thatsquality.com/docs/book/forms.html [12]
The docs haven't been proofread yet, I have questions I'll be asking
over the next few days, the type references aren't completed yet, and
there are more topics that will still need to be covered in cookbook
articles. But other than all of that, it's getting close :).
Comments and corrections warmly appreciated.
Thanks!
Ryan Weaver
US Office Head & Trainer - KnpLabs - Nashville, TN
http://www.knplabs.com [13]
http://www.thatsquality.com [14]
Twitter: @weaverryan
On Wed, Apr 13, 2011 at 5:00 PM, ryan weaver wrote:
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 [7]
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 [8]
http://www.thatsquality.com [9]
Twitter: @weaverryan
On Wed, Apr 13, 2011 at 4:52 PM, Lukas Kahwe Smith 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:
>>> 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 FOSUserBundle and SonataAdminBundle 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] [2]
--
If you want to report a vulnerability issue on symfony, please
send it to security at symfony-project.com [3]
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] [4]
To unsubscribe from this group, send email to
[email protected] [5]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en [6]
--
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 [16]
Links:
------
[1] mailto:[email protected]
[2] mailto:[email protected]
[3] http://symfony-project.com
[4] mailto:[email protected]
[5] mailto:symfony-devs%[email protected]
[6] http://groups.google.com/group/symfony-devs?hl=en
[7] https://github.com/weaverryan/symfony-docs/tree/forms
[8] http://www.knplabs.com/en
[9] http://www.thatsquality.com
[10] mailto:[email protected]
[11] https://github.com/symfony/symfony-docs/tree/forms
[12] http://www.thatsquality.com/docs/book/forms.html
[13] http://www.knplabs.com/en
[14] http://www.thatsquality.com
[15] mailto:[email protected]
[16] 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
