This is kind of what I'm thinking as it keeps it consistent with normal folders...
Ex. 1:
paper:pf
PF's path: <xypaper>\pf.txt
Breadcrumbs: > paper: > pf
Actions:
> - Computer, Drives, etc.
paper: - Go to <xypaper>
> - List folders in <xypaper>
Ex. 2:
paper:a\pf
PF's path: <xypaper>\a\pf.txt
Breadcrumbs: > paper: > a > pf
Actions:
> - Computer, Drives, etc.
paper: - Go to <xypaper>
> - List folders in <xypaper>
a - Go to <xypaper>\a
> - List folders in <xypaper>\a
pf - Nothing
Ex. 3:
paper:C:\a\pf.txt
PF's path: C:\a\pf.txt
Breadcrumbs: > paper: > pf
Actions:
> - Computer, Drives, etc.
paper: - Go to C:\a
> - List folders in C:\a
pf - Nothing
Now the problem is the 'List folders in...' items, since it might be more desirable to change those to 'List paper folders in...'. The problem again though is there's no way to identify a paper folder file, so that would need to either display all txt files or all files making it less useful (at least when outside of <xypaper>).
That's where I'm stuck.
This is one of those times I wish there were better support for what I'll now call "Cascading Extensions".
This is the idea that a file might be named: "file.pf.txt"
It's primarily a text file, but the secondary extension ('pf') tells us its more specifically a 'paper folder'.
Other examples:
'file.cc.xys' - An XYplorer Script File, for a custom column.
'file.lib.xys' - An XYplorer Script File, that is a library of scripts.
'file.moviePoster.jpg' - An image file that is a movie poster.
'file.eb.pdf' - PDF that is an e-book.
I realize we can already do this but it can be a bit painful because no tools that I'm aware of actually supports the full logic and thus they only ever care and work with the primary generic extension.