file-system-access VS libwdi

You can read about the privacy concerts the community group published [1].

[1]: https://wicg.github.io/file-system-access/#privacy-considera...

WHATWG File System Standard provides a means to write directories and files to the private origin storage associated with a Web page origin. If you want you can use WICG File System Access API to write data directly to your filesystem in the browser. WHATWG File System Standard uses the same FileSystemDirectoryHandle and FileSystemFileHandle defined by File System Access API.

Chromium-based browsers support File Systeam Access API.

We have stopped using the file system access API: https://github.com/WICG/file-system-access/issues/401

Where file handling is concerned, there are at least

- File System Access API, https://wicg.github.io/file-system-access/

- File Handling, https://github.com/WICG/file-handling/blob/master/explainer....

- Origin Private File System, https://github.com/WICG/file-system-access/blob/main/AccessH...

There was also Storage Foundation API to which the reaction was "I don't think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.

Huh. Disregard what I wrote entirely, then. Reading through https://github.com/WICG/file-system-access/blob/main/AccessH..., I can see how they’ve bypassed most of the problems I saw—I was making unnecessary assumptions.

Thank you for correcting me.

> Browsers have never let anything (not even JS) have raw access to the host FS

I'm not sure what you mean by "raw access", but the File System Access API certainly allows web applications to do a lot of things.

> The File System Access API (formerly known as Native File System API and prior to that it was called Writeable Files API) enables developers to build powerful web apps that interact with files on the user's local device, like IDEs, photo and video editors, text editors, and more.

https://web.dev/file-system-access/

> After a user grants a web app access, this API allows the app to read or save changes directly to files and folders on the user’s device. Beyond reading and writing files, this API provides the ability to open a directory and enumerate its contents. Additionally, web apps can use this API to store references to files and directories they’ve been given access to, allowing the web apps to later regain access to the same content without requiring the user to select the same file again.

> Additionally this API also makes it possible for websites to get access to some directory without having to first prompt the user for access.

https://wicg.github.io/file-system-access/

It's not just a draft, it's been part of Chrome since version 78 in 2019.

> After a user grants access, this API allows web apps to read or save changes directly to files and folders on the user's device. It does all this by invoking the platform's own open and save dialog boxes.

https://blog.chromium.org/2019/09/chrome-78-beta-new-houdini...

Discussion at the time:

https://news.ycombinator.com/item?id=21032537

In the post, the Vite webserver is only used to serve the HTML and JS static files to the browser. When the user saves or opens text files, the code uses the web File System Access API (https://wicg.github.io/file-system-access/) to interact with the user file system.

Have you heard of Project Fugu and their idea of a File System Access API in the browser? https://wicg.github.io/file-system-access/

I don't know a C++ equivalent of HTML , prompt(), or File System Access API (https://wicg.github.io/file-system-access/; https://web.dev/file-system-access/) using JavaScript in the browser window.

They probably use WCID, which is a mechanism for devices to tell Windows that they are compatible with the generic WinUSB driver. Zadig is useful for older versions of windows, non-WCID devices, and when you want to override that auto-specified driver.

Here's more information from the author of Zadig: https://github.com/pbatard/libwdi/wiki/WCID-Devices

If you do that'll bring you here where you'll find everything you ever wanted to know about WCID.

Using this config files from zadig's github page, it (in my case) got all the correct settings from the start and all I need to do is click replace driver. Place the zadig.ini files in the same directory as your zadig.exe. You might have to choose the correct device.

USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.