On Tuesday, March 5, 2013 12:35:33 PM UTC+2, Javier Domingo wrote: > > > I am not an expert python developer, but I usually work out my ideas. > > I am still trying to imagine how would it be to maintain the plugins > interface with a django framework. I have thought of making it a > django app, but I dropped that idea because I like the way you have to > manage plugins and functionalities. > > I am thinking more on something like this: > http://stackoverflow.com/questions/579511/using-only-the-db-part-of-django > > Mmmmkay. Well the thing is, for general purpose apps, Trac also has other issues besides just not having a high-level DAL. Even if you get it working on top of just another db layer, that's all good, but it will still leave a laaaaarge amount of manual work to be done for any general app feature.
There are issues with the existing schema for example (search GenericTrac) that should be improved as well. IMHO a django app (or Pyramid app? I don't know its structure, but I do know players are using it) would be a much more thorough and future proof solution than just trying to rotate a few foundation components underneath the highly specialized app implementation that Trac is today. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
