Earlier quoted context omitted.
I summon Google Assistant and press the what's on my screen button, that one usually allows me to select text even when the apps don't.
The layers of extreme complexity in this situation are astounding. The app has some text internally, it renders it by rasterizing fonts to a bitmap, the OS takes the bitmap and composites it within the wider UI. Google Assistant grabs a screenshot of the fully composited, post-processed OS UI, sends it over the internet to a server, which uses an OCR model to read all the text, and a different model to work out which…
Egui – An immediate mode GUI written in Rust
81–90 of 143 posts
Re: Egui – An immediate mode GUI written in Rust
#82Earlier quoted context omitted.
You generally can't copy text in native UIs unless the app author goes to extra effort to allow it. It's really the web that is the odd one out here because it was originally intended for documents.
> You generally can't copy text in native UIs You mean mobile apps, right? With desktop UIs this has traditionally never been an issue.
Re: Egui – An immediate mode GUI written in Rust
#83I'm afraid that until browsers provide APIs to help render fonts with sub-pixel rendering (note: that would add fingerprinting bits), canvas-based UI rendering libraries will always have a big disadvantage (vs DOM-based) on all but the high pixel density devices. (This is well known by the egui authors, which is a great library!)
Plus modern displays can have all sorts of weird subpixel layouts so it's not as simple as it used to be.
Re: Egui – An immediate mode GUI written in Rust
#84Demo pages like this are fun, and technically impressive when compiled to a browser environment. But I suffer from a lack of imagination so these widget demos don't really help me envision what an egui-powered app can do or might look like. Does anyone have any examples of fun things that use egui?
Re: Egui – An immediate mode GUI written in Rust
#85Earlier quoted context omitted.
I use it in Sharpview. It's really for GUI programs, not web pages. It redraws everything on every frame, so it's most useful for 2D overlays on 3D game-type programs. For that, it's pretty good. It's one pass. As a result, layouts which are ordered left to right and top to bottom work well, but ones which displace or resize items above or to the left don't work well. Egui tries to fix things up on the next frame, th…
> It redraws everything on every frame, so it's most useful for 2D overlays on 3D game-type programs. So it's not a GUI. In my book a GUI only redraws when something changes, to save the user's power.
Afaik nobody is forcing to rerender the ui layer if nothing changes, though. Just render it to a texture and compose … no need to put everything to the same render target?
Re: Egui – An immediate mode GUI written in Rust
#86Re: Egui – An immediate mode GUI written in Rust
#87Am I the only one that has a problem with all non dom/html renderers that I can't copy the text on mobile? The same with flutter etc, it's such a regression in my eyes but nobody prioritizes it.
Re: Egui – An immediate mode GUI written in Rust
#88Demo pages like this are fun, and technically impressive when compiled to a browser environment. But I suffer from a lack of imagination so these widget demos don't really help me envision what an egui-powered app can do or might look like. Does anyone have any examples of fun things that use egui?
Re: Egui – An immediate mode GUI written in Rust
#89Earlier quoted context omitted.
> worse/impossible adblocking Obviously that's not a downside from a software developer perspective.
I’m a software developer, and it seems like a positive to me? Why wouldn’t you want the ability to post-facto manipulate with script the interfaces you are presented with?
Re: Egui – An immediate mode GUI written in Rust
#90Earlier quoted context omitted.
I summon Google Assistant and press the what's on my screen button, that one usually allows me to select text even when the apps don't.
The layers of extreme complexity in this situation are astounding. The app has some text internally, it renders it by rasterizing fonts to a bitmap, the OS takes the bitmap and composites it within the wider UI. Google Assistant grabs a screenshot of the fully composited, post-processed OS UI, sends it over the internet to a server, which uses an OCR model to read all the text, and a different model to work out which…