On Thu, Sep 18, 2008 at 12:50 PM, Jean-Baptiste BRIAUD - Novlog <
[EMAIL PROTECTED]> wrote:
> Hi qooXdoo list !
>
> I read that part of the doc
>
> http://qooxdoo.org/documentation/0.8/ui_form_handling#the_form_element_interface
>
> but I still have questions as lots of widgets are not documented.
>
> * Why Table doesn't appears to be a widget but I can see it in the
> demo and it look like a widget ... Is it because of data handling ?
> I also read somewhere that Tables were not ready or something like
> that but it might be a very old document (google ...)
Table is a mature widget being used in numerous applications. The table is,
in fact, a widget. You may be confused because the individual rows and
cells within the table are not widgets. The table gets its data from a data
model and renders only those rows of the table which are currently visible.
As you've probably discovered, rendering is about the slowest thing you can
do, so rendering as little as possible allows for the ability to display
vast amounts of data while still maintaining a pleasant user experience.
Since table cells are not widgets, you instead define a cell renderer for a
column of cells, and you can define a cell editor if you want that data to
be editable.
>
> * I planed to use RPC JSON would you advice me to go that way with
> qooXdoo 0.8 (doc look like to be for 0.7 but I hope the differences
> are very small) ?
There have been no significant changes in the communication classes nor in
the JSON-RPC class between recent 0.7 and 0.8.
>
> * Table data appears to be javascript array and not JSON data. I'm not
> sure how to handle that. Is there a mapper js arrays <-> JSON in
> qppXdpp ?
Yes, table data, the data model I referred to earlier, is an array of rows
of data. Each row is an array of cell data. If you need to convert
manually from any javascript object (like this data array) to a JSON string,
you can use the method qx.util.Json.stringify(). To convert the other
direction you can use eval().
>
> * I need advice on the "before the RPC client part" : extract data, if
> possible generically from widgets (including table) to provide data to
> the RPC client API
My preferred method of making requests of a server and receiving responses
is to use the remote procedure call paradigm. There is already a JSON-RPC
class in qooxdoo, qx.io.remote.Rpc, which allows you to issue remote
procedure calls and receive the results back from the server. There are a
number of backends (server-side) that you can choose to use. They are all
in qooxdoo-contrib. You'll find RpcPhp, RpcJava, and RpcPerl.
>
>
> * I globaly see how the RPC client and server worked but where can I
> find details for the particular case of qooXdoo (as client) and PHP
> and JAVA for server side ?
In addition to the documentation in the wiki, some of these provide
documentation in the backend directory as well.
>
>
> * Is it stable enought on 0.8 to use JSON RPC client in qooXdoo ?
I believe so. I'm using it. :-)
Derrell
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
