Eclipse Community Forums: Remote Application Platform (RAP)

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » TextArea in the Qooxdoo API

Show: Today's Messages :: Show Polls :: Message Navigator

TextArea in the Qooxdoo API [message #753407]

Thu, 27 October 2011 06:29

S. Schulz

Messages: 72
Registered: September 2011

Member

Hi everybody!

We want to create custom self-validating RAP widgets based on qooxdoo to minimize the traffic of our application. Because of that we build a qx.ui.form.TextField and everything went okay, but with the text area we get the following error:

Error: TypeError: qx.ui.form.TextArea is not a constructor

We searched our qooxdoo plugin (org.eclipse.rap.rwt.q07 in 1.4 and org.eclipse.rap.rwt in 1.5) and there really is no TextArea.js, other classes like PasswordField.js are missing to.

Now we learned (at least we thought so), that RAP is based on Qooxdoo, so we'd assume that RAP text area and password field would not work without them beeing present in Qooxdoo - but of course they are working.

Can someone please shed some light on how Qooxdoo and RAP are connected? And how we might be able to use the other Qooxdoo controls or at least get a decent API that only shows controls we are able to use?

Thanks in advance!

Report message to a moderator

Re: TextArea in the Qooxdoo API [message #753447 is a reply to message #753407]

Thu, 27 October 2011 09:48

Rüdiger Herrmann

Messages: 335
Registered: July 2009

Senior Member

Hi,

although the RAP client is based on qooxdoo, the development has split
up and the classes and widgets in RAP are now heavily modified.

In case of the TextArea.js it was replaced by
org.eclipse.rwt.widgets.Text.js. Be aware that Text.js is not part of
the API and thus may change without prior notice.

Regards,
Rüdiger

On 27.10.2011 08:29, s.schulz wrote:
> Hi everybody!
>
> We want to create custom self-validating RAP widgets based on qooxdoo to
> minimize the traffic of our application. Because of that we build a
> qx.ui.form.TextField and everything went okay, but with the text area we
> get the following error:
>
> Error: TypeError: qx.ui.form.TextArea is not a constructor
>
> We searched our qooxdoo plugin (org.eclipse.rap.rwt.q07 in 1.4 and
> org.eclipse.rap.rwt in 1.5) and there really is no TextArea.js, other
> classes like PasswordField.js are missing to.
>
> Now we learned (at least we thought so), that RAP is based on Qooxdoo,
> so we'd assume that RAP text area and password field would not work
> without them beeing present in Qooxdoo - but of course they are working.
>
> Can someone please shed some light on how Qooxdoo and RAP are connected?
> And how we might be able to use the other Qooxdoo controls or at least
> get a decent API that only shows controls we are able to use?
>
> Thanks in advance!
>
--
Rüdiger Herrmann

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/

Report message to a moderator

Re: TextArea in the Qooxdoo API [message #753452 is a reply to message #753447]

Thu, 27 October 2011 10:09

S. Schulz

Messages: 72
Registered: September 2011

Member

Thank you, now I was able to create the text area. Are you aware of a documentation showing only the RAP branch of Qooxdoo?

> Be aware that Text.js is not part of the API and thus may change without prior notice.

So building these custom widgets is not future-oriented? Is there another way for minimizing the network traffic for basic validations?

Report message to a moderator

Re: TextArea in the Qooxdoo API [message #753503 is a reply to message #753452]

Thu, 27 October 2011 13:53

Tim Buschtoens

Messages: 396
Registered: July 2009

Senior Member

Am 27.10.2011 12:09, schrieb s.schulz:

>> Be aware that Text.js is not part of the API and thus may change
>> without prior notice.
>
> So building these custom widgets is not future-oriented? Is there
> another way for minimizing the network traffic for basic validations?

You certainly can build a custom widget based on current RWT client
widgets, but they are not API and might change with every new release.
We are toying with ideas how to easily add little pieces of logic to the
client based on the RAP protocol. That would cover such scenarios and
would be future-proof. The RAP protocol will be part of the 1.5 release.

Greetings,
Tim

Report message to a moderator