puter
puter copied to clipboard
HeyPuter
moving into live Desktop
Hey men I played around with puter.com I LOVED it, why not move into moving into live desktop application, take derbian and fit the UI of puter on top of it, please don't go ubuntu the parent company is a mother fucken evil. men am willing to help you make this come true. I love the web os, have you thought about making it available on cloud (like make it installable on cloud by users).
I was thinking an Arch-based distribution. We recently talked about Droplet Images and AMIs for Puter, that's definitely on the roadmap when we can spare a moment to do it.
Well arch or derbian any can work, I want to be part of that journey
On Tue, 6 Aug 2024, 3:55 am Eric Dubé, @.***> wrote:
I was thinking an Arch-based distribution. We recently talked about Droplet Images and AMIs for Puter, that's definitely on the roadmap when we can spare a moment to do it.
— Reply to this email directly, view it on GitHub https://github.com/HeyPuter/puter/issues/655#issuecomment-2270215761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQT5ZXLZGECQXQX7GCTWVFDZQAUKPAVCNFSM6AAAAABMAUE5DCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZQGIYTKNZWGE . You are receiving this because you authored the thread.Message ID: @.***>
this could be more stable and put to wide range of use case than just a browser. i think we can raise up a motion and if may people sign up we can proceed
I'm going to list a few prerequisites here for future reference:
- filesystem mountpoints are definitely needed for better local filesystem integration
- one of these two:
- for OS-native DE: Puter electron release; I already experimented with this a bit when I was working on YAET and the results were promising.
- for kiosk-mode browser: Greenfield Wayland Compositor integration in Puter.
and this brings to surface the first big decision: do we do OS-native desktop environment (i.e. Puter apps in a native window manager, integration with notification manager and other parts of the DE), or do we make the browser our "operating system above the kernel" and render everything in there?
I think we have to try both approaches to be sure to get it right, but this will require a greater amount of support from the community as well.
Good ideas! I support the idea for OS native DE, it is also important and necessary as specified that the community around Puter has to get involved.
On Tue, Aug 6, 2024 at 9:33 PM Eric Dubé @.***> wrote:
I'm going to list a few prerequisites here for future reference:
- filesystem mountpoints are definitely needed for better local filesystem integration
- one of these two:
- for OS-native DE: Puter electron release; I already experimented with this a bit when I was working on YAET https://github.com/HeyPuter/yaet and the results were promising.
- for kiosk-mode browser: Greenfield Wayland Compositor integration in Puter.
and this brings to surface the first big decision: do we do OS-native desktop environment (i.e. Puter apps in a native window manager, integration with notification manager and other parts of the DE), or do we make the browser our "operating system above the kernel" and render everything in there?
I think we have to try both approaches to be sure to get it right, but this will require a greater amount of support from the community as well.
— Reply to this email directly, view it on GitHub https://github.com/HeyPuter/puter/issues/655#issuecomment-2272002641, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQT5ZXMYIMJWXV5X33ORQQDZQEQG5AVCNFSM6AAAAABMAUE5DCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZSGAYDENRUGE . You are receiving this because you authored the thread.Message ID: @.***>
This one can be started on boot from the shell without any desktop manager required (Debian: Autologin to shell, start Framebuffer-browser using .bashrc): https://github.com/e1z0/Framebuffer-browser
I'm currently building a Raspberry PI 4 image which autoboots to puter.
This one can be started on boot from the shell without any desktop manager required (Debian: Autologin to shell, start Framebuffer-browser using .bashrc): https://github.com/e1z0/Framebuffer-browser
I'm currently building a Raspberry PI 4 image which autoboots to puter.
I'm really curious to see how this performs! On my laptop I did a quick test and it takes 0.0097 seconds to fill the framebuffer with blue pixels... so 103 FPS - not bad! What's the drawback? I'm guessing 3D graphics wouldn't be available this way. What happens if you open something that uses WebGL?
I didn't know about /dev/fb0 before and I have been having too much fun with this new information. Behold, framebuffer cat!
This one can be started on boot from the shell without any desktop manager required (Debian: Autologin to shell, start Framebuffer-browser using .bashrc): https://github.com/e1z0/Framebuffer-browser I'm currently building a Raspberry PI 4 image which autoboots to puter.
I'm really curious to see how this performs! On my laptop I did a quick test and it takes 0.0097 seconds to fill the framebuffer with blue pixels... so 103 FPS - not bad! What's the drawback? I'm guessing 3D graphics wouldn't be available this way. What happens if you open something that uses WebGL?
fbrowser uses qt5webengine for displaying the content, which sadly throws an "This plugin does not support createPlatformOpenGLContext!" error.
Let me know when the Pi works. Would love to post it on our social media 🔥
Here it is: https://drive.google.com/file/d/13V9P9Y33HlK5Hl6kc4OIC_u60qoMYVF9/view?usp=sharing
The image will automatically expand the partition on first start and reboot once to do so. Default user is "puter" with the password "puterbooter". Please change it after first boot.
SSH access is enabled by default. To change the URL for using a self-hosted puter instance, edit run_browser.sh on the boot partition.
It's the first version, so some stuff like sourcefiles is still on the image.
QEMU doesn't want to boot this so I guess I'll have to wait until I have access to my physical rpi
QEMU 不想启动它，所以我想我必须等到我可以访问我的物理 rpi
I encapsulated the front-end part of the Puter into a client using Energy.
