vvvvhat happened in January 2019February 2, 2019 posted by: joreg
here we go,
clickclickclick. 2018 is numbered and we’re now heading towards the biggest release in vvvv history. as announced previously: vvvv gamma.
we’re still on track regarding our roadmap and here is a little status report:
- UI rework is well under way, looking smooth and shiny
- spreadable IOBoxes are a thing, need refinements
- editing patches is no longer blocking renderers
- we simplified the document structure to have a better default workflow
- tons of helppatches are in the works none of these are in alphas yet, but if things go well, they should land soon.
- and not part of the initial release, but work is also progressing on integrating xenko…
while you’re waiting and haven’t yet, please fill out the 2019 Survvvvey!
- Gea.NaiveGPUbeta-contribution by dottoreuser
- VL Dynamic instancing without Delegatesbeta-contribution by domjuser
- etching hatching line engravingbeta-contribution by tatyouser
- self distort feedbackbeta-contribution by tatyouser
- vvvv dependency installerbeta-contribution by u7angeluser
released as work in progress:
:vvvVR Robotics by MultiNILuser
and three more:
- Screenization Experiment - Materiality by Lorenzuser
- ALEA(s) - audiovisual performance by Boris26user
- Forest by boplbopluser
that was it for january. anything to add? please do so in the comments!
Comments are no longer accepted for this post.
@microdee @joreg I agree that multiple patch views are a must and clicking back and forth between patches increases cognitive load and I think discourages from modularizing the code well. Although I also think that maybe free floating windows might not be the best answer as for me at least in vvvv they always tend to become a bit of a mess as long as there is no proper way to lay them out. I would suggest to maybe think about a similar approach to what blender uses (if the multiwindow features are ignored) - hosting multiple editors inside a single window.
I tried my hand now switching from multiple windows for editors in my project to a single window hosting multiple editors via the super simple to use Skia Panel.
It’s a crude and fixed implementation but I think it has potential to reduce window clutter, have savable workspaces, etc. I could imagine any future internal VL debugging tools be neatly packed in these panels as well.
there are libraries out there taking care of this. what’s stopping you hosting your Skia renderers in these: https://www.youtube.com/watch?v=jLkHZh5Mbx8 or this is a more bare-bones example https://www.youtube.com/watch?v=oB4s2LpYHqc it even runs on linux (using avalonia) even Imgui can do it which supposed to be a debugger user interface but got blown out of proportions recently: https://www.youtube.com/watch?v=G6F1c5xJAX8
so ain’t no more excuses! especially if you want people to pay for your software!