Easy, to change the content of the control, I send something like:
my-custom-id.setValue(newValue);
Granted, I do an EVAL on the client side and many people hate this,
but for me it works fine. And with the speed of todays computers, it
executes very quickly even with large blocks of code.
Jim
Jim
I think I am understanding why your server returns javascript. If the
server app wants to update a field what type of code snippet does it
pass to the client?
I was approaching this with the intention of passing a json object to
the client that would pass the parameters required to modify the
Yes, we maintain a 1 to 1 mapping of controls and we designate the ID
of the control. We create objects with code like:
var my-custom-id = new swep.customObject(); // it is created in the
correct scope to make it easy to update
and the server knows that I have a customObject named my-custom-id a
Jim and Derrel,
Thanks for identifying how I can retrieve the identifier for each
widget. If I can't specify an identifier for a widget how does the
back-end know the qooxdoo identifier for a widget?
Do you maintain a mapping of identifiers on the client side?
Thanks,
Christopher
On Wed, Feb 22
Actually Derrell, maintaining the state at the server works quite well
for us (we have a custom written server in Delphi that interfaces with
our Oracle server and maintains the status of each connected user). We
are able to redisplay the page, in it's current state, whenever the
users hits F5 beca
On Wed, Feb 22, 2012 at 18:10, Chris Bunn wrote:
> Hello
>
> I am new to working with qooxdoo, and am still trying to familiarize
> myself with the API. I am trying to determine the best way to access a
> widget object after it has been created and outside of the scope it
> was created in. In the
Hello
I am new to working with qooxdoo, and am still trying to familiarize
myself with the API. I am trying to determine the best way to access a
widget object after it has been created and outside of the scope it
was created in. In the application that I am working on the back-end
logic maintains
