version suggestions, data binding

[vitezg]

Hi!

Which qooxdoo+qxtransformer version would you suggest for a stable,
live site?
Could you point me to data binding docs to these versions? I had a
really hard time figuring out which data
binding method belongs to which version.

Having said that, I'm really impressed by qxtransformer and qooxdoo, I
would have never imagined making good looking web GUIs can be so easy.
Please keep up the good work!

regards,
Gábor

[Siarhei Barysiuk]

Hi Gábor,

I suggest using trunk with the latest version of qooxdoo.

https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/QxTransformer/trunk/

What do you mean by databinding - qooxdoo databinding or qcl extension?

Cheers,
Serge

> --
> You received this message because you are subscribed to the Google
> Groups "QxTransformer" group.
> To post to this group, send email to qxtran...@googlegroups.com.
> To unsubscribe from this group, send email to qxtransforme...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/qxtransformer?hl=en
> .
>

[Gabor Vitez]

Hi!

> What do you mean by databinding - qooxdoo databinding or qcl extension?

Our preferences would be simple usage, and as few dependencies as
possible. The objective would be getting
data from the server into the widgets, like search results, etc - we
plan to retrofit an old website to use qooxdoo.

The "updateclient" in 0.3 looked really good.

best,
Gábor

[Christian Boulanger]

Hi, the old way of databinding (like in 0.3) is no longer supported. We fully switched to using the databinding architecture of qooxdoo (since 0.8):

http://qooxdoo.org/documentation/1.0/data_binding

No need to provide anything from QxTransformer in this regard any more. However, there are a couple of tags that support the .bind() method of qooxdoo widgets:

<qxt:bind />  bind a target object

<qxt:observe />  bind the widget of the parent tag

<qxt:sync /> bind bi-directionally

We are very sorry that there is no release and such little documentation yet. Siarhei and I wish we had more time for this. But keep asking, we'll respond to clear up your immediate questions.

Best,

Christian

2010/4/13 Gabor Vitez <gabor...@gmail.com>

Gábor

[Christian Boulanger]

Forgot to say that this applies only to the trunk.

2010/4/13 Christian Boulanger <c.bou...@qxtransformer.org>

[Christian Boulanger]

2010/4/13 Christian Boulanger <c.bou...@qxtransformer.org>

We are very sorry that there is no release and such little documentation yet. Siarhei and I wish we had more time for this. But keep asking, we'll respond to clear up your immediate questions.

Actually, looking into the existing documentation, it should be enough to get you going:

http://qooxdoo.org/contrib/project/qxtransformer

 

[Gabor Vitez]

Hi!

Sorry but I'm still baffled, I'm still missing bidirectional
communication with the server. The data stores are unidirectional
aren't they?

Let's say I have a form, with a text fields named "email", and
"fullname", and a "submit" button.
I also have a JSON-RPC server at the url "/services/" , classname
"app.contacts", and a method named "emailtofullname".
On buttonpress I'd like to send the content of the email field to my
method, which sends back the full name of the contact. I'd like to
fill out the "fullname" field with it.

How can I solve this use-case with qxtransformer+qooxdoo?

Thanks for the patience :)

Gábor

[Christian Boulanger]

Hello Gábor,

QxTransformer is about UI generation, databinding is a business logic thing that you need to solve in the javascript/qooxdoo classes. QxTransformer models widgets with a "graphic" representation, and allows you to represent widget properties with tag attributes. And those properties can be bound to server data with qooxdoo - databinding. 

http://qooxdoo.org/documentation/1.0/data_binding

I am afraid you will have to aquaint yourself how this databinding works - you need models and controllers. Then, when you have a model that you can bind to, QxTransfomer comes into play

<qx:textField>

  <qxt:sync propertyChain="value" target="name-of-model" targetPropertyChain="value" />

<qx:textField>

This would, for example, create a bi-directional connection between the text field and the model. The model, in turn, is bound to server data, which is out of the "responsibility" of QxTransformer. I am currently revising a tutorial which shows how to use QxTransformer in a data-driven application, but it is far from finished. I'll let the list know when it is online.

Cheers,

Christian

2010/4/15 Gabor Vitez <gabor...@gmail.com>

Gábor

[Gabor Vitez]

Gosh, I'm barking up the wrong tree, thanks :)

Gábor