Virtual Folder / Container / Pike

[Stef123]

2. It shouldn't just remove the files if they aren't found ..... (may be present on remote location)

I agree when it comes to drive letters and remote locations.
But I like the live-mirroring of my ongoing actions in currently available locations.

If we're not allowed to treat listed files as if they were the real thing, then why not just create folders holding shortcuts instead of actual files?
No, the only reason I'd like to have a virtual FOLDER is to gather in a single place files (and folders someday, I hope!) spread all around and treat them AS THE REAL THING.

Couldn't have said it better. It's the warp and woof of this feature, what it is all about.

[admin]

If we're not allowed to treat listed files as if they were the real thing, then why not just create folders holding shortcuts instead of actual files?
No, the only reason I'd like to have a virtual FOLDER is to gather in a single place files (and folders someday, I hope!) spread all around and treat them AS THE REAL THING.

Couldn't have said it better. It's the warp and woof of this feature, what it is all about.

Yes, I agree as well. The point of PF is display: (1) WHAT is shown, (2) HOW it is shown (sort order). However, items behavior and action on items is REAL.

place files (and folders someday, I hope!)

But you can have folders in the PF. What do you mean?

[admin]

I want scripting commands.

Originally I had planned an SC LoadList by which you could directly pass a list of items to be shown in the current tab in a Paper Folder.

But now I think it would be bloat. The PF system is so simple and transparent, it's just a couple of lines to achieve the same with the currently existing scripting commands.

So: What are you missing?

[SkyFrontier]

place files (and folders someday, I hope!)

But you can have folders in the PF. What do you mean?

Now I see: trailing backslashes for folder paths on PaperF files are not supported. Don?
-take into account that some files may not have extensions...

[admin]

Aaah! Ok, bug. Coming...

[admin]

You'll probably keep using that paper airplane icon, so I won't mention I want to change it.

Custom File Icons:

Code: Select all

paper:*>omelet.ico

[eil]

Just an idea: a paper folder could have some settable attributes, stored by keywords in the first line(s) of the file. These could, for example, define the default action for delete.

i like this! as PF file is kinda like a portable-container it should be autonomous: save it's sort, view, portable-icon, etc.

[Stef123]

Just an idea: a paper folder could have some settable attributes, stored by keywords in the first line(s) of the file. These could, for example, define the default action for delete.

i like this! as PF file is kinda like a portable-container it should be autonomous: save it's sort, view, portable-icon, etc.

Deserves giving it more thought. A smart idea, really.

[admin]

Just an idea: a paper folder could have some settable attributes, stored by keywords in the first line(s) of the file. These could, for example, define the default action for delete.

i like this! as PF file is kinda like a portable-container it should be autonomous: save it's sort, view, portable-icon, etc.

Deserves giving it more thought. A smart idea, really.

I had planned exactly this originally, as a header in the PF file. But then I destroyed my notes because it was unnecessarily complicated. Paper Folders should work as much as possible like normal folders. View settings are handled by tabs or FVS or CFI etc.

[Stef123]

Paper Folders should work as much as possible like normal folders. View settings are handled by tabs or FVS or CFI etc.

Good points. And since XY is portable - and portable paper folders per se wouldn't make much sense without XY anyway - their portability is built in already.

[admin]

... and portable paper folders per se wouldn't make much sense without XY anyway ...

Well, they are simple lists of items. They could make sense with many applications. I see import/export usage and inter-app communication options. (But I don't have to care about that, I just make the tool.)

[nerdweed]

Duplicates are currently displayed. I trust that this is bug.

I think adding a scripting command would be good even if it becomes a bloat. Reason: If you decide on changing some internal working - like currently duplicates are allowed and you want to disallow it, etc, the new SC can handle it.

[admin]

Duplicates are currently displayed. I trust that this is bug.

Only if you manually edit the PF file, right? That is not a bug.

[Stef123]

I see import/export usage and inter-app communication options.

- not to mention I've already started using them as a reporting tool.

[nerdweed]

Duplicates are currently displayed. I trust that this is bug.

Only if you manually edit the PF file, right? That is not a bug.

Yes. But accessing the paper folder, it overwrites the file. Will it remove duplicate in that instance. OK, even if it doesn't