[Subversion] / Trellis / setup.py |
No default branch
Bookmark a link to HEAD:
(view)
(download)
(as text)
Prep for release
Bump version to 0.5b1dev-r2366
Remove dependency on Contextual -- although it'll be back eventually.
High level API: Component class, decorators, properties. The tests are disorganized and the docs are non-existent, but it works, by golly. Docs and test re-orgs will begin next week.
The Trellis will be using ObjectRoles from now on...
Rip out the old Trellis implementation and replace with a shiny new algorithm. This is nowhere near adequately tested, and Constant conversion doesn't work. The doctests are in horrible shape and don't describe the current algorithm at all. The fancy API described in my mailing list posts is nowhere to be found, and none of the new functionality is tested in the slightest. Experiment at your own risk; this is just a placeholder/proof-of-concept test to see if the new algorithm at least passes the old tests (except for Constant conversion.) And it does. :) So, everything from here on out should effectively be either documentation, tests, syntax sugar, or convenience/reference implementations of higher-level features.
Refactor to use a Cells-like forward/backward propagation system. Separated thread-specific "current observer" state from trellis state. Tests still pass, but are far from sufficient and the docs are crap; you're better off not reading them yet. Effectively this is just a checkpoint to have a jumping-off point for more extensive changes, like making values know what trellis they belong to, and redoing the docs/tests to maximize both line and scenario coverages.
Trellis: a new paradigm for event-driven programming, based on ideas from Gelernter's "Trellis" system, and Tilton's "Cells" for Lisp. Eventually, this will grow up to do the rest of the things that peak.events does now, only with deterministic updates and no need for explicit dependency management.
cvs-admin@eby-sarna.com Powered by ViewCVS 1.0-dev |
ViewCVS and CVS Help |