On Tue, Jul 25, 2017 at 4:54 PM, David Adams via 4D_Tech < [email protected]> wrote:
> Hmmm. Well, 4D's tools for manipulating JSON are sub-standard, if your goal > is to parse/produce JSON freely. In this respect, the XML tools (external > libraries built into 4D) are far more standard and comprehensive. > I hear you say that a lot but I don't agree. For me they have been quite adequate. I haven't had any issue parsing or producing JSON from c-objects or back again. Having said that it seems I'm not using c-objects is some of the esoteric ways others appear to be. For me they have opened up great ranges of possibilities and made interacting with web apps much easier and faster. And now that I have a fuller grasp of exactly how they are referenced I see even more potential. So, a tick on the interesting new features but no tick on basic JSON > support. For that, you need NTK. > Well one thing you can't currently do with NTK is update a single key in a nested object. I discovered this while trying to replicate the commands from Cannon's component in a v13 db using NTK. I'm using NTK for json quite a lot in that database. I do like the way I can access array objects using NTK. And being able to add items directly to an array without having to un-pack it from the object is nice. But on the whole I find 4D's c-objects easier to deal with on the fly, as it were. In another project where I'm using NTK for HTTP comms for example. What can you only do with NTK you can not do with 4D c-objects? -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
