Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-05 Thread Hugh Gibson
> as far as I recognize, something like this > > //... > setColumns(["First name", "Middle name", "Last name"], > [0, 1, 2]); > //... > // Data "example" > data = [ {"foo", "bar", "baz"}, >{"Foo!","BAR!", "zoo"}, ...]; Neat trick, but presumably you meant: da

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-05 Thread Peter Schneider
> Yes, that did the trick, thank you! However, since > qx.ui.table.model.Simple does fine without named column data, it would > be worth thinking about reworking the remote table model accordingly. > not having the repetitive column ids in the transferred code saves a lot > of bandwith and with

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-04 Thread dperez
This is a little more compact (removing quotes) and more bandwidth friendly: [ {f:"foo", m:"bar", l:"baz"}, {f:"Foo!", m:"BAR!", l:"zoo"}, ...] Hugh Gibson wrote: > > Then your data will be: > > [ {"f":"foo", "m":"bar", "l":"baz"}, > {"f":"Foo!", "m":"BAR!", "l":"zoo"}, ...] > -- View

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-04 Thread bibliograph
Yes, that did the trick, thank you! However, since qx.ui.table.model.Simple does fine without named column data, it would be worth thinking about reworking the remote table model accordingly. not having the repetitive column ids in the transferred code saves a lot of bandwith and with the right

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-04 Thread bibliograph
Hello Hugh, thanks for the info. I'll try that. I simply assumed that the data structure would be the same as in the Simple Table Model. I use tables throughout my app with qx.ui.table.model.Simple and the data structure is always like the one I describe. Christian Hugh Gibson schrieb: >> th

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-04 Thread Hugh Gibson
> thanks, but this is not the problem. Both the setRowCount() and the > setRowData() methods are called with the respective data. > setRowData() passes the data to the superclass _onRowDataLoaded() > method as required by the superclass. The data is there - I can get > it with getTableModel().g

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-03 Thread bibliograph
Hugh Gibson schrieb: >> this.addEventListener("dataReceived",function(e){ >> result = e.getData(); >> if ( result== null ) >> { >> this.setRowCount(null); >> this.setRowData([]); >> } >> else if ( "rowCount" in result ) >> { >> this.se

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-03 Thread Hugh Gibson
> this.addEventListener("dataReceived",function(e){ > result = e.getData(); > if ( result== null ) > { > this.setRowCount(null); > this.setRowData([]); > } > else if ( "rowCount" in result ) > { > this.setRowCount(result.rowCount); >

Re: [qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-02 Thread bibliograph
forgot to explain that the whole thing works with the qcl.databinding.simple.MDataManager mixin, which does all the i/o stuff and dispatches the "dataReceived" event when the data has arrived. this part works flawlessly, the data is just not rendered in the table rows bibliograph schrieb: >

[qooxdoo-devel] qx.ui.table.model.Remote implementation problems

2007-10-02 Thread bibliograph
Hello, it took me a while to figure out how to write an implementation of the qx.ui.table.model.Remote class. I will provide this class as a much-needed example. Now everything works with the backend - the data is prefetched and everything - sweet! But nothing shows up in my table, event