CN114416640A - File management method and device - Google Patents

Abstract

The specification provides a file management method and device, which are applied to a client. The method comprises the following steps: and 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 includes a directory of representative files and a plurality of levels of nodes representing the files. And acquiring user operation of a user aiming at the nodes 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.

Description

File management method and device

Technical Field

The embodiment of the specification relates to the technical field of computers, in particular to a file management method and device.

Background

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

File management generally involves managing file structures (such as file directories) related to files, in addition to managing files themselves. In practical applications, if the managed file involves a relatively complex file structure, the file management efficiency may be affected.

Disclosure of Invention

To overcome the problems in the related art, the present specification provides the following methods and apparatuses.

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

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.

In a second aspect of embodiments of the present specification, there is provided a file management apparatus applied to a client, the apparatus including:

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.

In a third aspect of embodiments of the present specification, there is provided a storage medium; the storage medium is stored with a client, and the client realizes the following steps when executing:

the system comprises a file management page, a thinking guide graph and a user interface, wherein the file management page is used for responding to file management operation triggered by the user, organizing a file structure corresponding to a file to be managed into the thinking guide graph and outputting the thinking guide graph to the user through the 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;

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.

In a fourth aspect of embodiments herein, 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 the processor implements the following method when executing the program:

the system comprises a file management page, a thinking guide graph and a user interface, wherein the file management page is used for responding to file management operation triggered by the user, organizing a file structure corresponding to a file to be managed into the thinking guide graph and outputting the thinking guide graph to the user through the 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;

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.

The above embodiments of the present specification have at least the following advantageous effects:

on one hand, files to be managed are organized into a thinking graph and output to a user, and nodes on the thinking graph are used for representing the files and file directories corresponding to the files, so that the hierarchical relationship between the file directories of the files and the files can be visually shown;

on the other hand, since the user can perform the file management operation of the file or the file directory represented by the node by directly operating the node on the thought graph, the management efficiency of the user in file management can be improved.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and other drawings can be obtained by those skilled in the art according to the drawings.

FIG. 1a schematically illustrates a schematic view of a mode of displaying a file in the form of an icon;

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

FIG. 2 schematically illustrates a schematic diagram of a mode of displaying files in the form of a left-side directory tree;

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

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

FIG. 5 schematically illustrates a schematic diagram of a thought graph of an output according to an embodiment of the present description;

FIG. 6 schematically illustrates a schematic diagram of a thought graph of an output according to an embodiment of the present description;

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

FIG. 8 is a schematic diagram illustrating the operation of a newly created next level node according to an embodiment of the present disclosure;

FIG. 9 is a diagram schematically illustrating a drag operation according to an embodiment of the present disclosure;

fig. 10 schematically illustrates a schematic diagram of a hidden lower node operation according to an embodiment of the present specification;

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

FIG. 12 is a diagram schematically illustrating a hardware configuration of a computer device in which a file management apparatus according to an embodiment of the present specification is located;

fig. 13 schematically shows 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 indicate the same or corresponding parts.

Detailed Description

The principles and spirit of the present description will be described with reference to a number of exemplary embodiments. It is understood that these embodiments are given solely to enable those skilled in the art to better understand and to implement the present description, and are not intended to limit the scope of the present description in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the description to those skilled in the art.

As will be appreciated by one skilled in the art, embodiments of the present description may be embodied as a system, apparatus, device, method, or computer program product. Thus, the present description may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to an embodiment of the specification, a load balancing method, a medium, a device and a computing device are provided.

In this context, it is to be understood that the terms referred to are as follows:

file directory: in a computer or related device, a file directory is a file structure that describes a correspondence between files and file storage locations. The file directory is similar to a virtual container and may contain a group of files and other file directories.

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

Mindset map (mind map): also called brain graph, mind graph, etc., is a visual display form using image to arrange information, uses a central key word to connect all the representative words, ideas, tasks or other related items in radial line form, and displays the relationship of all levels of topics by using mutual membership and related hierarchical graphs,

moreover, any number of elements in the drawings are by way of example and not by way of limitation, and any nomenclature is used solely for differentiation and not by way of limitation.

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

Application scene overview

In a computer device, files are generally stored in a local or cloud storage device in the form of a multi-level file directory. A file directory is a virtual file container that may contain several files and several other file directories, one file directory being referred to as its subfiles.

When a user needs to view and manage a file, the file can be displayed in a plurality of different display modes of visual display.

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

first, a mode in which display is performed in the form of an icon. In this mode, the path of the current file directory is usually shown using an address bar, and the files and directories in the current file directory are shown in the file display area in the form of file icons and directory icons.

Referring to fig. 1a, fig. 1a is a schematic diagram of a file displayed in an icon form, and an address bar 111 shows that a currently displayed file directory DirAA is a subfile directory of a subfile directory DirA of a file directory Sample; all the subfile directories and files in the file directory DirAA are displayed in the file display area 121, and are displayed in the form of icons corresponding to the files or the file directories, and each icon represents one subfile directory or file.

Second, a mode in which display is performed in the form of a list.

When the display is carried out in the icon form, only one layer of file directory can be displayed on a single interface, and when the file operation of designing multiple layers of file directories is carried out, the multiple interfaces need to be switched layer by layer or opened simultaneously, so that the operation is complex and the efficiency is low. In addition, because a single interface can only display one layer of file directory, a user needs to know the whole file structure or the files contained in a certain other file directory, and the files need to be checked layer by layer through the directories, so that the efficiency is low.

Referring to fig. 1b, fig. 1b is a schematic diagram of a file displayed in a list form, which is similar to an icon form, and an address bar 112 shows that the currently displayed file directory DirAA is a subfile directory DirA of a subfile directory Sample; all the sub-file directories and files under the file directory DirAA are shown in the file showing area 121, and are shown in a list form, where each line of the list represents one sub-file directory or file.

Similar to the icon display, when the icon display is performed in a list form, only one layer of file directory can be displayed on a single interface, and when the file operation of designing multiple layers of file directories is performed, switching among multiple interfaces needs to be performed layer by layer, or multiple interfaces need to be opened simultaneously, so that the operation is complex, and the efficiency is low. Moreover, because a single interface can only display one layer of file directory, a user needs to know the whole file structure or which files are contained in a certain other file directory, and the files need to be checked layer by layer through the directories, so that the efficiency is low.

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

Referring to FIG. 2, FIG. 2 is a diagram of a directory tree view of a file; the file directory shown in fig. 2 is an improvement of the icon view, and is added with a directory tree 23 on the basis of the address bar 21 and the file display area 22, the directory tree 23 displays all the file directories under the root file directory Sample in a tree structure, wherein the highlighted file directory DirAA231 is the currently displayed file directory.

The files are displayed in the form of a left directory tree, and the hierarchical relationship between directories can be viewed by means of the left directory tree, but it is still inconvenient to know which files are contained in a specific file directory. However, when the file directory hierarchy in the file to be managed is complex, the directory tree on the left side is long, and needs to be checked in a sliding manner, which still affects the efficiency. Meanwhile, as a single interface can only display one layer of file directory, when the file operation of designing multiple layers of file directories is carried out, the multiple interfaces also need to be switched or opened simultaneously, so that the operation is complicated and the efficiency is low.

Summary of the solution

As described above, when a file is viewed from a conventional file, such as when the file is displayed in the form of an icon, a list, or a left directory tree, the file is viewed and managed, and there are problems of inconvenient operation, low efficiency, and the like.

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

In implementation, the client may: organizing a file structure corresponding to a file to be managed into a mind map, and outputting the mind map to a user through a file management page; and executing corresponding file management actions aiming at the files or file directories represented by the nodes according to the user operation of the user aiming at the nodes on the thinking graph.

Based on the technical scheme, on one hand, files to be managed are organized into a thinking graph and output to a user, nodes on the thinking graph are used for representing the files and file directories corresponding to the files, and the hierarchical relationship between the file directories of the files and the files can be displayed intuitively;

on the other hand, since the user can perform the file management operation of the file or the file directory represented by the node by directly operating the node on the thought graph, the management efficiency of the user in file management can be improved.

Exemplary method

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

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

FIG. 3 is an architectural diagram of a file management system in accordance with an illustrative embodiment. As shown in fig. 3, the system may include a network 30, a server 31, a number of electronic devices, such as a cell phone 32, a cell phone 33, a cell phone 34, and so on.

The server 31 may be a physical server comprising an independent host, or the server 31 may be a virtual server, a cloud server, etc. hosted by a cluster of hosts. Cell phones 32-34 are just one type of electronic device that a user may use. In fact, it is obvious that the user can also use electronic devices of the type such as: tablet devices, notebook computers, Personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited by one or more embodiments of the present disclosure. The network 30 may include various types of wired or wireless networks.

In one embodiment, the server 31 may cooperate with the handsets 32-34; wherein, the mobile phones 32-34 can receive user operation, and upload the received command and file to the server 31 through the network 30, and then the server 31 processes the file based on the scheme of the present specification. In another embodiment, the handsets 32-34 may independently implement the file management scheme of the present specification; wherein, the mobile phones 32-34 receive user operation, and process the received commands and files based on the scheme of the specification to realize file management.

The embodiments of the present description will be described in detail below with reference to the accompanying drawings.

Referring to fig. 4, fig. 4 is a flowchart illustrating a file management method according to an exemplary embodiment.

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

step 402, 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 comprises the file and at least one level of file directory corresponding to the file; the mind map includes multi-level nodes including nodes representing files and nodes representing file directories; the child nodes of a node representing a file directory include nodes representing child file directories of the file directory or nodes representing files under the file directory;

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

For example, in one example, the client may have one or more file management keys corresponding to files to be managed, bind the file management operation, and trigger the file management operation for the corresponding files to be managed when the user clicks the file management key.

For another example, in another example, the client may have one or more file tags, where the file tags correspond to one or more different files, and when the user selects one or more tags, a set of files corresponding to the user tag selected by the user is regarded as a file to be managed, and a file management operation for the file to be managed is triggered.

The file structure of the file may generally include a file and at least one level of file directory corresponding to the file. As described above, the specific form of the file directory is not particularly limited in the present specification; for example, in the illustrated embodiment, the file directory may be in the form of a folder, or may be in the form of a storage address or path.

In the process of file management by a user using a client, the client can monitor the file management operation triggered by the user in the background. When the client monitors the file management operation triggered by the user, the file structure corresponding to the file to be managed can be organized into a thought guide graph, and the thought guide graph is output to the user through a file management page.

For example, in an example, the file management operation is an operation of the user clicking a file management button, in which case, the client may monitor the file management button, and trigger the file management operation in response to the monitoring of the click operation of the user mouse on the file management button.

The thinking map is composed of a representative file and a multi-level node representing a file directory. The node representing the root file directory of the file to be managed serves as the central node of the above-mentioned thought graph, or called 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 node, and the child file directory and the files under the file directory are connected to the file directory as child nodes. The present specification does not specifically limit the connection manner between the nodes, and may use a broken line connection, an arc connection, or other connection manners that can clarify the association relationship between the nodes, which is not specifically limited in the present specification.

The multilevel file directory structure of a file is similar to the multilevel node structure of a thought graph, with the nodes of the thought graph corresponding to the file or file directory. Therefore, the file structure is conveniently and intuitively organized in the form of a mind map, the multi-level file directory structure of the file can be intuitively displayed in one interface, and the operation on the file is corresponding to the operation on the node by a user.

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

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

The nodes on the thought graph may use information related to the nodes as contents of the nodes, so as to facilitate a user to identify and operate the nodes, for example, a file name or a file directory name corresponding to a file or a file directory represented by the node may be used, an icon or a type icon of the file or the file directory corresponding to the node may be used, or a user-defined name of the node may be used, which is not specifically limited in this specification.

It should be noted that the contents of the node on the thought-map may be displayed at the corresponding position of the node. When the node content includes a plurality of contents, the plurality of contents may be displayed at the same position corresponding to the node, or may be displayed at different positions corresponding to the nodes, which is not specifically limited in this specification.

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

In one embodiment shown, a node on the thought graph may use a file name or file directory name corresponding to a file or file directory represented by the node as the content of the node, or may use an icon or type icon of a file or file directory corresponding to the node as the content of the node, or may use both a file name or file directory name corresponding to a file or file directory represented by the node and an icon or type icon of a file or file directory corresponding to the node as the content of the node.

For example, referring to fig. 5, the content of each node includes a file name or a file directory name of a file or a file directory corresponding to the node, and an icon of the file directory or a 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 "Mdm 1".

In one embodiment, the node content of a node representing a file directory on the thought graph may also include the number of files of the file contained in the file directory represented by the node. 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 may be determined, and the number of files may be displayed at a position corresponding to the node.

For example, referring to fig. 5, if the number of files contained in the file directory DirA is 2, the node content of the node 52 representing the file directory DirA may further include the number of files contained in the file directory DirA, and the number of files may be specifically output and displayed at a position corresponding to the node 52 (for example, inside an icon of the node 52 shown in fig. 5). Accordingly, if the number of files contained in the file directory DirB is 0, the node content of the node 53 representing the file directory DirB may further include the number of files contained in the file directory DirB, and the number of files may be specifically output and displayed at a position corresponding to the node 52.

The number of files may be the number of files included in the current-level directory of the file directory corresponding to the node. When a sub-file directory exists in the file directory corresponding to the node, the number of files may be a total number of files obtained by adding the numbers of files included in the current-level directory of the file directory corresponding to the node and the sub-file directories of each level included in the current-level directory, and is not particularly limited in this specification.

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

A node on the thought graph representing a file may also have child nodes, and the child nodes representing nodes of the file may represent files associated with the file.

For example, FIG. 6 illustrates a mind map output in an exemplary embodiment. Node 61, representing file DocA, has two child nodes, node 611 and node 612.

For example, in practical application, a document a requests a series of files B, and all nodes representing the series of files B can be used as child nodes of the nodes representing the document a, and compared with the case where the document a and the series of files B are placed under a file directory, the relationship between the file and the file under the file directory can be better embodied.

Step 404, obtaining user operation of the user for the node on the thought-guiding graph.

After the client outputs the file to be managed in the form of the mind map, the user can perform various preset user operations on the nodes on the mind map to trigger the file management action. And the client can also monitor the user operation of the user aiming at the node. After the client monitors the user operation, the corresponding file management action can be executed.

Wherein, the client can predefine a plurality of user operations aiming at the node. The user operation may be a mouse or touch operation such as clicking, long-pressing, dragging, or the like on an area corresponding to the node, or a key operation input through a keyboard when the node state is selected, or a user operation input through other input devices such as a microphone and a camera, which is not specifically limited in this specification. The specific user operations mentioned in all embodiments in this specification are exemplary and will not be described in detail below.

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

And after the client acquires the user operation, executing a file management action corresponding to the user operation on the file or the file directory represented by the node aimed at by the user operation.

The client can bind the corresponding file management action for the defined user operation in advance. The file management actions may include various different file management actions for files or file directories, such as preview, view, edit, rename, move, sort, delete, and the like, which is not specifically limited in this specification.

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

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

In this case, after monitoring the operation of the user on the region corresponding to the mouse left click node of the node, the client may open a viewing interface and output the content of the file or the file directory corresponding to the node in the viewing interface for the user to view or further operate.

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

In this case, after the client monitors the long-time pressing operation of the user on the touch screen for the predetermined time period on the file type icon of the file corresponding to the node in the node content, an information display frame may be output above the node, and the editing history information of the file may be displayed in the information display frame.

In one exemplary embodiment shown, the obtained user operations of the user on the node on the mind map include a file preview operation.

For example, a mouse pointer hover operation may be bound to a file preview operation at the desktop end, and when it is detected that a user moves a mouse pointer to an area corresponding to a node for a predetermined time period, it is determined that the file preview operation is triggered.

And responding to the file preview operation, judging the node type of the node, and if the node is a node representing a file, outputting the preview content of the file represented by the node at a position corresponding to the node.

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

For example, referring to FIG. 7, FIG. 7 illustrates a schematic diagram of a file preview operation in an exemplary embodiment.

Node 721 is a node representing a file, which represents the text file Doc 7. When the user moves the mouse pointer 700 over the node 721 for a specified length, a preview window 7210 is displayed in the area corresponding to the node 721, the preview window including the file content of the text file Doc 7.

In one exemplary embodiment shown, the obtained user operations of the user on the nodes on the mind map comprise new next-level node operations.

For example, a mouse right click node corresponding area or a keyboard Enter key can be bound to a new next-level node at the desktop end for operation.

After the operation of creating a next-level node by a user is acquired, a selection menu is output at a position corresponding to the node, and the menu comprises a plurality of file type options, such as texts, tables, brain images, presentations, folders and the like.

And after the file type option selected by the user is obtained, a next-level node of the node is newly established, wherein 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 a 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 next level node represents an empty file directory.

The selection menu can provide an option for creating a file from the template, and after the user selects the option, another option menu is output, the option menu comprises a preset file template option, and the user can select the file template option to create the file from the template as a child node of the current node.

For example, referring to fig. 8, fig. 8 is a diagram illustrating the operation of creating a new next level node in an exemplary embodiment.

The node 81 is a node representing the file directory Dir8, and after the user mouse clicks the node, the selection menu 811 is output beside the node, and the selection menu 811 includes options such as text, table, brain map, presentation, whiteboard, folder, slave template, and the like, so as to create a node representing a blank file of a corresponding type as a child node of the node 81 according to the option selected by the user.

Specifically, when the user selects the "folder" option, a node representing a file directory is created as a child of node 81; when the user selects the "from template" option, an option menu is output to allow the user to select a preset template from which to create a new file as a child of node 81.

In one embodiment shown, the obtained user operations of the user on the nodes on the mind map comprise new peer node operations.

For example, at the desktop end, a keyboard Tab key may be bound to a newly created peer node for operation.

After new peer operation of a user is acquired, a selection menu is output at a position corresponding to a node, and the menu comprises a plurality of file type options, such as texts, tables, brain images, presentations, folders and the like.

And after the file type option selected by the user is obtained, establishing a peer node of the node, wherein 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 peer node represents a blank text file, and when the file type option selected by the user is a folder, the newly created peer node represents an empty file directory.

The selection menu can provide an option for creating a file from the template, and after the user selects the option, another option menu is output, the option menu comprises a preset file template option, and the user can select the file template option to create the file from the template as a child node of the current node.

For example, a new peer node operation is performed on the node 81 in fig. 8, and the new peer node is a child node of the node 60.

In one embodiment shown, the obtained user operations of the user on the nodes on the mind map include a file import operation.

And after acquiring the file import operation of the user aiming at the node, outputting a selection menu, wherein the selection menu comprises a local file or a file directory of the user for the user to select. And when the user selects the file or the file directory, acquiring the file or the file folder selected by the user, and creating a child node of the node to represent the file or the file directory selected by the user.

In an illustrated embodiment, after a local file directory is imported by a file import operation, whether the local file directory contains a file or a subfile directory is determined, and if the local file directory contains a file or a subfile directory, a multi-level node is established for each level of file directory and subfiles under the local file directory.

In one embodiment shown, the acquired user operations of the user on the nodes on the mind map comprise renaming operations, wherein the renaming operations comprise a renaming trigger operation and an input character string operation;

for example, a mouse left button double click may be performed on the desktop end to trigger the operation corresponding to the region binding renaming.

Acquiring a character string input by a user after acquiring a renaming trigger operation of the user for a node, and modifying a file name of a file or a file directory name of a file directory corresponding to the node into the character string input by the user.

In practical application, the legality of the character string input by the user as the file name or the file directory name can be judged, if the character string is illegal, a warning is popped up, and the user is prompted to input the character string as the file name or the file directory name again.

In one embodiment shown, the obtained user operation of the user on the node on the mind map comprises a drag operation.

When a user selects and drags a node to a position designated by the user, whether the position designated by the user is located in a corresponding area of another node is judged, and if the position designated by the user is located in the corresponding area of another node, the node is taken as a child node of the other node and is moved to a corresponding position.

And when the position specified by the user is considered as the area corresponding to the parent node of the current node, judging whether the relative position of the position specified by the user and the current position of the node at the same level is changed or not compared with the current position of the node, and if the relative position of the position specified by the user and the current position of the node is changed, moving the current node to the position specified by the user. At this time, the user's dragging operation changes the ordering of the file or file directory corresponding to the node under the current file directory.

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

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

In practical applications, for a node where a subordinate node exists, the dragging operation may move the node and all subordinate nodes thereof as a whole.

In one embodiment shown, the obtained user operation of the user on the node on the mind map comprises switching hidden subordinate node operations.

The child nodes of a node on the thought graph may be referred to as the next level node of the node, the child nodes of the node, and the child nodes of each level of the child nodes, referred to as the next level nodes of the node. When the thought-map has many hierarchical relationships and many nodes in each layer, the thought-map may be large. However, sometimes the user only cares about the first few levels of the mind map or the child nodes of a specific node, and the like, and at this time, the lower nodes of some nodes can be hidden and expanded when necessary.

Switching hidden subordinate node operations may include hiding subordinate node operations and unhiding subordinate node operations. The hidden subordinate node operation and the hidden subordinate node cancellation operation may be bound to the same user operation or may be bound to different user operations.

In one embodiment shown, the obtained user operations of the user on the nodes on the mind map include hiding subordinate node operations.

For example, the keyboard left key may be bound to hide the operations of the subordinate nodes at the desktop side.

After the hidden subordinate node operation of a user for a node is acquired, whether the subordinate node of the node is in a hidden state or not is judged, if not, the subordinate node of the node is hidden, and the number of the subordinate nodes of the node is displayed at the position corresponding to the node.

As shown in fig. 10, fig. 10 shows a schematic diagram of hiding the operation of a lower node in an exemplary embodiment.

As shown in FIG. 10(a), node 102 has two child nodes 1021 and node 1022, where node 1021 has one child node, node 10211. After acquiring the command of hiding the subordinate nodes of the node 102 from the user, since the nodes under the node 102 are not hidden, all the subordinate nodes of the node 102, including the node 1021, the node 2111 and the node 1022, are hidden, and the number mark 1000 of the subordinate nodes of the node 102 is displayed at the corresponding position of the node 102, and since the number of the subordinate nodes of the node 102 is 2, the number mark 1000 is displayed as 2, as shown in fig. 10 (b).

In practical applications, the number of the subordinate nodes of the node, which may be displayed at the corresponding positions of the nodes with the hidden subordinate nodes, may be the number of the nodes at the next stage of the node, may also be the total number of the subordinate nodes of the node, or the total number of the nodes representing files in the subordinate nodes of the node, which is not specifically limited in this specification.

In one embodiment shown, the obtained user operation of the user on the node on the mind map comprises unhiding a subordinate node operation.

For example, the right key of the keyboard can be bound to be removed from hiding the operation of the subordinate nodes at the desktop end.

After the operation of canceling the hidden subordinate node of the node by the user is acquired, whether the subordinate node of the node is in the hidden state or not is judged, if the subordinate node of the node is not in the 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.

In practical application, the hidden state of the next-level node of the node can be cancelled by cancelling the hidden operation, and the next-level node of the node still keeps the hidden state; the hidden state of each level of lower nodes of the node may also be simultaneously cancelled by cancelling the hidden operation, which is not specifically limited in this specification.

In one embodiment shown, the files to be managed support multiple display modes. The display mode includes the above-described mind map view for organizing files in the mind map form, and may include other common display modes such as a mode for displaying files in the form of a list, a mode for displaying files in the form of icons, and a mode for displaying files in the form of a left-side directory tree.

The file management page is provided with a group of view options, and each view option corresponds to a corresponding file display mode. The group of view options may be a group of buttons, multiple options in a pull-down menu under one button, or a group of shortcut keys, and the like.

And after the view option selected by the user is acquired, switching to a file display mode corresponding to the view option selected by the user, and outputting the file display mode to the user on the file management interface, so that the user can view and manage the file to be managed.

In one embodiment shown, the default display mode supported by the document management page for the document to be managed is a mode of mind map based display.

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

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

The files may include local files and online files, which may include online documents. The online documents may include online documents such as online text, online forms, online brain maps, online presentations, etc., and online folders for storing the online documents. The online document can be conveniently checked and edited at the cloud.

The client may include various software clients with file management requirements or file management functions, such as an operating system, file management software, communication software, and a network disk software, which are not specifically limited in this specification.

In one exemplary embodiment shown, the client comprises enterprise instant messaging software.

The enterprise instant messaging software generally relates to the scenes of file transmission, management, collaboration and the like, and comprises the collaborative management of online documents, and the scheme of the specification is applied.

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

the organizing unit 1110 is configured to respond to a file management operation triggered by a user, organize a file structure corresponding to a file to be managed into a thought map, and output the thought map 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;

an obtaining unit 1120, configured to obtain a user operation of a user for a node on the mind map;

an executing unit 1130, configured to respond to the user operation, execute a corresponding file management action for the file or the file directory represented by the node.

Optionally, the organization unit 1110 is further configured to display node contents in the node, where the node contents include: 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 organizing unit 1110 is further configured to determine a node representing a file directory in the mind map, where the number of files included in the represented file directory is determined; and displaying the file number at the position corresponding to the node.

Optionally, the obtaining unit 1120 is specifically configured to: acquiring file preview operation of a user aiming at the nodes of the thought guide graph;

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

Optionally, the obtaining unit 1120 is specifically configured to: acquiring a first node new construction operation of a user aiming at the node of the thought guide graph;

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

Optionally, the obtaining unit 1120 is specifically configured to: acquiring a second node new construction operation of the user aiming at the node of the thought guide graph;

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

Optionally, the obtaining unit 1120 is specifically configured to: acquiring file import operation of a user aiming at the nodes of the thought guide graph;

correspondingly, the execution unit 1130 is specifically configured to output a selection menu in response to the file import operation, where the selection menu includes an option representing a local file or file directory of the user, acquire the option selected by the user, and create a new child node of the 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: acquiring renaming operation of a user for the nodes of the thought guide graph;

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

Optionally, the obtaining unit 1120 is specifically configured to: acquiring a dragging operation of a user for a node of the mind map;

correspondingly, the executing unit 1130 is specifically configured to move the node to a position specified by a user in response to the dragging operation.

Optionally, the obtaining unit 1120 is specifically configured to: acquiring hidden subordinate node operation of a user aiming at the nodes of the thought-guiding graph;

correspondingly, the executing unit 1130 is specifically configured to determine, in response to the hidden lower node operation, whether the lower node of the node is in a hidden state, hide the lower node of the node if the lower node of the node is not in the hidden state, and display the number of the lower nodes of the node at a position corresponding to the node.

Optionally, the obtaining unit 1120 is specifically configured to: obtaining hidden lower node cancelling operation of a user aiming at the nodes of the thought guide graph;

correspondingly, the executing unit 1130 is specifically configured to determine, in response to the operation of hiding the subordinate node, whether the subordinate node of the node is in a hidden state, if the subordinate node of the node is in the hidden state, hide the subordinate node of the node, and delete the number of the subordinate nodes of the node at a position corresponding to the node.

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

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the elements can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

In exemplary embodiments of the present description, embodiments of an apparatus and a terminal applied thereto are also provided.

The embodiment of the file management device in the specification can be applied to computer equipment, such as a server or terminal equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor in which the file management is located. From a hardware aspect, as shown in fig. 12, it is a hardware structure diagram of a computer device 120 in which a file management apparatus is located in an embodiment of the present disclosure, and except for the processor 1212, the memory 1230, the network interface 1220, and the nonvolatile memory 1240 shown in fig. 12, a server or an electronic device in which the apparatus 1231 is located in an embodiment may also include other hardware according to an actual function of the computer device, which is not described again.

In an exemplary embodiment of the present specification, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the present description may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the present description described in the "exemplary methods" section above of the present description, when the program product is run on the terminal device.

Referring to fig. 13, a program product 130 for implementing the above method according to an embodiment of the present specification is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present specification is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection 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. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate 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 operations for this specification may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. 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. 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 (e.g., through the internet using an internet service provider).

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. In other instances, features described in connection with one embodiment may be implemented as discrete components or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system elements and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying 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 description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

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