By the way guys, I am listening. I just happened to be writing documentation for DBSprockets when the messages popped up! http://code.google.com/p/dbsprockets/wiki/DevelopmentEnvironment
Anyway. > - Chris P is commited to ToscaWidgets for DBSprockets. It seems like > this is the case, Chris can you weigh in on this? Chris's dedication and > approach to DBSM ( ha ha! new nickname! oh I kill me ... ) is very > impressive and if he is committed to TW then I am more comfortable > committing to it hoping it won't be a collapsed barn I am committed to using the *best* widget engine to create DBSprockets. DBSprockets doesn't care which engine to use. (I separated ValidatorSelector and WidgeSelector for a reason) I think Toscawidgets, and the magic it contains is THE BEST solution available. And I have NO problem with people writing dox for me. Come and join my team Ian. > - we get more developers with full access to tw repository so that if we > find issues people like Chris and Florent can just fix 'em as they see > fit ( maybe this is already the case? I dunno, same issue as Mark's ) I'm all ears if people have fixes.... - some weird monkey patching issues need to be either smoothed out, or eradicated ( ie, the voodoo of adding FilteringSchema if on TG, huh? ) WOW, I agree with this one 100% I had to put this particular hack in my code for TG1 DBmechanic. It was a good thing I knew about it from back when I was writing TW all the time. The good news is that that particular voodoo is not needed in TG2/Pylons because TW is wsgi complient. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
