US5651108A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Development system with methods for visual inheritance and improved object reusability
Assignee: CODEGEAR LLC
•
Filing: 1996-01-11
•
Granted: 1997-07-22
•
Expires: 2016-01-11
Abstract
Abstract A system of the present invention includes a relational database management system (RDBMS), having an object-based, interactive visual-programming language providing programming by "visual inheritance." A user places screen objects (e.g., boxes, screen buttons, table objects, and the like) on an on-screen window or "form," visually attaches selected "properties" and "methods" to the screen objects, and then establishes an containership-based event model that dictates how and when these properties and methods will be invoked. An object inherits (derives) properties and methods from other (parent) objects via its visual containership. In this manner, the task of creating and maintaining application programs is greatly simplified.
Inventors
- 👤 Ronald Allen Cain
- 👤 Janet Andrea De Lu
- 👤 Ralph E. Lemke
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 09:31
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/30; G06F8/34
Claims Analysis
Total Claims: 22
Claim 1
Independent Claim
211 words
In a computer system, a method for creating application programs, said method comprising: displaying a form on a screen for placement of screen objects at desired locations at design time; receiving user input for placing a first screen object on said form; receiving user input for attaching program logic to said first screen object, said program logic specifying program action undertaken upon occurrence of a particular event at said first screen object at runtime; receiving user input requesting copying of said first screen object; in response to said user input requesting copying of said first screen object, creating a copy of said first screen object in system memory, said copy including a copy of said program logic attached to said first screen object; receiving user input requesting pasting of the copy of said first screen object at a desired location; and in response to said user input requesting pasting of the copy of said first screen object, pasting a copy of the first screen object by creating a second screen object at said desired location, said second screen object being created from the copy of the first screen object in system memory, wherein said second screen object also includes a copy of said program logic attached to said first screen object.
Claim 2
Dependent Claim
211 words
In a computer system, a method for creating application programs, said method comprising: displaying a form on a screen for placement of screen objects at desired locations at design time; receiving user input for placing a first screen object on said form; receiving user input for attaching program logic to said first screen object, said program logic specifying program action undertaken upon occurrence of a particular event at said first screen object at runtime; receiving user input requesting copying of said first screen object; in response to said user input requesting copying of said first screen object, creating a copy of said first screen object in system memory, said copy including a copy of said program logic attached to said first screen object; receiving user input requesting pasting of the copy of said first screen object at a desired location; and in response to said user input requesting pasting of the copy of said first screen object, pasting a copy of the first screen object by creating a second screen object at said desired location, said second screen object being created from the copy of the first screen object in system memory, wherein said second screen object also includes a copy of said program logic attached to said first screen object.
Claim 3
Dependent Claim
15 words
The method of claim 1, wherein said form comprises a window for containing other objects.
Claim 4
Dependent Claim
31 words
The method of claim 1, wherein said first screen object is a screen object having an object type selected from a push-button object, a table object, and an edit field object.
Claim 5
Dependent Claim
49 words
The method of claim 1, wherein said first screen object is a screen button and wherein said program logic attached to said first screen object comprises user program code specifying method steps which the computer system is to perform upon occurrence of an event occurring at said screen button.
Claim 6
Dependent Claim
84 words
The method of claim 1, wherein said program logic attached to said first screen object is attached by: receiving user input requesting attachment of program code to the first screen object; displaying a list of built-in methods which operate in response to occurrence of particular events at said first screen object; receiving user input for selecting a particular built-in method which to add user-specified program logic; and displaying a program editor for receiving user inputs specifying particular program logic for the selected built-in method.
Claim 7
Dependent Claim
34 words
A method of claim 1, wherein said user input requesting copying of said first screen object comprises: selecting the first screen object with a pointing device; and invoking a copy command for the system.
Claim 8
Dependent Claim
42 words
A method of claim 1, wherein said program logic attached to said first screen object comprises p-code instructions specifying operation of the system, and wherein said copy of said first screen object in system memory includes a copy of said p-code instructions.
Claim 9
Dependent Claim
35 words
The method of claim 7, wherein said second screen object includes a copy of said p-code instructions, so that said second screen object undertakes the same program action as said first screen object at runtime.
Claim 10
Dependent Claim
61 words
The method of claim 1, wherein said system includes a shared-memory clipboard of system memory for sharing data between objects, and wherein said creating a copy of said first screen object step includes: registering a clip object format with said shared memory clipboard, said clip object format specifying a protocol for copying program logic attached to an object to the clipboard.
Claim 11
Dependent Claim
21 words
The method of claim 9, wherein said system comprises Microsoft® Windows and wherein said shared memory clipboard comprises Microsoft® Windows clipboard.
Claim 12
Dependent Claim
58 words
The method of claim 1, wherein said pasting step includes: determining from said user input requesting pasting of a copy of said first screen object a particular destination; determining an object type for said first screen object; and before pasting a copy of the first screen object, determining whether the destination is suitable for the determined object type.
Claim 13
Dependent Claim
27 words
The method of claim 11, wherein said determined object type comprises a push-button and wherein said particular destination comprises a screen box capable of containing said push-button.
Claim 14
Dependent Claim
56 words
The method of claim 12, wherein said determined object type comprises a push-button and wherein said particular destination comprises a text object which is not capable of containing a push-button, whereupon said system displays a message to the user indicating that a request to paste a push-button inside a text object is not a valid operation.
Claim 15
Dependent Claim
41 words
The method of claim 11, further comprising: if the particular destination is determined not to be suitable for the determined object type, displaying a message to the user indicating that the request to paste an object is not a valid operation.
Claim 16
Dependent Claim
26 words
The method of claim 1, further comprising: displaying a second form; and wherein said pasting step includes pasting a screen object from one form to another.
Claim 17
Dependent Claim
139 words
In a form-based application development system, a method for providing visual inheritance between screen objects comprising: displaying a form on a screen for placing at design time screen objects, each screen object having properties and methods which operate in response to occurrence of events at the object, some of said screen objects capable of containing other screen objects; placing a first screen object on said form, said first screen object capable of serving as a container object for other screen objects; placing a second screen object within said first screen object, so that second screen object is contained within said first screen object, whereupon said second screen object inherits access to methods of said first screen object; and displaying an object tree for visually indicating an inheritance hierarchy between objects based on objects which are contained by other objects.
Claim 18
Dependent Claim
139 words
In a form-based application development system, a method for providing visual inheritance between screen objects comprising: displaying a form on a screen for placing at design time screen objects, each screen object having properties and methods which operate in response to occurrence of events at the object, some of said screen objects capable of containing other screen objects; placing a first screen object on said form, said first screen object capable of serving as a container object for other screen objects; placing a second screen object within said first screen object, so that second screen object is contained within said first screen object, whereupon said second screen object inherits access to methods of said first screen object; and displaying an object tree for visually indicating an inheritance hierarchy between objects based on objects which are contained by other objects.
Claim 19
Dependent Claim
19 words
The method of claim 16, wherein said screen objects capable of containing other screen objects include a screen box.
Claim 20
Dependent Claim
32 words
The method of claim 17, wherein said screen box is capable of containing a push-button, so that a push-button placed within a screen box inherits access to methods of the screen box.
Claim 21
Dependent Claim
48 words
The method of claim 16, further comprising: placing the second screen object outside of the first screen object; and in response to the second screen object lying outside of the first screen object, eliminating access of the second screen object to the methods of the first screen object.
Claim 22
Dependent Claim
41 words
The method of claim 19, further comprising: upon placement of the second screen object outside the first screen object, updating display of the object tree to indicate that said second screen object is no longer contained within the first screen object.
References Cited (Backward Citations)
US5487141A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2000-07-21 | 2001-01-20 | 2001-07-22 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2004-07-21 | 2005-01-20 | 2005-07-22 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2008-07-21 | 2009-01-20 | 2009-07-22 | $7700.00 | Window Closed / Lapsed |