Well, I think we should still wait to do major work on the plugin to bring it to a stable 100% finished state until Doctrine is also 100% finished and 1.0 stable.
Basically the reason why is because I won't have time to fix something if by chance something in Doctrine does change. At this point the api is pretty stable(more than it was before), but still the chance exists that something could be deprecated. Well, some of my ideas are the same as yours. I want to totally re-factor the pake tasks. This includes a complete renaming of everything, rewriting everything, and moving a lot of the functionality out of sfDoctrine and in to the core of Doctrine. - loadData() and dumpData() will be a core feature in Doctrine for dumping & loading data to & from xml/yml files, and sfDoctrinePlugin will just implement the Doctrine functionality in pake tasks. - The yml/xml schema model importing/exporting will be a part of Doctrine core, and again sfDoctrinePlugin will just implement the Doctrine functionality in pake tasks. Basically I want to make it so sfDoctrinePlugin is not doing any of the lifting and is just proxies and implements existing functionality that exists in the Doctrine core. - Jon On 8/22/07, Matthias Nothhaft <[EMAIL PROTECTED]> wrote: > > > Hi Jon. > > AFAIK Doctrine's API is pretty stable now, isn't it? > Maybe you could ask zYne- one more time? > > Another problem I see is that we need to provide tasks for both, symfony > 1.0 and the new CLI system of the 1.1 branch (trunk). > > And the other problem I have is the missing support for plugins that > don't use a schema.yml file. With the possibility to mix both worlds. > This is required if we ever want to use models of foreign libraries like > Sensei! > > IMHO these two "worlds" should be separated as the schema.yml stuff is > only symfony related. We need clean task names that show this > separation. For example all Doctrine tasks should be named the same way > we know it from Doctrine: > > doctrine-export should use Doctrine::exportSchema() > doctrine-import should use Doctrine::importSchema() > > > Maybe it's a good way to start adding symfony 1.1 tasks refactoring the > good old ones and then merge back the cleaned up code to the 1.0 tasks? > > Well.. ok.. I also think that we should wait some more days.. > But maybe I will change or add some little things I really need without > BC issues in the next days. > > Maybe you could already share your ideas for the plugin, too? > > Regards, > Matthias > > > > Jonathan Wage schrieb: > > Mathias, > > > > I started a lot of work on sfDoctrinePlugin, but it was just too much to > > keep the functionality working and up-to-date with all the core changes > > in Doctrine. I have left everything as is and I think we should wait to > > clean up the plugin until Doctrine 1.0 is released. > > > > I am happy to be the maintainer and I have lots of ideas for the plugin, > > but I am not going put any solid time on the plugin to make it > > completely finished until I have something to work with that is not > > going to change. What do you think? > > > > - Jon > > > > On 8/22/07, *Matthias Nothhaft* <[EMAIL PROTECTED] <mailto:[EMAIL > > PROTECTED]>> > > wrote: > > > > > > Hi folks, > > > > I ask all of you who recently developed on the sfDoctrinePlugin to > share > > your ideas for the future developement of the plugin. Maybe we could > > even find a new maintainer for the plugin as it seems that it needs > > some > > cleanups.. doesn't it? > > > > As I see from Trac the follwing persons commited to the plugin > recently: > > > > - Jon Wage -- seems to work pretty heavy on doctrine stuff at all > ;-) > > - gnat -- don't know his/her name.. sorry > > - chtito -- good old maintainer, but he seems to be inactive (any > > information?) > > - me > > - who else? please raise your hand > > > > > > There is need for the following things to do: > > > > - add new tasks for making it compatible with symfony 1.1 > > --> would be nice to cleanup the task names here! > > > > - remove dependency to Creole/Propel and add a task to completely > remove > > Creole/Propel from a frozen project. > > > > - add support for those (e.g. me) who don't use schema files and > > want to > > export/import record classes to/from database > > - implies support to mixup plugins using a schema.yml and those > who > > contain "user coded record classes" > > > > > > Any help with that is appreciated. > > > > Regards, > > Matthias > > > > > > > > > > > > > > -- > > Jonathan Wage > > http://www.jwage.com > > http://www.centresource.com > > > > > > > -- Jonathan Wage http://www.jwage.com http://www.centresource.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
