2013/3/5 Peter Stuge <pe...@stuge.se> > Javier Domingo wrote: > > I think that going django would mean a complete remake of trac, but > > would simplify a lot trac deployment (in for example appengine) > > Stop the madness. > > Trac has existed for 10+ years. You're a student who doesn't really > know Python (you said). > I don't know which is the level you can say that really know a language.
It makes no sense whatsoever for you to rewrite Trac using hipster > frameworks! > > You would be completely alone working on that, it would take an > enormous amount of time because you have to learn so many things, > and in the end it's not likely going to be any better than what is > already there. > > Please just learn to develop the existing Trac instead, and work > together with existing community. You will be able to accomplish > much more with much less effort. > > I'll echo Ethan's question: Have you already looked into my > suggestion to extend the existing permission system? > I did, but I would still need to hit against the database, and some other things. > I think that would be a pretty simple solution to your problem (I'd > estimate one week if you can read and write Python) and I imagine > that your code would inspire other cool new ideas for how Trac > permissions can be used. Its not only about my problem, my idea is to extend trac to be easier to extend, or even easier to hack the core without having to understand that hard how things in a database are managed. In addition to this, I have asked in #django about any way to implement the component manager, which I think its the greatest thing I have seen in last months (appart from the way to authz), and I have found a guy very interested on your component manager, and talking to him, he has given me an idea about how to create it. ------------------- Well, TBH I haven't done or even used something like that before, but I think it'd be possibe to create an app and then subclass (child module) the rest of the project's apps, so the modular app would handle all the "plugins". ------------------- I have found the django-wiki app[1], which has plugins in it, with something very similar to what he suggested. I am going to try it with my team, as I think its a very great idea, and will have a great profit in future developing if I finally succeed. If I finally work out some way to have all trac, with its key features ported, and succeed on it, I will come back to report. Take into account that if I use django, I would be able to use all the facilities that framework gives, referring specifically to DAL, urls, templating, etc. Javier Domingo [1] django-wiki: https://github.com/benjaoming/django-wiki -- 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.
