|
|
|
|
|
|
| Re: any doc or help for creating native custom widget with rap 2.0? [message #1009162 is a reply to message #1009068] |
Thu, 14 February 2013 15:13  |
|
Hi Thorsten,
> I just started migrating a non-GUI widget based on the links you
> provided. Communication between server and client side is working fine
> (using pure JSON now). Notifications (triggered on client side) are
> working as well.
That's good to hear :)
> Using the LCA approach for implementing custom widgets isn't recommend
> by the release notes of RAP 2.0. Nonetheless RAP 2.0 still uses LCAs for
> its widgets. Why?
Because it's a whole lot of work to change that. Anyway, the widget LCAs
will be changed to use the Remote API as well. We're looking forward to
replace the concept of lifecycle phases in favor of the remote API in
some future version.
> Is using the LCA approach still a way for migrating my
> custom widgets? Or shall I eliminate all LCA usage?
LCAs are still supported but discouraged for new widgets. At some point
in time, we'll have to discontinue support for LCAs.
> How do I migrate custom widgets based on qooxdoo? Where do I have to
> place my code handling things like
> "rap.registerTypeHandler('myCustomWidget')" and the like? In the
> qooxdoo-constructor of my widget?
You probably know that RAP maintains a modified subset of qooxdoo. The
classes have moved to the rwt namespace. However, you can use these
classes at your own risk.
The typehandler has to be registered only once, directly in the code
that defines the widget. In the factory function, you'd create an
instance of your widget.
Regards, Ralf
--
Ralf Sternberg
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.03708 seconds
] 
Search
Help
Register
Login
Home
