Xilem Python integration sketch #2185
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is similar to lasagna but with strongly typed elements. Let's see how it goes.
Support for type erasure of views and widgets.
Bring in more widget tuples with a macro.
Event propagation has no mutable access.
This passes the app state down through an Rc using a lens-like construction. I'm not sure this is the best construction. Perhaps it should be combined with adapt (the callback could take both mutable state references), but that's 3 callbacks. Also makes state mutable in event propagation, which seems useful.
Also trying out a few more node types in the example.
Can call into Python and downcast resulting object...
Now to wire up some state
Make the main type `View<PyObject, PyObject>` Implement ViewTuple similarly.
Use PyTuple rather than PyObject, so downcasting happens in call to functions like `column` rather than in the ViewTuple impl.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch contains an experiment to see whether Python bindings for the Xilem architecture would be viable. The code itself is very hacky, with a bunch of unwraps and no good error reporting, as well as somewhat dubious use of state on the Python side, but it does prove that the ideas can work. Hopefully there will be real Python bindings at some later time, and hopefully that can refer to this work.