6 ms·

The TextEdit example is super impressive. I don't remember many WYSIWYG editors being so responsive. http://example.qt.io/qt-webassembly/widgets/richtext/texte

by yoavm 8y ago

The TextEdit example is super impressive. I don't remember many WYSIWYG editors being so responsive. http://example.qt.io/qt-webassembly/widgets/richtext/textedit/textedit.html http://example.qt.io/qt-webassembly/widgets/richtext/textedi...

r0ze-at-hn 8y ago
So the question is can I run the demo Qt browser in webassembly in my browser? Then I could write my html and not have to worry about which end user browser it runs on as long as the end user browser supports webassembly ;)
- llornkcor 8y ago
  If it compiles, you might run into memory issues
pier25 8y ago
It really is!
seba_dos1 8y ago
Unlike most of web editors, this one doesn't have to operate on DOM at all.
- wlesieutre 8y ago
  One tradeoff of this is that the text smoothing is wrong (or at the very least, inconsistent with everything else on my computer, and does not respect my text smoothing settings). Personally I hope this "screw the OS, I'm rendering everything myself" strategy doesn't take off on account of that. It's like the web version of godawful cross platform Java apps from the 90's where they stick the Mac version's menubar inside the window because it looks right on their machine. I wonder if screenreaders work for reading and navigating this. EDIT: This comment comes across as totally negative, so I'd like to amend that I think there are good use-cases for it. Games or more visual things, sure, I don't care if the text isn't a pixel perfect match to everything else on my computer. But for things where reading or writing text is the primary purpose, having the same font face at the same size render differently from the rest of my computer is not something I want to see becoming common.
  - toyg 8y ago
    > I hope this "screw the OS, I'm rendering everything myself" strategy doesn't take off on account of that. Dude, that battle was lost when Electron gained traction. I hate it with all my heart, but it's a sad reality.
    - OskarS 8y ago
      Electron uses platform-native font rendering. It's just Chromium, and Chromium uses Uniscribe on Windows and CoreText on Mac. Compare Chrome on Windows and Mac, you'll see the difference in text rendering.
      - badsectoracula 8y ago
        Don't worry, people will simply start using Qt for WebAssembly with Electron to fix that issue.
      - jcelerier 8y ago
        uh... what ? the text on all electron apps looks like a blurred shit on my machine, and does not look at all like the text settings I apply.
        deleted 8y ago
        [deleted]
      - toyg 8y ago
        Nobody cares. Developers use Electron because it gives consistent results across platforms, not because it looks native. If Chromium were to switch to a custom font renderer that looks exactly the same on all platforms, no developer using Electron would care - in fact, they would probably like it even more.
        OskarS 8y ago
        I care! I care a lot! Good font rendering makes SO much difference in how stuff looks. No joke: font rendering is the number one reason I prefer the look of macOS over Windows (especially now since WSL exists). I realize I'm a weirdo font nerd and probably alone in that stance, but working with computers mean staring at text on a screen for hours and hours every day. It fucking better be rendered right.
- deleted 8y ago
  [deleted]
TheAceOfHearts 8y ago
I'm on macOS and unfortunately it doesn't seem to support many of the native platform's hotkeys, nor does scrolling work with a trackpad. But it's still a really impressive feat, hopefully they can continue improving on it!
- toyg 8y ago
  The basic ones look fine to me. It even opens the emoji keyboard (although input then doesn't work). Considering it's a cross-platform widget toolkit running in a cross-platform sandbox (the browser, Firefox here), it's actually pretty good.
- zem 8y ago
  mouse scroll wheel doesn't work either (on linux + chrome). but very nice and responsive.
  - llornkcor 8y ago
    mouse wheel support was added after this blog and its tech preview
- favorited 8y ago
  It also doesn't work with VoiceOver at all... :(
- llornkcor 8y ago
  mouse wheel and trackpad support was added, but did not make it into that blogs tech preview
zokier 8y ago
..it is buggy as hell? For an official example it is bit embarrassing how bad it is.
- llornkcor 8y ago
  this is an early tech preview, not at release level.
kllrnohj 8y ago
It's a lot less responsive than something like WordPad, which has a comparable feature set. All those extra text features that most WYSIWYG editors add do actually add up, especially common programmer features like syntax highlighting.
ttflee 8y ago
On macOS safari shows a hint “this webpage is using significant energy. Closing it may improve the responsiveness of your mac”. And the app is using 100% of time on a core, apparently.
singularity2001 8y ago
The font looks horrible, even after disabling zoom plugin.
thiht 8y ago
Really? HTML/JS editors based on the standard contentEditable attribute seem as responsive to me (and they don't break basic browser features like scrolling) For reference: http://jakiestfu.github.io/Medium.js/docs/#invoke http://jakiestfu.github.io/Medium.js/docs/#invoke
hajile 8y ago
VS Code also uses canvas elements for their terminal. I suspect we'll see VS Code (and perhaps Atom as they mentioned it somewhere) moving the main editor window to canvas as well. Overall, I think that's a decent trade-off. Most of the UI is quick, easy, and (potentially) extensible using HTML while the performance-sensitive parts move to what's basically a raw buffer. https://code.visualstudio.com/blogs/2017/10/03/terminal-renderer https://code.visualstudio.com/blogs/2017/10/03/terminal-rend...

by yoavm 8y ago

r0ze-at-hn 8y ago

So the question is can I run the demo Qt browser in webassembly in my browser? Then I could write my html and not have to worry about which end user browser it runs on as long as the end user browser supports webassembly ;)

llornkcor 8y ago
If it compiles, you might run into memory issues

pier25 8y ago

It really is!

seba_dos1 8y ago

Unlike most of web editors, this one doesn't have to operate on DOM at all.

wlesieutre 8y ago
One tradeoff of this is that the text smoothing is wrong (or at the very least, inconsistent with everything else on my computer, and does not respect my text smoothing settings). Personally I hope this "screw the OS, I'm rendering everything myself" strategy doesn't take off on account of that. It's like the web version of godawful cross platform Java apps from the 90's where they stick the Mac version's menubar inside the window because it looks right on their machine. I wonder if screenreaders work for reading and navigating this. EDIT: This comment comes across as totally negative, so I'd like to amend that I think there are good use-cases for it. Games or more visual things, sure, I don't care if the text isn't a pixel perfect match to everything else on my computer. But for things where reading or writing text is the primary purpose, having the same font face at the same size render differently from the rest of my computer is not something I want to see becoming common.
- toyg 8y ago
  > I hope this "screw the OS, I'm rendering everything myself" strategy doesn't take off on account of that. Dude, that battle was lost when Electron gained traction. I hate it with all my heart, but it's a sad reality.
  - OskarS 8y ago
    Electron uses platform-native font rendering. It's just Chromium, and Chromium uses Uniscribe on Windows and CoreText on Mac. Compare Chrome on Windows and Mac, you'll see the difference in text rendering.
    - badsectoracula 8y ago
      Don't worry, people will simply start using Qt for WebAssembly with Electron to fix that issue.
    - jcelerier 8y ago
      uh... what ? the text on all electron apps looks like a blurred shit on my machine, and does not look at all like the text settings I apply.
      - deleted 8y ago
        [deleted]
    - toyg 8y ago
      Nobody cares. Developers use Electron because it gives consistent results across platforms, not because it looks native. If Chromium were to switch to a custom font renderer that looks exactly the same on all platforms, no developer using Electron would care - in fact, they would probably like it even more.
      - OskarS 8y ago
        I care! I care a lot! Good font rendering makes SO much difference in how stuff looks. No joke: font rendering is the number one reason I prefer the look of macOS over Windows (especially now since WSL exists). I realize I'm a weirdo font nerd and probably alone in that stance, but working with computers mean staring at text on a screen for hours and hours every day. It fucking better be rendered right.
deleted 8y ago
[deleted]

TheAceOfHearts 8y ago

I'm on macOS and unfortunately it doesn't seem to support many of the native platform's hotkeys, nor does scrolling work with a trackpad. But it's still a really impressive feat, hopefully they can continue improving on it!

toyg 8y ago
The basic ones look fine to me. It even opens the emoji keyboard (although input then doesn't work). Considering it's a cross-platform widget toolkit running in a cross-platform sandbox (the browser, Firefox here), it's actually pretty good.
zem 8y ago
mouse scroll wheel doesn't work either (on linux + chrome). but very nice and responsive.
- llornkcor 8y ago
  mouse wheel support was added after this blog and its tech preview
favorited 8y ago
It also doesn't work with VoiceOver at all... :(
llornkcor 8y ago
mouse wheel and trackpad support was added, but did not make it into that blogs tech preview

zokier 8y ago

..it is buggy as hell? For an official example it is bit embarrassing how bad it is.

llornkcor 8y ago
this is an early tech preview, not at release level.

kllrnohj 8y ago

It's a lot less responsive than something like WordPad, which has a comparable feature set. All those extra text features that most WYSIWYG editors add do actually add up, especially common programmer features like syntax highlighting.

ttflee 8y ago

On macOS safari shows a hint “this webpage is using significant energy. Closing it may improve the responsiveness of your mac”. And the app is using 100% of time on a core, apparently.

singularity2001 8y ago

The font looks horrible, even after disabling zoom plugin.

thiht 8y ago

Really? HTML/JS editors based on the standard contentEditable attribute seem as responsive to me (and they don't break basic browser features like scrolling) For reference: http://jakiestfu.github.io/Medium.js/docs/#invoke http://jakiestfu.github.io/Medium.js/docs/#invoke

hajile 8y ago

VS Code also uses canvas elements for their terminal. I suspect we'll see VS Code (and perhaps Atom as they mentioned it somewhere) moving the main editor window to canvas as well. Overall, I think that's a decent trade-off. Most of the UI is quick, easy, and (potentially) extensible using HTML while the performance-sensitive parts move to what's basically a raw buffer. https://code.visualstudio.com/blogs/2017/10/03/terminal-renderer https://code.visualstudio.com/blogs/2017/10/03/terminal-rend...