This is very good news for me. TG2 is looking forwarded to a Rule Dispatch free future, and it looks like there's a race between ToscaWidgets and TurboJson to get a RD free release out first.
I'd love to do a 1.9.7beta1 release of TurboGears this week (after this weekend's sprint) and it would be super awesome if we could use the new TurboJson and avoid the need to manage the RD dependency ;) --mark Ramm On Sat, May 31, 2008 at 7:19 AM, Christoph Zwerschke <[EMAIL PROTECTED]> wrote: > > I'm currently working on tickets 1480, 1619 and 1842 (content type and > encoding for TurboJson). > > Though simplejson has some interesting options such as "ensure_ascii" > and "encoding" (which sets the input encoding), TurboJson so far used > only the default otions. > > I made these configurable in r4629 now. To make this work, the options > must still be added to turbogears.view.base.load_engines. I'd like to > get some feedback before doing this: > > * Do we want to make TurboJson configurable in TG 1.0 as well? > * All options will get the same name as in simplejson, only prefixed > with "json.". > * Exception: "json.assume_encoding" instead of "encoding", similar to > the Kid options, since "encoding" usually means the output encoding? > * Default values for the options the same as in simplejson? > * Exception: ensure_ascii=False instead of True, this will make > non-enlgish json ouput much smaller and better readable? > > -- Christoph > > > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
