Description
The post proposes adding a generic File I/O node to Modly's node workflow, with a type signature like File (type) → File (type). The File would carry metadata such as name, extension, MIME type, size, and data or reference, while the extension determines how to interpret the contents. The post also suggests generalizing the existing Export Model extension into a generic Export extension that accepts Image, Text, and File.
Motivation
This would make Modly's node workflow more flexible without adding too much complexity. It would allow arbitrary files to be passed to and from extensions, including formats like .glb, .ply, .json, custom formats, or intermediate data between extensions. The post also notes that this approach avoids needing dedicated nodes or types for every possible format.
Proposed Solution
Add a generic File node that can accept and output arbitrary files, with optional extension-specified expected file types so Modly can warn about mismatched connections without necessarily blocking them. Also generalize the Export Model extension into a generic Export extension that accepts Image, Text, and File, making it easier to retrieve arbitrary File outputs.
Automatically imported from Discord.
Discord: https://discord.com/channels/1476254551991386279/1545550912976593003 (by iridescentdeveloper)
Description
The post proposes adding a generic File I/O node to Modly's node workflow, with a type signature like
File (type) → File (type). The File would carry metadata such as name, extension, MIME type, size, and data or reference, while the extension determines how to interpret the contents. The post also suggests generalizing the existing Export Model extension into a generic Export extension that accepts Image, Text, and File.Motivation
This would make Modly's node workflow more flexible without adding too much complexity. It would allow arbitrary files to be passed to and from extensions, including formats like
.glb,.ply,.json, custom formats, or intermediate data between extensions. The post also notes that this approach avoids needing dedicated nodes or types for every possible format.Proposed Solution
Add a generic File node that can accept and output arbitrary files, with optional extension-specified expected file types so Modly can warn about mismatched connections without necessarily blocking them. Also generalize the Export Model extension into a generic Export extension that accepts Image, Text, and File, making it easier to retrieve arbitrary File outputs.
Automatically imported from Discord.
Discord: https://discord.com/channels/1476254551991386279/1545550912976593003 (by iridescentdeveloper)