Success! With some javascript hacking I have managed to get it working. I
can retrieve props and state and also set state from an onClick callback.
Below is my contrived solution
@JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object")
public class AbstractClassicComponent {
On Wed, Mar 16, 2016 at 8:51 AM, Paul Stockley wrote:
> I am running the latest snapshot build as of a couple of days ago and
> starting SD mode with
>
> Running CodeServer with parameters: [-noprecompile, -port, 9876,
> -sourceLevel, 1.8, -bindAddress, 127.0.0.1,
I tried using a JsType instead of JavaScriptObject and it is still
undefined. I have logged a ticket with the details.
On Wednesday, March 16, 2016 at 12:05:30 PM UTC-4, Goktug Gokdogan wrote:
>
>
>
> On Wed, Mar 16, 2016 at 8:51 AM, Paul Stockley > wrote:
>
>> I am
Paul, brilliant news. Look forward to hopefully taking a look at your code
if you're able to share.
On Fri, Mar 18, 2016 at 4:15 PM Paul Stockley wrote:
> Success! With some javascript hacking I have managed to get it working. I
> can access state and props and set state
I'm sorry, I'm very busy right now, but I will take a look as soon as I can.
On Wed, Mar 16, 2016 at 5:16 PM, Paul Stockley wrote:
> Well I think I have hit a roadblock with the current state of JsInterop.
> Given the code below
>>
>>
>
>
>> public class Example {
>>
>>
On Tue, Mar 15, 2016 at 8:26 PM, Paul Stockley wrote:
> I have made a bit more progress. I managed to get functional components
> working.
>
> @JsType(isNative = true)
> private static class FuncProps extends BaseProps {
> public String aProp;
> }
>
> static final
Success! With some javascript hacking I have managed to get it working. I
can access state and props and set state as a result of an onClick event. I
think it might be possible to get react fully working. Below is my somewhat
contrived solution
--
You received this message because you are