pywebview VS sciter

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.

> wondering if css and svg could be used as abstraction over graphics and UI libraries

There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com

> I wonder how hard it was to implement css. I've heard it can be pretty complex.

It was hard, but the biggest barrier is the obscurity of the knowledge.

Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.

But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).

[1] https://gitlab.gnome.org/GNOME/pango/

otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.

[1] https://sciter.com

I've still never used it but I've long been curious about Sciter:

https://sciter.com

These bullet points are exactly what I did in Sciter (https://sciter.com)

- Windowing

-- Tabs

-- Menus

-- Painting

-- Animation

-- Text

-The compositor

-Handling input

-- Pointer input

-- Keyboard input

- Accessibility

- Internationalization and localization

- Cross-platform APIs

- The web view

- Native look and feel

On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.

I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.

https://sciter.com/