According to Mike Nordell <[EMAIL PROTECTED]>: > Hubert Figuiere wrote: > > > > The idea is that when you open a document, the file requester dialog > > (platform code) return a file object to pass it to the PD_Document that > > will open and use it transparently. > > I'm with you so far, but I still don't understand why an already opened > _stream_ couldn't be provided (using a small wrapper around the native > filesystem requester returned filename), instead of a "file".
That could be done too. I don't see why we can't just that currently we can't. > > If you are curious, look at the BeOS API where they make difference > beetween > > file systeme operations and input/output operations. > > I know (and I still miss the BeOS API(s) ). What I don't know is why we > should limit ourselves to using "files", when we (AFAIK) in reality could > grab input from any source. Using files limits us (semantically) to only > operating system filesystem-style I/O. Re-read what I said. Streams are NOT files. Stream are IO things, File IO being one kind. That's why filesystem objects are separated. Hub
