Re: [whatwg] Accessing local files with JavaScript portably and securely

On 2017-04-11 14:50, Philipp Serafin wrote:
> Patrick Dark schrieb am Di., 11.
> Apr. 2017 um 13:55 Uhr:
>
>> [...] The only good reason to distribute an application this way is
>> because you want it to be confidential [...]
>
> Another use-case would be to develop a HTML app that does not require
> internet access.
>
>> If you really want a private HTML-based application, you might consider
>> a password-protected webpage. If the application isn't a throwaway app,
>> you'll want to do that anyway, so there isn't anything lost from the
>> upkeep required of maintaining an online server.
>
> Why would I even want to run a server?

These are my concern as well.

Making a Soundboard using HTML(5) is very difficult.
And via file:// you can't add (drag'n'drop or file requester) files as 
the file paths/names are not made available.
So storing filenames in localstorage and then getting that the next time 
the app is started won't work.
Storing the audio in localstorage is just wasteful, and localstorage is 
limited to a total size. A handful of loops/background/sfx will quickly 
eat that up.

Trying to use the audio processing features of modern browsers are also 
a issue as you trigger CORS.

There is also no way to get the filenames of a sub folder relative of 
the html file, that way .wav/.ogg/.flac/.mp3 could have been copied into 
a subfolder and automatically show up in the soundboard when started.

Having end users have to run a server (even a mini/lightweight one) is 
just silly. In that case a native (and much more powerful) Windows 
application could be created instead be it NWS/Electron, or C++.

Having end users poke around in browser advanced options or worse the 
browser flags or command line switches is not something a end user 
should have to do either.


-- 
Roger Hågensen,
Freelancer, Norway.

Received on Thursday, 13 April 2017 09:30:52 UTC