Yes, I confirm that most likely the new infrastructure will be available around January. Here there are few preview videos (in the audio, I explain the interactions) (pure VTK) of what we are developing:
Reading the lab page, the new widget rework that I am doing should cover the majority of the desired improvements.
Our idea is to have for a first implementation everything within Slicer (vtkwidgets in Modules/Loadable/Markups/VTKWidgets, and for each widget a relative markups node, etc…). This will allow a much faster prototype, dev and test (then in future we may move them upstream in VTK). In addition, having the widget directly in Slicer will allow additional feature: save the state of the scene for undo at each widget interaction, easier communication between different 2D/3D views, etc…
The vtkwidgets have few layers of abstract classes, so it should be relatively easy to implement a new annotations with the new widgets.
From point of view of implementation at VTK level we don’t use anymore the vtkHandle to interact with the widget. This will greatly boost the performance (the fps while interacting with a closed curve with 2000 points were still > 30) and make all the infrastructure much easier/lighter.