0.10.3

Commits on Sep 09, 2020

• fix misc examples + remove known issues section - 0379633

Commits on Sep 11, 2020

• update client package name and description - f5f60a1
• generalize client layout interface … - f338572
• import TaskGroup from anyio.abc - 0016a82
• bump client version - cfdd8cc
• no more anyio.exceptions - 9e054c3
• run tests every day on master - e822640
• use python-build … - de78263

Commits on Sep 12, 2020

• fix docs - 456228e
• Revert "use python-build" … - e0d546b
• publish package before docs - 90148ae

0.10.2

The most recent release of snowpack allows for many more packages to be installed correctly. For example @material-ui/core, which previously did not work, now works flawlessly. There are a bunch of internal changes that have been made to enable this upgrade since the 2.x version of snowpack included a large number of breaking changes. Most for the better though.

0.10.1

Upgrade anyio

0.10.0

• Rename Renderer to Dispatcher - I think this will reduce confusion since the word "render" is used all over to mean different things.
• AbstractElement does not need an id attribute - we can just use id() instead.
• misc doc updates

0.9.2

Element render functions are no longer coroutines. To new users async functions don't really seem approachable, plus delayed actions are best left to the use_effect hook. To compensate we enable the use_effect hook to support async functions - docs are added to this effect.

0.9.1

Quick release to publish docs without a mangled dev version visible.

0.9.0

The One With Hooks

This is a huge release that reworks much of IDOM to use a React-like Hooks API.

The documentation has been updated to reflect these changes so it's probably best to check the README to learn about the state of the project. In short though...

• Most of React's hooks have been faithfully re-implemented in Python (a new "Life Cycle Hooks" section reflects these additions).
• The only "basic hook" missing from this release is useContext given that its most useful in sprawling code-bases. Given that IDOM has no such usage a use_context hook isn't useful yet.
• Much of IDOM's internal logic for computing and transmitting layout updates was reworked.
• Updates are no longer computed in parallel and distributed as completed, instead they an executed serially (this may be reverted in a future version). While has negative performance implications in some cases it simplified logic.
• Updates are now transited over the wire using the JSON-patch format since the old format assumed on targeted updates would be triggered by imperative code.

Side Notes

• it's now much easier to set up an layout server in a Jupyter notebook - just use idom.widgets.jupyter.init_display(...)

0.7.0

IDOM now officially supports referencing arbitrary ES modules as part of its layouts. See the docs for more info.

This release also includes a few other quality of life improvements:

• the vdom() constructor now supports passing children as positional arguments outside of a list. This comes with the caveat that element attributes must not contain a tagName key (which seems like a reasonable concession).
• update calls can now be made from within separate threads. This means when you define an element with run_in_executor=True you'll be able to update it later. Until now updates had to be managed from the thread where the layout's event loop was.

0.7.0-dev.1

We're dropping the 0.6.1 in favor of 0.7.0 version tag since the changes here are large enough to warrant a minor bump rather than a patch. This release includes various fixes and improvements that were a result of expanding test coverage. Better documentation has also been merged in to describe the new way to import ES modules.

0.6.1-a.2

Each client can now pass parameters to an IDOM element via an HTML query. This allows clients to alter the view they receive based on the query. This is used by the multiview() widget in introduction.ipynb to allow multiple active views to be accessible at the same time because each cell in the notebook passes a view_id parameter to the multiview() widget to specify what element should be displayed.