minggo
Yep, i think so.
As discussed, may let developers encode the url if needed.
It is better to provide a function to encode the string.
What i mean is to encode the space, as did in the PR.
> I have always used unsigned int to store window size. There are some graphics/system APIs which take float as input, but AFAIK they only use the integer part. Yep,...
We can depend on Appcompat, but these resources are not needed. So should find a way to remove these resources when generating apk.
As we haven't integrated game text input, so we should remove Appcompat. When we decide to integrate game text input, then we can add Appcompat back.
Thanks @oahc09
Can not make decision currently.
Does it affect native usage? In native, we just use IntrusivePtr to control the lifecycle.