Bonsai 2.9.0 #2318
glopesdev
announced in
Announcements
Bonsai 2.9.0
#2318
Replies: 1 comment 3 replies
-
|
This looks great so far! I am really liking the new features, and am super excited to see where it goes in the future. I did want to say that I think I've found a small bug related to the docking panels / explorer. A couple of times we have seen that the name does not update to match the filename (this is sporadic behavior at this point). The steps below can sometimes reproduce the issue:
To fix the dock panel names, I can remove them and then add them back in by clicking on the top-level in the explorer, at which point the tabs have the correct name, but the explorer still retains the old filename. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment





Uh oh!
There was an error while loading. Please reload this page.
-
This is the first release in the 2.9 series, which introduces significant changes to the language editor experience. Please give us any feedback either in the comments below or by opening a new discussion.
In Bonsai 2.9 we introduce a new workflow navigation model leveraging a flexible docking layout panel, and a nested hierarchy tree view with breadcrumbs to allow easily and quickly jumping between different parts of a complex project. The docking architecture also enabled us to start developing new editor tools such as the new find all references window.
The new workflow state watch mode provides an unprecedented level of runtime feedback about the inner workings of a reactive workflow, including when sequences are subscribed to, when they produce values, terminate, or are cancelled. We expect this mode to provide an invaluable tool for learning visual reactive programming and understanding the behavior of programs written in Bonsai.
In anticipation of new editor features, we are introducing a reorganization of the
.layoutfiles, which were previously used to store debugger visualizer settings over multiple runs. These files previously cluttered folders containing multiple workflow files, and were very hard to extend to more complex project-based settings. With this reorganization we expect to facilitate a cleaner project folder structure and introduce more clarity on the version control of workflows.Finally, we modernized the package manager dialog and completed our migration from MyGet to NuGet. As discussed during the last MyGet outage, we urgently needed to broaden our community package deployment options. The new package manager introduces support for two new package types:
BonsaiLibraryandBonsaiGalleryfor packages providing libraries of Bonsai operators and example workflows, respectively.These package types will be used to curate the
nuget.orgfeed to keep our package manager focused on libraries providing reactive operators. Currently package type filtering is only supported for thenuget.orgfeed, but it is turned on by default there. New packages deployed tonuget.orgare expected to declare bothDependencyandBonsaiLibraryas their package types for maximum discoverability.Important
In the near future, we will move entirely out of MyGet and will archive the community feed.
What's Changed
🔮 Release Highlights
🎉 New Features
🐞 Bug Fixes
Extensions.csprojhandling and add unit testing for it by @PathogenDavid in Fix various issues withExtensions.csprojhandling and add unit testing for it #2180🚀 Performance Improvements
🔧 Engineering
Full Changelog: 2.8.5...2.9.0
This discussion was created from the release 2.9.0.
Beta Was this translation helpful? Give feedback.
All reactions