v0.113.0

minor evolution :
The PyScript Runner don't need anymore the "js.window" ! So, its run() method look likes others ;-)

now you can run your App in a pyscript/html page like this :

from htag.runners import PyScript
PyScript( App ).run() 

BTW, the run() method is retro compatible with old ways.

v0.112.0

The websocket is now initialized with "//", and don''t try anymore "ws://" or "wss://". Now it uses the js mechanism to set the websocket ssl or not, depending on ssl or not.

It's a lot simpler (like in old days of v0.103), and a lot more robust in all cases ;-)

v0.111.2

a little fix ;-)

v0.111.1

Fix for compatibily with py<3.9

v0.111.0

Add real argument parser in command line, see :

$ python3 -m htag -h
usage: htag [-h] [--host HOST] [--port PORT] [--gui | --no-gui] [--dev | --no-dev] [file]

Entrypoint to help you <to create> or <to run> a htag'app. If a [file] is given: it will try to run it (using dev mode), else it will create an empty htag file. The options are just
here for the run mode.

positional arguments:
  file             if present, the htag'file will be runned (reload/debug mode)

options:
  -h, --help       show this help message and exit
  --host HOST      Host listener (default: 127.0.0.1)
  --port PORT      Port number (default: 8000)
  --gui, --no-gui  Automatically open interface in a browser (default!)
  --dev, --no-dev  Run in dev mode (reload+debug) (default!)

v0.110.0

The "Runner" now try to connect to websocket using "ws://" (first), and fallback to "wss://" (second).
Thus, this new Runner should work OOTB on repl.it, idx.dev or glitch.com, without the need of htagweb.

On theses platforms, the webserver is over SSL. So you'll need to use htagweb, where you can force the socket to use SSL with an option. But you'll need to explicitly force the server to use one or the other. (BTW it makes sense to use htagweb if you want to serve your app for many different users ... htag default runner is only for one user at a time)

Now, the default htag "Runner" should work, because it will implicitly try one and fallback to the second.

By default, it try "ws://", because the goal of the default Runner, is for desktop/android app, where SSL is not mandated (one client, one server). But now, it should work implicitly OOTB in a ssl webserver context.

(Perhaps, in the future, htagweb will introduce the same kind of mechanism ... but now, you should explicitly define it in the htageweb runner ... but I don't wanted to add this kind of option in the default htag Runner ... KISS first!)

UPDATE :

• it's validated https://idx.google.com/ : it works now OOTB ;-)
• the trouble seems more complex for repl.it ;-( ... need to dig that

v0.103.0

prepare the import "ui" for the new htagui version >=0.3

nothing else

v0.102.0

declare an "htag.ui" namespace for objects defined in "htagui" package

v0.101.0

Runner is now in htag namespace

technically, you can do

from htag import Tag, Runner

...

no more need to import from "htag.runners"

v0.100.1 "fix ev"

minor fixes

• the autostop server (aka "watchdog"), when UI close : works better (it wait the 1st cnx before watching for suicide)
• the "ev" mechanism works well in all cases (see previous release bug)
• new manual_tests_event_0.100.1.py which tests all kinds of event bindings in one shot ;-) (todo: will be in selenium tests later)