AltME groups: search

nope. i corrected that and still the same error.


i have data stored in json. i use json.r to convert to rebol objects. 
i want to create a query layer on top of this - which is why the 
expression builder...
the fact1 is an attr of the data object. these can be nested.
how best can i build the expression to retrieve the value i want?

Chris or Graham, do you know if %json.r on json.org needs to change? 
That is, does it do the right thing given whatever scenario it is 
that required altjson to change?

I stopped using json.r because it didn't do something for me ... 
can't recall what it was now :(

I think I had an escaping issue with json.r last time I used it. 
But as that was in 2008, so I guess this has been fixed, since.

I used json.r.
New to json....
	I'm going to want an json object right?

If a query gives me a rebol block of blocks and I send it through 
json.r I don't get a json object.

Should I work on converting the query to a rebol object first?

Hello, about JSON.r, the one on rebol.org is old, here is the latest 
http://www.json.org/json.r


but working with the flickr api I found hopefully a bug, here is 
the patch:

--- http://www.json.org/json.r
+++ (clipboard)
@@ -188,7 +188,7 @@
     ]
     ex-chars: charset {\"}
     chars: complement ex-chars
-    escaped: charset {"\>bfnrt}

+    escaped: charset {"\>bfnrt/}	;!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!added 
"/" otherwise this returned from flikr! give error {{"name":"Taiwan 
Panorama \/ \u53f0\u7063\u5bec\u8996\u91ce"}} 
     escape-table: [
         {\"} "^""
         {\\} "\"
@@ -198,6 +198,7 @@
         {\r} "^M"
         {\n} "^/"
         {\t} "^-"

+        {\/} "/"	;!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!see 
above
     ]
     digits: charset "0123456789"
     hex-c: union digits charset "ABCDEFabcdef"

There must be something, but I don't have anything here that turned 
up, and I don't remember doing one myself. If it helps, you could 
use the JSON converter in %json.r as a starting point.

I know what AJAX is.  ;-)  I've used it many times, I've just never 
set up the server side before.  I am planning on using the json.r 
script from the Library...  I'll just play with it and see what I 
come up with...

Ok, false alarm, no bug in RSP request decoder:

json.r
<%= mold request/content %>
<%= mold as-string request/posted %>
<%= mold as-string request/parsed/content %>
<%= mold request/parsed/arg %>


>> print read/custom http://localhost/json.rsp?test[POST {{"a": 
1, "b": 2}}] none
connecting to: localhost
[{"a": 1, "b": 2} "" test ""]
{{"a": 1, "b": 2}}
{{"a": 1, "b": 2}}
test

The <%= in addition to PROBE was producing a misleading output.

hmm... cheyenne binary and the source works differently w the same 
configfile.
$ cheyenne --version
0.9.20.129
WORKS
latest source doesn't work with the following config:

modules [ internal extapp static action rsp alias ]
globals [ listen [8080]    bind RSP to [ .r ] ]
guan-huat [ debug root-dir %./ alias "/docs" %jsondb/to-json.r ]

im testing w $ curl http://guan-huat:8080/docs/test/1

Translated file: %./jsondb/to-json.r
in case of the source version; so there is no differnece there.

>> do %json.r
Script: "JSON to Rebol converter" (21-Apr-2008)
>> text: {print "hello"}
== {print "hello"}
>> a: rebol-to-json make object! [ t: text ]
== {{"t": "print \\"hello\\""}}
>> json-to-rebol a
** User Error: Invalid JSON string. Near: <end of input>
** Near: json-to-rebol a

Gregg??

I have a fixed version of %json.r. Do you want it Graham? I'll also 
send it to Douglas Crockford to post on JSON.org.


Thanks for catching that. The naive escaping has been there all along.

It's a Core-only script, so the changes to create a version that 
runs under R3 (or even runs under R2 and R3) may be fairly simple.

Ladislav and I have both documented our early efforts to convert 
scripts. If someone does convert JSON.r, that may uncover other useful 
conversion guidelines.
   http://www.rebol.org/art-display-index.r?a=R3

Hmm, I think I have a json.r adapted for R3 somewhere.