about pynecone
Opened this issue · 1 comments
I know it's irrelevant but don't you think pynecone is more suitable for desktop than for web ?
I don't know why it hasn't proper tools for desktop packaging .
can it be combined with htag ?
no ... It can't be combined with htag.
They share a lot of thing, in the concept field. But pynecone is a different beast, which need nodejs in the background.
whereas htag is only pure python. Make it easier to embbed everywhere, where html/js is render'able (and py runs).
From the ground, pynecone is designed for web apps as first class citizen, whereas htag (the core) is a simple component (rendering/interaction) manager. (the "rendering" part is delegated to "htag runners").
htag is a lot more modulable, and does'nt come with ui components ootb (which is less sexy ;-) ). Whereas pynecone comes with a lot of ui components ready-to-use, heavily based on nodejs interactions (vuejs behind ?!).
It's really two different beasts.
Pynecone is designed for the web, btw it should be possible to embbed it in cef/electron thing, with nodejs. But not with htag's help.
htag can easily be embbeded in "desktop app" , thru a "runner"... using the pywebview lib (which is not really a full chrome cef, and have limitations ... don't know if it can run complex html/js interactions in a nodejs context) ... or using a "faked" chrome (chrome instance runned in app-mode (headless)).