[qooxdoo-devel] json rpc over websocket javascript client to use in qooxdoo

Hello, I've a json rpc server with websocket transport only. Does any one knows about a javascript library that implement json rpc over websocket that I can use? Regards, -- View this message in context: http://qooxdoo.678.n2.nabble.com/json-rpc-over-websocket-javascript-client-to-use-in-qooxdo

Re: [qooxdoo-devel] JSON - getItem

geBubble|bubble|903"], 'idBubble-439-0':null, 'idBubble-202-0':["changeBubble|bubble|908"]}}], length:1, $$user_autoDisposeItems:true, __cK:{'idBubble-177-0':["changeBubble|bubble|904"]}}, __cK:{'idBubble-202-0':["changeBubble

Re: [qooxdoo-devel] JSON - getItem

ble|bubble|902"]}}, __cK:{'idBubble-433-0':["changeBubble|bubble|903"], 'idBubble-439-0':null, 'idBubble-202-0':["changeBubble|bubble|908"]}}], length:1, $$user_autoDisposeItems:true, __cK:{'idBubble-177-0':["changeBubble|bubb

Re: [qooxdoo-devel] JSON - getItem

Hello Stefan, > first of all congratulation to QooxDoo 3.0 - great job ! Thanks. :) > I'm using a JSON file with the following structure. > > { >"name": "Test Suites", >"children": [ >{ >"name": "ContiTeves", >"children": [ >{ >

[qooxdoo-devel] JSON - getItem

Hi, first of all congratulation to QooxDoo 3.0 - great job ! I'm using a JSON file with the following structure. { "name": "Test Suites", "children": [ { "name": "ContiTeves", "children": [ { "name": "ESC10",

[qooxdoo-devel] JSON Serialization and deserialization

Hi, I use qx.data.marshal.Json for deserialization and qx.util.Serializer.toJson for serialization What Is the best way for working with Date By default my server serialize to long value format : Ex : 1365037218979 but I can force it to use StdDateFormat : Ex : "2013-04-04T01:00:18.979+00

Re: [qooxdoo-devel] JSON call

Try it and you'll see :) It works of course. Only if browser would disallow it for some reason ti wouldn't work. You need to use Xhr thou.. Mikee On Fri, Jan 25, 2013 at 5:38 PM, Marc-André Dubois wrote: > Hi, > > ** ** > > I need to know if qooxdoo support json call for GET, POST, PUT and

[qooxdoo-devel] JSON call

Hi, I need to know if qooxdoo support json call for GET, POST, PUT and DELETE I know it’s working for GET and POST but for PUT and DELETE? Thank you Marc-André Dubois [email protected] Programmeur-Analyste Description : Lanauco_logo_couleur_long Signature 1.877.881.5151 p.261 (sans

Re: [qooxdoo-devel] json data into a table. I'm close....

On Thu, Dec 29, 2011 at 15:52, Scott Chapman wrote: > >> That worked. Big thanks! > Great. > I'm not clear on the use of "delegates". Can I make a delegate do this as > in : > > qx.data.store.Json(null, delegate = foo()); > > ... and have foo do this? > I'm no expert on the data store functi

Re: [qooxdoo-devel] json data into a table. I'm close....

On Thu, Dec 29, 2011 at 12:32 PM, Derrell Lipman < [email protected]> wrote: > > to the following, it should probably work: > > jsonFetcher.addListener( > "loaded", > function(e) > { > var tData = e.getData(); > var nativeData = [ ]; > tData.toArray().forEach( >

Re: [qooxdoo-devel] json data into a table. I'm close....

On Thu, Dec 29, 2011 at 14:05, Scott Chapman wrote: > Top part of debug output. Even at 2 levels, it's a huge amount of output. > How much of it do you want? > > 019940 qx.dev.Debug: event data Array, length=7: > 0: Object > $$hash: 929

Re: [qooxdoo-devel] json data into a table. I'm close....

This is from my other email address. > Ok, so apparently the internal components are qx.data.Arrays as well. > > Must you use the new Rest transport to retrieve your data? If you can use > the old transports, they won't do any of this qx.data.Array conversion > stuff... > > Let's see what you rea

Re: [qooxdoo-devel] json data into a table. I'm close....

On Thu, Dec 29, 2011 at 13:39, Derrell Lipman < [email protected]> wrote: > > qx.dev.Debug.debugObject(e.getData().toArray()); > Hmmm... That may cause too much output. Replace it with this, which will limit to 3 levels of recursion: qx.dev.Debug.debugObject(e.getData().toArray

Re: [qooxdoo-devel] json data into a table. I'm close....

On Thu, Dec 29, 2011 at 13:24, Scott Chapman wrote: > Here's my current code: > > > var __tableModel = new qx.ui.table.model.Simple(); > __tableModel.setColumns([ "Date", "DelayAvg", "First", "Last" ]); > > var url = "/avg_checkin_times/" + label; > var jsonFetcher = new q

Re: [qooxdoo-devel] json data into a table. I'm close....

-Derrell Lipman wrote: - The problem is that you're mixing the nice new data binding stuff with the antique Table widget. The Table widget is wonderful, and there's not yet a data binding-version of it, so you need to do a bit of fiddling to get the two to work together. Data bindi

Re: [qooxdoo-devel] json data into a table. I'm close....

On Thu, Dec 29, 2011 at 12:42, Scott Chapman wrote: > Thanks for the help. I did: > > console.log(e.getData()) > then: > __tableModel.setData(e.getData()); > > The log shows "Please use toArray() to see the content" > > The setData gave me an error in the console.log: > > this.__rowArr[rowIn

Re: [qooxdoo-devel] json data into a table. I'm close....

-Derrell Lipman wrote: -   var __tableModel = new qx.ui.table.model.Simple();   __tableModel.setColumns([ "Date", "DelayAvg", "First", "Last" ]);   var url = "/avg_checkin_times/" + label;   var jsonFetcher = new qx.data.store.Json(null);   jsonFetcher.addListener

Re: [qooxdoo-devel] json data into a table. I'm close....

On Wed, Dec 28, 2011 at 16:28, Scott Chapman wrote: > I've got the table showing up but the values are not showing up. I'm > fetching data via json and trying to put it in a table. > > var __tableModel = new qx.ui.table.model.Simple(); > __tableModel.setColumns([ "Date", "DelayAvg",

[qooxdoo-devel] json data into a table. I'm close....

I've got the table showing up but the values are not showing up.  I'm fetching data via json and trying to put it in a table.   var __tableModel = new qx.ui.table.model.Simple();   __tableModel.setColumns([ "Date", "DelayAvg", "First", "Last" ]);   var url = "/avg_checkin_times/" + l

[qooxdoo-devel] JSON tree from tree widget

Hello, I am trying to get all data from tree widget, but now I have no result. I already have qx.ui.tree.Tree widget, got all data from server and widget is now filled with my data. But now I need to do the same in reverse order. And in my current case, I just need JS object (or JSON) of all tree

Re: [qooxdoo-devel] JSON additional parameters and list selection

Hi, the selection from the list returns a array with selected ListItems and the ListItem has property "model" where you can get the instance from the connected item from the sore item. Cheers, Chris Am 16.09.2011 02:35, schrieb ISE: > My questions may be quite strange, I am totally newbie in q

[qooxdoo-devel] JSON additional parameters and list selection

My questions may be quite strange, I am totally newbie in qooxdoo. I have some problems with JSON. So, for example I have JSON with items like user name and user rights in the system. JSON store is used for the list controller, but how to access another data of the JSON that is being connected to

Re: [qooxdoo-devel] JSON-RPC 2.0 Router for .NET

> Gian, what does a JSON-RPC "router" do? In .NET (but also in Java) you have to write a lot of boilerplate code to "route" a JSON-RPC request that comes over HTTP to the corresponding method call. This code is mostly standard, the only part that is custom to the application is how to map from a m

Re: [qooxdoo-devel] JSON-RPC 2.0 Router for .NET

On Thu, Sep 1, 2011 at 11:10, Gian Marco Gherardi < [email protected]> wrote: > I want to let you know that i've developed a JSON-RPC2 router for > .NET. ... > PS: Given that Qx conforms to JSON-RPC 2.0 specs for RPC layer, i > don't consider this thread off-topic. > As a reminder, w

[qooxdoo-devel] JSON-RPC 2.0 Router for .NET

Hi all, I want to let you know that i've developed a JSON-RPC2 router for .NET. AFAIK this is the only JSON-RPC 2.0 router currently available in .NET space. This is an experimental library and is still a work in progress, but can be worth looking for anyone that is trying to integrate Qx with .NE

Re: [qooxdoo-devel] json marshaller in 1.5 and this.tr('string')

Hello, it's a bug as stated by Sak http://bugzilla.qooxdoo.org/show_bug.cgi?id=5455 Regards oetiker wrote: > > Hi Mustafa, > > Today Mustafa Sak wrote: > >> Hi >> >> Its a Bug Not a Sony ;) >> >> Please try this.tr("SSD").toString() > > this would work, but then the strings are not runtime

Re: [qooxdoo-devel] JSON Data into table

Okay fixed!!! The problem was the html and body tag of the php document! -- View this message in context: http://qooxdoo.678.n2.nabble.com/JSON-Data-into-table-tp6528848p6529024.html Sent from the qooxdoo mailing list archive at Nabble.com. -

[qooxdoo-devel] JSON Data into table

Hi all, I tried to put some data into a table. I fetch the data with php to a json string: This is now the output: [{"praeparat":"test","menge":"1","einheit":"l"}] Now I try to parse this code, but I get follow error: qx.io.remote.RequestQueue[244]: Request qx.io.remote.Request[243] handler

Re: [qooxdoo-devel] Json marshaller: numeric keys

Hi Adrian, Thanks for your answer. I filed a bug report: #5223. http://bugzilla.qooxdoo.org/show_bug.cgi?id=5223 Regards, Marc On 06/08/2011 03:41 PM, Adrian Olaru wrote: > IMO is a bug. As long as is valid JSON I don't see why this shouldn't work. > Nevertheless, you should open a bug with thi

Re: [qooxdoo-devel] Json marshaller: numeric keys

IMO is a bug. As long as is valid JSON I don't see why this shouldn't work. Nevertheless, you should open a bug with this... Cheers, Adrian -- View this message in context: http://qooxdoo.678.n2.nabble.com/Json-marshaller-numeric-keys-tp6453283p6453659.html Sent from the qooxdoo mailing list arc

[qooxdoo-devel] Json marshaller: numeric keys

Hi all, The following line will throw an assertion error: "The key '0' is not a valid JavaScript identifier." qx.data.marshal.Json.createModel({"0" : "test"}); I can see why this error is thrown, but I think the marshaller should be able to handle this special case, especially since the fo

Re: [qooxdoo-devel] JSON to Simple

Hi, did Ana Rita's answer of our second question (Object of qx.util.Json.parse) also solve the issue you described in this thread? Am 02.06.2011 um 13:24 schrieb comm1x: > Hi all > I tried to search for the decision of the problem at a forum, but and > haven't found. I write the container which

[qooxdoo-devel] JSON to Simple

Hi all I tried to search for the decision of the problem at a forum, but and haven't found. I write the container which accepts JSON-data and set them in the table. Application.js: // var scenario = ([ {id: 1, name: "fs", after: [

Re: [qooxdoo-devel] json store

As far as I know, there is no json-rpc store yet. It is not difficult to implement one, though. I have one implementation in the VirtualData contrib: http://qooxdoo-contrib.svn.sf.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/VirtualData/trunk/source/class/virtualdata/store/JsonRpc.js?view=mark

[qooxdoo-devel] json store

I am trying to using a json store. It seems like it just takes a URL. How do a specify a specific service method on the json server? I've been doing it this way: rpc.callSync("getStats"); but now I want to use the data binding functionality now the qx.data.store.Json object just takes a url

Re: [qooxdoo-devel] JSON Date format

Thanks. :) Am 07.03.2011 um 22:52 schrieb sub: > Hi Martin, > > Done!! -> Bug 4746 > > Cheers > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/JSON-Date-format-tp6047708p6099208.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ---

Re: [qooxdoo-devel] JSON Date format

Hi Martin, Done!! -> Bug 4746 Cheers -- View this message in context: http://qooxdoo.678.n2.nabble.com/JSON-Date-format-tp6047708p6099208.html Sent from the qooxdoo mailing list archive at Nabble.com. -- What You Don'

Re: [qooxdoo-devel] JSON Date format

Hey, this sounds like its worth an enhancement report in our bugzilla. In the mean time, if you are using a store, you can easily use the delegate and set the "manipulateData" method which could parse all data and convert the ISO strings to date objects. Best, Martin Am 21.02.2011 um 23:23 schr

Re: [qooxdoo-devel] JSON Date format

I misunderstood getCurrentTimestamp. It requires the return of the object, not Date. Thanks for the explanation, I will focus on native JSON ISO format -- With best regards, Michael Filonenko. -- Index, Search & Analyz

Re: [qooxdoo-devel] JSON Date format

Hi Martin, The current system supports serializing QX objects to a JSON string notation using the ISO standard for dates (qx.util.Json). But serializing in the opposite direction - a JSON string notation into QX objects (qx.data.marshal.Json) does not attempt to process string literals in the ISO

Re: [qooxdoo-devel] JSON Date format

Hey, > First of all thanks for really great work. Earlier I used Qt with > QtScript, and I think I just re-invented the Web browser. Thanks for the great feedback. :) > Could you tell me what Date format for JSON is used now? > I download RpcExample and found something like this: > > result: {

[qooxdoo-devel] JSON Date format

Hi to all. First of all thanks for really great work. Earlier I used Qt with QtScript, and I think I just re-invented the Web browser. Could you tell me what Date format for JSON is used now? I download RpcExample and found something like this: result: { now: "MAYBE ISO" jsonDate: "ISO,

Re: [qooxdoo-devel] json data into table

Ok, I got it... var test = new qx.data.Array; test = qx.lang.Json.parse(data); ...solved my problem for the first. Thank you anyway. ;-) -- View this message in context: http://qooxdoo.678.n2.nabble.com/json-data-into-table-tp6036150p6039522.html Sent from the qooxdoo mailing list archive at

Re: [qooxdoo-devel] json data into table

Hi, I changed my sourcecode now, but the result is, that the first column of the table is filled with single chars. These are the chars of my string. Can you tell me how to write this string from the request to an array to be able to extract the single values from the string? Example: [1999,34.4

Re: [qooxdoo-devel] json data into table

Hi, - make your backend return just data, not the column headers - then use tableModel.setData(data) - read the API at http://demo.qooxdoo.org/1.3.x/apiviewer/#qx.ui.table.model.Simple for info on accessing the table rows/cells, etc Cheers, Fritz On Thu, 17 Feb 2011, chrjab wrote: > > Hi

[qooxdoo-devel] json data into table

Hi there, I'm a qooxdoo newbie and need some help. I try to fill a table with json data. This is my sourcecode: var doc = this.getRoot(); var tableModel = new qx.ui.table.model.Simple(); tableModel.setColumns([ "Jahr", "Wert" ]);

Re: [qooxdoo-devel] json-rpc-2

Hey, > wanted to ask how it looks with the expansion of > http://groups.google.com/group/json-rpc/web/json-rpc-2-0 batch (point 6). > Can one expect the version Qooxdoo it? A roadmap for this? We are currently working on streamlining the io layer. So there is some movement on that but currently n

Re: [qooxdoo-devel] json-rpc-2

Hello Martin, wanted to ask how it looks with the expansion of http://groups.google.com/group/json-rpc/web/json-rpc-2-0 batch (point 6). Can one expect the version Qooxdoo it? A roadmap for this? Thank you, Fahri -- View this message in context: http://qooxdoo.678.n2.nabble.com/json-rpc-2-tp54

Re: [qooxdoo-devel] Json and Table models

Hi aditya console.log(qx.lang.Object.getKeys(test[0])); => ["col1", "col2", "col3"] It's an interesting method you are suggesting to use directly column names from SQL, but if I need to localize/translate the column names ? There's a way to accomplish this ? How i should use this.tr() ? Thank

Re: [qooxdoo-devel] Json and ComboBox serializing problem.

Hey, I openend up a bug report for that issue [1]. If you want to get rid of that workaround, you should add yourself as CC to be up to date when it will be fixed. Thanks for the report and for posting the workaround, Martin [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=4552

Re: [qooxdoo-devel] Json and ComboBox serializing problem.

I've used a workaround because i cannot find the bug. I've wrote this function: objectToJson : function(object) { var keys = qx.lang.Object.getKeys(object); var values = qx.lang.Object.getValues(object); var json = '{';

Re: [qooxdoo-devel] Json and ComboBox serializing problem.

Hi Martin, I've recreated the error in the playground with the code below so you can see the error. I'm looking in the framework code maybe with some luck i'll find what's wrong. I've tested a selectBox and it works fine, it's seems a ComboBox related problem. var doc = this.getRoot(); var form

Re: [qooxdoo-devel] Json and ComboBox serializing problem.

Hey, thanks for the mail. This sounds like a bug to me. Maybe we can find a workaround but that should be definitely fixed in the framework. Do you have a working code example to share? It would be best if you could put it into the playground so can get my hands on. Best, Martin Am 13.01.2011

[qooxdoo-devel] Json and ComboBox serializing problem.

Hi qooxdooers, I'm using the qx.util.serializer.toJson to serialize data of a Form object. I have a problem with the comboBox widget. This is my comboBox widget: var combo = new qx.ui.form.ComboBox(); combo.add(new qx.ui.form.ListItem(this.tr("Kiev"), null, "Kiev")); combo.add(new qx.ui.form.Li

Re: [qooxdoo-devel] Json and Table models

If your json table is big (about >100 items) and you think it is too slow you can use the generator function we have added to bugzilla: http://bugzilla.qooxdoo.org/show_bug.cgi?id=4384 It has helped us by getting slow qooxdoo tables to load faster. Another approach we looked at was to load the

Re: [qooxdoo-devel] Json and Table models

You were right. Thank you Derrell I get the difference now! Thank you very much for your explanation. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Json-and-Table-models-tp5803644p5805361.html Sent from the qooxdoo mailing list archive at Nabble.com. ---

Re: [qooxdoo-devel] Json and Table models

On Sun, Dec 5, 2010 at 09:00, Marco Pompili wrote: > > If i use the qx.data.Array() wrapper i get the error above: > > this.__rowArr[rowIndex] is undefined > return this.__rowArr[rowIndex][columnIndex]; > > I'm missing something. I guess i'm missing a row ? > You're not just missing a row; I thi

Re: [qooxdoo-devel] Json and Table models

Sorry, Now I've used the source version and this is the uncompressed error message: this.__rowArr[rowIndex] is undefined return this.__rowArr[rowIndex][columnIndex]; from qx.ui.table.model.Simple() line(439): // overridden 433 getValue : function(columnIndex, rowIndex) 434 { 435 if (rowIndex < 0

Re: [qooxdoo-devel] Json and Table models

If you want you can set the column names automatically too - qx.lang.Object.getKeys(obj) turns the keys of obj into an array. For example going off my previous code : console.log(qx.lang.Object.getKeys(test[0])); => ["col1", "col2", "col3"] and you can use this to set the columns in your model:

Re: [qooxdoo-devel] Json and Table models

I think that qx.lang.core automatically adds a Javascript implementation of forEach if there isn't a native one. It's hard to tell from looking at your error message, but it looks like you may have missed a column. -deech On Sat, Dec 4, 2010 at 8:32 PM, Marco Pompili wrote: > > Thank you for yo

Re: [qooxdoo-devel] Json and Table models

On Sat, Dec 4, 2010 at 21:32, Marco Pompili wrote: > > Thank you for your suggestions. I'm following aditya's method so I don't > need > to know what the column's name are. > > I've set up this code: > > var data = response.getContent(); > var rows = new Array(); > > var addRow = function (obj) {

Re: [qooxdoo-devel] Json and Table models

Thank you for your suggestions. I'm following aditya's method so I don't need to know what the column's name are. I've set up this code: var data = response.getContent(); var rows = new Array(); var addRow = function (obj) { rows.push(qx.lang.Object.getValues(o

Re: [qooxdoo-devel] Json and Table models

I hadn't realized that "arrayForEach" was already added to the Array object, so the line: test.forEach(log,test); works in place of : test.arrayForEach = qx.lang.Core.arrayForEach; test.arrayForEach(log,test); -deech On Sat, Dec 4, 2010 at 2:13 PM, aditya siram wrote: > You can us

Re: [qooxdoo-devel] Json and Table models

You can use the qx.lang.Object.getValues(obj) function to turn the values in a map into an array. Eg. var test = [{col1:"a",col2:"aa",col3:"aaa"}, {col1:"b",col2:"bb",col3:"bbb"}, {col1:"c",col2:"cc",col3:"ccc"}]; var log = function (obj) { c

Re: [qooxdoo-devel] Json and Table models

On Sat, Dec 4, 2010 at 14:16, Marco Pompili wrote: > > Hi qooxdoers, > > I'm retreiving data in json format and i want to put that data in a > Simple() > data model with the method: > > var jsonData = response.getContent(); > setData( jsonData ); > > The problem is that the Json data is an array

[qooxdoo-devel] Json and Table models

Hi qooxdoers, I'm retreiving data in json format and i want to put that data in a Simple() data model with the method: var jsonData = response.getContent(); setData( jsonData ); The problem is that the Json data is an array of object and so the method doesn't work. I would like to add directly

Re: [qooxdoo-devel] json response convert into a variable

Pass a callback function into the fetchLogins method and call that function once the call has returned from the server: fetchLogins : function(username, password, callback, context) { this.__callback = callback; this.__context = context; [...] }, Response : function(response){ var myData = J

Re: [qooxdoo-devel] json response convert into a variable

o.k. it works. Thank you very much. Did you know how i can the response (myData) return to the Application.js? regards, Georg qx.Class.define("moto.Loginservice", { extend : qx.core.Object, members : { fetchLogins : function(username, password) { if (this.__store == null) { // Call the backend

Re: [qooxdoo-devel] json response convert into a variable

Hi, I am not really sure what you mean by "header" content, but you can simply parse the JSON data into a javascript object by using qx.lang.Json.parse(): http://demo.qooxdoo.org/current/apiviewer/#qx.lang.Json -- View this message in context: http://qooxdoo.678.n2.nabble.com/json-response-con

[qooxdoo-devel] json response convert into a variable

Hi, i don't know how i get the data from the header content into a variable. This is my response of a remote.Request(url, "POST", "application/json"): var result = response.getContent(); (header-content: [{"first":"katja","last":"katja"}]) I need the variable to decide if the login true or fal

Re: [qooxdoo-devel] JSON store or rpc?

Hey Martin, thanks for the info, that's fine. Greetings, Stefan On 26.09.2010 11:23, Martin Wittemann wrote: > Hey, > Well, we still haven an bug open for such a RPC remote data store but sure we > will not can get it done this year. I want to check the RPC layer before that > and that takes s

Re: [qooxdoo-devel] JSON store or rpc?

Hey, Well, we still haven an bug open for such a RPC remote data store but sure we will not can get it done this year. I want to check the RPC layer before that and that takes some time too. But there will in some time a solution in the sdk, but not in 1.3 for sure. Regards, Martin PS: We have f

Re: [qooxdoo-devel] JSON store or rpc?

Hi Christian, Martin and others, I somehow had in mind that you were working on a JsonRpc store, perhaps from an earlier posting of yours on the m.l. Can you tell if the source is stable so far? And if so, wouldn't you agree that a JsonRpc store would perfectly fit into the framework itself? I'

Re: [qooxdoo-devel] JSON store or rpc?

The VirtualData contribution in qooxdoo-contrib contains an example how to make a JsonRpc data store: http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/VirtualData/trunk/source/class/virtualdata/store/JsonRpc.js?view=markup Cheers, Christian -- View this m

Re: [qooxdoo-devel] JSON store or rpc?

Hey, Its interesting to see this thread and thanks stefan for your answer. I could not have said it better. I just want to add some details. You can still use the data binding if you just use the json marshaler to create the objects loaded with RPC. Without hat, you can still use all the contro

Re: [qooxdoo-devel] JSON store or rpc?

Hej, the store, while using the simpler qx.io.remote.Request system to retrieve data, has the advantage of being coupled to the (rather new) qooxdoo data binding system. This makes binding the data to qooxdoo widgets (like lists, or forms) quite simple. qx.io.remote.Rpc is the more advanced IO

Re: [qooxdoo-devel] JSON store or rpc?

In the data binding chapter in the manual it is recommended to use stores to retrieve the data. However, in the communication chapter there are no instructions for setting up a json service for use with the json store. On the other hand, there are instructions for setting up an rpc server, includi

Re: [qooxdoo-devel] JSON store or rpc?

JSON Store fetches json data from the server, so, yes, you should return json data. :) From I can see, that PHP function does the trick. I don't think you can use JSON Store in combination with RPC. -- View this message in context: http://qooxdoo.678.n2.nabble.com/JSON-store-or-rpc-tp5564779p

[qooxdoo-devel] JSON store or rpc?

In http://manual.qooxdoo.org/1.2.x/pages/data_binding/stores.html it seems the recommended way of retrieving data is using a JSON store. You have some examples showing how to set up an rpc server. But as far as I can figure out, it isn't possible to use the JSON store with an rpc server. So, if

Re: [qooxdoo-devel] json-rpc-2

Hello David, We hope to get a look at the whole RPC layer in qooxdoo for the upcoming release: http://qooxdoo.org/about/roadmap#release_1.3 We will see if there is enough time to include the batching feature. I really hope we can get it done because I also think it can improve speed, especially

[qooxdoo-devel] json-rpc-2

Hi, Is somebody working on http://groups.google.com/group/json-rpc/web/json-rpc-2-0 ? Batch (point 6) it's a major improvement for rpc speed. Any discussion, tickets, documentation I can refer to ? A roadmap for this ? Do you plan to keep xml-rpc support ? Thank you, David ---

Re: [qooxdoo-devel] json-rpc/node - "service" parameter

Hello Christina, > I am currently porting Martin's json-rpc/node code [1] to qxoo to run on the > server (as a contribution named "RpcNode"). Thats really good to hear that my code is worth something at last. :) > In contrast to Derrell's RPC implementation [2], the current 1.0 [3] and > 2.0 [

[qooxdoo-devel] json-rpc/node - "service" parameter

Hello, I am currently porting Martin's json-rpc/node code [1] to qxoo to run on the server (as a contribution named "RpcNode"). I plan various modifications, but want to announce the following beforehand to hear your thoughts: In contrast to Derrell's RPC implementation [2], the current 1.0 [3]

Re: [qooxdoo-devel] Json Date format from server to client

I suspect you've hit the nail on the head, Derrell, the call_date value is quoted in the return data. Had it shown up as a literal "new Date(...)" after being evaled on the client side, I probably would have figured this out. It was quite late both nights I looked at this, and it took me a while

Re: [qooxdoo-devel] Json Date format from server to client

On Mon, Mar 22, 2010 at 23:35, Patrick Paskvan wrote: > Hello List, > > >From what I can tell from the documentation and qooxdoo code, qooxdoo > is simply evaling the json return value of an RPC call. In order to > pass a date from the server to client and have the client > automagically turn it

Re: [qooxdoo-devel] Json Date format from server to client

Pat, On 03/23/2010 04:35 AM, Patrick Paskvan wrote: > Hello List, > >>From what I can tell from the documentation and qooxdoo code, qooxdoo > is simply evaling the json return value of an RPC call. In order to > pass a date from the server to client and have the client > automagically turn it in

[qooxdoo-devel] Json Date format from server to client

Hello List, >From what I can tell from the documentation and qooxdoo code, qooxdoo is simply evaling the json return value of an RPC call. In order to pass a date from the server to client and have the client automagically turn it into a javascript date object, we should simply use "new Date()" a

Re: [qooxdoo-devel] JSON: eval() vs. Function

Peter, Haha, I thought that's what you meant, meaning your original statement was probably more correct, that the issue is decreasing. Thanks for clarifying. Gene On Thu, 2009-12-17 at 10:14 +0100, Peter Schneider wrote: > Hi Gene, > > sorry if I have created so much confusion. ;) > > He

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Gene, sorry if I have created so much confusion. ;) Here's what I meant: * The longer you wait, the lesser performance is an issue. * Performance is increasing (it's getting better and better) Hope that helps, Peter Original From: Gene Amtower Date: 16.12.2009 18:40 >

Re: [qooxdoo-devel] JSON: eval() vs. Function

Please see small clarification below... On Wed, 2009-12-16 at 18:10 +0100, Peter Schneider wrote: > >> As with most of the JavaScripts engine features, it seems to be > that the > >> performance issue of eval() is decreasing with every new browser > version. > > > > I don't have this impression.

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Andreas, here's my 2nd (more detailed) reply: > Hi Peter, > [...] [...] Wouldn't "Function" be the better choice? >>> >>> Why would it? There doesn't seem to be a real difference to me (except >>> regarding scoping, but this should be irrelevant here). >> >> I think it's a bit more than j

Re: [qooxdoo-devel] JSON: eval() vs. Function

Dear Peter, On Wed, 16 Dec 2009, Peter Schneider wrote: > It is all about "do I trust the other side". In our special case the backend > is > under our control as well, so we know what to expect from that server. and you are sure there is no bug in the server-side implementation ... under no ci

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Andres, just a quick reply >> [...] >> As with most of the JavaScripts engine features, it seems to be that the >> performance issue of eval() is decreasing with every new browser version. > > I don't have this impression. Do you have any tests/references for this > assumption? Sorry, that wa

Re: [qooxdoo-devel] JSON: eval() vs. Function

On Wed, Dec 16, 2009 at 09:40, Peter Schneider wrote: > > Checking the received JSON message before parsing it is a good point in any > case, anyway. I'm not sure, but I think something like that can be found in > the > "contrib"... > No, that's already done when the response type is set to "appl

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Peter, Am 16.12.2009 um 15:03 schrieb Peter Schneider: [...] Wouldn't "Function" be the better choice? Why would it? There doesn't seem to be a real difference to me (except regarding scoping, but this should be irrelevant here). I think it's a bit more than just scoping. As far as I

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Derrell > [...] > Hi Peter, > > "eval() is evil" is a common phrase that helps discourage those who don't > understand the possible consequences of using it from ever using it. There > is nothing inherently evil about eval(). The input to eval() must be > sanitized to ensure that there is no c

Re: [qooxdoo-devel] JSON: eval() vs. Function

On Wed, Dec 16, 2009 at 09:03, Peter Schneider wrote: > Hi Andreas, > > >> [...] Wouldn't "Function" be the better choice? > > > > Why would it? There doesn't seem to be a real difference to me (except > > regarding scoping, but this should be irrelevant here). > > I think it's a bit more than jus

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Andreas, >> [...] Wouldn't "Function" be the better choice? > > Why would it? There doesn't seem to be a real difference to me (except > regarding scoping, but this should be irrelevant here). I think it's a bit more than just scoping. As far as I remember the eval() call starts a complete

Re: [qooxdoo-devel] JSON: eval() vs. Function

Hi Peter, Am 16.12.2009 um 10:28 schrieb Peter Schneider: > while I was 'cleaning up' our code base I've come along the JSON > class of > qooxdoo. > Is there any reason why it uses the evil eval() function for > evaluating and > parsing the backend responses? Wouldn't "Function" be the better

[qooxdoo-devel] JSON: eval() vs. Function

Hi folks, while I was 'cleaning up' our code base I've come along the JSON class of qooxdoo. Is there any reason why it uses the evil eval() function for evaluating and parsing the backend responses? Wouldn't "Function" be the better choice? I've tried the following replacement in our application

  1   2   3   >