Author here: This project is incredibly buggy and immature at this point and not really intended to be run yet. I am blown away by the reception. Notes for people trying to run this: - it is MacOS only - the window bounds are hardcoded for my system, because GPUI lacks a way to center a fixed size window - the accessibility is pretty much non-existent. GPUI doesn’t provide an accessible text input yet, so this is a h…
I appreciate you adding the caveats section to the README:) It's nice to clarify those things up front
Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
11–20 of 44 posts
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#12Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#13Build fails for me on Linux. It appears GPUI is only intended for mac
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#14First I thought "well, zed is just another editor, pfff" but the more news I see about it, the more it gets relevant. Especially the GPUI because it gets an alternative to Electron and Taurin. And rust..
now imagine if zed embedded a scheme instance for writing plugins....
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#15Posting this primarily because I frequently run into people who use kde but have never used krunner.
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#16Author here: This project is incredibly buggy and immature at this point and not really intended to be run yet. I am blown away by the reception. Notes for people trying to run this: - it is MacOS only - the window bounds are hardcoded for my system, because GPUI lacks a way to center a fixed size window - the accessibility is pretty much non-existent. GPUI doesn’t provide an accessible text input yet, so this is a h…
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#17First I thought "well, zed is just another editor, pfff" but the more news I see about it, the more it gets relevant. Especially the GPUI because it gets an alternative to Electron and Taurin. And rust..
GPUI, by all indications, looks like it's potentially got legs as a UI framework - the team behind it seem driven and I overall do like their approach. I'm not downing on GPUI and I do hope it succeeds, let's just avoid the hyperbole.
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#18Author here: This project is incredibly buggy and immature at this point and not really intended to be run yet. I am blown away by the reception. Notes for people trying to run this: - it is MacOS only - the window bounds are hardcoded for my system, because GPUI lacks a way to center a fixed size window - the accessibility is pretty much non-existent. GPUI doesn’t provide an accessible text input yet, so this is a h…
Nice project! How was your experience building with GPUI? How does it compare to other native GUI libs, if you’ve used any?
Pros:
- GPUI is heavily inspired by Tailwind, which made me productive pretty quickly.
- I love the tight coupling between the Rust structs and the rendering. Makes for nice and reusable components similar to Svelte.
- It's obviously purpose built for performance/latency and it shows. I haven't optimized Loungy at all, but it feels way smoother than the previous Tauri version.
Cons:
- GPUI is very obviously still in it's infancy. There isn't even a text input!
- There is no animation system. This is a huge drawback compared to CSS/Svelte
- There is no global hotkey API like in Tauri. But I could just take the hotkey crate by the Tauri guys and make it work for GPUI.
Re: Loungy: An Application Launcher Written with GPUI, the Zed GPU UI Framework
#19Author here: This project is incredibly buggy and immature at this point and not really intended to be run yet. I am blown away by the reception. Notes for people trying to run this: - it is MacOS only - the window bounds are hardcoded for my system, because GPUI lacks a way to center a fixed size window - the accessibility is pretty much non-existent. GPUI doesn’t provide an accessible text input yet, so this is a h…
Could you elaborate on this part? As I recall, communication between webview and the node.js backend was my main gripe with Electron as well. Sounds like it hasn't been solved in Tauri.