![]() If you find PySimpleGUI useful, please consider sponsoring the project on GitHub or BuyMeACoffee. Duplicating Excel in every detail is an example of something not well suited for PySimpleGUI. It depends on the details of your program. It's difficult to define exactly which programs are well suited for PySimpleGUI and which are not. By definition, PySimpleGUI implements a subset of the underlying GUI frameworks' capabilities. Some programs are not well-suited for PySimpleGUI however. While the architecture is simple to understand, it does not necessarily limit you to only simple problems. Your code is not required to have an object oriented architecture which makes the package usable by a larger audience. Further simplification happens by changing event handling from a callback-based model to a message passing one. The window definition is simplified by using Python core data types understood by beginners (lists and dictionaries). Transforms the tkinter, Qt, WxPython, and Remi (browser-based) GUI frameworks into a simpler interface. Sort of like running X on top of Win32, or Win32 on top X.īut the posibilities of higher level and lower level windowing system are really unlimited - mix and match, basically.C967880E71496470E40E click here to visit course page In other words, a windowing system - on top of another windowing system. Note that I am sure there are probably a whole lot of other windowing systems out there that also support these, let's call them "back-end" (for lack of better terminology) pre-existing windowing systems. Which makes it interesting and worthy of study. Most notably the source files that start with 'scr_', and of those most notably: scr_sdl2.c, scr_win32.c, scr_x11.c, scr_djvesa.c, scr_fb.c - we see that this windowing system can apparently run on top of an existing windowing system, whether that system is SDL2, Win32, X11, VESA, Linux's framebuffer - or several others. Project mention: Tinyx – resurrected Xvesa from the depths of Git history | | WebView2 has a very large feature-set though which make take a while to implement for macOS. Unless WebView2 for macOS arrives, which would have a more sane cross-platform story. Maybe because WebKit didn't have a build for Windows was an issue too.īut now that we have Bun, perhaps it's time that WebKit becomes that browser target of choice for desktop apps on macOS. The fact that Node used V8 made Chromium the choice, and that Node being called from the renderer was the original way of working. It makes me think that perhaps WebKit was the better choice for embedding. > it's difficult to reuse their work.if another WebKit-based application or another port wanted to do multiprocess based on Chromium WebKit, it would be necessary to reinvent or cut & paste a great deal of code. ![]() The fact that Chromium Embedded Framework exists and is third-party makes me think that Chromium wasn't designed for being embedded, and Electron is filling that gap. In this case, why do we still need Electron? Why does it have to be tied to V8/Node.js? Tools like Tauri use a simple cross-platform single-header abstraction called webview.h.Įlectron no longer allows Node.js to be called from renderer processes, all communication with Node.js is done via IPC. ![]() Windows has WebView2 based on Edge/Chromium. Project mention: Ask HN: Do we still need Electron? | | Įach platform has it's own webview control available as a shared library installed with the OS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |