search

seandenigris / Resources-Live

GNU General Public License v3.0
4 stars 0 forks source link

File Locations #19

Open seandenigris opened 5 years ago

seandenigris commented 5 years ago

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 commented 5 years ago

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