ialex32x

Yes, it's just can not build for WebGL, because I haven't finished this part, and have no specific plan yet on this part of the work. BTW, I'll check the...

The performance issue has been fixed now. It's because of some missing compiler flags in the make file.

Yes, it's possible. I'll have a try to build it. But as I see, the WebGL build is not so reasonable and valuable because of the performance issue and many...

I've fixed the build error. But got the same memory access runtime error issue. And have no idea about why at present. It seems the memory allocated in NewRuntime has...

You could implement your own `IBindingProcess` to define which types are available in JS/TS (and how they are being accessed). There is an example: `jsb_build/dotnetcore/CustomBinding.cs`.

Hi jo32, can you give more detail about the crash? I can't reproduce it in my environment. BTW, the generic parameter T of TypedScriptPromise is expected as a C# type....

Hi jo32, which commit are you currently using? It looks different from my version? ```cs protected virtual void Dispose(bool bManaged) { if (_context != null) { var context = _context;...

The ```Update``` call was moved into another MonoBehaviour ```JSBehaviourFull``` (I'm finding a better way to friendly switch between JSBehaviour and JSBehaviourFull (You can not change one into another in Unity...

I've updated the editor of JSBehaviour. It's easier to toggle whether the JSBehaviour is updatable or not. 

the error ```script runtime not ready``` is caused by uncertain execution order, it's difficult to resolve, because the script engine initialization process could/should be asynchronous (e.g waiting for the async...