Re: GWT JSON-B

[Nándor Előd Fekete]

I needed portable code between client/server and polymorphism (through { 
'type': 'SomeTypeIdentifier', ...other properties...}). Is there some 
straightforward way to do that with jsinterop annotations?

On Monday, May 21, 2018 at 12:43:59 AM UTC+2, Thomas Broyer wrote:
>
> How about "just" using @JsType classes?

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT JSON-B

[Nándor Előd Fekete]

I had great success with https://github.com/nmorel/gwt-jackson, which is a 
json library written for gwt that emulates much of jackson's functionality. 
But note that it uses gwt generator infrastructure and hence is not 
forward-compatible with future GWT3.
There's also https://github.com/vegegoku/gwt-jackson-apt that should be 
forward compatible with GWT3, but I haven't tried it out yet. Check their 
roadmap for a quick picture on supported/not-yet-supported 
features: https://github.com/vegegoku/gwt-jackson-apt#road-map. Instagram 
also has something, but I haven't tried that 
either: https://github.com/Instagram/ig-json-parser

On Saturday, May 19, 2018 at 10:09:38 PM UTC+2, richip wrote:
>
>
>
> On Saturday, 19 May 2018 14:07:35 UTC-6, richip wrote:
>>
>> Is there support for JSON-B or any other JSON-object binding API in GWT? 
>> If not, is it possible to implement this without reflection? I wouldn't 
>> mind taking a stab at it, but am not sure how I'd do it without Java 
>> reflection. The goal is to call a RESTful service passing a Java object and 
>> getting a Java object in response. All nice and Java-like.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] The elusive J2CL

[Nándor Előd Fekete]

I am *really* interested. Can you sign me up?

On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote:
>
> The main blocker for releasing J2CL for wider audience is even basic 
> missing functionalities around building it in open-source and seeing at 
> least some output for your compilations. That is blocked on missing 
> functionalities in bazel. After that we can probably finished in more 
> timely manner.
> There is still tone of work to do for a polished open source experience 
> but at least we can give access to more people who is really interested.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/8de62b64-4bc8-4158-80d4-b15ef688f523%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Super slow compilation in projects with many wildcard generics

[Nándor Előd Fekete]

The fix for this bug got backported to the 4.7 line of Eclipse. Will there 
be a 2.8.3 GWT release and do you guys plan to upgrade to this version of 
JDT if so?

On Monday, October 2, 2017 at 10:05:31 AM UTC+2, Ignacio Baca Moreno-Torres 
wrote:
>
> Yep, IMO the best compromise between solution & risk is to apply the patch 
> over the last CUSTOM JDT build and wait for java9 lang support to upgrade 
> to the last JDT.
>
> On Mon, Oct 2, 2017 at 9:48 AM Thomas Broyer  > wrote:
>
>> Note that this means GWT will effectively require JDK 8 for development 
>> (gwt-servlet could possibly still work with 1.7, though at that point I'd 
>> push for 1.8 too)
>>
>> https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_8.xml#appendix
>>
>>
>> On Monday, October 2, 2017 at 8:42:22 AM UTC+2, Ignacio Baca 
>> Moreno-Torres wrote:
>>>
>>> FYI The patch will be released for 4.8M3 
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=521438#c17
>>>
>>> On Wednesday, September 27, 2017 at 11:09:43 PM UTC+2, Roberto 
>>> Lublinerman wrote:

 I would wait until an eclipse jdt release is done and upgrade JDT.

 On Tue, Sep 26, 2017 at 10:56 AM, Ignacio Baca Moreno-Torres <
 ign...@bacamt.com> wrote:

> JDT has a bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=521438) 
> that make it super slow to compile some project involving wildcards 
> generics. Actually, there are many problems with performance and memory 
> consumption since Java 8, this has just lived longer bc it was a bit more 
> difficult but seem to be a combination of wildcard+inheritance that makes 
> the internal type map to explode. RxJava 2 takes >3min to compile caused 
> by 
> this bug so it makes impossible to work with.
>
> The bug has been already solved. It needs to be merged and release in 
> JDT and later on, it will be nice to be merged in the GWT JDT version as 
> soon as possible, anyway as this seems to be a long process I have 
> already 
> released a patched version here.
>
> 
> rxjava-gwt-repo
> 
> https://raw.githubusercontent.com/intendia-oss/rxjava-gwt/mvn-repo/
> 
>
>
> The patched commit is this one 
> https://github.com/ibaca/eclipse.jdt.core/commit/995495659bddcaf193c0107f8489e698624ceea7
> And applied in GWT here 
> https://github.com/ibaca/gwt/commit/63218f3d695cfc6ec20fea776908b9801952f462
>
> Do I create an issue in github? What do you think it is better, to 
> just add the patch (as I have done) over the last version, or to upgrade 
> to 
> last JDT?
>
> PD: this will improve a bit compilation times and memory consumption 
> ;).
>
  

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/0f1d9ec3-6516-4cb2-8d27-e3057c481593%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT2.8.1 errors "Exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : object_0_g$.getXXX_30_g$ is not a function"

[Nándor Előd Fekete]

When I first encountered this problem, GWT 2.8.1 wasn't even released. I 
got this error at random times while developing using SDM incremental 
compilation. See my earlier post on the subject - 
https://groups.google.com/d/topic/google-web-toolkit/rdoCr79EQbE/discussion - 
it's from 2016.

On Friday, May 19, 2017 at 10:12:24 PM UTC+2, Marteijn Nouwens wrote:
>
> If you use a framework that uses 2.8.0 and importing 2.8.1 yourself. In 
> that case exclude everything that the library is importing. We use gwt 
> amterial and there this helps. Some dependencies in gwt have changed andthe 
> changes  result in these conflicts.
>
> Marteijn
>
> Op donderdag 18 mei 2017 17:56:10 UTC+2 schreef Nándor Előd Fekete:
>>
>> I think I have the same problem as you. See my earlier post on this 
>> forum: 
>> https://groups.google.com/d/topic/google-web-toolkit/rdoCr79EQbE/discussion
>> I wanted to file an issue about this problem, but I couldn't track down 
>> the exact behavior of the GWT compiler when this happens (except the info 
>> you can see in my linked post). I didn't file an issue in the end because I 
>> didn't have a deterministic way to reproduce it. If we would be able to 
>> reliably reproduce the issue, that would be the first major step towards 
>> fixing it. Also, for me, it happened with normal classes too, not just 
>> anonymous classes. Also worth mentioning that I never had this problem with 
>> the normal GWT compiler, only with SuperDevMode.
>>
>> On Wednesday, May 17, 2017 at 4:37:46 PM UTC+2, Darren Smith wrote:
>>>
>>> Hi all
>>>
>>> since upgrading to GWT2.8.1 I am seeing an error message never before 
>>> encountered (and I've been developing with GWT for numerous years).
>>>
>>>"Exception: com.google.gwt.core.client.JavaScriptException: 
>>> (TypeError) : object_0_g$.getXXX_30_g$ is not a function"
>>>
>>> Reverting back to GWT2.8 caused the problem to disappear.
>>>
>>>
>>> The problem has only occurred in anonymous classes up until now (but no 
>>> idea if that is important or not).
>>>
>>>
>>> For example, I have
>>>
>>> public class SomeTable extends DataGrid {
>>>
>>>   private void initTable() {
>>>
>>>  TextColumn arcIdCol = new TextColumn() {
>>> @Override
>>> public String getValue(SomeClass object) {
>>> logger.info("= " + object.get());  // EXECUTION PROBLEM HERE
>>> return object.get()
>>> }
>>> };
>>>..
>>> }
>>>
>>> The java code compiles fine, and the GWT compilation works fine when 
>>> SuperDev mode is launched (all done in Eclipse).
>>>
>>> When the logger.info line is reached, the error ".. not a function" is 
>>> thrown.
>>>
>>> Examining in the browser debugger, I can see that the prototype 
>>> (_proto_) associated to the " SomeClass object" parameter  does not contain 
>>> the function get.
>>>
>>> If I re-edit the file SomeClass.java, adding in a new dummy method, and 
>>> re-save, then this time it works -- the function get exists.
>>>
>>> Sounds like an incomplete incremental compilation?
>>>
>>> What is frustrating is that the problem is sporadic - other classes 
>>> employing the same design patterns work fine.
>>>
>>> Has anyone encountered similar issues?
>>>
>>> Rgs
>>> Darren
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT2.8.1 errors "Exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : object_0_g$.getXXX_30_g$ is not a function"

[Nándor Előd Fekete]

I think I have the same problem as you. See my earlier post on this 
forum: 
https://groups.google.com/d/topic/google-web-toolkit/rdoCr79EQbE/discussion
I wanted to file an issue about this problem, but I couldn't track down the 
exact behavior of the GWT compiler when this happens (except the info you 
can see in my linked post). I didn't file an issue in the end because I 
didn't have a deterministic way to reproduce it. If we would be able to 
reliably reproduce the issue, that would be the first major step towards 
fixing it. Also, for me, it happened with normal classes too, not just 
anonymous classes. Also worth mentioning that I never had this problem with 
the normal GWT compiler, only with SuperDevMode.

On Wednesday, May 17, 2017 at 4:37:46 PM UTC+2, Darren Smith wrote:
>
> Hi all
>
> since upgrading to GWT2.8.1 I am seeing an error message never before 
> encountered (and I've been developing with GWT for numerous years).
>
>"Exception: com.google.gwt.core.client.JavaScriptException: (TypeError) 
> : object_0_g$.getXXX_30_g$ is not a function"
>
> Reverting back to GWT2.8 caused the problem to disappear.
>
>
> The problem has only occurred in anonymous classes up until now (but no 
> idea if that is important or not).
>
>
> For example, I have
>
> public class SomeTable extends DataGrid {
>
>   private void initTable() {
>
>  TextColumn arcIdCol = new TextColumn() {
> @Override
> public String getValue(SomeClass object) {
> logger.info("= " + object.get());  // EXECUTION PROBLEM HERE
> return object.get()
> }
> };
>..
> }
>
> The java code compiles fine, and the GWT compilation works fine when 
> SuperDev mode is launched (all done in Eclipse).
>
> When the logger.info line is reached, the error ".. not a function" is 
> thrown.
>
> Examining in the browser debugger, I can see that the prototype (_proto_) 
> associated to the " SomeClass object" parameter  does not contain the 
> function get.
>
> If I re-edit the file SomeClass.java, adding in a new dummy method, and 
> re-save, then this time it works -- the function get exists.
>
> Sounds like an incomplete incremental compilation?
>
> What is frustrating is that the problem is sporadic - other classes 
> employing the same design patterns work fine.
>
> Has anyone encountered similar issues?
>
> Rgs
> Darren
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

[Nándor Előd Fekete]

Hello Manuel,

wasn't Vaadin going into the direction of migrating it's client side 
components to web components in the Vaadin Framework itself? If not, can 
you shed some light on the motivation behind the decision?

Thanks!

On Friday, April 21, 2017 at 9:10:06 PM UTC+2, Manuel Carrasco wrote:
>
> Hi all,
>
> From today, Vaadin has transferred the ownership of the 
> gwt-polymer-elements and gwt-api-generator libraries to me.
>
> https://github.com/manolo/gwt-polymer-elements/
> https://github.com/manolo/gwt-api-generator/
>
> Vaadin decision is based on encouraging communities to maintain polymer 
> bridges for their favourites frameworks, hence Vaadin can focus their 
> efforts on delivering high quality UI elements made in Polymer. It also 
> happened recently with the Angular2Polymer bridge.
>
> I will design a roadmap for the next months.
>
> I'm looking for contributors so let me know who is interested on any 
> matter: coding, testing, reporting, answering, etc, and I will grant access 
> to the repos.
>
> Thanks
> - Manolo
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Need some help with debugging an issue in GWT SDM compiler

[Nándor Előd Fekete]

Well, yes, of course, I can always start from scratch, but that's around 3+ 
minutes (it's a bigger project), which is worse than what I currently do, 
"touching" the Java source file that the compiler is having problem 
generating correct code for. The biggest problem is that it's breaking my 
workflow, and I'd rather spend some time finding a probable bug in the 
compiler itself and give back to the community by fixing it than constantly 
working around the issue.

On Saturday, December 17, 2016 at 2:11:09 AM UTC+1, Kirill Prazdnikov wrote:
>
> mvn clean and clean temp folder before compile will help
>
>
>  суббота, 17 декабря 2016 г., 0:49:30 UTC+3 пользователь Nándor Előd 
> Fekete написал:
>>
>> Hi!
>>
>> I have this strange problem in SDM, where a method in the generated 
>> output JS gets defined under a name, but gets referenced under another name.
>>
>> I'll try to show it through actual compiled JS code vs original code.
>>
>> function *getBoundingClientRect_3_g$*(this$static_0_g$, 
>> withinOffsetParent_0_g$){
>>   $clinit_ElementOverlayMixin_0_g$();
>>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>>   if (is_4_g$(offsetParent_0_g$)) {
>> parentBCR_0_g$ = 
>> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
>> true);
>> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getTop_15_g$();
>> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getLeft_16_g$();
>>   }
>>else {
>> deltaY_0_g$ = getScrollTop_4_g$();
>> deltaX_0_g$ = getScrollLeft_6_g$();
>>   }
>>   return 
>> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>>  
>> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
>> }
>> getBoundingClientRect_3_g$.displayName = 
>> 'ElementOverlayMixin.$getBoundingClientRect';
>>
>>
>> This is the original Java source of the method:
>>
>> public final ClientRect *getBoundingClientRect*(boolean 
>> withinOffsetParent) {
>> float deltaY;
>> float deltaX;
>> Element offsetParent = getOffsetParent();
>> if (Element.is(offsetParent)) {
>> ClientRect parentBCR = ElementOverlayMixin.as(offsetParent).
>> *getBoundingClientRect*(true);
>> deltaY = offsetParent.getScrollTop() - parentBCR.getTop();
>> deltaX = offsetParent.getScrollLeft() - parentBCR.getLeft();
>> } else {
>> deltaY = Window.getScrollTop();
>> deltaX = Window.getScrollLeft();
>> }
>> return withinOffsetParent ? getBoundingClientRect().translated(deltaX, 
>> deltaY) : getBoundingClientRect();
>> }
>>
>> I've highlighted the important parts with bold+red/green. Note that it's 
>> a recursive method invoking itself on another object. In the generated 
>> output, the name of the function in the function declaration and the name 
>> used while referring to the same function is different.
>>
>> After a "touch" on the source code file, the compiler now generates the 
>> correct JS output:
>>
>> function *$getBoundingClientRect_2_g$*(this$static_0_g$, 
>> withinOffsetParent_0_g$){
>>   $clinit_ElementOverlayMixin_0_g$();
>>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>>   if (is_4_g$(offsetParent_0_g$)) {
>> parentBCR_0_g$ = 
>> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
>> true);
>> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getTop_15_g$();
>> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getLeft_16_g$();
>>   }
>>else {
>> deltaY_0_g$ = getScrollTop_4_g$();
>> deltaX_0_g$ = getScrollLeft_6_g$();
>>   }
>>   return 
>> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>>  
>> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
>> }
>>
>> $getBoundingClientRect_2_g$.displayName = 
>> 'ElementOverlayMixin.$getBoundingClientRect';
>>
>> I'm using incremental mode, but I think it happened on the first 
>> compilation too with all previous compilation caches cleared.
>>
>> Do you guys have any tips on where to look in the compiler code where the 
>> method name handling / mangling happens?
>>
>> Many thanks!
>>
>> Nandi.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Need some help with debugging an issue in GWT SDM compiler

[Nándor Előd Fekete]

Hi!

I have this strange problem in SDM, where a method in the generated output 
JS gets defined under a name, but gets referenced under another name.

I'll try to show it through actual compiled JS code vs original code.

function *getBoundingClientRect_3_g$*(this$static_0_g$, 
withinOffsetParent_0_g$){
  $clinit_ElementOverlayMixin_0_g$();
  var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
  offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
  if (is_4_g$(offsetParent_0_g$)) {
parentBCR_0_g$ = *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
true);
deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getTop_15_g$();
deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getLeft_16_g$();
  }
   else {
deltaY_0_g$ = getScrollTop_4_g$();
deltaX_0_g$ = getScrollLeft_6_g$();
  }
  return 
withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
 
deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
}
getBoundingClientRect_3_g$.displayName = 
'ElementOverlayMixin.$getBoundingClientRect';


This is the original Java source of the method:

public final ClientRect *getBoundingClientRect*(boolean withinOffsetParent) 
{
float deltaY;
float deltaX;
Element offsetParent = getOffsetParent();
if (Element.is(offsetParent)) {
ClientRect parentBCR = ElementOverlayMixin.as(offsetParent).
*getBoundingClientRect*(true);
deltaY = offsetParent.getScrollTop() - parentBCR.getTop();
deltaX = offsetParent.getScrollLeft() - parentBCR.getLeft();
} else {
deltaY = Window.getScrollTop();
deltaX = Window.getScrollLeft();
}
return withinOffsetParent ? getBoundingClientRect().translated(deltaX, 
deltaY) : getBoundingClientRect();
}

I've highlighted the important parts with bold+red/green. Note that it's a 
recursive method invoking itself on another object. In the generated 
output, the name of the function in the function declaration and the name 
used while referring to the same function is different.

After a "touch" on the source code file, the compiler now generates the 
correct JS output:

function *$getBoundingClientRect_2_g$*(this$static_0_g$, 
withinOffsetParent_0_g$){
  $clinit_ElementOverlayMixin_0_g$();
  var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
  offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
  if (is_4_g$(offsetParent_0_g$)) {
parentBCR_0_g$ = *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
true);
deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getTop_15_g$();
deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getLeft_16_g$();
  }
   else {
deltaY_0_g$ = getScrollTop_4_g$();
deltaX_0_g$ = getScrollLeft_6_g$();
  }
  return 
withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
 
deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
}

$getBoundingClientRect_2_g$.displayName = 
'ElementOverlayMixin.$getBoundingClientRect';

I'm using incremental mode, but I think it happened on the first 
compilation too with all previous compilation caches cleared.

Do you guys have any tips on where to look in the compiler code where the 
method name handling / mangling happens?

Many thanks!

Nandi.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Extending native JsTypes from Java with GWT 2.8.0-rc2

[Nándor Előd Fekete]

Hi everyone!

Are we supposed to be able to extend native (browser) JsTypes from Java? 
Specifically, having the following declaration (from Elemental2):

@JsType(isNative = true, namespace = JsPackage.GLOBAL)
public class HTMLDivElement extends HTMLElement {...}

and the extending type

public class DummyElement extends HTMLDivElement {...}

I'm getting TypeError: Illegal invocation from the compiled js code when it 
tries to define the class (com.google.gwt.lang.Runtime.copyObjectProperties 
(Runtime.java:104)), while copying native properties from the extends js 
type's prototype. The property in this case is 'align' but it happens on 
other browser native properties too.

Thanks for the help!

All the best,
Nandi.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.