Quote:
|
If it were to be done, I would suggest that perhaps the path just follows the hierarchy of the Data Explorer tree... either have the My Data item serve as the "root" of the virtual drive, or perhaps you could assign an Info Item to be the root for a virtual drive. [/B]
|
I was proposing the idea of a path attribute because you would probably only want to use this virtual disk for certain objects within the UR database and the physical location of these objects within the UR tree may not necessarily correspond to your desired path names.
For example, I might have a folder called "documents" that is nested many levels deep within the UR tree. However, it would be inconvenient to have to type a whole long path name every time I wanted to access this folder. Also, if I move this folder around within the tree, I wouldn't want the path to change, from the perspective of the Windows file system.
Therefore, I would like to be able to designate a path name, such as "U:\documents" that would be permanently attached to this object. Once that attribute is defined, I could always access the "documents" Info Item and its children using the "U:\documents" path name, even if I moved it to a different location within the tree.
The idea of assigning an Info Item as the root of the virtual drive is a valid alternative to what I proposed. You could have your virtual drive (or perhaps even multiple virtual drives) mapped to Info Items. Then, you could store all your files within those virtual drives and create logical links to the files contained within the virtual drives, from other locations within the UR database.
I think this type of functionality would give UR a huge advantage over every other PIM/Outliner on the market. It would really move UR out of the realm of traditional outliners into an entirely new class of software that would literally replace the Windows file system. The thing is, I don't think this would be that difficult from a programming perspective. The reason I say that is because:
1. UR already has most of the core functionality to support this. It has the capability to store/index files within its database. The only thing that's missing is the virtual device driver.
2. There are many applications on the market that use virtual disks for all sorts of things. For example, there are numerous applications that create encrypted containers on your hard drive and these containers appear in Windows Explorer as virtual drives. I'm sure there is off-the-shelf code readily available for implementing virtual disks within Windows applications.