Thank you for correcting me. I was merely looking into the example provided,
and indeed proposed a simplified solution. And further I was ignoring that as
any of the "standard" ways of representing data expand, there won't be a
generalized way of sorting those out (for example vCARDS). And I d
On 15 May 2014, at 8:47 pm, Pyyhtiä Christer wrote:
> Just set itemDelimiter to "}” to extract the JSON elements, strip "{"
> -characters from those, look what you need to use as the next itemDelimiter
> and do it again. Then move to array.
>
> It probably takes less that 10 lines of code.
Th
It is very easy with pure LiveCode.
Just set itemDelimiter to "}” to extract the JSON elements, strip "{"
-characters from those, look what you need to use as the next itemDelimiter and
do it again. Then move to array.
It probably takes less that 10 lines of code.
This is the way I have done i
On 15 May 2014, at 12:53 pm, Rodney Green wrote:
> [...] I can't figure out how to get this ready to be converted to an array. I
> have not yet installed any plugins or external files, so I was trying to do
> this on my own.
In order to 'convert' your json data to a LiveCode array, you will have
Sorry - please bear with me. When I said noob, I meant it. I was wanting to
know how my parsed json should look. I already have the json coming in and
I have learned the basics of parsing. My json looks like this:
{"results":[{"definition":"before - in
front","word":"ante","createdAt":"2014-03-24T
Igor-
Wednesday, May 14, 2014, 4:52:55 PM, you wrote:
> A while ago I wrote a JSON parser in LiveCode. The *very heavily
> commented* code can be found here:
> https://github.com/luxlogica/easyjson
> I hope this may be of help!
Please do notice, though, that you've had a pull request from me
w
Igor de Oliveira Couto wrote:
> I released the code quite specifically in the public domain - there
> is an accompanying 'License' declaration, with a disclaimer.
Thanks for that, and for sharing the code. Very valuable for all of us.
> Apart from believing that providing an explicit license i
On 15 May 2014, at 10:39 am, Alejandro Tejada wrote:
> The License file of easyjson reads:
License
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute this
software, either in source code form or as
On 15 May 2014, at 10:32 am, Richard Gaskin wrote:
> Igor de Oliveira Couto wrote:
>
>> A while ago I wrote a JSON parser in LiveCode. The *very heavily commented*
>> code can be found here:
>>
>> https://github.com/luxlogica/easyjson
>
> Thanks for that, Igor.
>
> I'd check it myself but it
e LiveCode community, by
sending a pull request here on GitHub!
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/noob-array-question-tp4679497p4679510.html
Sent from the Revolution - User mailing list archive at Nabble.com.
_
Igor de Oliveira Couto wrote:
A while ago I wrote a JSON parser in LiveCode. The *very heavily commented*
code can be found here:
https://github.com/luxlogica/easyjson
Thanks for that, Igor.
I'd check it myself but it seems I can't reach GitHub today (I can ping
it, but all web URLs just t
On 15 May 2014, at 7:32 am, Rodney Green wrote:
> [...] In attempting to parse some json data I can't find what the final output
> should look like. [...]
You can view the official JSON specs - very easy to understand - here:
http://json.org
As you probably already know, JSON documents are pla
Hi All,
In attempting to parse some json data I can't find what the final output
should look like. Should it be something like this?:
[{key:value,key:value,key:value},{key:value,key:value,key:value}]
Thanks in advance
___
use-livecode mailing list
use-
13 matches
Mail list logo
