On 07.09.2010, at 11:44, Fabien Potencier wrote: > On 9/7/10 11:29 AM, Lukas Kahwe Smith wrote: >> >> On 07.09.2010, at 11:23, Fabien Potencier wrote: >> >>> On 9/7/10 9:43 AM, Jordi Boggiano wrote: >>>> Heya, >>>> >>>> Didn't look at the patch itself, but conceptually I kinda like it. >>>> >>>> I'm not sure however if the multiplication of configuration options >>>> (xml/yaml/php/annotations) isn't gonna bite us in the ass at some point >>>> int he future.. It's nice and all that things are so flexible but aren't >>>> we abusing it at the moment? >>> >>> I have the exact same concern. We need to settle on one default >>> configuration format (especially for the documentation -- even if right >>> now, we always provide all formats in a nice tabbed box). >>> >>> What other think? >> >> >> i think it will be non trivial to offer a proper cascade logic when >> extending classes with annotations to be able to customize things. for >> example with a route, the controller shouldn't care about what the URL's >> look like, there could actually be multiple URL's all pointing to the same >> controller. All the controller should care about is the parameters being >> passed to it. > > Right. I think you are talking about the FrameworkExtraBundle I have just > released. As I said, I see it as a nice way to create prototypes faster. > Also, I have provided a bunch of annotations to see which ones looks nice, > and which ones are not good at all. I hope we as a community will have a > discussion about that. >
yes, right. discussions spanning mailinglist and twitter can be confusing to follow :) anyway, it was just an example about a general concern i have with annotations. for one they need to still enable extending, that being said in many cases extending will obviously be limited by whats possible without breaking the "is a" relation, in which case its mainly overwriting a previous definition with another value and not necessarily removing or adding entirely new things that need to be merged. but just like my routing example, there are some things that simply shouldnt be moved into the controller or whatever definition. regards, Lukas Kahwe Smith [email protected] -- 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
