On Sat, Feb 14, 2009 at 11:19 AM, Jorge Vargas jorge.var...@gmail.com wrote:
On Sat, Feb 14, 2009 at 8:45 AM, Mark Ramm mark.mchristen...@gmail.com
wrote:
On Fri, Feb 13, 2009 at 11:35 PM, percious ch...@percious.com wrote:
Personally I think we should default to SimpleJson, and then if
On Fri, Feb 13, 2009 at 11:35 PM, percious ch...@percious.com wrote:
Personally I think we should default to SimpleJson, and then if the
user has TurboJson installed, we should
default to that. It should be simple enough to put a switch in
config.
try:
import turbojson
except:
On Sat, Feb 14, 2009 at 8:45 AM, Mark Ramm mark.mchristen...@gmail.com wrote:
On Fri, Feb 13, 2009 at 11:35 PM, percious ch...@percious.com wrote:
Personally I think we should default to SimpleJson, and then if the
user has TurboJson installed, we should
default to that. It should be
On Fri, Feb 13, 2009 at 4:10 PM, jorge.vargas jorge.var...@gmail.com wrote:
Hello,
Today while working on the updated dependencies ticket I found out something.
Currently we are using the buffet legacy plugin for json, you may know
it as TurboJson,
TurboJson, was ones used by TW/TGWidgets
On Fri, Feb 13, 2009 at 9:54 PM, jorge.vargas jorge.var...@gmail.com wrote:
On Fri, Feb 13, 2009 at 4:10 PM, jorge.vargas jorge.var...@gmail.com wrote:
Hello,
Today while working on the updated dependencies ticket I found out something.
1- should we create a render_json function in
maybe we should just keep it like it for the first release and aim to
eliminate the buffet interface afterwards. (keeping tj or removing it
in the process as we choose)
Yea, this is what we should do. Anything else will break too many
people's TG2 apps.
--Mark
Personally I think we should default to SimpleJson, and then if the
user has TurboJson installed, we should
default to that. It should be simple enough to put a switch in
config.
try:
import turbojson
except:
import simplejson
or such.
I feel that for simple jsonifications
