On 2/28/11 10:24 AM, Jordi Boggiano wrote:
1) Alphabetically take the two components/libs together, and anything
that connects them goes in there:
Symfony\Bridge\DoctrineForm\..
Symfony\Bridge\AclDoctrine\..
+ consistency and no need to have two dirs to connect one component to a
library or another component
+ just one namespace clearly saying what is what
- looks a bit weird
2) Take the component name as the "owner" and add anything in it that
supports it:
Symfony\Bridge\Form\Doctrine\..
Symfony\Bridge\Form\Twig\..
Symfony\Bridge\Acl\Doctrine\..
Symfony\Bridge\Validator\Translation\..
Symfony\Bridge\Validator\Translation\.. does not exist. Bridges are only
for third-party libraries, not for dependencies between Symfony Components.
+ looks nicer
+ maybe clearer dependencies, i.e. if you use the Form component, you go
in that dir and see all your options for bridges.
3) Take the library as the owner, and list all components in it
Symfony\Bridge\Doctrine\Form..
Symfony\Bridge\Doctrine\Acl\..
Symfony\Bridge\Translation\Validator\..
+ also looks decent
- dependencies are backwards, if you use doctrine you can check any
component that supports it, but that's probably not too interesting for
people using components out of symfony, and symfony users won't have to care
I think 3) is better. As a bridge is about the integration of a
third-party library, I think it makes sense that the library name comes
first. Also, chances are that if you use Doctrine, you will need the
integration with many Symfony Components. In that case, you can just get
the Symfony\Bridge\Doctrine sub-tree repository.
Fabien
--
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
