Nathan Graule

I initially had interleaved float arrays as the buffer type in my internal audio engine for Wavr, but changed it to a custom audio buffer similar to `vst-rs`'s because I...

Hi! I've had this problem too and decided to fork it under another name. Check out [Django Populate](https://gitlab.com/solarliner/django-populate), and `pip install django-populate`.

That's what the prompt is doing. Users don't really care or want to know the specifics of AppImage vs. other means of installation is. They want their app accessible like...

Also, I should add that it being limited is the point. Too much text or information and the user will more likely refrain from doing anything rather than read.

But what's the worst that could happen as a result here? The launcher moves the AppImage file into `~/Applications` and copies the desktop file from within it. That's nothing so...

¯\\\_(ツ)_/¯ man, please put forward arguments on why having a "warning dialog" (that's the name I'll stick with unless you tell me what it is) is good in this case,...

> you're double clicking an AppImage, so anything you'd be prompted there should eventually lead to an execution of that app That is a good point. My point of view...

> "reverse" is the wrong term. What we call "integration" is basically a) move into `~/Applications` and b) integrate into launcher. If you want to integrate, both actions will be...

> Check how it works on the Mac. No such dialogs needed at all. Much more elegant. No, instead the user has to know where to put the .app file....

> If done wrong, it also limits the (perceived) flexibility. E.g., can I put an application onto a network share rather a local machine? How about a DVD? USB drive?...