尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗To learn more about vvvv, visit: visualprogramming.net.
For dev-talk around libraries in this repository join our VL.StandardLibs chat.
If you're merely using vvvv, this repository is not for you. It is only useful for developers who want to fix/improve/add-to libraries that are part of this repository.
The individual libraries are organized in directories. Each directory starting with "VL." holds the sources of one library.
Here are the steps required to work with this repository
VL.StandardLibs.sln using Visual Studio 2022 (>= Version 17.5.1)At this point you've replaced all libraries shipping with your vvvv installation with the ones in the repository. This means you're now running them "from source" and could e.g. switch to other branches. Still at this point you'll not be able to edit files, because by default they are precompiled! To enable editing of files for specific libraries you now have to run vvvv with another commandline argument that specifies which of the libraries you want to work on, like so:
--editable-packages VL.Stride.*;VL.SkiaLike this you still get the fast startup-time for all the other libraries that you don't work on.
For agents migrating legacy VL nodes to C# imports, see the C# import migration guide.
Please see our Contribution Guide.