Development system with methods for visual inheritance and improved object reusability

• US 5,487,141 A
• Filed: 01/21/1994
• Issued: 01/23/1996
• Est. Priority Date: 01/21/1994
• Status: Expired due to Term

• Current Assignee: CodeGear (Idera, Inc.)
• Original Assignee: Borland International, Inc. (Open Text Corporation)
• Inventors: Cain, Ronald A., De Lu, Janet A., Lemke, Ralph E.
• Primary Examiner(s): Nguyen, Phu K.
• Application Number:
  US08/184,611
• Time in Patent Office: 732 Days
• Field of Search: 395/133, 395/135, 395/155, 395/161, 395/159, 395/160, 345/119, 345/120
• US Class Current: 715/764
• CPC Class Codes: G06F 8/34 Graphical or visual programming

Abstract

Relational database management system (RDBMS) with an object-based, interactive visual-programming language provides 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 or derives properties and methods from other (parent) objects via its visual containership. The creation and maintenance of application programs is greatly simplified.

Claims

1. In a computer system, a method for creating an application program, the method comprising:

(a) providing a set of screen objects, each object having a set of properties and built-in methods for responding to user events, said set of objects including some objects which may be contained within other objects of the set;

(b) displaying a blank form for placement of objects;

(c) placing desired ones of said objects at desired locations on the form, each object having a visual boundary on screen;

(d) positioning first and second objects so that said first object is positioned inside the visual boundary of said second object; and

(e) in response to said positioning step, establishing an object hierarchy specifying a container relationship between said first and second objects, said container relationship specifying that user events occurring at said first object are passed to said built-in methods of said second object for processing after processing by said built-in methods of said first object.

2. The method of claim 1, wherein said objects include screen buttons, box objects, text objects, and table objects.

3. The method of claim 1, further comprising:

(e) receiving an event at a particular one of said objects;

(f) passing the event first to the form for processing;

(g) passing the event back to said particular object for processing; and

(h) passing the event up the object hierarchy for processing by other objects which are containers to said particular object.

4. The method of claim 1, wherein said user events comprise user input events.

5. The method of claim 4, wherein said user input events include selected ones of keyboard input events and pointing device input events.

6. The method of claim 1, wherein said blank form comprises a window object displayed on a screen device.

7. The method of claim 1, wherein step (c) includes:

displaying a menu of objects;

receiving first input for selecting one object from said menu of objects;

receiving second input for selecting a position on a screen device, said position specifying a particular location on the blank form; and

in response to said first and second inputs, placing the selected object on the form at the particular location.

8. The method of claim 1, wherein step (e) further comprises:

for each at least one object placed within a boundary of another object, testing whether the object is compatible with the other object; and

establishing a container relationship between the objects only when they are compatible.

9. The method of claim 1, further comprising:

(e) for each at least one object placed within the boundary of another object, testing whether the object is too large for the other object; and

(f) automatically resizing the other object so that said each at least one object can be contained within the boundaries of the other object.

10. The method of claim 1, further comprising:

moving the first object from within the boundaries of the second object to within the boundaries of a third object; and

responsive to said moving step, destroying the container relationship between the first and second objects and establishing a new container relationship between the first object and the third object.

11. The method of claim 1, wherein said properties include selected ones of size, position, and color.

12. The method of claim 1, wherein said container relationship specifies that an object can access the methods and properties of objects it is contained within.

13. The method of claim 1, wherein said objects include user-supplied names, and wherein objects contained within the boundaries of the same object have unique names.

14. In a computer system, a method for creating an application program, the method comprising:

(a) providing a set of objects, each of said objects including a set of properties and methods;

(b) modifying at least one method of a particular object for creating a custom object;

(c) selecting said particular object from a screen device with an input device;

(d) copying said particular object with its set of properties and methods to a region of memory;

(e) selecting a destination location on the screen device; and

(f) placing an identical copy of said particular object with its set of properties and methods at the selected destination.

15. The method of claim 14, wherein said methods comprise programming steps for responding to user events.

16. The method of claim 14, wherein said region of memory comprises a region of shared memory allocated for interprocess communication.

17. The method of claim 16, wherein said interprocess communication is compatible with Microsoft Windows clipboard format.

18. The method of claim 14, wherein said objects include selected ones of screen buttons, box objects, text objects, and table objects.

19. The method of claim 14, wherein step (f) includes:

determining a type for said particular object;

determining whether an object of the determined type can be placed at the selected destination; and

placing an identical copy of said particular object with its set of properties and methods at the selected destination only if the type of object can be placed at the selected destination.

20. The method of claim 14, wherein said methods comprise user-supplied steps specifying action to be undertaken in response to occurrence of a particular event.

21. The method of claim 14, wherein said set of properties includes selected ones of size, position, and color.

22. The method of claim 14, further comprising:

if the copy of said particular object is placed within boundaries of another object, providing said copy with access to methods and properties of the other object.

23. The method of claim 14, wherein step (f) includes:

determining a type for said particular object;

determining whether the type of object can be placed at the selected destination; and

placing an identical copy of said particular object at the selected destination only if an object of that type can be placed at the selected destination.

24. A visual development system for creating an application program, the system comprising:

a computer system having a processor and a memory;

means for displaying a set of screen objects, each object having a visual boundary and having a set of properties and built-in methods for responding to user events, said set of objects including some objects which may be contained within other objects of the set;

means for displaying a blank form for placement of objects;

input means for placing desired ones of said objects at desired locations on the form and for positioning certain objects within the boundaries of other objects; and

means for specifying a container relationship between first and second objects when said first object is positioned within the visual boundary of said second object, said container relationship specifying that said first object has access to methods and properties of of said second object for processing of events occurring at said first object.

25. The system of claim 24, wherein said objects include selected ones of screen buttons, box objects, text objects, and table objects.

26. The system of claim 24, further comprising:

means for receiving an event at a particular one of said objects;

means for passing the event first to the form for processing;

means for passing the event back to said particular object for processing; and

means for passing the event up the object hierarchy for processing by other objects which are containers to said particular object.

27. The system of claim 24, wherein said user events comprise user input events.

28. The system of claim 27, wherein said user input events include selected ones of keyboard input events and pointing device input events.

29. The system of claim 24, wherein said input means includes:

means for displaying a menu of objects;

means for receiving first input for selecting one object from said menu of objects;

means for receiving second input for selecting a position on a screen device, said position specifying a particular location on the blank form; and

means, responsive to said first and second inputs, for placing the selected object on the form at the particular location.

30. The method of claim 24, wherein said establishing means comprises:

means for testing, for each at least one object place within a boundary of another object, whether the object is compatible with the other object; and

means for establishing a container relationship between the objects only when they are compatible.

31. In a graphical user interface, an improved method for cutting and pasting objects, the method comprising:

providing said objects with user-specified properties and methods operative on said objects;

establishing a shared memory protocol for copying objects, said protocol specifying a format for copying properties and methods of objects;

receiving a request from a user for copying an object;

copying to the shared memory information defining the object and its user-specified properties and methods operative on the object;

receiving a request from a user for copying the object to a new screen location; and

based on said information defining the object, creating a new object, said new object having properties and methods identical to the copied object.

32. The system of claim 31, wherein said objects comprise screen buttons.

33. The system of claim 31, wherein shared memory protocol is compatible with Microsoft Windows clipboard format.

34. The system of claim 33, wherein shared memory protocol includes a user-defined format for storing methods in p-code format.

35. The system of claim 31, wherein said information copied to the shared memory comprises data specifying a type of the object, properties of the object, and methods of the object.