-
Notifications
You must be signed in to change notification settings - Fork 120
Open
Description
Here is a list to keep track of the currently outstanding PRs that make significant changes to MMCore/MMDevice, in proposed order of merging. This does not mean that these PRs are ready to be merged in their current form -- only that I think this is a reasonable order in which we can review, adapt, and merge.
- Split camera device base class into Base and LegacyBase #590 (and Migrate Cameras from
CLegacyBase
toCCamerBase
#598)- 590 should be rebased so as not to touch the camera adapters that it doesn't have to (cameras that don't use legacy functions should receive no changes)
- Otherwise this should be straightforward (and does not affect Device Interface Version)
- New MM::StorageDevice and addition to the MMCore API #535
- 535 is mostly independent of the rest and could be reordered, as long as it does not add deeper interactions with camera acquisition
- Standard properties for device adapters #584
- Any bikeshedding on naming scheme?
- Allow camera device adapters to call
InsertImage
on snap #592 and New camera API #593- 592 should be considered part of 593
- Depends on 590 and 584
- Requires adding tests to be sure that we don't break existing cameras
- We need a clear story for migration (for cameras and apps) without permanently splitting the interface
- New image buffer #570
- Probably by splitting (as branches off the PR branch) into a few reviewable/testable units
- We may want to reduce risk by introducing a pluggable buffering scheme
- Need migration strategy for Multi Camera
- Need safer way to track Java-owned pointers to C++ memory
Metadata
Metadata
Assignees
Labels
No labels