Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
DETAILED ACTION
1. This action is responsive to application communication filed on 9/10/2024.
2. Claims 1-10, 14 and 15 are pending in the case.
3. Claims 11-13 are cancelled.
4. Claims 14 and 15 are newly added.
5. Claims 1, 14 and 15 are independent claims.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claim 15 is rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter.
Claim 15 recites the phrase “computer readable storage medium”. In light of the specification, a "storage medium” may be any medium that can store program code (see par. 178). Examiner submits that one of ordinary skill in the art would interpret the phrase to include a carrier wave, which is considered non statutory subject matter. Therefore, in such instance, the recited phrase is merely a signal and is not a process, a machine, a manufacture or a composition of matter.
Accordingly, the claim fails to recite statutory subject matter as defined in 35 U.S.C. § 101.
To overcome the 35 U.S.C. 101 rejection, Examiner suggests to amend claim to recite “non-transitory computer readable storage medium”.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-3, 6-10, 14 and 15 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Rose; Greg, 20100205559 A1.
Independent Claim 1:
Rose teaches An embedded window display method, comprising: when detecting a preset operation instruction, starting an embedded window in a currently displayed parent window based on the preset operation instruction; (e.g., selecting a compartment within the grid (i.e., embedded window) of the main window (i.e., currently parent window) to highlight the location to display an application icon par. 34; When a mouse pointer 34 moves over any of the squares 30, a visual indicator such as a distinct color, surrounds the square, indicating selection of the square. In FIG. 3, the selected square 32 is surrounded by a yellow color. The compartments or squares 30 are to be populated with icons 55 or other visual indicators that are associated with a desired function to be executed by the user, as described below.)
displaying an embedded window application corresponding to the preset operation instruction in the embedded window, (e.g., displaying an added application icon (i.e., embedded window application) within compartment of main window par. 49; In some embodiments, the Mouser application 100 allows executable software programs to be loaded into the main window in other ways besides the drag-and-drop technique.) wherein the embedded window and the parent window are at a same layer or adjacent layers, and an application displayed in the embedded window is associated with the parent window; (e.g., at a same layer or adjacent layers, customizing a grid of application icons (i.e., application display in the embedded window) associated with the main window (i.e., parent window) par. 34; In some embodiments, the main window 50 may be customized as to both the number of squares 30 and the arrangement of the squares. Thus, the main window 50 may be a 3.times.3 grid pattern (nine squares), a 5.times.3 grid pattern (fifteen squares), a 6.times.6 grid pattern (36 squares), and so on)
and performing, when receiving an operation instruction of the embedded window application, an interaction operation based on the operation instruction of the embedded window application. (e.g., performing quick launches and keystroke macros, based on selection of application icons within grid of main window par. 22; The application enables facile launch of executable programs, commonly used keystrokes, launches within a launch, and other operations. Users are able to customize the quick-launch application to suit personal preferences. Par. 25; The user populates the main window 50 with icons associated with and representing functions, such as commonly used programs, web page addresses, frequently used keystroke sequences, embedded keystroke operations, and so on, converting the main window (empty) to a master window 60. Par. 31; When the user selects an icon 55 by clicking thereon with a pointing device, the Mouser application 100 causes the underlying script 45 to be launched. The script may be simple, such as the address to an executable program or web page. Or, the script 45 may launch a series of keystrokes, in the case of macros. Or, the script 45 may perform a combination of keystroke sequences and address access, in the case of combinational operations, such as where a web page or executable program is accessed and certain keystroke operations are to be performed within the web page or program.)
Claim 2 depends on claim 1:
Rose teaches wherein the starting an embedded window in a currently displayed parent window based on the preset operation instruction comprises: drawing a parent window based on the preset operation instruction; and starting the embedded window in the drawn parent window. (e.g., displaying a main window with customizable grid par. 25; . A user launches the Mouser application 100 by clicking on the mouse icon 40. A main window 50, or popup window, appears on the computer desktop. The main window 50 is unpopulated and may be adjusted in shape and size, as described further below. Par. 34; In some embodiments, the main window 50 may be customized as to both the number of squares 30 and the arrangement of the squares. )
Claim 3 depends on claim 2:
Rose teaches wherein the drawing a parent window based on the preset operation instruction comprises: obtaining a window size of a to-be-drawn parent window (e.g., adjusting size of main window par. 25; The main window 50 is unpopulated and may be adjusted in shape and size, as described further below.)
and placeholder information of an embedded window in the to-be-drawn parent window; (e.g., drag and drop icon into grid of main window par. 47; The user simply clicks on the desktop icon and, while holding down the mouse button, drags the icon 55 to one of the empty squares 30 and drops the icon into the square by releasing the mouse button until the icon is visible within the main window 120. The Microsoft.RTM. Office Access.RTM. icon 55 is being dragged over to the main window 120 as shown. Once the icon 55 is present, the Mouser application 100 automatically generates an associated script 45 that includes the address to the Microsoft Access executable program stored on the hard drive or other non-volatile medium of the processor-based system. Subsequently, Microsoft Access is launched by simply clicking on the Access icon in the main window 120.)
and performing window drawing and layer composition based on the window size of the to-be-drawn parent window and the placeholder information of the embedded window, to obtain the drawn parent window. (e.g., displaying main window with icons within grid as shown in Figure 10 par. 47; In some embodiments, the Mouser application 100 enables the main window 50 to be populated with these program icons 55 using a feature known as "drag and drop.")
Claim 6 depends on claim 1:
Rose teaches wherein the displaying an embedded window application corresponding to the preset operation instruction in the embedded window comprises: during drawing of the embedded window, obtaining a window size of an application corresponding to the preset operation instruction and configured window dimensions of the embedded window; (e.g., minimizing or maximizing or resizing or relocating main window to adjust display position of grids within main window par. 25; The main window 50 is unpopulated and may be adjusted in shape and size, as described further below. par. 33; Standard in Windows.RTM. applications, the minimize button 24 allows the user to minimize the main window 50, such that a Mouser 100 icon will appear in the system tray.)
determining a display area of the application corresponding to the preset operation instruction based on the window size and the configured window dimensions of the embedded window; and displaying the application corresponding to the preset operation instruction based on the display area. (e.g., populating icon into the grid to determine display area of application based on the dimensions of the grid par. 25; The user populates the main window 50 with icons associated with and representing functions, such as commonly used programs, web page addresses, frequently used keystroke sequences, embedded keystroke operations, and so on, converting the main window (empty) to a master window 60. Par. 34; The compartments 30 may assume another shape besides being square-shaped, such as in the embodiments of FIGS. 7 and 8, below. In some embodiments, the main window 50 may be customized as to both the number of squares 30 and the arrangement of the squares.)
Claim 7 depends on claim 1:
Rose teaches wherein after the displaying an embedded window application corresponding to the preset operation instruction in the embedded window, the method further comprises: obtaining a preset synchronization event; and adjusting a display position of the embedded window based on the preset synchronization event. (e.g., minimizing or resizing main window to adjust display position of grids of main window par. 25; The main window 50 is unpopulated and may be adjusted in shape and size, as described further below. par. 33; Standard in Windows.RTM. applications, the minimize button 24 allows the user to minimize the main window 50, such that a Mouser 100 icon will appear in the system tray.)
Claim 8 depends on claim 1:
Rose teaches wherein the performing, when receiving an operation instruction of the embedded window application, an interaction operation based on the operation instruction of the embedded window application comprises: performing interface switching based on the operation instruction of the embedded window application when receiving the operation instruction of the embedded window application. (e.g., switching focus on launched application window par. 47; More precisely, once the user clicks on the Microsoft Access icon in the main window 120, the associated script 45 is run automatically, causing Microsoft Access to be launched.)
Claim 9 depends on claim 1:
Rose teaches wherein after the performing, when receiving an operation instruction of the embedded window application, an interaction operation based on the operation instruction of the embedded window application, the method further comprises: obtaining an exit instruction, and returning to a target interface based on the exit instruction. (e.g., closing out of a launched window par. 33; The close button 28 allows the user to exit the Mouser 100 application. par. 35; While the mouse cursor 34 is positioned over a square 30, a left mouse click on that square executes the function 35 (whether it be an executable application, a macro, or other operation) and closes the main window 50. par. 47; More precisely, once the user clicks on the Microsoft Access icon in the main window 120, the associated script 45 is run automatically, causing Microsoft Access to be launched.)
Claim 10 depends on claim 9:
Rose teaches wherein the obtaining an exit instruction, and returning to a target interface based on the exit instruction comprises: removing an embedded task stack based on the exit instruction, and returning to the target interface. (e.g., closing out of a launched window to remove the launched window in effort to display a remaining target window par. 33; The close button 28 allows the user to exit the Mouser 100 application. par. 35; While the mouse cursor 34 is positioned over a square 30, a left mouse click on that square executes the function 35 (whether it be an executable application, a macro, or other operation) and closes the main window 50. par. 47; More precisely, once the user clicks on the Microsoft Access icon in the main window 120, the associated script 45 is run automatically, causing Microsoft Access to be launched.)
Independent Claim 14:
Claim 14 is substantially encompassed in claim 1, therefore, Examiner relies on the same rationale set forth in claim 1 to reject claim 14.
Independent Claim 15:
Claim 15 is substantially encompassed in claim 1, therefore, Examiner relies on the same rationale set forth in claim 1 to reject claim 15.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claims 4 and 5 are rejected under 35 U.S.C. 103 as being unpatentable over Rose as cited above, in view of Kim et al. (hereinafter “Kim”), U.S. Published Application No. 20140164990 A1.
Claim 4 depends on claim 1:
Rose teaches wherein the starting an embedded window in a currently displayed parent window based on the preset operation instruction comprises: obtaining a target window, a window mode, window dimensions of the embedded window, a mark bit of the embedded window, and a touch mode of the embedded window; and drawing the embedded window based on the target window, the window mode, the window dimensions of the embedded window, the mark bit of the embedded window, the stack mode of the embedded window, and the touch mode of the embedded window, to obtain the embedded window. (e.g., displaying main window of Figure 10 with default settings while handling control to known Microsoft operating system)
Rose fails to expressly a stack mode of the embedded window.
However, Kim teaches a stack mode of the embedded window (e.g., managing windows in a stack par. 85; As the launcher application runs, the controller creates and manages a launcher application stack 301 in an activity stack.)
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the launched application windows as taught by Rose to include a controller for creating and managing stacks as taught by Kim to provide the benefit of improving the management and organization of multiple windows being launched.
Claim 5 depends on claim 4:
Rose/Kim teaches wherein after the drawing the embedded window based on the target window, the window mode, the window dimensions of the embedded window, the mark bit of the embedded window, the stack mode of the embedded window, and the touch mode of the embedded window, the method further comprises: when completing creation of the stack mode of the embedded window, handing over stack control to a host process corresponding to the parent window. (e.g., displaying main window of Rose’s Figure 10 with default settings while handling control to known Microsoft operating system) (e.g., managing windows in a stack Kim; par. 85; As the launcher application runs, the controller creates and manages a launcher application stack 301 in an activity stack.)
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Parker; Marsten H. US 5600789 A
Col. 11 line 19; Window parent statements are used to specify the parent window of the LSE being declared. A parent statement is required for any LSE that a GUI defines as a "child" of another window. Different GUIs do not always build their internal LSE hierarchies in the same way. Generally, if a window looks like a window to the user (that is, it has scroll bars, a caption, a system menu, etc.), all GUIs will define it as a "top-level" window, and the test tool will not require a parent statement in order to locate it. Parent statements should be written for most other windows, especially if portability is a concern. A parent statement has the form:
(88) [gui-type]parent window-name The field window-name is the identifier of the parent window. The parent window needs to be declared somewhere in the test script. The field gui-type is optional.
(89) Child windows should be declared in a script as one of the window-statements in the parent window's declaration. Declaring child windows in this way can make it easier to maintain the test script, since declarations for related LSEs appear together.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HENRY ORR whose telephone number is (571)270-1308. The examiner can normally be reached 9AM-5PM EST M-F.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Adam Queler can be reached at (571)272-4140. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/HENRY ORR/Primary Examiner, Art Unit 2172
Prosecution Insights