pywebview VS JUCE

In case anyone else is unfamiliar:

> pywebview uses native GUI for creating a web component window: WinForms on Windows, Cocoa on macOS, QT or GTK on Linux and Kivy for Android.

https://github.com/r0x0r/pywebview

- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview)： Base on [pywebview](https://pywebview.flowrl.com/) using Python，the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。

Somehow related, I've been using pywebview for some internal tools: https://github.com/r0x0r/pywebview

Probably not as full-featured as Electronjs, but since we have a bunch of python scripts to convert to desktop apps, it's very useful.

I've been on a blitz experimenting with pywebview (electron but for Python) and a ReactJS UI.

The native mode uses pywebview under the hood which has libs for running on several platforms. Pyinstaller will pull these dependencies in. If you want more info on which platforms are supported by pywebview, check this directory: https://github.com/r0x0r/pywebview/tree/master/webview/lib

For reference to anyone not familiar - https://github.com/r0x0r/pywebview

import webview window = webview.create_window('Woah dude!', 'https://pywebview.flowrl.com') webview.start()

pywebview (https://github.com/r0x0r/pywebview) is an excellent suggestion and is already being used in NiceGUI to create a native desktop window with "native=True" option (see http://127.0.0.1:8080/documentation#ui_run).

Thanks for sharing. The issue is tracked at https://github.com/zauberzeug/nicegui/issues/576. But it looks like something which originates from the pywebview lib which is used to provide the native mode.

Personally, I started by writing externals for Pure Data, then started to contribute to the care. Later I took the same path for SuperCollider.

The more typical path, I guess, would be to start with simple audio plugins. Have a look at JUCE (https://juce.com/)!

Realtime audio programming has some rather strict requirements that you don't have in most other software. Check out this classic article: http://www.rossbencina.com/code/real-time-audio-programming-...

Check out https://juce.com in the meantime

You can definitely start putting C++ into your embedded projects, and get familiar with things in an environment in which you're already operating. A lot of great C++ code can be found with motivated use of, for example, the platformio tooling, such that you can see for yourself some existing C++ In Embedded scenarios.

In general, also, I have found that it is wise to learn C++ socially - i.e. participate in Open Source projects, as you learn/study/contribute/assist other C++ developers, on a semi-regular basis.

I've learned a lot about what I would call "decent C++ code" (i.e. shipping to tens of thousands, if not hundreds of thousands of customers) from such projects. I would suggest finding an open source C++ project, aligned with your interests, and study the codebase - as well as the repo history (i.e. gource) - to get a productive, relatively effortless (if the interests align) boost into the subject.

(My particular favourite project is the JUCE Audio library: https://juce.com/ .. one of many hundreds of great projects out there from which one can also glean modern C++ practices..)

Respect for the others here who recommend C but I think they’re possibly masochists. If anything JUCE, which uses C++ is in my opinion far more approachable.

Here's a link to their website: https://juce.com/

It seems like most audio plug-ins are built in C++ inside an audio coding program called JUCE, so maybe if I could open up the exisiting code inside that and then output it as an AU instead of a VST that could work.

C++ has https://juce.com/, I think.

Open source rule https://juce.com/