No, there is currently no widget for selecting/browsing files.

On native platforms, we could get close by using a native file dialog (see #317). In the long run, we should probably implement a file dialog using iced itself.

I'm not sure Iced needs a file dialog. I mean, is there any use-case where there is no file system/browser running? And even if there is, is it actually relevant enough to be worth the effort?

People just need a way to open files (Me included, actually), not 2+ ways. One will suffice provided it works well, on every target OS + the web version, even if some of the versions require something external, be it some browser or Javascript or whatever. Most people don't care.

[I ranted a bit but kept it since this may lead to me tackling this issue sometime]
For now I'm doing my own hack-ish thing, I would love to tackle this on if I thought I'd be able to do a good job, but I'm a beginner in both rust AND GUIs and I'm using this for only one of many side-projects, so I'll refrain for a while. That said, I've been doing mostly webdev and CLI stuff, for about 15 years professionally, and for some 20 years if you include the hobbyist/for-fun stuff, like mIRC Scripting, Pascal, and I've actually used Slackware for a few years starting from 2001, so provided I don't give up on Iced or Rust I should be able to create a PR before long. If anyone wants to give me some tips/pointers/insights I'd be very happy to attempt to do something about this.

Anyways rant aside, my point is: Files need to be loaded. It doesn't matter how, as long as people are able to load files. Maybe it could be done with one button that calls the file-system "open file" thing and receives the file it returns, or maybe the entire "open file" popup-thing could be created from scratch or whatever, the core of the issue is loading files, so that's what should be implemented, preferably in the simplest, smallest and easiest way possible (Maybe even just adding to the documentation some way that actually makes it possible to do it), so as to minimize the chances that it introduces any bugs or anything, at least IMHO. This is what is needed, and I think any more than that should probably be separated in a different issue, with a lower priority.

Uh oh!

File input #347

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions