Hello Richtermeister, > Personally, I'm pretty fine with code generation.. never got why > that's an issue.
Actually, I like code generation when it's useful. Like in query classes. If you looked at current Propel development practices they write behaviors into strings (not in native php file), then this strings are injected by code generator in model class, and only then you can use models with your behavior. Or you may see that your code contains stupid syntax mistake and you need to regenerate classes again, and again, and again... I don't see how to develop any complex behavior with this scheme. In this case I like Doctrine's events-listsners-templates, they are much simple then code generation and much usable then old sfMixer stuff. So Doctrator imho is right step in Doctrine and PHP ORM's evolution. But i really miss Propel 1.5 generated queries... > On Dec 5, 3:37 pm, Davert <[email protected]> wrote: >> Hello Pablo, >> >> >> >> As I see now it's Doctrine 1 based on Doctrine 2. Well done! >> >> I'm working with Doctrine 1.2 for about half a year and I miss several >> things that were in Propel 1.5. It's very good idea to merge the best of >> Doctrine 2, Doctrine 1 and Propel 1.5 together. >> >> I don't know where is Propel 2 now, but it's always developed in great >> secret and then.. boom! and here is a new version. >> >> What I like about Propel 1.5 - it's generated qureies, it's a real killing >> feature that is missed even in Rails ActiveRecord. But current Propel >> implementation is too much into code generation, so even behaviors are >> generated. >> >> >> >> What I propose, is to look at Propel 1.5 queries code. If there is a chance >> to use it for Doctrator It would be best ORM for PHP and maybe not only in >> PHP. >> >> >> >> >> >> Thanks Jon! :) >> >> >> >> Yep Daniel, I saw the Propel2 post, but like I didn't see any code of that, >> I thought could be a good idea to make Doctrator with Mondator. >> >> >> >> I'm with you with join forces, although a minimum competition is always good >> to improve the projects! :) >> >> >> >> Pablo >> >> >> >> >> >> On Sat, Dec 4, 2010 at 7:31 AM, Richtermeister <[email protected]> wrote: >> >> >> >> Hey Jon, >> >> >> >> yeah, probably right - and I'm not familiar with the details of each >> >> implementation, just hate seeing two similar efforts miss each other, >> >> so just pointing them out to each other. >> >> >> >> Daniel >> >> >> >> >> >> >> >> On Dec 3, 12:45 pm, Jonathan Wage <[email protected]> wrote: >> >> > Hi, >> >> > >> >> > I think Pablo is way further along than Propel. As far as I know Propel has >> >> > not done any work towards this and Pablo already has a completely working >> >> > implementation, and it is good. We're looking to make Doctrator the defacto >> >> > standard AR implementation on top of Doctrine. >> >> > >> >> > - Jon >> >> > >> >> > >> >> > >> >> > On Fri, Dec 3, 2010 at 12:31 PM, Richtermeister <[email protected]> wrote: >> >> > > Hey Pablo, >> >> > >> >> > > while I haven't looked at your code in detail, it sounds similar to >> >> > > the path Propel2 decided to take.. >> >> > > Have you looked at this: >> >> > >http://propel.posterous.com/propel2-will-be-an-activerecord-implement... >> >> >> >> > >> >> > > Might be smartest to join forces. >> >> > >> >> > > Have a great day, >> >> > > Daniel >> >> > >> >> > > On Dec 3, 1:39 am, Henrik <[email protected]> wrote: >> >> > > > Veeeery nice! >> >> > >> >> > > > On Nov 30, 12:05 pm, Pablo D�ez <[email protected]> wrote: >> >> > >> >> > > > > Hi all, >> >> > >> >> > > > > Last weekend I published Doctrator, an ActiveRecord implementation >> > > > > (or >> >> > > not) >> >> > > > > with real and flexible behaviors for Doctrine2. >> >> > > > > Yep, but... what does Doctrator do really? Yesterday I published a >> > > > > post >> >> > > > > about it also: >> >> > >> >> > > > >http://mondongo.es/blog/9/doctrator-real-and-flexible-behaviors-for-d. >> >> > > .. >> >> > >> >> > > > > If you are a Doctrine2 user, please tell me what you think about >> >> > > Doctrator >> >> > > > > and its way to use Doctrine2 and to build behaviors. >> >> > >> >> > > > > Doctrator comes with the following behaviors (for now): >> >> > > > > * Hashable >> >> > > > > * Ipable >> >> > > > > * Sluggable >> >> > > > > * Taggable >> >> > > > > * Timestampable >> >> > > > > * Translatable >> >> > >> >> > > > > I'm going to make the Tree and Versionable behaviors also. If you >> > > > > want >> >> > > to >> >> > > > > help me with them or to make more, please tell me! >> >> > >> >> > > > > By the way, Doctrator has also integration with Symfony2 with the >> >> > > > > DoctratorBundle. >> >> > >> >> > > > > Thanks, >> >> > > > > Pablo >> >> > >> >> > > > > -- >> >> > > > > *Pablo D�ez | @pablodip* >> >> > > > > MondonGO Lead Developerhttp://mondongo.es >> >> > >> >> > > -- >> >> > > 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" >> >> ... >> >> read more » -- Best regards, Davert mailto:[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
