CN108108077B - Desktop management method and device - Google Patents

Desktop management method and device Download PDF

Info

Publication number
CN108108077B
CN108108077B CN201611061993.9A CN201611061993A CN108108077B CN 108108077 B CN108108077 B CN 108108077B CN 201611061993 A CN201611061993 A CN 201611061993A CN 108108077 B CN108108077 B CN 108108077B
Authority
CN
China
Prior art keywords
desktop
sub
main
window
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201611061993.9A
Other languages
Chinese (zh)
Other versions
CN108108077A (en
Inventor
陈刚
廖湘平
王秋阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201611061993.9A priority Critical patent/CN108108077B/en
Publication of CN108108077A publication Critical patent/CN108108077A/en
Application granted granted Critical
Publication of CN108108077B publication Critical patent/CN108108077B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/168Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The embodiment of the invention discloses a desktop management method and a desktop management device, wherein the method comprises the following steps: acquiring a sub desktop establishing request on a preset main desktop; the main desktop is covered on the native desktop, and the window operation function of the main desktop is the same as that of the native desktop; creating a sub desktop according to the sub desktop creation request, and covering the sub desktop in a preset area of the main desktop; the window range of the sub-desktop is smaller than that of the main desktop, and the window operation function of the sub-desktop is the same as that of the main desktop; and acquiring an adding and deleting request associated with the sub-desktop, adding the target desktop object in the main desktop into the sub-desktop according to the adding and deleting request, deleting the icon of the target desktop object in the main desktop, and performing management operation on the target desktop object in the sub-desktop and the user interface of the sub-desktop based on the window operation function of the sub-desktop. By adopting the invention, the management efficiency of the files and the user interface can be improved when the desktop is managed.

Description

Desktop management method and device
Technical Field
The invention relates to the technical field of computers, in particular to a desktop management method and device.
Background
The current desktop provided by microsoft is a popular desktop, and when a user desktop is full of files, great inconvenience is brought to the user when the user searches for needed files. Although a plurality of folders may be created on a desktop and files of the same type may be placed in the created folders to reduce the number of files in the desktop, the folders do not have a function of managing files and user interfaces by the desktop completely, so that the way of managing files by the folders is too single and the function is not complete enough, and therefore, the way of creating the folders may reduce the efficiency of managing files and user interfaces when managing the desktop.
Disclosure of Invention
The embodiment of the invention provides a desktop management method and device, which can improve the management efficiency of files and user interfaces when managing a desktop.
The embodiment of the invention provides a desktop management method, which comprises the following steps:
acquiring a sub desktop establishing request on a preset main desktop; the main desktop is covered on the native desktop, and the window operation function of the main desktop is the same as that of the native desktop;
creating a sub desktop according to the sub desktop creation request, and covering the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop is the same as that of the main desktop;
acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a main desktop into the sub-desktop according to the adding and deleting request, deleting an icon of the target desktop object in the main desktop according to the adding and deleting request, and managing the target desktop object in the sub-desktop and a user interface of the sub-desktop based on a window operation function of the sub-desktop.
Correspondingly, an embodiment of the present invention further provides a desktop management device, including:
the request acquisition module is used for acquiring a sub desktop creation request on a preset main desktop; the main desktop is covered on the native desktop, and the window operation function of the main desktop is the same as that of the native desktop;
the first creating module is used for creating a sub desktop according to the sub desktop creating request and covering the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop is the same as that of the main desktop;
and the object operation module is used for acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a main desktop into the sub-desktop according to the adding and deleting request, deleting an icon of the target desktop object in the main desktop according to the adding and deleting request, and managing the target desktop object in the sub-desktop and a user interface of the sub-desktop based on a window operation function of the sub-desktop.
According to the embodiment of the invention, the sub-desktop creating request is acquired on the preset main desktop, the sub-desktop can be created according to the desktop creating request, the sub-desktop is covered in the preset area of the main desktop, the adding and deleting request associated with the sub-desktop is acquired, the target desktop object in the main desktop is added into the sub-desktop according to the adding and deleting request, the icon of the target desktop object in the main desktop is deleted according to the adding and deleting request, and the target desktop object in the sub-desktop and the user interface of the sub-desktop are managed based on the window operation function of the sub-desktop. Because the window operation function of the sub-desktop is the same as that of the main desktop, when the user interface of the sub-desktop and the target desktop object in the sub-desktop are managed, the effect the same as that of the window operation function of the main desktop can be completely enjoyed, so that the number of files in the main desktop can be reduced only by setting the sub-desktop, and the management efficiency of the files and the user interface can be improved when the desktop is managed.
Drawings
In order to more clearly illustrate the embodiments of the present invention 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 of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a desktop management method according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating another desktop management method according to an embodiment of the present invention;
FIG. 2a is a schematic interface diagram of a management operation list according to an embodiment of the present invention;
FIG. 2b is a schematic diagram of an interface for desktop reorganization according to an embodiment of the present invention;
FIG. 2c is a schematic diagram of an interface for another desktop collation according to the embodiment of the present invention;
FIG. 2d is a schematic diagram of an interface for organizing a desktop provided by an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a desktop management apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a request obtaining module according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of an object operation module according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an object adding unit according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another desktop management apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, a flowchart of a desktop management method according to an embodiment of the present invention is shown, where the method includes:
s101, acquiring a sub-desktop creating request on a preset main desktop; the main desktop is covered on the native desktop, and the window operation function of the main desktop is the same as that of the native desktop;
specifically, before step S101, a client (e.g., a desktop application) needs to set the main desktop on a native desktop, which may be a native desktop owned by the microsoft system. The process of setting the main desktop on the native desktop may be performed in the process of installing the desktop application, and the process of setting the main desktop on the native desktop may be: creating a visual window of a main desktop, wherein the visual window may be a ListView window (ListView refers to a visual LIST control in a microsoft system), overlaying the visual window of the main desktop on a native desktop, controlling the visual window of the main desktop to take over a window operation function of the native desktop based on a SHELL, controlling the visual window of the main desktop to take over a routing identifier corresponding to each desktop object in the native desktop based on the SHELL, wherein the routing identifier may be PIDL (PIDL is defined as PITEMIDLIST in the SHELL technology, that is, an identity representing one ITEM (ITEM), representing the identity in the form of a LIST of objects (LIST), adding icons corresponding to all desktop objects in the native desktop to the visual window of the main desktop, and configuring a sub-desktop creation management operation for the visual window of the main desktop, and adding a function key related to the child desktop creation management operation in a management operation list corresponding to the visual window of the main desktop. After the desktop application is installed, icons corresponding to desktop objects in the native desktop can be displayed in a visualization window of the main desktop. Although the visual window of the main desktop can take over all the window operation functions of the native desktop, the visual window of the main desktop can be provided with a custom user interface different from the native desktop, and the visual window of the main desktop can also add additional function keys in the custom user interface, so that the main desktop can have more desktop sorting functions than the native desktop. The management operation list in the main desktop may be a function list popped up after a mouse performs right click in a blank area of the main desktop, and the function keys in the management operation list may include: a "display mode" key, an "arrangement mode" key, a "new" key, a "screen resolution" key, a "personalization" key, a "new grid" key (i.e., a function key associated with the sub-desktop creation management operation), and other function keys.
Further, when a first click instruction corresponding to a function list key (such as a right mouse button) is detected in the main desktop, displaying the management operation list in a visualization window of the main desktop according to the first click instruction; and when a second click instruction corresponding to the function key associated with the child desktop creation management operation in the management operation list is detected, generating a child desktop creation request according to the second click instruction. For example, after right click is performed on a blank area of a main desktop through a mouse, a first click instruction corresponding to a function list key can be generated, and the management operation list is popped up and displayed in a visual window of the main desktop according to the first click instruction.
S102, creating a sub desktop according to the sub desktop creation request, and covering the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop is the same as that of the main desktop;
specifically, the client may create a visualization window of the sub-desktop according to the sub-desktop creation request, where the visualization window of the sub-desktop may also be a ListView window, and then cover the visualization window of the sub-desktop in a preset area in the visualization window of the main desktop, and control the visualization window of the sub-desktop to take over a window operation function of the visualization window of the main desktop based on SHELL, that is, the visualization window of the sub-desktop has the window operation function of the visualization window of the main desktop, and the visualization window of the main desktop still retains its own window operation function. The preset area is smaller than the interface area of the main desktop, namely the window range of the sub-desktop is smaller than the window range of the main desktop. For example, the child desktop can be located in a square area in the upper left corner of the visualization window of the main desktop. Because the visual window of the sub desktop takes over the window operation function of the visual window of the main desktop, the function list popped up after right click is carried out in the blank area of the sub desktop is the same as the function list popped up after right click is carried out in the blank area of the main desktop, and the processing modes of single click, double click, full selection, deletion and the like in the sub desktop are the same as the processing modes of the main desktop.
S103, acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a main desktop into the sub-desktop according to the adding and deleting request, deleting an icon of the target desktop object in the main desktop according to the adding and deleting request, and managing the target desktop object in the sub-desktop and a user interface of the sub-desktop based on a window operation function of the sub-desktop;
specifically, when a user wants to add a target desktop object in the main desktop to the sub-desktop, the user may click the target desktop object in the main desktop by controlling a mouse arrow and drag the target desktop object into the visualization window of the sub-desktop, and when the click of the mouse is released, the visualization window of the sub-desktop generates the addition/deletion request, and the client may further obtain the addition/deletion request generated by the visualization window of the sub-desktop, and add the target desktop object in the visualization window of the main desktop into the visualization window of the sub-desktop according to the addition/deletion request (i.e., an icon of the target desktop object may be displayed in the visualization window of the sub-desktop), and control the visualization window of the sub-desktop to take over a routing identifier corresponding to the target desktop object based on SHELL, therefore, the visualization window of the sub desktop can perform operations such as clicking, double-clicking, dragging and the like on the target desktop object through the route identifier corresponding to the target desktop object. Further, when the visualization window of the sub-desktop notifies that the visualization window of the main desktop has successfully taken over the routing identifier corresponding to the target desktop object, the client may delete the icon of the target desktop object in the visualization window of the main desktop according to the addition and deletion request, so that the user can only operate the target desktop object in the sub-desktop, and at the same time, the number of files in the main desktop may also be reduced, so that the user may easily find the required files in the main desktop. Based on the window operation function of the visualization window of the main desktop taken over by the visualization window of the sub-desktop and the routing identifier corresponding to the target desktop object, the management operation may be performed on the target desktop object and the user interface of the sub-desktop (in the SHELL technology, all the operations on the target desktop object are performed through the routing identifier (PIDL)). For example, the management operation list popped up in the sub desktop is the same as the management operation list popped up in the main desktop, therefore, if the function keys in the management operation list in the main desktop include the function keys such as "display mode" key, "arrangement mode" key, "new" key, "screen resolution" key, "personalized" key, "new grid" key, etc., the function keys in the management operation list of the sub-desktop may also include function keys such as a "display mode" key, an "arrangement mode" key, a "new" key, a "screen resolution" key, a "personalization" key, a "new grid" key, etc., as can be seen, the user can adjust the screen resolution in the sub-desktop by clicking the "screen resolution" button, without affecting the screen resolution of the main desktop, the user can also further create smaller sub-desktops in the sub-desktops by clicking the "new grid" button.
According to the embodiment of the invention, the sub-desktop creating request is acquired on the preset main desktop, the sub-desktop can be created according to the desktop creating request, the sub-desktop is covered in the preset area of the main desktop, the adding and deleting request associated with the sub-desktop is acquired, the target desktop object in the main desktop is added into the sub-desktop according to the adding and deleting request, the icon of the target desktop object in the main desktop is deleted according to the adding and deleting request, and the target desktop object in the sub-desktop and the user interface of the sub-desktop are managed based on the window operation function of the sub-desktop. Because the window operation function of the sub-desktop is the same as that of the main desktop, when the user interface of the sub-desktop and the target desktop object in the sub-desktop are managed, the effect the same as that of the window operation function of the main desktop can be completely enjoyed, so that the number of files in the main desktop can be reduced only by setting the sub-desktop, and the management efficiency of the files and the user interface can be improved when the desktop is managed.
Referring to fig. 2, a schematic flowchart of another desktop management method provided in an embodiment of the present invention is shown, where the method may include:
s201, when a first click instruction corresponding to a function list key is detected in a main desktop, displaying a management operation list in a visual window of the main desktop according to the first click instruction;
specifically, before step S201, a client (such as a desktop application) needs to be installed, and in the process of installing the client: the client may create a visualization window of a main desktop, where the visualization window may be a ListView window, and then cover the visualization window of the main desktop on a native desktop, and control the visualization window of the main desktop to take over a window operation function of the native desktop based on a SHELL, and control the visualization window of the main desktop to take over a routing identifier corresponding to each desktop object in the native desktop respectively based on the SHELL, where the routing identifier may be PIDL, and then add icons corresponding to all desktop objects in the native desktop respectively to the visualization window of the main desktop, and configure a sub-desktop creation management operation for the visualization window of the main desktop, and add a function key associated with the sub-desktop creation management operation in a management operation list corresponding to the visualization window of the main desktop. Although the visualization window of the main desktop can take over all the window operation functions of the native desktop, the visualization window of the main desktop can be provided with a custom user interface different from the native desktop, and the visualization window of the main desktop can also add additional function keys in the custom user interface, so that the main desktop can have more desktop sorting functions than the native desktop. After the client is installed, icons respectively corresponding to desktop objects in the native desktop may be displayed in a visualization window of the main desktop, and the visualization window of the main desktop may perform operation control on the icons respectively corresponding to the desktop objects in the native desktop displayed in the visualization window of the main desktop based on the taken-over window operation function and the taken-over route identifier respectively corresponding to the desktop objects in the native desktop, where the operation control may include double-clicking and single-clicking an icon, right-clicking an icon to pop up a function list for the icon, and delete the icon by clicking a delete key on the icon.
Therefore, after the client is installed, step S201 may be executed, that is, when a first click instruction corresponding to a function list key is detected, it indicates that the user controls the mouse to perform a right click operation in a blank area of the main desktop, and at this time, the main desktop may display the management operation list in a visualization window of the main desktop according to the first click instruction. Wherein, the function keys in the management operation list may include: a display mode key, an arrangement mode key, a new building key, a screen resolution key, a personalized key, a new grid key (namely a function key associated with the sub-desktop creation management operation), a one-key desktop sorting key, a desktop quitting sorting key and other function keys; the 'newly-built grid' key, the 'one-key arrangement desktop' key and the 'quit desktop arrangement' key are all newly-added function keys on the basis of the window operation function of the original desktop; the 'one-key desktop sorting' key can enable files in the main desktop to be sorted according to file types; the 'exit desktop sorting' button can exit the main desktop to restore the display of the native desktop, and redisplay icons of all files in the main desktop in the native desktop.
S202, when a second click instruction corresponding to a function key associated with the child desktop creation management operation in the management operation list is detected, a child desktop creation request is generated according to the second click instruction;
specifically, when a second click instruction corresponding to a function key associated with the child desktop creation management operation in the management operation list is detected, it is indicated that the user controls the mouse to click a "new grid" key in the management operation list, and the visualization window of the main desktop can generate the second click instruction, and at this time, the client can generate a child desktop creation request according to the second click instruction.
Fig. 2a is a schematic view of an interface for managing an operation list according to an embodiment of the present invention. After a user controls a mouse to click right in a blank area of a main desktop, a management operation list 100 shown in fig. 2a can be displayed in the main desktop; this management operation list 100 includes a plurality of function keys, specifically includes "display mode" button, "arrangement mode" button, "refresh" button, "paste shortcut" button, "newly build check" button 200, "newly build folder" button, "one key arrangement desktop" button, "withdraw from desktop arrangement" button, "newly build" button, "screen resolution" button, "individualized" button, and when the user clicked "newly build check" button 200, the client can generate sub-desktop and establish the request.
Fig. 2b is a schematic view of an interface for desktop arrangement according to an embodiment of the present invention. When the user clicks the exit desktop sort key in the management operation list 100 shown in fig. 2a, the main desktop may pop up an interface diagram shown in fig. 2b, and the interface diagram shown in fig. 2b may prompt the user to "determine to exit desktop sort? "; when the user clicks the "exit" button 300 in the interface diagram shown in fig. 2b, the main desktop can be exited to resume displaying the native desktop, and icons of all files in the main desktop are redisplayed in the native desktop; when the user clicks the "i try again" button 400 in the interface diagram shown in fig. 2b, the user interface of the main desktop continues to be displayed, and the interface diagram shown in fig. 2b is closed.
S203, creating a visual window of a sub desktop according to the sub desktop creation request, covering the visual window of the sub desktop in a preset area in the visual window of the main desktop, and controlling the visual window of the sub desktop to take over a window operation function of the visual window of the main desktop;
specifically, the client may create a visualization window of the sub-desktop according to the sub-desktop creation request, where the visualization window of the sub-desktop may also be a ListView window, and then cover the visualization window of the sub-desktop in a preset area in the visualization window of the main desktop, and control the visualization window of the sub-desktop to take over a window operation function of the visualization window of the main desktop based on SHELL, that is, the visualization window of the sub-desktop has the window operation function of the visualization window of the main desktop, and the visualization window of the main desktop still retains its own window operation function. The preset area is smaller than the interface area of the main desktop, namely the window range of the sub-desktop is smaller than the window range of the main desktop. For example, the child desktop can be located in a square area in the upper left corner of the visualization window of the main desktop. Because the visual window of the sub desktop takes over the window operation function of the visual window of the main desktop, the function list popped up after right click is carried out in the blank area of the sub desktop is the same as the function list popped up after right click is carried out in the blank area of the main desktop, and the processing modes of single click, double click, full selection, deletion and the like in the sub desktop are the same as the processing modes of the main desktop. In addition, the visual window of the sub-desktop can be provided with a user-defined user interface different from that of the main desktop, and the visual window of the sub-desktop can also be provided with additional function keys in the user-defined user interface, so that the sub-desktop can have more desktop sorting functions than the main desktop. The management operation list in the sub desktop may be a function list popped up after a mouse performs right click in a blank area of the main desktop, and the function keys in the management operation list in the sub desktop may also include: the display device comprises a display mode key, an arrangement mode key, a new building key, a screen resolution key, a personalized key, a new grid key, a one-key desktop sorting key, an exit desktop sorting key and other functional keys. When a 'new grid' button in the management operation list in the sub desktop is clicked, a smaller sub desktop can be further created in the sub desktop; when a 'one-key desktop sorting' key in the management operation list in the sub desktop is clicked, files in the sub desktop can be sorted according to file types; and when a 'quit desktop sorting' button in the management operation list in the sub desktop is clicked, the sub desktop can be quitted, so that the content of the main desktop is restored and displayed in a preset area occupied by the sub desktop, and the icons of all files in the sub desktop are redisplayed in the main desktop.
S204, acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a visual window of a main desktop into the visual window of the sub-desktop according to the adding and deleting request, and controlling the visual window of the sub-desktop to take over a route identifier corresponding to the target desktop object;
specifically, when a user wants to add a target desktop object in the main desktop to the sub-desktop, the user may click the target desktop object in the main desktop by controlling a mouse arrow and drag the target desktop object into the visualization window of the sub-desktop, and when the click of the mouse is released, the visualization window of the sub-desktop generates the addition/deletion request, and the client may further obtain the addition/deletion request generated by the visualization window of the sub-desktop, and add the target desktop object in the visualization window of the main desktop into the visualization window of the sub-desktop according to the addition/deletion request (i.e., an icon of the target desktop object may be displayed in the visualization window of the sub-desktop), and control the visualization window of the sub-desktop to take over a routing identifier corresponding to the target desktop object based on SHELL, therefore, the visualization window of the sub desktop can perform operations such as clicking, double-clicking, dragging and the like on the target desktop object through the route identifier corresponding to the target desktop object.
Or when a user names the created sub-desktop, the client may detect a naming operation associated with the sub-desktop, set file type information corresponding to the sub-desktop according to the naming operation, generate an addition/deletion request carrying the file type information, select a desktop object matched with the file type information in the visualization window of the main desktop according to the addition/deletion request to serve as a target desktop object, and add the target desktop object selected in the visualization window of the main desktop to the visualization window of the sub-desktop according to the addition/deletion request. For example, if the user names the child desktop as "my video file", the client may set file type information corresponding to the child desktop according to the naming operation of the user, where the file type information is "video file type information", and generate an addition/deletion request carrying the "video file type information", and then the client may add all files (i.e., video files) in the visualization window of the main desktop that are matched with the "video file type information" to the visualization windows in the child desktop according to the addition/deletion request. Further, the client controls the visualization window of the sub-desktop to take over the routing identifier corresponding to the target desktop object based on the SHELL, so that the visualization window of the sub-desktop can perform operations such as clicking, double-clicking, dragging and the like on the target desktop object through the routing identifier corresponding to the target desktop object.
S205, when the visual window of the sub desktop informs the visual window of the main desktop that the routing identifier corresponding to the target desktop object is successfully taken over, deleting the icon of the target desktop object in the visual window of the main desktop according to the adding and deleting request;
specifically, when the visualization window of the sub-desktop notifies that the visualization window of the main desktop has successfully taken over the routing identifier corresponding to the target desktop object, the client may delete the icon of the target desktop object in the visualization window of the main desktop according to the addition and deletion request, so that the user can only operate the target desktop object in the sub-desktop, and at the same time, the number of files in the main desktop may also be reduced, so that the user may easily find the required files in the main desktop.
S206, based on the window operation function of the visual window of the main desktop taken over by the visual window of the sub-desktop and the route identifier corresponding to the target desktop object, performing management operation on the target desktop object and the user interface of the sub-desktop;
specifically, the client may perform management operation on the target desktop object and the user interface of the sub desktop based on the window operation function of the visualization window of the main desktop taken over by the visualization window of the sub desktop and the route identifier corresponding to the target desktop object. For example, the management operation list popped up in the sub desktop is the same as the management operation list popped up in the main desktop, therefore, if the function keys in the management operation list in the main desktop include the function keys such as "display mode" key, "arrangement mode" key, "new" key, "screen resolution" key, "personalized" key, "new grid" key, etc., the function keys in the management operation list of the sub-desktop may also include function keys such as a "display mode" key, an "arrangement mode" key, a "new" key, a "screen resolution" key, a "personalization" key, a "new grid" key, etc., as can be seen, the user can adjust the screen resolution in the sub-desktop by clicking the "screen resolution" button, without affecting the screen resolution of the main desktop, the user can also further create smaller sub-desktops in the sub-desktops by clicking the "new grid" button.
Optionally, the client may create a plurality of sub-desktops in the main desktop, for example, one sub-desktop may be set in a square area at the upper right corner of the main desktop, and another sub-desktop may be set in a rectangular area at the upper left corner of the main desktop, and the creation process and the functions of each sub-desktop may refer to the above S201-S206, which is not described herein again. Optionally, a plurality of smaller sub-desktops may be further created in the sub-desktop, and the creation process and the functions of each smaller sub-desktop may also refer to the foregoing S201-S206, which is not described herein again, except that the window operation function taken over by each smaller sub-desktop is the window operation function from the sub-desktop in which it is located, and the route identifier of the desktop object taken over by each smaller sub-desktop is also the route identifier of the desktop object from the sub-desktop in which it is located; and when a desktop object in the sub-desktop is added to a smaller sub-desktop, the visual window of the sub-desktop can delete the icon of the desktop object in the sub-desktop. The main desktop, each sub-desktop and each smaller sub-desktop respectively correspond to the visualization windows which can be communicated with each other.
Optionally, a batch start operation is configured in a window operation function taken over by a visual window of the sub-desktop, and when a batch start operation request carrying a preset file format and corresponding to the sub-desktop is obtained, target desktop objects in the sub-desktop, all of which are in the preset file format, are simultaneously started in the visual window of the sub-desktop according to the batch start operation request. For example, if the preset file format is doc format, when the visualization window of the child desktop detects a batch start operation request, the visualization window of the child desktop may open all files in the child desktop in doc format at the same time. The method for configuring the batch start operation may be to add a function key associated with the batch start operation to a management operation list in the sub desktop, so that when a user clicks the function key associated with the batch start operation in the management operation list in the sub desktop, the batch start operation request may be detected by a visualization window of the sub desktop.
Optionally, when the user performs a drag operation (or a zoom operation) on the visualization window of the sub-desktop, the client may generate a drag instruction corresponding to the drag operation (or generate a zoom instruction corresponding to the zoom operation), and move the visualization window of the sub-desktop to a position indicated by a mouse arrow according to the drag instruction (or reduce or enlarge the visualization window of the sub-desktop to the position indicated by the mouse arrow according to the zoom operation). For example, when a user clicks a mouse on the edge of the visualization window of the sub-desktop and drags the mouse arrow to move left, the client may move the visualization window of the sub-desktop to move left according to the dragging instruction and move to the position where the mouse arrow stays last.
Fig. 2c and fig. 2d are schematic diagrams of another desktop organizing interface provided by the embodiment of the invention. As shown in FIG. 2c, a sub-desktop 600 and a sub-desktop 700 are included in main desktop 500. When the user clicks the right mouse button through a blank area in the main desktop 500 (i.e., an area except for a desktop object in the main desktop 500), the management operation list 100 shown in fig. 2a may be popped up and displayed in the main desktop 500, and the "new grid" button 200 in the management operation list 100 shown in fig. 2a is clicked through the mouse, so that the sub desktop 600 may be created and displayed in the main desktop 500, and at this time, the "new grid" area in the sub desktop 600 is a sub desktop name input area.
As shown in FIG. 2d, after the sub desktop 600 is created, a sub desktop 700 may be further created in the main desktop 500, and the process of creating the sub desktop 700 is the same as the process of creating the sub desktop 600. As shown in fig. 2d, when a user inputs a name "my video file" in a sub desktop name input area of the sub desktop 700, the sub desktop 700 with the name "my video file" may be displayed in the main desktop 500, at this time, the client may set file type information corresponding to the sub desktop 700 as video file type information, and generate an addition/deletion request carrying the video file type information, and the client may add all video files (specifically, 3 video files) in the main desktop 500 in fig. 2c to the sub desktop 700 according to the video file type information in the addition/deletion request, and delete icons of all video files in the main desktop 500 in fig. 2c, so as to obtain the sub desktop 700 shown in fig. 2d (i.e., 3 video files are displayed in the sub desktop 700, these 3 video files are no longer displayed in the main desktop 500). During the process of creating the sub desktop 600 and the sub desktop 700, both the sub desktop 600 and the sub desktop 700 may take over the window operation function of the main desktop 500. For example, when a right mouse button is clicked in the blank areas of the main desktop 500, the sub desktop 600, and the sub desktop 700, the management operation list 100 shown in fig. 2a may be popped up and displayed. Optionally, the user may also perform a dragging operation or a zooming operation on the sub-desktop 600 and the sub-desktop 700 by controlling a mouse arrow. Optionally, the user may also drag the desktop object in the main desktop 500 into the sub desktop 600 by controlling a mouse arrow, so that the sub desktop 600 may display an image of the dragged desktop object, and delete an icon of the dragged desktop object in the main desktop 500. Optionally, if the user drags 2 or more files in doc format in the main desktop 500 to the sub desktop 600 by controlling a mouse arrow, the "new grid" area in the sub desktop 600 may automatically name and display the name "my doc file".
According to the embodiment of the invention, the sub-desktop creating request is acquired on the preset main desktop, the sub-desktop can be created according to the desktop creating request, the sub-desktop is covered in the preset area of the main desktop, the adding and deleting request associated with the sub-desktop is acquired, the target desktop object in the main desktop is added into the sub-desktop according to the adding and deleting request, the icon of the target desktop object in the main desktop is deleted according to the adding and deleting request, and the target desktop object in the sub-desktop and the user interface of the sub-desktop are managed based on the window operation function of the sub-desktop. Because the window operation function of the sub-desktop is the same as that of the main desktop, when the user interface of the sub-desktop and the target desktop object in the sub-desktop are managed, the effect the same as that of the window operation function of the main desktop can be completely enjoyed, so that the number of files in the main desktop can be reduced only by setting the sub-desktop, and the management efficiency of the files and the user interface can be improved when the desktop is managed.
Fig. 3 is a schematic structural diagram of a desktop management device according to an embodiment of the present invention. As shown in fig. 3, the desktop management apparatus 1 may be applied to a client (e.g., a desktop application), and the desktop management apparatus 1 may include: a second creating module 10, an adding configuration module 20, a request obtaining module 30, a first creating module 40, an object operation module 50, a batch operation configuration module 60 and a batch operation module 70;
the second creating module 10 is configured to create a visualization window of a main desktop, cover the visualization window of the main desktop on a native desktop, control the visualization window of the main desktop to take over a window operation function of the native desktop, and control the visualization window of the main desktop to take over a routing identifier corresponding to each desktop object in the native desktop;
the adding configuration module 20 is configured to add icons corresponding to all desktop objects in the native desktop to the visual window of the main desktop, configure a sub-desktop creation management operation for the visual window of the main desktop, and add a function key associated with the sub-desktop creation management operation to a management operation list corresponding to the visual window of the main desktop.
For specific functional implementation manners of the second creating module 10 and the adding configuration module 20, reference may be made to the description of installing the client in S201 in the embodiment corresponding to fig. 2, which is not described herein again.
The request obtaining module 30 is configured to obtain a sub desktop creation request on a preset main desktop; the main desktop is covered on the native desktop, and the window operation function of the main desktop is the same as that of the native desktop;
the first creating module 40 is configured to create a sub desktop according to the sub desktop creation request, and cover the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop is the same as that of the main desktop;
the first creating module 40 is specifically configured to create a visualization window of a sub desktop according to the sub desktop creation request, cover the visualization window of the sub desktop in a preset area in the visualization window of the main desktop, and control the visualization window of the sub desktop to take over a window operation function of the visualization window of the main desktop.
The object operation module 50 is configured to obtain an add/delete request associated with the child desktop, add a target desktop object in a main desktop to the child desktop according to the add/delete request, delete an icon of the target desktop object in the main desktop according to the add/delete request, and perform a management operation on the target desktop object in the child desktop and a user interface of the child desktop based on a window operation function of the child desktop;
for specific functional implementation manners of the request obtaining module 30, the first creating module 40, and the object operating module 50, reference may be made to S101 to S103 in the embodiment corresponding to fig. 1, which is not described herein again.
The batch operation configuration module 60 is configured to configure batch startup operations in the window operation functions taken over by the visualization windows of the child desktop;
the batch operation module 70 is configured to, when a batch start operation request carrying a preset file format and corresponding to the child desktop is obtained, simultaneously start target desktop objects, all of which are in the preset file format, in the child desktop in a visual window of the child desktop according to the batch start operation request;
specifically, the batch operation configuration module 60 may configure batch start operations in a window operation function taken over by a visual window of the sub-desktop, and when a batch start operation request carrying a preset file format and corresponding to the sub-desktop is obtained, the batch operation module 70 may simultaneously start target desktop objects, all of which are in the preset file format, in the visual window of the sub-desktop according to the batch start operation request. For example, if the preset file format is doc format, when the visualization window of the sub desktop detects a batch start operation request, the batch operation module 70 may control the visualization window of the sub desktop to simultaneously open all files in the sub desktop in doc format. The batch start operation configured by the batch operation configuration module 60 may be a manner of adding a function key associated with the batch start operation to a management operation list in the sub desktop, so that when a user clicks the function key associated with the batch start operation in the management operation list in the sub desktop, the batch start operation request may be detected by a visualization window of the sub desktop.
Further, please refer to fig. 4, which is a schematic structural diagram of a request obtaining module 30 according to an embodiment of the present invention, where the request obtaining module 30 may include: a list display unit 301, a request generation unit 302;
the list display unit 301 is configured to, when a first click instruction corresponding to a function list key is detected in a main desktop, display the management operation list in a visualization window of the main desktop according to the first click instruction;
the request generating unit 302 is configured to generate a sub-desktop creation request according to a second click instruction when detecting the second click instruction corresponding to the function key associated with the sub-desktop creation management operation in the management operation list.
For specific functional implementation manners of the list display unit 301 and the request generation unit 302, reference may be made to S201 to S202 in the embodiment corresponding to fig. 2, which is not described herein again.
Further, please refer to fig. 5, which is a schematic structural diagram of an object operation module 50 according to an embodiment of the present invention, where the object operation module 50 may include: an object adding unit 501, an object takeover unit 502, a deletion unit 503, and a management operation unit 504;
the object adding unit 501 is configured to obtain an addition/deletion request associated with the child desktop, and add a target desktop object in a visualization window of a main desktop to a visualization window of the child desktop according to the addition/deletion request;
the object takeover unit 502 is configured to control a visualization window of the sub desktop to take over a route identifier corresponding to the target desktop object;
the deleting unit 503 is configured to delete an icon of the target desktop object in the visualization window of the main desktop according to the adding and deleting request when the visualization window of the sub desktop notifies that the visualization window of the main desktop has successfully taken over the route identifier corresponding to the target desktop object;
the management operation unit 504 is configured to perform a management operation on the target desktop object and the user interface of the sub desktop based on the window operation function of the visualization window of the main desktop taken over by the visualization window of the sub desktop and the route identifier corresponding to the target desktop object.
For specific functional implementation manners of the object adding unit 501, the object takeover unit 502, the deleting unit 503, and the management operation unit 504, reference may be made to S204-S206 in the embodiment corresponding to fig. 2, which is not described herein again.
Further, please refer to fig. 6, which is a schematic structural diagram of an object adding unit 501 according to an embodiment of the present invention, where the object adding unit 501 may include: the request generation subunit 5011, the object selection subunit 5012, the addition subunit 5013;
the request generating subunit 5011 is configured to, when a naming operation associated with the child desktop is detected, set file type information corresponding to the child desktop according to the naming operation, and generate an add/delete request carrying the file type information;
the object selection subunit 5012 is configured to select, according to the add/delete request, a desktop object that matches the file type information in a visualization window of the main desktop, so as to serve as a target desktop object;
the adding subunit 5013 is configured to add the target desktop object selected from the visualization window of the main desktop to the visualization window of the sub desktop according to the add/delete request;
according to the embodiment of the invention, the sub-desktop creating request is acquired on the preset main desktop, the sub-desktop can be created according to the desktop creating request, the sub-desktop is covered in the preset area of the main desktop, the adding and deleting request associated with the sub-desktop is acquired, the target desktop object in the main desktop is added into the sub-desktop according to the adding and deleting request, the icon of the target desktop object in the main desktop is deleted according to the adding and deleting request, and the target desktop object in the sub-desktop and the user interface of the sub-desktop are managed based on the window operation function of the sub-desktop. Because the window operation function of the sub-desktop is the same as that of the main desktop, when the user interface of the sub-desktop and the target desktop object in the sub-desktop are managed, the effect the same as that of the window operation function of the main desktop can be completely enjoyed, so that the number of files in the main desktop can be reduced only by setting the sub-desktop, and the management efficiency of the files and the user interface can be improved when the desktop is managed.
Fig. 7 is a schematic structural diagram of another desktop management device according to an embodiment of the present invention. As shown in fig. 7, the desktop management apparatus 1000 may include: at least one processor 1001, such as a CPU, at least one network interface 1004, a user interface 1003, memory 1005, at least one communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display) and a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a standard wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 7, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.
In the desktop management apparatus 1000 shown in fig. 7, the user interface 1003 is mainly used for providing an input interface for a user and acquiring data output by the user; and the processor 1001 may be used to invoke a device control application stored in the memory 1005 to implement
Acquiring a sub desktop establishing request on a preset main desktop; the main desktop is covered on the native desktop, and the window operation function of the main desktop is the same as that of the native desktop;
creating a sub desktop according to the sub desktop creation request, and covering the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop is the same as that of the main desktop;
acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a main desktop into the sub-desktop according to the adding and deleting request, deleting an icon of the target desktop object in the main desktop according to the adding and deleting request, and managing the target desktop object in the sub-desktop and a user interface of the sub-desktop based on a window operation function of the sub-desktop.
In one embodiment, before the processor 1001 obtains the child desktop creation request on the preset master desktop, the following steps are further performed:
creating a visual window of a main desktop, covering the visual window of the main desktop on a native desktop, controlling the visual window of the main desktop to take over a window operation function of the native desktop, and controlling the visual window of the main desktop to take over route identifications respectively corresponding to desktop objects in the native desktop;
adding icons corresponding to all desktop objects in the native desktop to a visual window of the main desktop, configuring a sub-desktop creation management operation for the visual window of the main desktop, and adding a function key associated with the sub-desktop creation management operation in a management operation list corresponding to the visual window of the main desktop.
In an embodiment, when the processor 1001 acquires a child desktop creation request on a preset primary desktop, the following steps are specifically performed:
when a first click instruction corresponding to a function list key is detected in a main desktop, displaying the management operation list in a visual window of the main desktop according to the first click instruction;
and when a second click instruction corresponding to the function key associated with the child desktop creation management operation in the management operation list is detected, generating a child desktop creation request according to the second click instruction.
In an embodiment, when the processor 1001 creates a child desktop according to the child desktop creation request and covers the child desktop in a preset area of the main desktop, the following steps are specifically performed:
and creating a visual window of the sub desktop according to the sub desktop creation request, covering the visual window of the sub desktop in a preset area in the visual window of the main desktop, and controlling the visual window of the sub desktop to take over the window operation function of the visual window of the main desktop.
In an embodiment, when the processor 1001 performs an operation of acquiring an add/delete request associated with the child desktop, adding a target desktop object in a main desktop to the child desktop according to the add/delete request, deleting an icon of the target desktop object in the main desktop according to the add/delete request, and performing a management operation on the target desktop object in the child desktop and a user interface of the child desktop based on a window operation function of the child desktop, the following steps are specifically performed:
acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a visual window of a main desktop into the visual window of the sub-desktop according to the adding and deleting request, and controlling the visual window of the sub-desktop to take over a route identifier corresponding to the target desktop object;
when the visual window of the sub desktop informs the visual window of the main desktop that the routing identifier corresponding to the target desktop object is successfully taken over, deleting the icon of the target desktop object in the visual window of the main desktop according to the adding and deleting request;
and based on the window operation function of the visual window of the main desktop taken over by the visual window of the sub-desktop and the route identification corresponding to the target desktop object, performing management operation on the target desktop object and the user interface of the sub-desktop.
In an embodiment, when the processor 1001 executes to acquire an addition/deletion request associated with the child desktop, and adds a target desktop object in a visualization window of a main desktop to a visualization window of the child desktop according to the addition/deletion request, the following steps are specifically executed:
when a naming operation associated with the sub desktop is detected, setting file type information corresponding to the sub desktop according to the naming operation, and generating an adding and deleting request carrying the file type information;
selecting a desktop object matched with the file type information in a visual window of the main desktop according to the adding and deleting request to serve as a target desktop object;
and adding the target desktop object selected from the visual windows of the main desktop into the visual windows of the sub desktops according to the adding and deleting request.
In one embodiment, the processor 1001 further performs the steps of:
configuring batch starting operation in the window operation function taken over by the visual window of the sub desktop;
when a batch starting operation request carrying a preset file format and corresponding to the sub-desktop is obtained, simultaneously starting target desktop objects in the sub-desktop, all of which are in the preset file format, in a visual window of the sub-desktop according to the batch starting operation request.
According to the embodiment of the invention, the sub-desktop creating request is acquired on the preset main desktop, the sub-desktop can be created according to the desktop creating request, the sub-desktop is covered in the preset area of the main desktop, the adding and deleting request associated with the sub-desktop is acquired, the target desktop object in the main desktop is added into the sub-desktop according to the adding and deleting request, the icon of the target desktop object in the main desktop is deleted according to the adding and deleting request, and the target desktop object in the sub-desktop and the user interface of the sub-desktop are managed based on the window operation function of the sub-desktop. Because the window operation function of the sub-desktop is the same as that of the main desktop, when the user interface of the sub-desktop and the target desktop object in the sub-desktop are managed, the effect the same as that of the window operation function of the main desktop can be completely enjoyed, so that the number of files in the main desktop can be reduced only by setting the sub-desktop, and the management efficiency of the files and the user interface can be improved when the desktop is managed.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.

Claims (13)

1. A desktop management method, comprising:
acquiring a sub desktop establishing request on a preset main desktop; the main desktop is covered on a native desktop, and the window operation function of the main desktop at least comprises the window operation function of the native desktop;
creating a sub desktop according to the sub desktop creation request, and covering the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop at least comprises the window operation function of the main desktop;
acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a main desktop into the sub-desktop according to the adding and deleting request, deleting an icon of the target desktop object in the main desktop according to the adding and deleting request, and managing the target desktop object in the sub-desktop and a user interface of the sub-desktop based on a window operation function of the sub-desktop;
when a batch starting operation request carrying a preset file format and corresponding to the sub-desktop is obtained, simultaneously starting target desktop objects in the sub-desktop, all of which are in the preset file format, in a visual window of the sub-desktop according to the batch starting operation request; the window operation function of the sub-desktop comprises batch starting operation.
2. The method of claim 1, wherein before the step of obtaining the child desktop creation request on the preset primary desktop, further comprising:
creating a visual window of a main desktop, covering the visual window of the main desktop on a native desktop, controlling the visual window of the main desktop to take over a window operation function of the native desktop, and controlling the visual window of the main desktop to take over route identifications respectively corresponding to desktop objects in the native desktop;
adding icons corresponding to all desktop objects in the native desktop to a visual window of the main desktop, configuring a sub-desktop creation management operation for the visual window of the main desktop, and adding a function key associated with the sub-desktop creation management operation in a management operation list corresponding to the visual window of the main desktop.
3. The method of claim 2, wherein obtaining the child desktop creation request on the pre-defined primary desktop comprises:
when a first click instruction corresponding to a function list key is detected in a main desktop, displaying the management operation list in a visual window of the main desktop according to the first click instruction;
and when a second click instruction corresponding to the function key associated with the child desktop creation management operation in the management operation list is detected, generating a child desktop creation request according to the second click instruction.
4. The method of claim 2 or 3, wherein the creating a child desktop according to the child desktop creation request and overlaying the child desktop in a preset area of the main desktop specifically comprises:
and creating a visual window of the sub desktop according to the sub desktop creation request, covering the visual window of the sub desktop in a preset area in the visual window of the main desktop, and controlling the visual window of the sub desktop to take over the window operation function of the visual window of the main desktop.
5. The method as claimed in claim 4, wherein the obtaining of the add/delete request associated with the child desktop, adding the target desktop object in the main desktop to the child desktop according to the add/delete request, deleting the icon of the target desktop object in the main desktop according to the add/delete request, and performing management operation on the target desktop object in the child desktop and the user interface of the child desktop based on the window operation function of the child desktop comprises:
acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a visual window of a main desktop into the visual window of the sub-desktop according to the adding and deleting request, and controlling the visual window of the sub-desktop to take over a route identifier corresponding to the target desktop object;
when the visual window of the sub desktop informs the visual window of the main desktop that the routing identifier corresponding to the target desktop object is successfully taken over, deleting the icon of the target desktop object in the visual window of the main desktop according to the adding and deleting request;
and based on the window operation function of the visual window of the main desktop taken over by the visual window of the sub-desktop and the route identification corresponding to the target desktop object, performing management operation on the target desktop object and the user interface of the sub-desktop.
6. The method of claim 5, wherein the obtaining of the add-delete request associated with the child desktop, and adding the target desktop object in the visualization window of the main desktop to the visualization window of the child desktop according to the add-delete request comprises:
when a naming operation associated with the sub desktop is detected, setting file type information corresponding to the sub desktop according to the naming operation, and generating an adding and deleting request carrying the file type information;
selecting a desktop object matched with the file type information in a visual window of the main desktop according to the adding and deleting request to serve as a target desktop object;
and adding the target desktop object selected from the visual windows of the main desktop into the visual windows of the sub desktops according to the adding and deleting request.
7. A desktop management apparatus, comprising:
the request acquisition module is used for acquiring a sub desktop creation request on a preset main desktop; the main desktop is covered on a native desktop, and the window operation function of the main desktop at least comprises the window operation function of the native desktop;
the first creating module is used for creating a sub desktop according to the sub desktop creating request and covering the sub desktop in a preset area of the main desktop; the window range of the sub desktop is smaller than that of the main desktop, and the window operation function of the sub desktop at least comprises the window operation function of the main desktop;
the object operation module is used for acquiring an adding and deleting request associated with the sub-desktop, adding a target desktop object in a main desktop into the sub-desktop according to the adding and deleting request, deleting an icon of the target desktop object in the main desktop according to the adding and deleting request, and managing the target desktop object in the sub-desktop and a user interface of the sub-desktop based on a window operation function of the sub-desktop;
the batch operation module is used for simultaneously starting target desktop objects which are all in the preset file format in the sub desktop in a visual window of the sub desktop according to the batch starting operation request when the batch starting operation request which is corresponding to the sub desktop and carries the preset file format is obtained; the window operation function of the sub-desktop comprises batch starting operation.
8. The apparatus of claim 7, further comprising:
the second creation module is used for creating a visual window of the main desktop, covering the visual window of the main desktop on the native desktop, controlling the visual window of the main desktop to take over the window operation function of the native desktop, and controlling the visual window of the main desktop to take over the route identifiers corresponding to the desktop objects in the native desktop respectively;
and the adding configuration module is used for adding icons corresponding to all desktop objects in the native desktop into the visual window of the main desktop, configuring a sub-desktop creating management operation for the visual window of the main desktop, and adding a function key related to the sub-desktop creating management operation into a management operation list corresponding to the visual window of the main desktop.
9. The apparatus of claim 8, wherein the request acquisition module comprises:
the management operation list display unit is used for displaying the management operation list in a visualization window of the main desktop according to a first click instruction when the first click instruction corresponding to a function list key is detected in the main desktop;
and the request generating unit is used for generating a sub-desktop creating request according to a second click instruction when the second click instruction corresponding to the function key associated with the sub-desktop creating management operation in the management operation list is detected.
10. The apparatus of claim 8 or 9,
the first creation module is specifically configured to create a visualization window of a sub desktop according to the sub desktop creation request, cover the visualization window of the sub desktop in a preset area in the visualization window of the main desktop, and control the visualization window of the sub desktop to take over a window operation function of the visualization window of the main desktop.
11. The apparatus of claim 10, wherein the object manipulation module comprises:
the object adding unit is used for acquiring an adding and deleting request associated with the sub desktop, and adding a target desktop object in a visual window of the main desktop into the visual window of the sub desktop according to the adding and deleting request;
the object takeover unit is used for controlling a visual window of the sub desktop to take over the route identifier corresponding to the target desktop object;
a deleting unit, configured to delete an icon of the target desktop object in the visual window of the main desktop according to the adding and deleting request when the visual window of the sub desktop notifies that the visual window of the main desktop has successfully taken over the route identifier corresponding to the target desktop object;
and the management operation unit is used for performing management operation on the target desktop object and the user interface of the sub desktop based on the window operation function of the visual window of the main desktop taken over by the visual window of the sub desktop and the route identifier corresponding to the target desktop object.
12. The apparatus of claim 11, wherein the object adding unit comprises:
the request generation subunit is configured to, when a naming operation associated with the child desktop is detected, set file type information corresponding to the child desktop according to the naming operation, and generate an addition/deletion request carrying the file type information;
the object selection subunit is used for selecting a desktop object matched with the file type information in a visual window of the main desktop according to the adding and deleting request to serve as a target desktop object;
and the adding subunit is configured to add the target desktop object selected in the visualization window of the main desktop to the visualization window of the sub desktop according to the adding and deleting request.
13. A desktop management device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 6.
CN201611061993.9A 2016-11-25 2016-11-25 Desktop management method and device Active CN108108077B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611061993.9A CN108108077B (en) 2016-11-25 2016-11-25 Desktop management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611061993.9A CN108108077B (en) 2016-11-25 2016-11-25 Desktop management method and device

Publications (2)

Publication Number Publication Date
CN108108077A CN108108077A (en) 2018-06-01
CN108108077B true CN108108077B (en) 2020-03-20

Family

ID=62204522

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611061993.9A Active CN108108077B (en) 2016-11-25 2016-11-25 Desktop management method and device

Country Status (1)

Country Link
CN (1) CN108108077B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108959490A (en) * 2018-06-25 2018-12-07 小港网络科技泗阳有限公司 The shape methods of exhibiting in kind of computer document

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102279694A (en) * 2010-06-08 2011-12-14 联想(北京)有限公司 Electronic device and display method of application software window thereof
CN102455873A (en) * 2010-10-15 2012-05-16 三星电子株式会社 Method and apparatus for selecting menu item

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103176687A (en) * 2011-12-26 2013-06-26 腾讯科技(深圳)有限公司 Regionalized management method and regionalized management system of desktop icons
CN103019513B (en) * 2012-11-30 2016-06-01 北京奇虎科技有限公司 The device and method that folder desktop is shown
CN103823614B (en) * 2014-03-10 2018-01-16 联想(北京)有限公司 Information processing method, device and electronic equipment
CN106066874B (en) * 2016-05-27 2019-11-12 腾讯科技(深圳)有限公司 Object processing method and terminal

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102279694A (en) * 2010-06-08 2011-12-14 联想(北京)有限公司 Electronic device and display method of application software window thereof
CN102455873A (en) * 2010-10-15 2012-05-16 三星电子株式会社 Method and apparatus for selecting menu item

Also Published As

Publication number Publication date
CN108108077A (en) 2018-06-01

Similar Documents

Publication Publication Date Title
CN101957730B (en) Messaging device and information processing method
US11112962B2 (en) Content-based directional placement application launch
US20070094597A1 (en) Dynamic graphical user interface for a desktop environment
US20070226650A1 (en) Apparatus and method for highlighting related user interface controls
EP3155507B1 (en) Storage system user interface with floating file collection
US20060085758A1 (en) Desktop alert management
WO2016081251A1 (en) Local representation of shared files in disparate locations
US20140359478A1 (en) Systems and Methods for Sharing a User Interface Element Based on User Gestures
TW201525776A (en) Invocation control over keyboard user interface
US10810698B2 (en) Information processing method and client
US11036344B1 (en) Managing application windows of applications from different servers within a same browser window on a user device
US20170168653A1 (en) Context-driven, proactive adaptation of user interfaces with rules
JPH10293760A (en) Object management method
US20200293164A1 (en) Html editing operations
WO2015184736A1 (en) Method and terminal for transforming background picture of touchscreen device
US20200134099A1 (en) Dynamically change user interfaces for web applications and associated methods
CN109725958A (en) The method and device that the file of resource manager management is handled
CN112947923A (en) Object editing method and device and electronic equipment
US9836469B2 (en) Techniques for processing digital assets for editing in a digital asset editing computer program
CN108108077B (en) Desktop management method and device
US20130086471A1 (en) Workflow integration and management of presentation options
CN103744573A (en) Data quick viewing and analyzing system based on graphic device interface
CN108605078A (en) Image processing equipment, image processing system and image processing method
CN112578961B (en) Application identifier display method and device
CN111796733A (en) Image display method, image display device and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant