Hi again, after making some more thoughts about naming and integration with symfony I came to another approach:
I suggest to simply integrate this with the existing factories.yml as the syntax is pretty much the same and I could imagine to change the config handler to support the old and new way to setup context objects. Because that is all we are doing here: setting up context objects. Nothing more... Or in other words: IoC will be available through the use of factories.yml without new terms. No 'Tone' and no 'Bean' no tone.yml Only an enhanced syntax of factories.yml In sfContext I will for example rename getTone() to a more common get(). So this will get even easier than it is already already. For those who wonder: I'm talking about my mahono branch and the dependency injection support I added recently for testing and getting feedback. Regards, Matthias On 20 Jun., 08:40, "Matthias N." <[EMAIL PROTECTED]> wrote: > Hi Jan. > > I'm not really convinced so far as the term 'bean' was only choosen by > the Spring people because it's Java.. > My opinion is that things should stay where they belong to. Beans > belong to Java. > I could imagine to find a more common name like 'object' or > 'component'. But 'object' is just too common and 'component' is > unfortunately already used for another thing. > But I will listen for other opinions about that. On the other hand > this is only a draft, an idea how to provide a IoC solution with > symfony. > > On 19 Jun., 23:28, Jan Markmann <[EMAIL PROTECTED]> wrote: > > > On 19 Jun., 18:25, "Matthias N." <[EMAIL PROTECTED]> > > wrote: > > > > - I renamed "bean" into "tone" as I thought "symfony tone" is > > > cooler... > > > Please change it back. I beg you. > > I see your interrest in finding a new cool name, but think about > > acceptance of your solution with others. > > Bean is a term from the java-world, but I guess the creators of garden > > knew why they kept it. > > Millions of developers know this term since years. Nearly every > > developer that ever came in contact with java (which are most likely > > the most around) knows what a bean is. A plain old object with > > accessor-methods corresponding to its properties that can be > > instantiated using a parameterless constructor. > > Think about those who don't read this mailing-list and stumble upon > > symfony. You force them to learn a new term they have to lookup each > > time. And that for a thing they already know by another term. > > > What if some friend would force you to recognize the term 'airplain' > > as a car? Wouldn't that drive you crazy? On the one hand because you > > used car to describe that 4-wheeled thing for years and on the other > > hand because you use the term car each time when you are talking to > > other people than that special friend. Some day you would stop talking > > to him about cars. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
