About crank I'm fine using it, it might be a good improvement, I just want to ensure that it won't cause issues to TurboGears as we are practically outsource the core part of the framework. It should never break compatibility with past TG and TG has to be a first citizen for crank. I can off course give help at maintaining it, not an issue for me. But I would like to hear others ideas about outsourcing one of the core parts of the framework.
On Thu, Dec 15, 2011 at 6:41 PM, percious <ch...@percious.com> wrote: > Hi all, > > Sorry I've been away for so long. Needless to say things have been crazy in > my life and I was unable to attend to TG in the last few months. I very > much appreciate the work that Michael and Amol have done in my stead. It is > especially encouraging to see that 4 releases have found their way out since > I have been busy. > > I have done some work in the last year that I would like considered in the > next minor release (2.2). I had worked last March to extract the dispatch > mechanism from TurboGears and put it on it's own footing. The name of this > project is Crank. This accomplishes a few goals: > > 1) By eliminating the Pylons/TG framework from the dispatch, testing was > made easier. Crank has 100% code coverage. > > 2) Crank can be used for URL dispatch outside of TurboGears. I wanted this > capability to be able to use it within TW2 without writing a new dispatcher, > and in another WSGI-only CRUD (admin) system I have been developing. Also, > I had initially been in cooperation with Alice Bevan-McGregor of web.core to > help provide an admin system for that project. By making the dispatch work > on it's own, I am able to maintain one codebase for all of these purposes, > which puts a lot less strain on me as the one who has historically done most > of the maintenance in this area of TG. > > Amol has agreed to participate in maintenance of Crank along side me. That > way we don't have a single-source developer. I have already done the work > to integrate Crank into TG. Amol finished up that work when it was merged > into the current Git repos on sf.net. The current repo for Crank is > at https://bitbucket.org/percious/crank/ but I am okay with it moving to the > main TG repo, or moved to github as it's own project. Also, I have kept > up-to-date with dispatch changes that affect some of our most important > constituents and have integrated them into Crank's codebase. > > I am writing this message to garner support and feedback from the community > before the inclusion of crank as a dispatch mechanism within TurboGears. > > cheers. > -chris > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/turbogears-trunk/-/YXqXzHnd3P0J. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
