Hi, to address your points individually:
PSR: i basicly only agree to PSR-0/4 and and PSR-3 such that we could provide a compatibility layer. Composer: that's already implemented (see https://packagist.org/packages/agavi/agavi) and will come into effect with the next release. There will be a 1.0.8 release in the near future. Until then i'd suggest using 1.0-dev for new projects. This is basicly 1.0.7 with patches for failing tests and the composer integration DI Container: Actually AgaviContext is a service locator. While this is may not be perfect changing everything to DI is something we need to discuss for 2.0 Traits: There are some great opportunities here to fix the AgaviParameterHolder and AgaviAttributeHolder coupling. But this is 2.0 stuff since that's a breaking change Generators: i don't see much use for generators in the scope of Agavi right now. Closures: yes please. Although there are not that many uses of callbacks right now in Agavi So yes we will adapt to those things, but only for 2.0. And before that i'd like to get the stuff which is in the pipeline for 1.x out first best regards, Dominik Am 03.03.2014 um 19:07 schrieb MugeSo <[email protected]>: > Hi, > > I'm glad to see this news! > We've long long long looked forward to this. > > PHP(and its trend) has very evolution: PSR, composer, DI container, trait, > generator, closure, etc... during development of agavi freezed. > So, I think, there is many tasks to adapt to thoese things. > > However, agavi reaped benefit of social coding now!! > Oh, we can fork and send pull request! yay! > > Thanks a lot for effort of Dominik, David and Noah! > > MugeSo > > _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
