11–18 of 18 posts
Can someone explain why this is useful over standard HTML/CSS or Bootstrap? Feels like I'm missing the point...
It looks like a lot of work and thought went into this library. I'd love to give it a shot except that I have no idea what the output might look like.
> htmlPy is a wrapper around PySide's QtWebKit library... Based on my experience using Qt (via PyQt) this is kind of puzzling, and the very limited doc doesn't do much to unpuzzle me. QtWebKit is basically a rendering engine wrapped as a Qt widget[0]. Where an entire app is based on a Qt main window, it can display HTML-encoded or Javascript-encoded content in a QWebView widget. QtWebKit also offers the "WebKit bridg…
Where an entire app is based on a Qt main window, it can display HTML-encoded or Javascript-encoded content in a QWebView widget. So it's another one of these "web everything" things... which in my experience seems more like "how to make your app consume 100x more memory and disk space that it should". What is with this aversion to native UIs that I've been seeing more of recently (and the tendency to invent controls…
Earlier quoted context omitted.
Where an entire app is based on a Qt main window, it can display HTML-encoded or Javascript-encoded content in a QWebView widget. So it's another one of these "web everything" things... which in my experience seems more like "how to make your app consume 100x more memory and disk space that it should". What is with this aversion to native UIs that I've been seeing more of recently (and the tendency to invent controls…
People are attracted to these solutions because they can build cross platform GUIs. Native UIs are great, no one is averse to them, people just don't want to write and maintain several different versions of the same thing in different languages.
Earlier quoted context omitted.
Where an entire app is based on a Qt main window, it can display HTML-encoded or Javascript-encoded content in a QWebView widget. So it's another one of these "web everything" things... which in my experience seems more like "how to make your app consume 100x more memory and disk space that it should". What is with this aversion to native UIs that I've been seeing more of recently (and the tendency to invent controls…
People are attracted to these solutions because they can build cross platform GUIs. Native UIs are great, no one is averse to them, people just don't want to write and maintain several different versions of the same thing in different languages.
htmlPy is meant for easy GUI development and integration with popular frameworks like Django for standalone app development. It adds to the memory usage of the application due to the use of QtWebkit.
If you are making a not-very-complex app and don't want to go to lot of trouble for making GUIs for standalone version, htmlPy is a great solution. But if your app is conservative about resources, doing lot of memory optimization or needs features which can't be done using HTML, probably best if you use native UI.
Earlier quoted context omitted.
People are attracted to these solutions because they can build cross platform GUIs. Native UIs are great, no one is averse to them, people just don't want to write and maintain several different versions of the same thing in different languages.
The irony is, Qt _IS_ a cross-platform GUI, where you build your UI once and it looks like Windows on Windows, Mac OS on Mac OS, and the look of whatever window manager on Linux.
Haha, I didn't realize that(not familiar w/ Qt). Was just responding to the "why are people averse to Native UIs" question
Earlier quoted context omitted.
People are attracted to these solutions because they can build cross platform GUIs. Native UIs are great, no one is averse to them, people just don't want to write and maintain several different versions of the same thing in different languages.
The irony is, Qt _IS_ a cross-platform GUI, where you build your UI once and it looks like Windows on Windows, Mac OS on Mac OS, and the look of whatever window manager on Linux.
Looks like, yes. Behaves like, not really (at least on Windows.) The few Qt apps I have certainly do not feel as responsive as the native ones, despite (mostly) looking that way, so it is rather awkward. They're noticeably laggier even in simple operations like displaying a menu, or responding to window resizing/moving.
from main import app
app.html