+1 on ease of use for new comers and getting started. It also is good for explanatory examples in documentation. We state this in the Doctrine documentation that annotations are used for documentation examples as they are easier to read because its all in one code block.
On Tue, Mar 8, 2011 at 8:08 AM, Fabien Potencier < [email protected]> wrote: > > On 3/8/11 2:47 PM, Thomas Rabaix wrote: > >> The main drawback of annotations is that the 'configuration' code is >> directly linked to the raw php code. So there is no clear separation and it >> make harder to tweak the configuration from an external points of view. (can >> it be view as an Anti-DIC Pattern ?) >> > > This main drawback is also a big advantage. Instead of having to go to > several different configuration files for validation, forms, routing, ... > the configuration is in the same file as the code itself. It eases things a > lot, especially for newcomers. > > As always, this is just one way to configure things but I think it's a real > good way when you get started. > > > If annotations are used in a final product/layer, I am fine with that. >> (configuration and code can be linked). But Annotations can be used as a >> solution for developing reusable Bundles and this situation is an open door >> to futur configuration issues. >> > > I think annotations are great for your own bundles you won't share. > > Fabien > > > >> >> On 8 mars 2011, at 14:00, Fabien Potencier wrote: >> >> On 3/8/11 1:50 PM, Robert Campbell wrote: >>> >>>> I am very impressed with the work of the SF2 dev >>>> team, but it's radical decisions like distributing FrameworkExtraBundle >>>> as a standard package that may deter me from embracing SF2 >>>> >>> >>> A radical decision? What are you talking about? We use annotations for >>> everything from validation to ORM model description. And it would not make >>> sense to use annotations for routes or cache? >>> >>> Sorry, but I don't get this discussion at all. If it's just a >>> documentation problem or a naming problem, tell me so. >>> >>> 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 >>> >> >> > -- > 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 > -- Connect with me on *http://twitter.com/jwage* <http://twitter.com/jwage> and http://about.me/jwage to keep in touch. -- 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
