I know this is just a draft for now, but we need to avoid using std::fs and std::path in core. This all needs to be a backend, or it won't be portable or testable.

Personally I already implemented it on a fork, it's not perfect nor clean. And the branch not up to date with upstream for now but you can find it here if you want:

https://github.com/Mesteery/ruffle/tree/partial-air/core/src/avm2/globals/flash/filesystem

Personally I already implemented it on a fork, it's not perfect nor clean. And the branch not up to date with upstream for now but you can find it here if you want:

https://github.com/Mesteery/ruffle/tree/partial-air/core/src/avm2/globals/flash/filesystem

Oh that is very cool. I am probably going to work on finishing FileReference first and work on this only afterwards. If you are interested I think you could probably rebase it on top of #14157. Your backend abstraction is good to have.

@Mesteery would you be interested in making a pull request for your work? We now have FileReference and some foundational AIR support already. The missing flash.filesystem.File support currently prevents even the most basic AIR applications from working.

Why not. I'll look into making a PR. There are still some problems with paths, I should rewrite this part.

Nice. I look forward to your PR. It might make sense to make the actual path completely opaque and only have some kind of file handle in the avm2 code, then all methods like "resolve path", "get storage path" etc. would just forward that to the backend.

Any update on this?

Personally I already implemented it on a fork, it's not perfect nor clean. And the branch not up to date with upstream for now but you can find it here if you want:

https://github.com/Mesteery/ruffle/tree/partial-air/core/src/avm2/globals/flash/filesystem

@Mesteery I rebased your fork against master on my fork (but I almost definitely did it wrong, I'm a rust/flash noob). https://github.com/JL2210/ruffle/tree/partial-air