CN114416640A - File management method and device - Google Patents

Abstract

This specification provides a file management method and device, which are applied to a client. The method includes: in response to a file management operation triggered by a user, organizing a file structure corresponding to a file to be managed into a mind map, and outputting the mind map to the user through a file management page. Wherein, the file structure includes the file and at least one-level file directory corresponding to the file. The mind map includes multi-level nodes representing file directories and representing files. Obtain the user's operation on the node on the mind map. In response to the user operation, a corresponding file management action is performed for the file or file directory represented by the node.

Description

A file management method and device

technical field

The embodiments of the present specification relate to the field of computer technology, and more particularly, the embodiments of the present specification relate to a file management method and apparatus.

Background technique

This section is intended to provide a background or context for the embodiments of the present specification that are recited in the claims. The descriptions herein are not admitted to be prior art by inclusion in this section.

File management, in addition to the management of the files themselves, usually also involves the management of file-related file structures (such as file directories, etc.). In practical applications, if the managed file involves a relatively complex file structure, it may affect the file management efficiency.

SUMMARY OF THE INVENTION

In order to overcome the problems existing in the related art, the present specification provides the following methods and devices.

In a first aspect of the embodiments of this specification, a file management method is provided, applied to a client, including:

In response to the file management operation triggered by the user, organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through the file management page; wherein, the file structure includes the file and at least one-level file directory corresponding to the file; the mind map includes multi-level nodes representing the file directory and the file;

obtaining user operations performed by the user on the nodes on the mind map;

In response to the user operation, a corresponding file management action is performed for the file or file directory represented by the node.

In a second aspect of the embodiments of the present specification, a file management apparatus is provided, which is applied to a client, and the apparatus includes:

The organization unit is used to respond to the file management operation triggered by the user, organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through the file management page; wherein, the file structure includes the file and file directories at all levels corresponding to the file; the mind map includes multi-level nodes, and the nodes include nodes representing files and nodes representing file directories;

an obtaining unit, configured to obtain user operations performed by the user on the nodes on the mind map;

The execution unit is configured to, in response to the user operation, execute a corresponding file management action for the file or file directory represented by the node.

In a third aspect of the embodiments of this specification, a storage medium is provided; a client is stored on the storage medium, and the client implements the steps of the following method when executed:

Used to respond to a file management operation triggered by a user, organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through a file management page; wherein the file structure includes the file and file directories at all levels corresponding to the files; the mind map includes multi-level nodes, and the nodes include nodes representing files and nodes representing file directories;

obtaining user operations performed by the user on the nodes on the mind map;

In response to the user operation, a corresponding file management action is performed for the file or file directory represented by the node.

In a fourth aspect of the embodiments of the present specification, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein when the processor executes the program Implement the following method:

Used to respond to a file management operation triggered by a user, organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through a file management page; wherein the file structure includes the file and file directories at all levels corresponding to the files; the mind map includes multi-level nodes, and the nodes include nodes representing files and nodes representing file directories;

obtaining user operations performed by the user on the nodes on the mind map;

In response to the user operation, a corresponding file management action is performed for the file or file directory represented by the node.

The above embodiments in this specification have at least the following beneficial effects:

On the one hand, by organizing the files to be managed into a mind map and outputting to the user, and using the nodes on the mind map to represent the file and the file directory corresponding to the file, the file directory and the file directory of the file can be visually displayed. the hierarchical relationship;

On the other hand, since the user can directly operate the node on the above mind map to complete the file management action of the file or file directory represented by the node, the management efficiency of the user in file management can be improved.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following briefly introduces the accompanying drawings required in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments described in this specification. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings.

Fig. 1a schematically shows a schematic diagram of a mode of displaying a file in the form of an icon;

Fig. 1b schematically shows a schematic diagram of a mode of displaying files in the form of a list;

Fig. 2 schematically shows a kind of schematic diagram of the mode that the file is displayed in the form of the left directory tree;

FIG. 3 schematically shows a schematic diagram of the architecture of a file management system according to an embodiment of the present specification;

FIG. 4 schematically shows a flow chart of a file management method according to an embodiment of the present specification;

FIG. 5 schematically shows a schematic diagram of an output mind map according to an embodiment of the present specification;

FIG. 6 schematically shows a schematic diagram of an output mind map according to an embodiment of the present specification;

FIG. 7 schematically shows a schematic diagram of a file preview operation according to an embodiment of the present specification;

FIG. 8 schematically shows a schematic diagram of an operation of creating a next-level node according to an embodiment of the present specification;

FIG. 9 schematically shows a schematic diagram of a drag operation according to an embodiment of the present specification;

FIG. 10 schematically shows a schematic diagram of an operation of hiding a subordinate node according to an embodiment of the present specification;

FIG. 11 schematically shows a block diagram of a file management apparatus according to an embodiment of the present specification;

FIG. 12 schematically shows a hardware structure diagram of a computer device where a file management apparatus according to an embodiment of the present specification is located;

FIG. 13 schematically shows a schematic diagram of a software product applied to a file management method according to an embodiment of the present specification.

In the drawings, the same or corresponding reference numerals denote the same or corresponding parts.

Detailed ways

The principles and spirit of this specification will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are given only to enable those skilled in the art to better understand and implement the present specification, but not to limit the scope of the present specification in any way. Rather, these embodiments are provided so that this description will be thorough and complete, and will fully convey the scope of this description to those skilled in the art.

As will be appreciated by those skilled in the art, the embodiments of the present specification can be implemented as a system, apparatus, device, method or computer program product. Accordingly, the present specification may be embodied in the form of complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

According to the embodiments of the present specification, a load balancing method, medium, apparatus and computing device are proposed.

In this article, it is to be understood that the terms involved are expressed as follows:

File directory: In a computer or related equipment, a file directory is a file structure that describes a corresponding relationship between files and file storage locations. A file directory is like a virtual container that can contain a set of files and some other file directories.

The specific form of the file directory is not particularly limited in this specification; for example, in practical applications, it may be in the form of a folder, or may be a storage address or a path.

Mind map: also known as brain map, mind map, etc., is a visual presentation form of organizing information with images, using a central keyword to connect all representative words, ideas, tasks or other associations in a radial line Project, the relationship between the themes at all levels is represented by a hierarchical diagram of mutual subordination and correlation,

Furthermore, any number of elements in the drawings is for illustration and not limitation, and any designation is for distinction only and does not have any limiting meaning.

The principles and spirit of the present specification are explained in detail below with reference to several representative embodiments of the present specification.

Application Scenario Overview

In a computer device, files are generally stored in a local or cloud storage device in the form of multi-level file directories. A file directory is a virtual file container. A file directory can contain several files and several other file directories. Another file directory in one file directory is called its sub-file directory.

When users need to view and manage files, files can be displayed in a variety of different visual display display modes.

In the related art, the display modes for visually displaying the managed files usually include the following:

The first is a mode that displays in the form of icons. In this mode, the address bar is usually used to display the path of the current file directory, and the files and directories in the current file directory are displayed in the file display area in the form of file icons and directory icons.

Please refer to FIG. 1a. FIG. 1a is a schematic diagram of displaying files in the form of icons. The address bar 111 shows that the currently displayed file directory DirAA is a sub-file directory of the sub-file directory DirA of the file directory Sample; in the file display area 121 All sub-file directories and files under the file directory DirAA are displayed, in the form of icons corresponding to files or file directories, each icon representing a sub-file directory or file.

The second mode is to display in the form of a list.

When using the display in the form of icons, a single interface can only display one layer of file directories. When designing multi-layer file directories for file operations, it is necessary to switch between multiple interfaces layer by layer, or open multiple interfaces at the same time. Cumbersome and less efficient. Moreover, since a single interface can only display one layer of file directories, users need to know the overall file structure or those files contained in a certain file directory, and need to view one directory layer by layer, which is inefficient.

Please refer to FIG. 1b. FIG. 1b is a schematic diagram of displaying files in the form of a list, similar to the display in the form of icons. The address bar 112 shows that the currently displayed file directory DirAA is a sub-file of the file directory Sample’s sub-file directory DirA Directory; The file display area 121 displays all the sub-file directories and files under the file directory DirAA, which are displayed in the form of a list, and each line of the list represents a sub-file directory or file.

Similar to displaying in the form of icons, when displaying in the form of a list, a single interface can only display one layer of file directories. When performing file operations for designing multi-layer file directories, it is necessary to switch between multiple interfaces layer by layer, or Open multiple interfaces at the same time, the operation is cumbersome and the efficiency is low. Moreover, since a single interface can only display one layer of file directories, users need to know the overall file structure or which files are contained in a certain file directory, and need to view each directory layer by layer, which is inefficient.

The mode in which files are displayed in the form of a directory tree on the left is an improvement in displaying in the form of icons or in the form of lists, adding a directory tree that displays the hierarchical relationship of all file directories.

Please refer to FIG. 2, which is a schematic diagram of the directory tree view of the file; the file directory view shown in FIG. 2 is an improvement to the icon view. On the basis of the address bar 21 and the file display area 22, an additional The directory tree 23, the directory tree 23 displays the file directories under the root file directory Sample in a tree structure, and the highlighted file directory DirAA231 is the currently displayed file directory.

Files are displayed in the form of a directory tree on the left. You can view the hierarchical relationship between directories with the help of the directory tree on the left, but it is still not easy to know which files are contained in a specific file directory. However, when the file directory hierarchy in the files to be managed is complex, the left directory tree will be very long, and you need to slide to view it, which will still affect the efficiency. At the same time, since a single interface can still only display one layer of file directories, when designing multi-layer file directories for file operations, it is also necessary to switch between multiple interfaces, or open multiple interfaces at the same time, which is cumbersome and inefficient.

Program overview

As mentioned above, when files are displayed in the form of icons, lists, or directory trees on the left, when traditional file views are used, there are problems such as inconvenient operation and low efficiency when viewing and managing files.

In view of this, this specification provides a technical solution for visually presenting the file structure of a file in the form of a mind map, so that the user can quickly complete the file management by operating the nodes on the mind map.

During implementation, the client can: organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through the file management page; The corresponding file management action is performed for the file or file directory represented by the node.

Based on the above technical solution, on the one hand, by organizing the files to be managed into a mind map and outputting to the user, and using the nodes on the mind map to represent the files and the file directories corresponding to the files, the files of the files can be displayed intuitively. The hierarchical relationship between directories and files;

On the other hand, since the user can directly operate the node on the above mind map to complete the file management action of the file or file directory represented by the node, the management efficiency of the user in file management can be improved.

Exemplary method

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of one or more embodiments of this specification, as recited in the appended claims.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe.

FIG. 3 is a schematic structural diagram of a file management system provided by an exemplary embodiment. As shown in FIG. 3 , the system may include a network 30 , a server 31 , and several electronic devices, such as a mobile phone 32 , a mobile phone 33 , and a mobile phone 34 .

The server 31 may be a physical server including an independent host, or the server 31 may be a virtual server, a cloud server, or the like carried by a cluster of hosts. Cell phones 32-34 are just one type of electronic device available to users. In fact, users can obviously also use electronic devices such as the following types: tablet devices, notebook computers, PDAs (PDAs, Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.) Various embodiments do not limit this. Network 30 may include various types of wired or wireless networks.

In an embodiment, the server 31 can cooperate with the mobile phones 32-34; wherein, the mobile phones 32-34 can accept user operations, and upload the received commands and files to the server 31 through the network 30, and then the server 31 based on this The protocol of the specification processes the file. In another embodiment, the mobile phones 32-34 can independently implement the file management scheme of this specification; wherein, the mobile phones 32-34 accept user operations, and process the accepted commands and files based on the scheme of this specification, so as to realize the file management scheme. manage.

The solution of this specification will be described in detail below with reference to the accompanying drawings.

Please refer to FIG. 4, which is a flowchart of a file management method provided by an exemplary embodiment.

The file management method is applied to the client, and the method executes the following steps:

Step 402, in response to the file management operation triggered by the user, organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through the file management page; said file and at least one-level file directory corresponding to said file; said mind map includes multi-level nodes, said multi-level nodes including nodes representing files and nodes representing file directories; child nodes of the nodes representing file directories Including nodes representing sub-file directories of the file directory or nodes representing files under the file directory;

The above-mentioned file management operation may include an operation triggered by the user on the client to start the management of the file to be managed; wherein, the specific form of the above-mentioned file management operation is not particularly limited in this specification.

For example, in one example, the above-mentioned client may have one or more file management buttons corresponding to the files to be managed, which are bound to the above-mentioned file management operations, and when the user clicks the above-mentioned file management buttons, triggering a File management operations.

For another example, in another example, the above-mentioned client may have one or more file tags, and the above-mentioned file tags correspond to one or more different files. When the user selects one or more tags, the user tag selected by the user corresponds to The set of files to be managed is regarded as the file to be managed, and the file management operation for the above-mentioned to-be-managed file is triggered.

The file structure of the above file may generally include a file and at least one level of file directory corresponding to the file. Wherein, as mentioned above, the specific form of the above-mentioned file directory is not particularly limited in this specification; for example, in the illustrated embodiment, the above-mentioned file directory may be in the form of a folder, or may also be in the form of a folder. Such as the form of storage address or path.

When the user uses the client to manage files, the client can monitor the above-mentioned file management operations triggered by the user in the background. When the client terminal monitors the above-mentioned file management operation triggered by the user, it can organize the file structure corresponding to the file to be managed into a mind map, and output the above-mentioned mind map to the user through the file management page.

For example, in an example, the above-mentioned file management operation is the operation of the above-mentioned user clicking the above-mentioned file management button as an example. In this case, the client can monitor the above-mentioned file management button. When the action is clicked, the response triggers the file management action.

The above mind map is composed of multi-level nodes representing files and file directories. The node representing the root file directory of the file to be managed serves as the central node of the above mind map, or is referred to as the root node. Each file or file directory under the root file directory is connected to the root node as a child node of the root section, and the sub-file directories and files under the file directory are connected to the file directory as child nodes. This specification does not specifically limit the connection method between nodes. Polyline segment connection, arc line connection, or other connection methods that can clarify the association relationship between nodes can be used, which is not specifically limited in this specification.

The multi-level file directory structure of the file is similar to the multi-level node structure of the mind map, and the nodes of the mind map correspond to files or file directories. Therefore, it is convenient and intuitive to use the form of mind map to organize the file structure. The multi-level file directory structure of the file can be visually displayed in one interface, and the operation of the corresponding file can be performed by the user's operation on the node.

For example, FIG. 5 shows a schematic diagram of an output mind map in an exemplary embodiment. In this exemplary embodiment, the root file directory of the file to be managed includes one file Mdm1, two file directories DirA and DirB, and the file directory DirA includes two files Doc1 and TlbA.

The corresponding mind map organized by the above method includes: root node 50, representing the root file directory Sample of the file to be managed; node 51, representing the file Mdm1 under the root file directory, connected to the root node 50; node 52, representing the root file The file directory DirA under the directory is connected to the root node 50; the node 53, representing the file directory DirB under the root file directory, is connected to the root node 50; the node 521 represents the file Doc1 under the file directory DirA, which is connected to the node 52, and the node 522 Represents the file TlbA under the file directory DirA, connected to the node 52.

The nodes on the above mind map can use the information related to the node as the content of the node, so as to facilitate the user to identify and operate the above node, for example, the file name or file directory name corresponding to the file or file directory represented by the node can be used, or The icon or type icon of the file or file directory corresponding to the node can be used, or the user-defined name of the node can be used, which is not specifically limited in this specification.

It should be noted that the content of a node on the mind map can be displayed at the position corresponding to the node. Wherein, when the content of a node includes multiple contents, the multiple contents of the node may be displayed at the same position corresponding to the node, or may be displayed at different positions corresponding to the node, which are not specified in this specification. limited.

For example, the location corresponding to the node may be inside the area where the node is located.

In the illustrated embodiment, a node on the mind map can use the file name or file directory name corresponding to the file or file directory represented by the node as the content of the node, or can use the icon of the file or file directory corresponding to the node Or the type icon is used as the content of the node, or the file name or file directory name corresponding to the file or file directory represented by the node and the icon or type icon of the file or file directory corresponding to the node can be used as the content of the node.

For example, referring to FIG. 5 , the content of each node includes the file name or file directory name of the file or file directory corresponding to the node, and the icon of the file directory or the type icon of the file. For example, the file corresponding to the node 521 is a brain map file Mdm1, and the content of the node includes a brain map file type icon and a file name "Mdm1".

In the illustrated embodiment, for the node content of the node representing the file directory on the mind map, the number of files included in the file directory represented by the node may also be included. In this case, for a node representing a file directory in the mind map, the number of files contained in the file directory represented by the node can be determined, and the above-mentioned number of files is displayed at the position corresponding to the node.

For example, referring to FIG. 5, the number of files contained in the file directory DirA is 2, which represents the node content of the node 52 of the file directory DirA, and may also include the number of files contained in the file directory DirA. The number of files may specifically be The output display is displayed at the position corresponding to the node 52 (for example, as shown in FIG. 5 , it is inside the icon of the node 52 ). Correspondingly, assuming that the number of files contained in the file directory DirB is 0, it represents the node content of the node 53 of the file directory DirB, and may also include the number of files contained in the file directory DirB. The output is displayed at the position corresponding to the node 52 .

It should be noted that the above-mentioned number of files may be the number of files contained in the current-level directory of the file directory corresponding to the above-mentioned node. When a sub-file directory exists in the file directory corresponding to the above node, the above-mentioned number of files may also be the sum of the number of files contained in the current-level directory of the file directory corresponding to the above-mentioned node and the sub-file directories at all levels contained in it. The total number of documents obtained is not specifically limited in this specification.

In an exemplary embodiment shown, child nodes of a node representing a file include nodes representing other files associated with the file.

The node representing the file on the mind map may also have child nodes, and the child node of the node representing the file may represent the file associated with the file.

For example, Figure 6 shows a mind map that is output in an exemplary embodiment. Node 61, which represents the document DocA, has two child nodes, node 611 and node 612.

For example, in a practical application, if a document A requires a series of documents B, all nodes representing the above series of documents B can be regarded as child nodes of the node representing document A. The series file B is placed in the file directory, which can better reflect the relationship between the file and the files in the file directory.

Step 404: Obtain user operations of the user on the nodes on the mind map.

After the client outputs the file to be managed in the form of a mind map, the user can perform various preset user operations on the nodes on the mind map to trigger file management actions. The client can also monitor user operations on the above nodes. When the client terminal monitors the above-mentioned user operation, it can execute the corresponding file management action.

The client can predefine several user operations for the node. The above-mentioned user operations can be mouse or touch operations such as clicking, long-pressing, dragging, etc. on the corresponding area of the node, or key operations entered through the keyboard when the node is selected, or user input through other input devices such as microphones and cameras. operation, which is not specifically limited in this specification. The specific user operations mentioned in all the embodiments in this specification are exemplary, and will not be repeated below.

Step 406, in response to the user operation, perform a corresponding file management action for the file or file directory represented by the node.

After acquiring the above-mentioned user operation, the client performs the file management action corresponding to the user operation on the file or file directory represented by the node targeted by the user operation.

Wherein, the client may bind the corresponding file management actions for the above-defined user operations in advance. The above file management actions may include various file management actions for files or file directories, such as previewing, viewing, editing, renaming, moving, sorting, and deleting, which are not specifically limited in this specification.

In the application, according to actual needs, on different types of terminals, different user operations, and user operations for different areas corresponding to nodes, different file management actions can be bound. The corresponding relationship between specific user operations and specific file management actions can be adjusted according to actual needs, which is not specifically limited in this specification.

For example, the user operation may be to click the area corresponding to the node with the left mouse button, and the bound file management action may be the view action.

In this case, after listening to the user's operation of clicking the area corresponding to the node with the left mouse button of the above node, the client can open a viewing interface, and output the file or file directory corresponding to the above node in the viewing interface content for viewing or further action by the user.

For another example, the user operation may be a long-press operation on the file type icon on the touch screen, and the bound file management action may be displaying the editing history information of the file.

In this case, after listening to the user's long-press operation on the touch screen on the file type icon of the file corresponding to the node in the node content, the client terminal can output an information display above the node for a predetermined period of time. box, and the editing history information of the file is displayed in the above information display box.

In an exemplary embodiment shown, the obtained user operations on the nodes on the mind map include a file preview operation.

For example, a mouse pointer hover operation can be used on the desktop to bind it as a file preview operation, and it is determined that the file preview operation is triggered when it is detected that the user moves the mouse pointer to the area corresponding to the node for a predetermined period of time.

In response to the above file preview operation, the node type of the node is determined, and if the node is a node representing a file, the preview content of the file represented by the node is output at the position corresponding to the node.

For example, a preview window may be displayed at the position corresponding to the node to be previewed, and the window may include the specific content of the file to be previewed, the file name, the file creation time, the file modification time and other information.

For example, please refer to FIG. 7, which shows a schematic diagram of a file preview operation in an exemplary embodiment.

The node 721 is a node representing a document, and this node represents the text document Doc7. When the user moves the mouse pointer 700 to the node 721 for a specified duration, a preview window 7210 is displayed in the area corresponding to the node 721, and the preview window includes the file content of the text file Doc7.

In the illustrated exemplary embodiment, the acquired user operation on the node on the mind map includes an operation of creating a new next-level node.

For example, on the desktop side, you can right-click the corresponding area of the node or bind the Enter key of the keyboard to create a new next-level node operation.

After obtaining the user's operation of creating a new next-level node, a selection menu is output at the position corresponding to the node. The above menu contains multiple file type options, such as text, table, brain map, presentation, folder, etc.

After obtaining the file type option selected by the user, a next-level node of the above node is created, and the next-level node represents a blank file of the file type selected by the user. For example, when the file type option selected by the user is text, the newly created next-level node represents a blank text file, and when the file type option selected by the user is a folder, the newly-created lower-level node represents an empty file directory.

The selection menu can provide an option to create a new file from a template. After the user selects this option, another option menu is output. The option menu contains preset file template options. The user can select the file template option to create a new file from the template as the current node. child node.

For example, please refer to FIG. 8, which shows a schematic diagram of an operation of creating a next-level node in an exemplary embodiment.

The node 81 is the node representing the file directory Dir8. After the user clicks on the node, a selection menu 811 is output next to the node. The options selected by the user create nodes representing blank files of the corresponding type as child nodes of node 81 .

In particular, when the user selects the "folder" option, a node representing the file directory is created as a child node of the node 81; when the user selects the "from template" option, an option menu is output to enable the user to select a preset template , creates a new file from the template as a child of node 81.

In the illustrated embodiment, the acquired user operation of the node on the mind map includes an operation of creating a new node at the same level.

For example, on the desktop side, you can bind the keyboard Tab key to create a new peer node operation.

After obtaining the user's new peer operation, a selection menu is output at the position corresponding to the node. The above menu contains multiple file type options, such as text, table, brain map, presentation, folder, etc.

After obtaining the file type option selected by the user, a peer node of the above node is created, and the peer node represents a blank file of the file type selected by the user. For example, when the file type option selected by the user is text, the newly created sibling node represents a blank text file, and when the file type option selected by the user is a folder, the newly created sibling node represents an empty file directory.

The selection menu can provide an option to create a new file from a template. After the user selects this option, another option menu is output. The option menu contains preset file template options. The user can select the file template option to create a new file from the template as the current node. child node.

For example, if the operation of creating a new peer node is performed on the node 81 in FIG. 8 , the newly created peer node will be used as a child node of the node 60 .

In the illustrated embodiment, the obtained user operation on the node on the mind map includes a file import operation.

After acquiring the user's file import operation for the node, a selection menu is output, and the selection menu includes the user's local file or file directory for the user to select. After the user selects a file or file directory, obtain the file or folder selected by the user, and create a child node of the above node, representing the file or file directory selected by the user.

In the illustrated embodiment, after a file import operation imports a local file directory, it is determined whether the local file directory contains a file or a sub-file directory, and if the local file directory contains a file or a sub-file directory, it is the local file The file directories and sub-files at all levels under the directory establish multi-level nodes.

In the illustrated embodiment, the obtained user operation on the node on the mind map includes a renaming operation, wherein the renaming operation includes a renaming trigger operation and an input string operation;

For example, on the desktop side, you can double-click the corresponding area of the node with the left mouse button to bind and rename the trigger operation.

After the user's renaming trigger operation for the node is obtained, the character string input by the user is obtained, and the file name of the file corresponding to the node or the file directory name of the file directory is modified to the character string input by the user.

In practical applications, it can also be added to judge the validity of the character string input by the user as the file name or file directory name.

In the illustrated embodiment, the acquired user operation on the node on the mind map includes a drag operation.

When the user selects and drags the node to the position specified by the user, it is judged whether the position specified by the user is located in the corresponding area of another node. If the position specified by the user is located in the corresponding area of another node, the node is regarded as the child nodes of the node and move to the corresponding position.

When the position specified by the user is considered as the area corresponding to the parent node of the current node, it is judged whether the position specified by the user is compared with the current position of the node, and whether the relative position of the node at the same level has changed. If there is a change, move the current node to the user. specified location. At this time, the user's drag operation changes the order of the file or file directory corresponding to the node in the current file directory.

As shown in FIG. 9 , FIG. 9 shows a schematic diagram of a drag operation for a node in an exemplary embodiment.

As shown in 9(a), node 91 is a child node of node 90, 901 is the position when the user selects node 91, and 902 is the position to which the user drags node 91 to move; since the position of 902 is the position corresponding to node 92, as shown in As shown in 9(b), node 91 will act as a child node of node 92 and move to the corresponding position.

In practical applications, for a node with subordinate nodes, the drag operation can move the node and all subordinate nodes as a whole.

In the illustrated embodiment, the acquired user operation of the node on the mind map includes an operation of switching and hiding lower-level nodes.

The child nodes of a node on the mind map can be called the next-level node of the node, the child nodes of the node, and the child nodes at all levels of the child node, called the lower-level node of the node. When the mind map has many hierarchical relationships and many nodes at each layer, the mind map may be very large. But sometimes the user only cares about the first few levels of the mind map or the child nodes of a specific node, etc. At this time, the lower-level nodes of some nodes can be hidden and expanded when necessary.

The toggling hide subordinate node operation may include a hide subordinate node operation and an unhide subordinate node operation. Hide subordinate node actions and unhide subordinate node actions can be bound to the same user action, or can be bound to different user actions.

In the illustrated embodiment, the obtained user operations on the nodes on the mind map include hiding lower-level node operations.

For example, on the desktop side, you can bind the left key of the keyboard to hide lower-level node operations.

After obtaining the user's hidden subordinate node operation on the node, determine whether the subordinate node of the node is in the hidden state. If the subordinate node of the node is not in the hidden state, hide the subordinate node of the node, and display the subordinate node in the corresponding position of the node. The number of subordinate nodes of the node.

As shown in FIG. 10 , FIG. 10 shows a schematic diagram of the operation of hiding lower-level nodes in an exemplary embodiment.

As shown in 10(a), node 102 has two child nodes 1021 and node 1022, and node 1021 has one child node, node 10211. After the user's command to hide subordinate nodes of node 102 is obtained, since the nodes under node 102 are not hidden, all subordinate nodes of node 102, including node 1021, node 2111, and node 1022, are hidden at the position corresponding to node 102. The number of subordinate nodes of node 102 is displayed as 1000. Since the number of subordinate nodes of node 102 is 2, the number of subordinate nodes of node 102 is displayed as 2, as shown in 10(b).

In practical applications, the number of subordinate nodes of the node that can be displayed at the corresponding position of the node that hides the subordinate node can be the number of subordinate nodes of the node, or the total number of subordinate nodes of the node, Or the total number of nodes representing files in the subordinate nodes of the node, which is not specifically limited in this specification.

In the illustrated embodiment, the acquired user operation on the node on the mind map includes an operation of unhiding lower-level nodes.

For example, on the desktop side, you can bind the right key of the keyboard to unhide the subordinate node operation.

After obtaining the user's operation of unhiding the subordinate nodes of the node, determine whether the subordinate nodes of the node are in the hidden state. The number of subordinate nodes to delete this node.

In practical applications, the unhiding operation can cancel the hidden state of only the next-level node of the node, and the subordinate nodes of the next-level node of the node remain hidden; the unhiding operation can also cancel the subordinate nodes at all levels of the node at the same time. The hidden state is not specifically limited in this specification.

In the illustrated embodiment, the file to be managed supports multiple display modes. The display mode includes the above-mentioned mind map view that organizes files in the form of a mind map, and can also include a mode displayed in the form of a list, a mode displayed in the form of an icon, and a mode displayed in the form of a directory tree on the left. and other common display modes.

The above file management page has a set of view options, and each view option corresponds to the corresponding file display mode. The group of view options may be a group of buttons, or multiple options in a pull-down menu under a button, or a group of shortcut keys and other forms. This specification does not specifically limit the form of view options.

After acquiring the view option selected by the user, switch to the file display mode corresponding to the view option selected by the user, and output to the user on the above-mentioned file management interface, so that the user can view and manage the files to be managed.

In the illustrated embodiment, the default display mode for the to-be-managed file supported by the file management page is a mode displayed based on a mind map.

When the user opens the above file management interface, the mind map view can be used by default as the file display mode of the file to be managed. The user can subsequently switch the file display mode through the above view options.

In an exemplary embodiment shown, the file includes an online document. The file directory includes folders for storing online documents.

Files can include local files and online files, and online files can include online documents. Online documents can include online texts, online forms, online brain maps, online presentations and other online files, and online folders are used to store online documents. Online documents can be easily viewed and edited in the cloud.

Clients may include various software clients with file management requirements or file management functions, such as operating systems, file management software, communication software, network disk software and other clients, which are not specifically limited in this specification.

In an exemplary embodiment shown, the client includes enterprise instant messaging software.

Enterprise instant messaging software usually involves scenarios such as file transfer, management, and collaboration, including collaborative management of online documents, and the solutions in this manual are applicable.

In an exemplary embodiment of the present specification, a file management apparatus is also provided. Please refer to FIG. 11. FIG. 11 is a block diagram of a file management apparatus according to an embodiment of the present specification. The device is applied to a client; the device includes:

The organization unit 1110 is used to respond to the file management operation triggered by the user, organize the file structure corresponding to the file to be managed into a mind map, and output the mind map to the user through the file management page; wherein, the file structure Including the file and file directories at all levels corresponding to the file; the mind map includes multi-level nodes, and the nodes include nodes representing files and nodes representing file directories;

an obtaining unit 1120, configured to obtain the user's user operation on the node on the mind map;

The executing unit 1130 is configured to, in response to the user operation, execute a corresponding file management action for the file or file directory represented by the node.

Optionally, the organizing unit 1110 is further configured to display node content in the node, where the node content includes: an icon corresponding to the file or file directory represented by the node, and/or a name corresponding to the file or file directory represented by the node.

Optionally, the organization unit 1110 is further configured to determine a node representing a file directory in the mind map, and the number of files contained in the represented file directory; and display the number of files at a position corresponding to the node.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the user's file preview operation for the node of the mind map;

Correspondingly, the execution unit 1130 is specifically configured to determine the node type of the node in response to the file preview operation, and if the node is a node representing a file, output the file represented by the node at the position corresponding to the node preview content.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the user's first node creation operation for the nodes of the mind map;

Correspondingly, the executing unit 1130 is specifically configured to, in response to the first node creation operation, create a new node representing a file or a file directory according to the user configuration, as a child node of the node.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the user's second node creation operation for the nodes of the mind map;

Correspondingly, the executing unit 1130 is specifically configured to, in response to the second node creation operation, create a new node representing a file or a file directory according to the user configuration, as a peer node of the node.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the user's file import operation for the nodes of the mind map;

Correspondingly, the execution unit 1130 is specifically configured to, in response to the file import operation, output a selection menu, where the selection menu includes options representing the user's local file or file directory, obtain the option selected by the user, and create a new node for the node. A child node, where the child node represents the file or file directory corresponding to the option selected by the user.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the user's renaming operation for the nodes of the mind map;

Correspondingly, the executing unit 1130 is specifically configured to, in response to the renaming trigger operation, obtain the character string input by the user, and rename the file or file directory corresponding to the node to the character string input by the user.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the user's drag operation on the node of the mind map;

Correspondingly, the execution unit 1130 is specifically configured to move the node to a position specified by the user in response to the drag operation.

Optionally, the obtaining unit 1120 is specifically configured to: obtain the hidden subordinate node operation of the user for the node of the mind map;

Correspondingly, the execution unit 1130 is specifically configured to, in response to the operation of hiding the subordinate node, determine whether the subordinate node of the node is in the hidden state, and if the subordinate node of the node is not in the hidden state, hide the subordinate node of the node, And display the number of subordinate nodes of the node at the corresponding position of the node.

Optionally, the obtaining unit 1120 is specifically configured to: obtain a user's operation of unhiding subordinate nodes for the nodes of the mind map;

Correspondingly, the execution unit 1130 is specifically configured to, in response to the operation of unhiding the subordinate node, determine whether the subordinate node of the node is in the hidden state, and if the subordinate node of the node is in the hidden state, unhide the subordinate node of the node. , and delete the number of subordinate nodes of this node at the corresponding position of this node.

Optionally, the apparatus further includes: a switching unit 1140, configured to acquire the view option selected by the user and, in response to the view option selected by the user, switch the display mode of the file management page to the display mode corresponding to the view option .

For details of the implementation process of the functions and functions of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method, which will not be repeated here.

For the apparatus embodiments, since they basically correspond to the method embodiments, reference may be made to the partial descriptions of the method embodiments for related parts. The device embodiments described above are only illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed over multiple network elements. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement it without creative effort.

In the exemplary embodiments of this specification, embodiments of an apparatus and a terminal to which it is applied are also provided.

The embodiments of the file management apparatus in this specification can be applied to computer equipment, such as a server or a terminal equipment. The apparatus embodiment may be implemented by software, or may be implemented by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for operation by the processor where the file management is located. From the perspective of hardware, as shown in FIG. 12 , it is a hardware structure diagram of the computer device 120 where the file management apparatus according to the embodiment of the present specification is located, except for the processor 1212 , the memory 1230 , the network interface 1220 , and the non-processor 1212 shown in FIG. 12 . In addition to the volatile memory 1240, the server or electronic device where the apparatus 1231 is located in the embodiment may also include other hardware, usually according to the actual function of the computer device, which will not be repeated here.

In an exemplary embodiment of the present specification, a computer-readable storage medium is also provided, on which a program product capable of implementing the above-mentioned method of the present specification is stored. In some possible embodiments, various aspects of this specification can also be implemented in the form of a program product, which includes program code for causing the program product to run on a terminal device when the program product is executed. The terminal device performs the steps according to various exemplary embodiments of this specification described in the above-mentioned "Example Method" section of this specification.

Referring to FIG. 13, a program product 130 for implementing the above method according to an embodiment of the present specification is described, which can adopt a portable compact disc read only memory (CD-ROM) and include program codes, and can be stored in a terminal device, For example running on a personal computer. However, the program product of this specification is not limited thereto, and in this document, a readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal in baseband or as part of a carrier wave with readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium can also be any readable medium, other than a readable storage medium, that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out the operations of this specification may be written in any combination of one or more programming languages, including object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural Programming Language - such as the "C" language or similar programming language. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

While this specification contains many specific implementation details, these should not be construed as limiting the scope of any invention or what may be claimed, but rather are used primarily to describe features of specific embodiments of particular inventions. Certain features that are described in this specification in multiple embodiments can also be implemented in combination in a single embodiment. On the other hand, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may function as described above in certain combinations and even be originally claimed as such, one or more features from a claimed combination may in some cases be removed from the combination and the claimed A protected combination may point to a subcombination or a variation of a subcombination.

Similarly, although operations are depicted in the figures in a particular order, this should not be construed as requiring the operations to be performed in the particular order shown or sequentially, or that all illustrated operations be performed, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various system elements and components in the above-described embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product , or packaged into multiple software products.

Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Furthermore, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.

The above descriptions are only preferred embodiments of this specification, and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in this specification. within the scope of protection.

Claims (16)

1. A file management method is applied to a client, and is characterized by comprising the following steps:

responding to file management operation triggered by a user, organizing a file structure corresponding to a file to be managed into a mind map, and outputting the mind map to the user through a file management page; wherein the file structure comprises the file and at least one level of file directory corresponding to the file; the mind map comprises a representative file directory and a plurality of levels of nodes representative of files;

acquiring user operation of a user for a node on the thinking guide graph;

in response to the user operation, performing a corresponding file management action with respect to a file or file directory represented by the node.

2. The method of claim 1, wherein the child nodes of the thought graph representing nodes of a file directory comprise: a node representing a subfile directory of the file directory or a node representing a file under the file directory;

the child nodes of the node representing the file include nodes representing other files associated with the file.

3. The method of claim 2, further comprising:

determining the number of the nodes representing the file directories in the thinking graph, wherein the number of the files contained in the represented file directories is determined;

and displaying the file number at the position corresponding to the node.

4. The method of claim 1, wherein the user operation comprises a file preview operation performed for a node on the mind map;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

responding to the file preview operation, and determining the node type of the node;

and if the node is the node representing the file, outputting the preview content of the file represented by the node at the position corresponding to the node.

5. The method of claim 1, wherein the user action comprises a first node creation action performed on a node on the mind map; the first node new construction operation is used for constructing a lower node for the node;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

responding to the new construction operation of the first node, and outputting a selection menu at a position corresponding to the node, wherein the selection menu comprises a plurality of type options, and the type options comprise a file directory option and a plurality of file type options;

acquiring a type option selected by a user; and newly building a node representing a file directory corresponding to the type option selected by the user or a node representing a blank file of the corresponding file type as a child node of the node.

6. The method of claim 1, wherein the user action comprises a second node creation action performed on a node on the mind map; the second node new creation operation is used for creating a peer node for the node;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

responding to the new construction operation of the second node, and outputting a selection menu at a position corresponding to the node, wherein the selection menu comprises a plurality of type options, and the type options comprise a file directory option and a plurality of file type options;

acquiring a type option selected by a user; and creating a node representing a file directory corresponding to the type option selected by the user or a node representing a blank file of the corresponding file type as a peer node of the node.

7. The method of claim 1, wherein the user operation comprises a file import operation for a node on the mind map;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

responding to the file import operation, and outputting a selection menu, wherein the selection menu comprises options of files or file directories which represent the local part of a user;

and acquiring options selected by a user, and creating child nodes of the node, wherein the child nodes represent files or file directories corresponding to the options selected by the user.

8. The method of claim 1, wherein the user operation comprises a rename operation for a node on the mind map, the rename operation comprising a rename trigger operation and an enter string operation;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

and responding to the renaming triggering operation, acquiring the character string input by the user, and renaming the file or the file directory corresponding to the node as the character string input by the user.

9. The method of claim 1, wherein the user operation comprises a drag operation for a node on the mind map;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

and moving the node to a position designated by a user in response to the dragging operation.

10. The method of claim 1, wherein the user action comprises hiding subordinate node actions for switching of nodes on the mind map;

the performing of the corresponding file management action with respect to the file or file directory represented by the node comprises:

in response to the switching to hide the subordinate node operation, determining whether a subordinate node of the node is in a hidden state;

if the subordinate node of the node is not in a hidden state, hiding the subordinate node of the node, and displaying the number of the subordinate nodes of the node at the position corresponding to the node;

and if the subordinate node of the node is in a hidden state, the hiding of the subordinate node of the node is canceled, and the number of the subordinate nodes of the node is deleted at the position corresponding to the node.

11. The method according to claim 1, wherein the document management page supports a plurality of display modes for the document to be managed; wherein the plurality of display modes include a mode of displaying based on a form of a mind map; the document management page includes a plurality of view options corresponding to the plurality of display modes;

the method further comprises the following steps:

acquiring view options selected by a user;

and responding to the view option selected by the user, and switching the display mode of the file management page to the display mode corresponding to the view option.

12. The method according to claim 11, wherein the default display mode supported by the document management page for the document to be managed is the mode of mind map based display.

13. The method of claim 1, wherein the file comprises an online document; the file directory includes folders for storing online documents.

14. A file management device applied to a client, the device comprising:

the organizing unit is used for responding to file management operation triggered by a user, organizing a file structure corresponding to a file to be managed into a thinking guide graph and outputting the thinking guide graph to the user through a file management page; the file structure comprises the file and file directories at all levels corresponding to the file; the mind map includes a plurality of levels of nodes including nodes representing files and nodes representing file directories;

the acquisition unit is used for acquiring user operation of a user aiming at the nodes on the thinking map;

and the execution unit is used for responding to the user operation and executing corresponding file management action aiming at the file or the file directory represented by the node.

15. A storage medium having stored thereon a client which, when executed, implements the method of any one of claims 1-13.

16. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the method of any one of claims 1-13.

Images