Home » Eclipse Projects » Remote Application Platform (RAP) » IFrame based Custom Widget and Incompatibility after RAP Target Update from 1.2.1 to 1.3M4
| IFrame based Custom Widget and Incompatibility after RAP Target Update from 1.2.1 to 1.3M4 [message #508714] |
Tue, 19 January 2010 22:56  |
 Nikolai Raitsev
Messages: 102
Registered: July 2009 |
Senior Member |
|
|
Hi,
We have a Custom Widget (Rich text HTML editor, based on TinyMCE). After
updating from 1.2.1 to 1.3.0 M4 I have detected & solved some problems
with it.
1.) The widget needs now a "backgroundGradient" property:
backgroundGradient : {
check : "Array",
nullable : true,
init : null,
themeable : true
}
(copy from GfxMixin.js, its not clear why that property is needed here,
that property is used only in one place, in swt theming in
AppearancesBase.js )
2.) The "registry" folder from registered resources is now
"rwt-resources". So that any programmatically access to the registered
resource needs that prefix, e.g. "rwt-resources/tinymce/tinymce.html"
(on 1.2.1 only "tinymce/tinymce.html"), otherwise an 404 error occurs.
So, these are minor changes, but I would like to ask if it so intended?
Best regards,
Nikolai
|
|
|
| Re: IFrame based Custom Widget and Incompatibility after RAP Target Update from 1.2.1 to 1.3M4 [message #508816 is a reply to message #508714] |
Wed, 20 January 2010 13:05  |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
Hi Nikolai,
in short, yes both changes are intended. Please also see my comments
below for further details.
Regards,
--
Rüdiger Herrmann
http://eclipsesource.com
On 19.01.2010 23:56, Nikolai Raitsev wrote:
> Hi,
>
> We have a Custom Widget (Rich text HTML editor, based on TinyMCE). After
> updating from 1.2.1 to 1.3.0 M4 I have detected & solved some problems
> with it.
>
> 1.) The widget needs now a "backgroundGradient" property:
>
> backgroundGradient : {
> check : "Array",
> nullable : true,
> init : null,
> themeable : true
> }
>
> (copy from GfxMixin.js, its not clear why that property is needed here,
> that property is used only in one place, in swt theming in
> AppearancesBase.js )
I will ask a colleague to answer this, stay tuned...
>
> 2.) The "registry" folder from registered resources is now
> "rwt-resources". So that any programmatically access to the registered
> resource needs that prefix, e.g. "rwt-resources/tinymce/tinymce.html"
> (on 1.2.1 only "tinymce/tinymce.html"), otherwise an 404 error occurs.
The "rwt-resources" prefix was introduced with this bug-fix:
281787: Bundle image resources exposed under changing context
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281787
BTW, IResourceManager#getLocation() will return the correct URL.
>
> So, these are minor changes, but I would like to ask if it so intended?
>
> Best regards,
>
> Nikolai
|
|
| | |
| Re: IFrame based Custom Widget and Incompatibility after RAP Target Update from 1.2.1 to 1.3M4 [message #512104 is a reply to message #508849] |
Wed, 03 February 2010 22:30 |
Nikolai Raitsev
Messages: 102
Registered: July 2009 |
Senior Member |
|
|
Hi Tim,
thank you for the answer,
the Widget on the Java side (not the LCA) extends Composite, not Widget,
maybe is it, what do you mean?
Actually, it is now does not matter, I have solved the problem by
myself. But maybe someone has the same thing and he can find the
solution described here.
Best Regards,
Nikolai
Tim Buschtöns schrieb:
> Hi.
>
>> 1.) The widget needs now a "backgroundGradient" property:
>>
>> backgroundGradient : {
>> check : "Array",
>> nullable : true,
>> init : null,
>> themeable : true
>> }
>>
>
> You are using an appearance in your widgets LCA (Java) or qooxdoo-class
> (javascript) that is not compatible, probably "composite" as described
> in the Developer Guide. (We need to update this.) If you want to get rid
> of the property, i would suggest to use another appearance (e.g. "widget").
>
> Greetings,
> Tim
|
|
|
Goto Forum:
Current Time: Fri Apr 26 05:23:21 GMT 2024
Powered by FUDForum. Page generated in 0.05047 seconds |
] 
Search
Help
Register
Login
Home
