Hi Michael, Two points:
1. The best implementation I've seen is included in the NTK plugin. You end up with an object you can navigate. 2. You may want to consider whether you really want to bring JSON into 4D. If you just want to move it from point A to point B, that's doable with a text field. If you want to manipulate it with 4D, it is awkward. Do you really gain anything by bringing it back? Javascript is so much cleaner for working with objects. Better to move what you really need between 4D and the browser and do object manipulation at the browser. Tom D. On Aug 18, 2011, at 12:57 PM, Michael Check wrote: > Hi all > > Wondering what the current consensus is for the most effective way to > get json data into 4D, via A4D. A4D json lib is a great one way lib, > but we need to send data back and forth between both Rails apps and > Ext. > > We don't have a need for complex nesting structures, but a basic 1 > level nesting would be nice. > > I know Steve Alex had some A4D scripts, and Pelican Engineering has a > JSON component that I was thinking about using to build an A4D lib (I > don't know if the lib is really necessary). > > But perhaps I am missing something? Any experience with other methods? > > Thanks, > > Michael Check > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev > Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ > _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
