» Let me present to you: File IO
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Let me present to you: File IO

previously on VL: vl-progress-report-3

Dave Skylark said
same same, but different

on the way to catch up with what you know and need from vvvv, the first choice for expanding VL core library was to work on file thingies. The following should look extremely familiar and probably quite unexciting for you:

FileReader and FileWriter
the very basics needs

These guys do exactly what you would expect them to do: read from file, respectively write to a file. as a convenience nodes you have string versions, the standard ones give you bytes.

since it's 2016, these nodes do their work asyncronously, hence these output pins, which keep you informed about the working status, giving you the opportunity to draw some nice loading animation.

async loading info
async working status info

it wouldn't quite feel like vvvv if the curious ones could not actually peek inside the node to see what's going on

inside the FileReader
the guts of the FileReader

looks a bit overdone for such a simple thing, right?
the motive for the splitting up into File and the actual IO operation has a couple of (imho) good reasons:

chaining operations
chaining io operations

no need anymore to load the whole file and then decide what to do with the content. you can for example parse the header of a video file, look up some frame offset and directly do a partial read of just the blob you are interested

control over file access

there are a bunch of ways to access files. now you can actually control all of that. one reason might be security, since you can decide, whether anyone else can read or write or even delete the file at the same time. you can set it to forcibly create a new file, so you don't accidentally overwrite something existing.
another reason is performance, you are welcome to dive into the deeps of the web to find out which combination of modes causes which thread to do the work. we tried to set the defaults for best performance for parallel reading.

stream stream stream
Stream Operations
the ops: left blocking, right async; also available for strings

the File node actually returns the FileStream. so all these operations can instantly be used with anything else, that is a stream (which is a lot of things in the .net world)

while the async details here are still hidden away in the c# code of the nodes, the process has paved the way towards general patching of threading/async computation. stay tuned...
woei, Thursday, Dec 1st 2016 Digg | Tweet | Delicious 1 comments  
readme 02/12/2016 - 10:02

Reading this to the very end (2 lines) is most rewarding.

  • 1

anonymous user login


~3d ago

joreg: @jzzxh not sure what you mean. please consider rephrasing and asking in the forum.

~3d ago

jzzxh: hi, guys it's any node (offsetscreen) for skiaRenderer??

~8d ago

joreg: absolutely. if it is for a repo that is public, just submit a pullrequest. otherwise please start a forum thread.

~8d ago

benjawmino: @joreg I ended up figuring out BezierSegment yesterday, so nevermind! Tell me, could a user submit a help patch? :)

~8d ago

joreg: @benjawmino please elaborate on this question a bit in a new forum thread. otherwise it is hard to answer..

~9d ago

benjawmino: so are there no splines/curves in gamma yet??

~13d ago

skyliner: wanna do drone shows or applications? then check this super cool project of our man e1n