Thanks, it worked. I also tried the recently discovered
jsinterop-generator. Unfortunately the generator does not support
enum-types yet and stops generating.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and
Hello,
I'm working on Lovefield bindings for JSInterop. While the basic stuff
(init, insert, ...) works with the elemental2-promise-beta quite well, I'd
like to have bindings for the Lovefield query mechanism as well.
Sadly I don't know how to write the matching Java classes. Consider the
I haven't found the responsible "namer-code" by myself yet, I'll guess I
have to live with the current display-scheme.
If it's related to Chrome I'll be happy to investigate in that direction.
Sadly I currently have no pointer which would lead me to this assumption.
--
You received this
Do you know which class is responsible for naming the
translated JavaScript-classes? All I could find right now were the namer
for fields and methodnames. I guess that this is the part one would have to
look into in order to understand, why the class names are shown as they do.
--
You
Hello,
As I understand your MentionPanel is the contenteditable (DIV) you are
inserting DOM-nodes into. And your code crashes in
"MentionPanel.this.removeFromParent()"?
That is probably because you are never inserting the MentionPanel in the
widget hierarchy as a child of another widget.
Yeah I tried to modify that parameter within the CodeServer. Sadly I wasn't
able to get it to work.
>From the mentioned commit all I found was that it only affects the naming
of the field (JSIncrementalNamer on/off). But I couldn't find any evidence
of the "class name" that is shown right to
"-style" gives an error and even changing the JSOutputOption to PRETTY
within a debugging session of CodeServer doesn't change the style. I would
prefer an opt-out for this behaviour for maybe "not so big"-Projects. But
it may have some deeper technical reasons that I don't see.
Yes, maybe
Does nobody have this problem? Or am I the only one, who's interested in
the actual class being used (especially in polymorphism cases).
I would like to maximize my productivity in a newly started project.
Best regards
Klemens
Am Freitag, 18. März 2016 07:33:12 UTC+1 schrieb Klemens Schrage:
>
Hello,
maybe I missed something within all those GWT 2.8 discussions / jsinterop
announcements, but since switching to 2.8 beta (and even current snapshot)
chrome doesn't show the variable's class name / type while debugging in dev
tools. There is only the obfuscated name. Not the biggest deal
