Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Locations #19

Open
seandenigris opened this issue Aug 4, 2019 · 1 comment
Open

File Locations #19

seandenigris opened this issue Aug 4, 2019 · 1 comment

Comments

@seandenigris
Copy link
Owner

seandenigris commented Aug 4, 2019

The dream is that we hand a file to the library and it figures it out. The point of this library is to take away the burden of file-y things like locations. However, there may be cases where manipulating the location might be beneficial.

Example 1: The Cloud

I store a PDF in Google Drive. This introduces a concern not handled by the file

Example 2: Fine-grained control over

For example, I have some files that would be most easily navigable in a hierarchy. I don't want to write a web app to access my data, so I dump them into the cloud so that I have a poor man's UI on my mobile device by navigating through the files. If they were all in the same folder and there were a lot of files, this would not be possible.

Now, the next issue is where to put the logic. Injecting it into RL naively is causing a rapid multiplication of messages to handle every cell in the matrix i.e. file + location + move/copy. Two possible ideas are an Import object, or provide hooks for the object that gets passed in e.g. anObject preferredLocationIn: self "aResourceLibrary"

@seandenigris
Copy link
Owner Author

Working on the "import command" option. It seems promising

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant