> > > Be specific. What is the problem? > > I hope that this will be answered, so that everyone can understand > the concrete issues.
I forgot to answer ^^!, the problem is that if I want to reimplement my own ticketing system, using the existing one as a base, I will have to hit against a lot of code that is hitting against the db, another part will have mixed authz and workflow. Just using a DAL would simplify a lot the model.py (in tickets i.e.) 's code, but I was proposing going one step ahead and converting trac in a django app. I just wanted to know whether if this had been recently discussed, and which ideas trac's devs had. This would allow someone to integrate the tracker with much a lot of webapps, which I think its great. I love doing such experiments. -- 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.
