A variety of ORM layers would not be too bad. I heard of Junction already and I think it's worth to keep an eye on it - but as Ian mentioned before, Junction is in a really early state and Doctrine seems to be the right choice for now.
On Oct 5, 3:31 pm, Kiril Angov <[EMAIL PROTECTED]> wrote: > Ian P. Christian wrote: > > Kiril Angov wrote: > > >> It is funny because, the site looks like some marketing site for an > >> application or something. The link to the actual documentation and wiki > >> is in small letters with the text "If you are a developer please check > >> out the developer page for details about how to get started with > >> Junction. " Well, who else will come to your site if not a developer :) > >> Found it kind of ironic. > > > The feature list looks pretty basic, and it's 'planned' features only > > seem to go as far as implementing only some of the stuff doctrine does - > > wonder why they are bothering rather then just contributing to doctrine :) > > Isn't this a question for most of the OSS? People always think that > having a different vision is a reason to make a new project rather than > extending an existing one to implement your vision. Should I be creating > a form of symfony because I believe the css and javscript combining in > one file is job of the framework rather than some half done plugins? ;) > > Kupo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
