Ben Sizer wrote: >> Please move this discussion to the elixir mailing list, if you don't >> mind, as it doesn't really have anything to do with TurboGears :) > > I understand why you said that, but really this just came off the back > of the TG stuff. I'm firmly of the belief that the TurboGears project > can't just abdicate all documentation responsibility for their default > model system to the Elixir project...
I agree, however, Elixir won't be the default for TurboGears 1.1 or 2.0. Plain SQLAlchemy will be, and I think thats the right choice. Elixir will of course be supported, since its basically just SQLAlchemy under the hood, and I'll likely provide some templates or docs on the Elixir wiki for using Elixir in Pylons, TurboGears 2.0, etc. As one of the Elixir authors, I can gladly admit that Elixir won't always be the right choice for every project out there, and that we currently have some warts, especially when it comes to documentation. Elixir will continue to get better, but its not designed to solve every single case and design decision like plain SQLAlchemy is. I also suspect that a large number of users will elect to utilize Elixir, even though it isn't going to be the default, since it will be a good choice for a large number of projects that are comfortable with Elixir's limitations. Thanks for the feedback! I'd love it if we had more smart folks like yourself contributing to the documentation for elixir via the wiki we have set up, as it will help us improve the weakest part of our project! -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
