Use libraries to manage files in Windows7

In the Windows7 operating system, another new type of file management is provided, that is, managing files through a library. The following figure is a screenshot of the Library management interface.

Illustration: Using libraries to manage files in Windows7

This is a new and effective file management mode in the WINDOWS7 operating system. It looks similar to a folder. But there's a big difference. In this article, the author of this library file management method to do a more in-depth analysis and testing, to help you understand this new function.

First, the similarities and differences with the common folder.

From the above interface, we can see that the library seems to resemble the traditional folder more. Indeed, from a certain point of view, libraries and folders do have a lot in common. As with folders, you can include a variety of fader and files in the library, among other things. But it's essentially a lot different from folders. Files or subfolders that are saved in a folder are stored in the same place. The files stored in the library can be from corners. such as files that can be associated with a user's computer or from a mobile disk. Although this difference is relatively small, it is the most essential difference between the traditional folder and the library.

In fact, the library's management approach is much closer to shortcuts. Users can use a specific storage location for a relationship file or folder. Link them all to a library for management. In this case, you can see all the files the user needs to know in the library (as long as the user joins the files or folders in the library beforehand). Or, the object in the library is a snapshot of various folders and files, the library does not really store files, providing a more efficient way of management. If the user has some working documents are mainly on their own computer on the D disk and mobile hard disk. For the convenience of later work, the user can put the D disk and the files in the mobile hard disk into the library. When you need to use, just open the library directly (provided that the mobile hard disk has been connected to the user host), without the need to navigate to the mobile hard disk.

Second, after deletion is not able to rejoin is a loophole?

As shown above, the author first put a folder on the hard disk WinXP, add to this library. The way to add a folder to a library is simple, just select the destination folder, click and click "Include in the Library". But the author in the test, but found an organ problem. If you add this folder to the library, then delete the WinXP folder in the library. Then, add the folder to the library again. But at this point the system prompts "already WinXP included in the library" and does not display this folder in the library. But in fact the WinXP file in the library has been deleted.

Then you can create a success by adding the file to the library in the case where the WinXP file exists in the library. Only the name of the library will become WinXP (2). This error is not caused by adding a folder to the library repeatedly. Because the test shows that the system allows the same folder to be added to the library multiple times. The reason for this error may be that there is a problem with the display in the library, and the folders that have been added to the library are not displayed properly due to some special operations (such as deleting and then adding).

Third, delete the actual folder impact on the library file.

As pictured above, the author has a WinXP folder on the hard drive and then includes this folder in the library. Now I delete the WinXP folder on this hard drive. What does this have to do with the WinXP folder in the library? First, I open the WinXP folder in the library by double-clicking it. Visible Library file management and shortcut management is still a certain difference. If it is a shortcut, when the user deletes the original file, the shortcut will not open, will allow users to confirm the accuracy of the path. In the library, you can still open the library files that were deleted by the original folder. There is nothing in this library that was originally saved. The most surprising is that, although the original folder back deleted, but in the library file can go to WinXP this library to add files, such as can create a new folder. So where is this newly added content library? At this time I opened the original WinXP this folder storage location, found that the original in the old place a new WinXP file. This is created automatically by the operating system, and it is saved by the newly created folder in the library.

Iv. shared files on the network cannot be added to the library.

Can the shared folders on the network also be added to the library for management? The author inquires the relevant technical data. According to Microsoft's Official document, it is possible to add shared files from the network to the library, only to open the library at a slower rate due to network reasons. But after the author's test seems not workable. As the author now

A new folder was created on the other host and set to shared. Then connect this file on the Windows7 host. The author wants to add this shared file to the library, but the operating system prompts the error message "This folder cannot be included because it is a shared file instead of an index," as shown in the following illustration.

Illustration: Using libraries to manage files in Windows7-Illustration 2

However, the author still does not give up, the shared file is mapped to a network drive. Then create a new "new folder" in this network drive. Unfortunately, it is still not possible to add this folder to the library. The author pulls the new folder into the library by dragging, and still displays the error message: This folder cannot be included because it is a shared file rather than an index. Through several tests, the author finally forget. Windows7 now provides a version that does not have the ability to add shared folders on the network to the library.

Five, the library and the actual folder can not be equated.

If you first add a WinXP folder to the library, there will be more than one font in the library called WinXP. Note that the font WinXP in the library is not the same as the actual stored folder WinXP. Some of the operations on the font WinXP do not affect the actual WinXP folder. If you can get some folders in the library, wrap them in the library. If the font winxp selected, then right click on the property. We can see a button in the Open dialog box that contains a folder. After clicking this button, we can add some of the existing folders in the current hard drive to this WinXP library. However, although some folders are added to the library in the Font WinXP library, this has no effect on the WinXP of the folders actually stored. That is, the contents of that folder are not copied to the WinXP folder because the user adds a folder to the library WinXP. Visible, adding a folder to the library, although by default the name is the same, but the two are not clear. One is the actual stored folder, one is the name of the library. The two are irrelevant.

Vi. sharing in the library.

In a library, you can maintain and manipulate the files contained in the library. If you can share a file in a library. But the real realization seems to have a lot of trouble. As the author of the WinXP Library, a new folder "Test shared folder." Then select the folder, right-click, and select Share. However, there are few options available for users to choose from, only "Nobody", Homegroupread, Homegroupread/write, specific personnel, and so on. There are some awkward English words in these options, perhaps there are some documents in translation. The author chooses "Specific person" to set this "test shared folder" to share. However, the shared flags are not displayed on this "Test shared folder" in the library. But the author looked at the original folder, and then this folder to have a share of the logo. As you can see, shared settings for the files in the library are reflected in the original folder. Unfortunately, there is no sign of sharing in a folder that is already shared in the library, which is more or less regrettable. It was later tested and found to be a problem with the display. If you need to turn off the library and then reopen it, the shared icon will be displayed. If you cancel the share, you must reopen the library to cancel the icon. But you can see the effect immediately on its corresponding folder. This can easily lead to misunderstanding. To this end, I suggest that Microsoft, in this respect, although the icon display is not a big thing, but for the user has a great guiding significance. In terms of display, it's best to be as timely as a regular folder. You don't need to update the icon the next time you reopen it. In addition, if you want to make complex shared settings, it is a good idea to open the Properties dialog box after selecting a folder in the library. Here you can do some detailed setup of permissions control and so on. This is much more verbose than setting up a shared dialog box directly.