Consider support/handling of System.IO #779

Open
DaniilVeriga opened this Issue Dec 22, 2015 · 2 comments

Projects

None yet

4 participants

@DaniilVeriga
Contributor

http://forums.bridge.net/forum/general/open-discussions/1320

The System.IO namespace appears to be unimplemented. At least some basic support should be available as an extension package. Especially the exceptions like System.IO.TimeoutException should be available. While they are in the System.IO namespace they get used elsewhere.

In terms of the System.IO namespace, I think supporting Stream, Reader, Writer, and MemoryStream along with the readers/writers such as BinaryReader, BinaryWriter, TextReader, TextWriter etc would be sufficient. It would at least allow existing code that accepts a stream/reader/writer parameter. It occurs to me supporting the encoding classes would probably be necessary to help with the IO routines as well.

@DaniilVeriga DaniilVeriga changed the title from Consider support of System.IO to Consider support/handling of System.IO Dec 22, 2015
@PluginIO
PluginIO commented Jun 18, 2016 edited

Hi, is there any movement on this? I am really hoping to get access to the following:

System.IO.Stream
System.IO.BinaryWriter
System.IO.BinaryReader

Together these 3 classes would support almost any case for reading and writing data efficiently from a HTML5 Typed Array.

My case is a complete 3D engine platform and editor where all resource data is abstracted to a byte[]. If correctly implemented, the data should be read as a stream, along with pointer offsets, as this is highly optimized and required for the WebGL buffer channels.

Link to reference and notable nod to WebGL.
http://www.html5rocks.com/en/tutorials/webgl/typed_arrays/

@geoffreymcgill
Member

Hello. Unfortunately we have not been able to make any progress with this functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment