Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.
This repository was archived by the owner on Jan 30, 2020. It is now read-only.

Documentation clarifications (quick-start) #147

Open
@bitwombat

Description

@bitwombat

Docs for ZF are so good and so essential for the often newbie-mystifying ZF. So I thought I'd seek a few clarifications to the quick start docs.

Happy to work this out and submit a PR once I understand...

From zend-form/quick-start

Item 1:

The chief benefits to using the Factory are allowing you to store definitions in configuration,
and usage of significant whitespace.

"significant whitespace" as in whitespace is significant (a la Python), or there's a significant amount? Either way, "huh"?

Item 2:

The default Form implementation is backed by the Factory. This allows you to extend it,
and define your form internally. This has the benefit of allowing a mixture of programmatic
and factory-backed creation, as well as defining a form for re-use in your application.

What does it mean in OOP or ZF for something to be 'backed by a Factory'? I know what factories are, and how they're used by ZF managers, but as a layman, I see the phrase "This allows you to extend it" and think "But I can extend any non-final class..."

And, many objects implement something like $this->add(), so how does Form being "backed by a Factory" make any difference here?

I think it is important to discuss some of the internals, as knowledge there can help people from being mystified when they 'new' their form in a controller and don't have any access to the usual managers. But some clarification or more explanation is needed for the above.

Thanks for great docs and I hope the above makes sense.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions