search

vvvv / VL.StandardLibs

A collection of standard libraries for vvvv including VL.Stride, VL.Skia, VL.ImGui, msgpack.org[VL]
https://visualprogramming.net
GNU Lesser General Public License v3.0
41 stars 16 forks source link

Asset nodes should also work if runtime content manager is not available #615

Open tebjan opened 5 years ago

tebjan commented 5 years ago

check later when we have exe export. code and test the following workflow: develop at runtime with external project, then export executable -> all assets should of course be available.

azeno commented 4 years ago

Two things come to my mind here 1) Allow to reference C# project files - there's a branch in vvvv allowing that, it depends on the NuGet API branch which we already discussed must be merged soon due to .NET 5 coming up. 2) The node factories could help here. If we'd allow referencing arbitrary files (like Stride project or assets files), a node factory could provide all the contained assets as nodes and further on export it could apply the necessary action on the generated C# project file so that those assets are seen by the asset compiler.

As an alternative - because that could already be done now - we could write an asset node factory looking for a certain pattern below a VL document right now. The before mentioned export part is already available.