v0.9.2

now, the class "body.htagoff" comes with a default predefined style (set cursor not-allowed for all body childs). It will be the default, and you can surcharge it for your needs.

Full Changelog: v0.9.1...v0.9.2

v0.9.1

Same as previous, but without the autoreconnect feature on ws loss.

Full Changelog: v0.9.0...v0.9.1

v0.9.0

WARNING : this version try to reconnect WS on WS loss. I don't really sure, that this behaviour still be the default. Because, in big/complex apps (imagine an online code editor (my case)) ... you may loose your work while editing, when ws disconnects (because it will destry/recreate context). It's not really cool ... Currently it's just here for my tests IRL. You should use the 0.8.1 or the 0.9.1

Add some features :

• try to reconnect (reinit 1st cnx) on socket disconnexions
• toggle "body.htagoff" class when disconnected (when interactions produce errors in all cases).
• fullerror is now transmitted when in debug mode (so full python traceback is emitted when calling window.error on js side). It's got sense in debug mode.

Full Changelog: v0.8.1...v0.9.0

v0.8.1

minor fixes on packages/tests

Full Changelog: v0.8.0...v0.8.1

v0.8.0

The futur ;-)

Complete rewrite ... the only 2 runners are HtagServer & AppServer.

HtagServer is just a subclass of AppSever now.

AppServer can deal with many ways to handle the session (in file, in mem, etc ...)

But now, this version is just for my tests

What's Changed

• Futur by @manatlan in #2

Full Changelog: v0.7.1...v0.8.0

v0.7.1

FQN (full qualified name) should not contains ":", only dots to the target class.

when fqn is in url, browser considers ":" as a protocol, and all goes wrong ;-(. Now, the trouble is gone away.

Now, AppServer is fully compatible with WebServer/WebServerWS/WebHTTP/WebWS (classic web ones), except :

• if you are on a SSL transport, you should instance AppServer(ssl=True) (to let the ws communicates on wss:// in place of ws:// (default))
• when you hit F5, it doesn't reuse the instance (like classic web ones), it destroy/recreate all. So states should be saved in self.root.state (dict)
• no unittests on htagweb.AppServer yet (NEED TO CREATE SOMES)

I use it in production, on https://www.mlan.fr/ ...and seems to works great with all my htag apps (not availables for all)

Full Changelog: v0.7.0...v0.7.1

v0.7.0

Add another new runner "AppServer", which is fully compatible with old classics ones : WebServer/WebServerWS/WebHTTP/WebWS.
Except: tags should use "self.root.state" to maintain a state (because F5 will destroy/recreate instances)

And yes, there is no "0.6.0" (because, lot of troubles when ci/cd/crafting whl for pypi) ;-)

Full Changelog: v0.5.0...v0.7.0

v0.5.0

• the htagserver runner, works as others htag classical runners (can handle a main tag for its '/' path, have a .run() method, can use add_route )
• an example of an oauth2 flow (google), using authlib, and inner runners (WebServer, WebServerWS & HTagServer)
• the one liner "python3 -m htagweb" accept a parameter 'fqn' (ex: 'main:App'), to define a htag class for its "/" page.

Full Changelog: v0.4.3...v0.5.0

v0.4.3

WebServer & WebServerWS don't create trailing vars in session (ht_create/ht_interact)

v0.4.2

• WebServer & WebServerWS are now compatible with htagweb'fqn .... in place of "module.App" you can use "module:App". More compliant.
• htagweb try to clear the imports of the class, if not defined, to avoir cluttering statics spaces