4 ms·

Congratulations on the release! It looks very interesting. Does the GUI library embed a web-view, or does it use native controls? What's you estimate of when it

by edko 6y ago

Congratulations on the release! It looks very interesting. Does the GUI library embed a web-view, or does it use native controls? What's you estimate of when it will be available for Android and iOS?

amedvednikov 6y ago
No webview, that's not our way :) Although we do have a webview module for embedding the system's webview component. The GUI library renders everything, and the result looks very similar to the native widgets: https://raw.githubusercontent.com/vlang/ui/c2f802a137b5171dade1d5fdc364cd92d34e3ca7/examples/users/screenshot.png https://raw.githubusercontent.com/vlang/ui/c2f802a137b5171da... We are going to support native widgets, for example TextBox will be native due to accessibility and support for Chinese/Japanese/Korean/R2L input. However things like text rendering will always be handled by the V graphics library, since GDI+ is just way too slow (calculating text bounds is ~10 times slower than in V), and Apple's drawing API is not very nice to use, and it's also 2-3 times slower at rendering text.
- solarkraft 6y ago
  It's great to see accessibility/compatibility taken into account here, but are you only doing that for the text input or going further? E.g. can I copy text or use a screen reader?
  - amedvednikov 6y ago
    We will do this for the text rendered via V's graphics library as well, by using system accessibility APIs directly.
- csande17 6y ago
  > GDI+ is just way too slow (calculating text bounds is ~10 times slower than in V), and Apple's drawing API is not very nice to use, and it's also 2-3 times slower at rendering text. Does V's text library support the kinds of shaping and nested bidirectional layout needed to render Arabic text? I've heard that's a cause of a lot of complexity and slowness in text rendering, so stripping it out would be an easy performance win for people like me who can't read Arabic anyway.
amedvednikov 6y ago
As for Android/iOS, V itself has been running on phones for quite a while: https://www.youtube.com/watch?v=fIijYm1MfmI&feature=youtu.be https://www.youtube.com/watch?v=fIijYm1MfmI&feature=youtu.be The UI library will support mobile asap, since it'll receive lots of attention now that 0.2 is out, and we now have 2 people contributing to it.

by edko 6y ago

Congratulations on the release! It looks very interesting. Does the GUI library embed a web-view, or does it use native controls? What's you estimate of when it will be available for Android and iOS?

amedvednikov 6y ago

No webview, that's not our way :) Although we do have a webview module for embedding the system's webview component. The GUI library renders everything, and the result looks very similar to the native widgets: https://raw.githubusercontent.com/vlang/ui/c2f802a137b5171dade1d5fdc364cd92d34e3ca7/examples/users/screenshot.png https://raw.githubusercontent.com/vlang/ui/c2f802a137b5171da... We are going to support native widgets, for example TextBox will be native due to accessibility and support for Chinese/Japanese/Korean/R2L input. However things like text rendering will always be handled by the V graphics library, since GDI+ is just way too slow (calculating text bounds is ~10 times slower than in V), and Apple's drawing API is not very nice to use, and it's also 2-3 times slower at rendering text.

solarkraft 6y ago
It's great to see accessibility/compatibility taken into account here, but are you only doing that for the text input or going further? E.g. can I copy text or use a screen reader?
- amedvednikov 6y ago
  We will do this for the text rendered via V's graphics library as well, by using system accessibility APIs directly.
csande17 6y ago
> GDI+ is just way too slow (calculating text bounds is ~10 times slower than in V), and Apple's drawing API is not very nice to use, and it's also 2-3 times slower at rendering text. Does V's text library support the kinds of shaping and nested bidirectional layout needed to render Arabic text? I've heard that's a cause of a lot of complexity and slowness in text rendering, so stripping it out would be an easy performance win for people like me who can't read Arabic anyway.

amedvednikov 6y ago

As for Android/iOS, V itself has been running on phones for quite a while: https://www.youtube.com/watch?v=fIijYm1MfmI&feature=youtu.be https://www.youtube.com/watch?v=fIijYm1MfmI&feature=youtu.be The UI library will support mobile asap, since it'll receive lots of attention now that 0.2 is out, and we now have 2 people contributing to it.