Re: [WebDNA] WebDNA development
This WebDNA talk-list message is from 2017
It keeps the original formatting.
numero = 113444
interpreted = N
texte = 1039 Hi Tom! I suppose you could try something like this: first, create the = table, something like this should work fine [JSONstore table=3DtabJSONPARSE] JSONobject [/JSONstore] you do not need to know the exact structure of the incoming JSON = response, WebDNA will do it for you (I have personally not tested with a = table, but it does with a db) Then, you can use [convertwords]: [convertwords table=3DtabJSONPARSE]error:type and = error:message[/convertwords] This should work=E2=80=A6 - chris > On Mar 4, 2017, at 16:59, Tom Duke
wrote: >=20 > Chris, >=20 > Hi - I'm using [jsonstore] and it's great to have it. It's not a = flexible as [xmlparse] though. >=20 > So if I want to pull out the error message from a Stripe.com json = response I have to do the following: >=20 > [table = name=3DtabJSONPARSE&fields=3DtID,error:type,error:message][/table][!] > [/!][jsonstore = table=3DtabJSONPARSE][varSTRIPERESPONSE][/jsonstore][!] > [/!][search = table=3DtabJSONPARSE&netIDdatarq=3Dfind_all][founditems][!] > [/!][text]error:type=3D[error:type][/text][!] > = [/!][text]error:message=3D[error:message][/text][!] > [/!][/founditems][/search] >=20 > Only then can I access the variable [error:message]. I also need to = know the exact structure of the incoming JSON response so I can set up = the table correctly. >=20 > If we had similar functionality to [xmlparse] then I could do = something like: >=20 > [jsonparse = var=3Djson_var1][varSTRIPERESPONSE][/jsonparse] > [jsonnode = ref=3Djson_var1&path=3Dnamed:error:message][value][/jsonnode] >=20 > It would also be great to be able to traverse the JSON response, = particularly if we are not sure about the structure of the incoming JSON >=20 > [jsonnodes ref=3Djson_var1] > [name]=3D[value] > [/jsonnodes] >=20 >=20 > - Tom >=20 >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Digital Revolutionaries > 1st Floor, Castleriver House > 14-15 Parliament Street > Temple Bar,Dublin 2 > Ireland > ---------------------------------------------- > [t]: + 353 1 4403907 > [e]: > [w]: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > On 3 March 2017 at 15:27, wrote: > Hi Tom! WebDNA already includes a JSON parser, that takes any JSON = Object, parse and store it: it will automatically create the database if = it does not exist, create the fields and populate it. >=20 > http://www.webdna.us/page.dna?numero=3D307 >=20 > =46rom this, it is easy to use the data by treating the database (or = table) like any other WebDNA database. >=20 > best regards, >=20 > - chris >=20 >=20 >=20 > > On Mar 3, 2017, at 15:57, Tom Duke wrote: > > > > Chris, > > > > Hi - great to hear that you are working on this. > > > > The features that I would love to see are: > > > > > > [json_encode]{data}[/json_encode] > > > > It would operate the same as the matching PHP function: = http://www.php.net/manual/en/function.json-encode.php > > > > So the data would be a WebDNA array and/or perhaps name/value pairs = separated by line returns. Nested JSON would require some thought, some = ideas here: = http://stackoverflow.com/questions/15810257/create-nested-json-object-in-p= hp > > > > > > [json_parse]{data}[/json_parse] > > > > It would operate in a similar way to [xmlparse] allowing us to = traverse and extract the JSON data by node. Also similar to the PHP = json_decode function: = http://www.php.net/manual/en/function.json-decode.php > > > > > > > > - Tom > > > > > > > > > > > > > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Digital Revolutionaries > > 1st Floor, Castleriver House > > 14-15 Parliament Street > > Temple Bar,Dublin 2 > > Ireland > > ---------------------------------------------- > > [t]: + 353 1 4403907 > > [e]: > > [w]: > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > On 27 February 2017 at 14:24, = wrote: > > Hello, > > > > we are interested to expand and develop the JSON capabilities and = compatibility of WebDNA, particularly treating JSON-formatted returns = from javascript as well as submitting JSON-formatted info to external = programs and applications. > > > > If you have any related ideas, we are listening! :-) > > > > - chris--------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > > > --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
1039 Hi Tom! I suppose you could try something like this: first, create the = table, something like this should work fine [JSONstore table=3DtabJSONPARSE] JSONobject [/JSONstore] you do not need to know the exact structure of the incoming JSON = response, WebDNA will do it for you (I have personally not tested with a = table, but it does with a db) Then, you can use [convertwords]: [convertwords table=3DtabJSONPARSE]error:type and = error:message[/convertwords] This should work=E2=80=A6 - chris > On Mar 4, 2017, at 16:59, Tom Duke wrote: >=20 > Chris, >=20 > Hi - I'm using [JSONstore] and it's great to have it. It's not a = flexible as [xmlparse] though. >=20 > So if I want to pull out the error message from a Stripe.com json = response I have to do the following: >=20 > [table = name=3DtabJSONPARSE&fields=3DtID,error:type,error:message][/table][!] > [/!][jsonstore = table=3DtabJSONPARSE][varSTRIPERESPONSE][/jsonstore][!] > [/!][search = table=3DtabJSONPARSE&netIDdatarq=3Dfind_all][founditems][!] > [/!][text]error:type=3D[error:type][/text][!] > = [/!][text]error:message=3D[error:message][/text][!] > [/!][/founditems][/search] >=20 > Only then can I access the variable [error:message]. I also need to = know the exact structure of the incoming JSON response so I can set up = the table correctly. >=20 > If we had similar functionality to [xmlparse] then I could do = something like: >=20 > [jsonparse = var=3Djson_var1][varSTRIPERESPONSE][/jsonparse] > [jsonnode = ref=3Djson_var1&path=3Dnamed:error:message][value][/jsonnode] >=20 > It would also be great to be able to traverse the JSON response, = particularly if we are not sure about the structure of the incoming JSON >=20 > [jsonnodes ref=3Djson_var1] > [name]=3D[value] > [/jsonnodes] >=20 >=20 > - Tom >=20 >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Digital Revolutionaries > 1st Floor, Castleriver House > 14-15 Parliament Street > Temple Bar,Dublin 2 > Ireland > ---------------------------------------------- > [t]: + 353 1 4403907 > [e]: > [w]: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > On 3 March 2017 at 15:27, wrote: > Hi Tom! WebDNA already includes a JSON parser, that takes any JSON = Object, parse and store it: it will automatically create the database if = it does not exist, create the fields and populate it. >=20 > http://www.webdna.us/page.dna?numero=3D307 >=20 > =46rom this, it is easy to use the data by treating the database (or = table) like any other WebDNA database. >=20 > best regards, >=20 > - chris >=20 >=20 >=20 > > On Mar 3, 2017, at 15:57, Tom Duke wrote: > > > > Chris, > > > > Hi - great to hear that you are working on this. > > > > The features that I would love to see are: > > > > > > [json_encode]{data}[/json_encode] > > > > It would operate the same as the matching PHP function: = http://www.php.net/manual/en/function.json-encode.php > > > > So the data would be a WebDNA array and/or perhaps name/value pairs = separated by line returns. Nested JSON would require some thought, some = ideas here: = http://stackoverflow.com/questions/15810257/create-nested-json-object-in-p= hp > > > > > > [json_parse]{data}[/json_parse] > > > > It would operate in a similar way to [xmlparse] allowing us to = traverse and extract the JSON data by node. Also similar to the PHP = json_decode function: = http://www.php.net/manual/en/function.json-decode.php > > > > > > > > - Tom > > > > > > > > > > > > > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Digital Revolutionaries > > 1st Floor, Castleriver House > > 14-15 Parliament Street > > Temple Bar,Dublin 2 > > Ireland > > ---------------------------------------------- > > [t]: + 353 1 4403907 > > [e]: > > [w]: > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > On 27 February 2017 at 14:24, = wrote: > > Hello, > > > > we are interested to expand and develop the JSON capabilities and = compatibility of WebDNA, particularly treating JSON-formatted returns = from javascript as well as submitting JSON-formatted info to external = programs and applications. > > > > If you have any related ideas, we are listening! :-) > > > > - chris--------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > > > --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Searching multiple databases (1998)
Math (1997)
Reversing [ipaddress] normalization (1998)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
nesting limits? (1998)
Webstar v (2001)
OT: Typhoon (1998)
garbage on page (2000)
Online reference (1997)
Running 2 two WebCatalog.acgi's (1996)
Bug or syntax error on my part? (1997)
Problems passing [SKU] with $Replace in 2.0 (1997)
Catalog page question (1999)
writing db to disk (1997)
cookies ok ??? (2006)
Building Calendars (1997)
Followup question re: checksum for credit cards? (1997)
search criteria (2000)
Database Options (1997)
Mac Vs WindowsNT (1997)