Sorry, "apparently broken" per @jeromg's
comment (2012-09-22, 10:41:22) re searches on native Windows Libraries not working.
I'm not sure whether they are/were
actually "broken", or if it wasn't Search that was broken. If native Windows Libraries were OK, then the solution to the requirement for VFs would be within our reach - I presume. Or maybe it's just too hard to use them easily/flexibly as VFs?
Separately, I recall the author of xplorer² commenting in the http://netez.com/bbs/
forum that Microsoft's implementation of Libraries was a seriously badly done hack, or something. I'm not sure how much this related to the difficulty Libraries presented to him as a developer.
"Poorly-documented" was in there somewhere, as well, I recall.
When Google first introduced "Labels"
for Google Drive, I was blown away by this easy creation of VFs. Suddenly, one could have a file that might appear in several different VFs (Labels). I mean, if Google could do it, then why the heck hadn't MS done it in the OS for the hard drive?
Then Google later essentially withdrew VF Labels, and turned the Labels into conventional logical folders (same as Windows folders), leaving links to those documents which had appeared in several VF Labels on Google Drive. At the same time, without a by-your-leave, Google messed with some of the files - e.g., turning them into proprietary Google docs.
All this seemed to indicate that VFs might have been simply "too much trouble".
What I would like is to be able to set up a VF parent called (say) "Vegetables", with subfolders (child VFs) called "Carrot", "Lettuce", "Cabbage", etc.
Any file with the tag [Carrot] would automatically go into the VF "Carrot", and be inherited by the parent VF, and so on for [Lettuce], etc.
If you dragged and dropped a file called "Foofile" into
the VF "Carrot", then the tag [Carrot] would be inserted into the filename - now "Foofile [Carrot]" - and if that file was later dragged out of
the VF "Carrot", then that tag would be automatically removed, whereas if you copied it into
the VF "Cabbage", then that file would get an additional tag [Cabbage], so becoming "Foofile [Carrot] [Cabbage]".
Over a period of years, by dint of careful use of tags and Regex searches and a lot of tedious and meticulous file tag naming, @Armando
has apparently managed to move in this general direction.
It's all been done manually and/or in batch, but it seems to work OK despite any prevailing constraints.