Hi Jan,

thank you for your feedback.

I did not use Garden - I only built one class based on the
ApplicationContext class of Garden and wrote another class: a yaml
config driver - and that's it. Maybe I shouldn't mention here that my
work was inspired by Garden (which is a simplified port of the IoC
from Spring) to not confuse people as my solution is even much easier
than Garden is (as I ommited the whole xml stuff in favor of yml which
saves me from a bunch of classes...)

Well I don't know Spring but my opinion is that AOP should be
supported by the language itself and not be implemented somehow hacky
in the code. I know the typo3 people have an AOP solution in their 5.0
branch but this is such a big thing with about 20 classes or more.. I
don't think that we really want such an overhead with symfony..!?
But feel free to contribute like I do with the IoC stuff. ;-)

Regards,
Matthias


On 19 Jun., 23:50, Jan Markmann <[EMAIL PROTECTED]> wrote:
> I haven't reviewed garden yet but it looks like it is no longer
> maintained.
> Perhaps it's better to create something new based on garden instead of
> using garden.
> Sorry Matthias if already done, didn't review your commits yet as
> well.
> One idea I would like to bring to you would be to also take a bunch of
> inspiration from the spring-framework, like the creator of garden did.
> They ceated a really nice AOP-component (~ Aspect-oriented programming
> <http://en.wikipedia.org/wiki/Aspect-oriented_programming>) that makes
> things like securing objects an enjoyment and brings even more
> decoupling.
> Since security is a very important topic in symfony and in symfony,
> like in other MVC frameworks, we have well organized call-stacks, AOP
> would be a great benefit in decoupling big parts of that call-stacks.
> Perhaps it would even be a good idea to implement the IoC-Container
> independed from symfony (like lime) and just use it inside.
> I don't know whether you are familiar with spring, but if not I would
> like to encourage you to read one of the great introductions to spring
> (<http://www.springframework.org/documentation>) prior to going futher
> in your IoC4symfony approaches, since I guess you would like many of
> theĆ­r concepts as well.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to