What issues have you had? Ive been using orca for about a year without any issues all. I'm running Mint, both stable and beta branch have been without issues for me.
Appimage doesn't start because it relies on a system package that does exist anymore, dialogs with grey text on grey backgrounds in dark mode, stl repair not included...
Flatpak is in the works but honestly and hope that helps bit I get better prints out of prusaslicer for some reason so not holding my breath or anything.
The image just isn't being built correctly which is more a problem with appimages but the fact it's still broken... Linux is clearly a neglected platform for them.
All the problems I listed have bug reports just nothings happening to fix them.
Libwebkit isn't actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.
The rest of this comment is going to necessarily be nerdy Linux internals. sorry.
Unfortunately, I'm pretty sure chromium includes it inside it's binary and does provide or use any webkit libraries.
Orca uses it internally for it's browser so it won't start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.
Appimage is one of the ways you get around this distro problem by including the versions of libraries. That's why they're so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.
Orca hasn't bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can't start.
That's a lot but I hope it explains the problem better.
I would like to help but my personal computer doesn't currently have enough memory to compile orca so back to just watching warning people it's a coming problem for them too.
You're four forks deep now
Slic3r to Prusa Slicer to Bamboo's slicer to Orca. It also borrowed a lot of ideas from Super Slicer. Since it's open source, and has been gaining some momentum, it seems to have a decent amount of contributors
Why Orca?
all the features you know and love from things up the tree
a revamped UI
built in tuning tests (temp tower, extrusion multiplier, volumetric flow, pressure advance, etc)
The UI of Prusa slicer is hot garbage though. I started with prusa slicer and moved to orca after a few months. Orca is a much nicer experience, and the built-in test-models (temp towers etc.) are nice.
In find the location and grouping of parameters more intuitive in orca. I always had to look through several tabs to find the parameter I wanted to adjust when I was using prusa, it was never where I thought it should be.
I guess it's not relevant for your setup, but I like rofi because there is a fork that works in Wayland, and it's the only Wayland window switcher I have found that isn't tied to a specific window manager.
That was the idea! I came across it looking for something else. I've been using a blueprint for a while (since you haven't even looked yet) that will pull when the alarm is sounding and snoozed and such.
I have moved back to Node Red and made it myself there now though. What I use it for is I set the alarm to ramp up volume after 3 minutes, but the alarm also triggers my lights turning on.
Since the lights usually wake me up I usually have a silent alarm clock, meaning I don't wake The Wife at 5am when I get up for work.
My son heard about it so now he also wakes up to the lights coming on.
You can use that to start your morning automations if you're so inclined, so when your alarm goes off and the Kitchen motion sensor is triggered for your morning cup of Joe, you can fire your morning reminders and traffic info
One limitation that may or may not matter for your particular use case: I don't believe that Xephyr has a mechanism to do pass-through 3d acceleration. So if you're gonna have everything go through Xephyr, one constraint is that any window that you're sticking in a dwm is just gonna have access to a plain-Jane framebuffer.
If you're only managing terminal windows -- you mention tmux as an alternative, so that may be what you're going for -- then that may not be a concern, though there are some accelerated virtual terminal software packages.
EDIT: I have not done this myself, but it sounds like it's possible to run nested compositors inside Wayland.
I don't know if that can be used in the same way, but running dwl -- like the X11 dwm window manager, but a Wayland compositor -- inside a host Wayland session might work, if you're using Wayland rather than X11 as the "host" environment. I'd guess that that wouldn't have the same limitation.
Sorry yeah I've gotten so used to building android apps its probably more complicated than I think.
Open android studio. Select new project from version control. Enter the url of the github and click enter. This will download the source code and open it to view/edit. Android studio should then prepare dependencies etc, it will say something like "building gradle" in the bottom corner. Wait for that to finish then in the toolbar at the top of the screen there is a dropdown labeled build which has the different build options. There should be one called "build apk" this will build the app.
Now that I've written this out it does seem more complicated that I thought.
Wow, thank you so much!, that's great, nice concise instructions, something I can certainly follow.. Will have go tomorrow as I'm just about to turn in...
Thanks again 👍🏼
whoa, I installed Android Studio, did all that, waited a bunch and it... worked? just like that? is that what you computer people do with computers at work? do I apply for a six figure job now?
github.com
Hot