Abstract: A visual development system is described which provide “method pointers” allowing a developer/user to achieve delegation between objects programmatically as well as visually. Delegation “binds” an event source with an event handler. This binding is directly supported within the programming language of the system. Using a simple assignment statement, the user can assign a handler of one object (i.e., delegated-to object) to the method pointer of another object (i.e., delegated-from object). A delegation through assignment leads to not only the address of the method being copied but also the address of the delegated-to object (i.e., “this” pointer) being copied into the method pointer. The method pointer, when called, can invoke the pointed-to method on that (delegated-to) object, complete with the context (e.g., local data) of the object. The object knows about itself and, thus, can provide the appropriate context.

Abstract: A three-tier data processing system of the present invention includes a client application, operating on a client machine (i.e., first tier), which obtains data from a back-end data source (e.g., database server) by submitting a request (e.g., SQL query) to a middle tier. The middle tier, in turn, comprises a provider and a resolver. Data is actually returned to the client by means of a "data packet" of the present invention, which is a platform-independent self-describing data format used to exchange data between different subsystems of the architecture. A data packet normally represents a result set, which is received by a client from a remote server, containing both data and metadata. Upon receiving the data packet from the provider, the client unpacks the data and then proceeds to process and manipulate the data as if it were local data (e.g., for insert, deletes, updates, and the like).

Abstract: A development system having a client which employs a virtual machine for executing programs written in the Java programming language is described. The client executes a "compiled" (i.e., bytecode or pseudo-compiled) Java program, which has been created by compiling a Java source code program or script with a Java compiler. The pseudo-compiled program comprises the bytecode emitted by the compiler. The development system further includes a just-in-time compiler which natively compiles each pseudo-compiled method of a Java program on a "just-in-time" basis--that is, compiles each method as it is actually used into native machine code for a target microprocessor. Methods which are unused are left uncompiled (i.e., left as bytecode). During program execution, when a method call is made from interpreted code, the system employs an "invoker" slot of the callee. When a method call is made from compiled code, the system employs a "compiled code" slot of the callee.

Abstract: An electronic spreadsheet system of the present invention includes a notebook interface having a plurality of notebook pages, each of which may contain a spread of information cells, or other desired page type (e.g., Graphs page). Methods are provided for rapidly accessing and processing information on the different pages, including displaying a plurality of page identifiers for selecting individual pages, and further including a preferred syntax for referencing information. Additional methods are described for in-memory management and persistent storage of notebooks and their pages.

Abstract: A development system having a monitor/profiler tool for monitoring functions in natively compiled software programs is described. According to the present invention, the monitor/profiler tool is constructed to work directly on a natively compiled software application which only have debugging info. Unlike prior approaches, the monitor/profiler tool does not require a special compile or link phase for the application under exam. The tool can monitor any function in software application which has debug info, thus relieving program developers from the burden of maintaining two ways of building an application. The developer can simply use the same executable for both development and function analysis.

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. An alternative embodiment providing an "Object Explorer" is also described. The Explorer collapses object inspector and object tree functionality into a single UI (user interface) element.

Abstract: Graphical user interface system and methods for providing "hints" for screen objects of interest, particularly user interface elements which rely upon multitudes of iconic (bitmap image) indicia. The interface includes a static (status) frame or window positioned in a non-intrusive fashion below or to one side of a client area (active portion) of a user interface. The frame is continually updated with appropriate descriptors or "hints" (e.g., text and/or graphics) as a screen cursor moves from one screen object to another.

Abstract: A visual development system is described which allows a user to derive forms from other "ancestor" forms, inheriting their components, properties, and code as a starting point for one's own forms. During system operation, the user selects an "Inherit" menu choice for indicating to the system that the form to be created inherits from an existing ancestor form. Ancestor forms can be any forms already contained in an existing project or in an "object repository" provided by the system. Form inheritance allows the user to create a library of standard form templates, either within a single application or across an entire suite of applications. Any changes made to the ancestor form immediately appear in the descendant forms. Further, the use can customize each form type so derived while still retaining the ability to modify the standard form and have those changes reflected in the derived forms.

Abstract: A development system is described which provides a form-based development environment for partitioning an application such that it can be seamlessly integrated into corporate Webs (i.e., "intranets"). A form is implemented as an "application page" and published as an ActiveX object. Specifically, a new "application" page MIME type is defined: application/x-appdoc. This contains information necessary to create a document (e.g., Microsoft ActiveX Document) locally but, in addition, also includes information necessary to find and download the program code for rendering the view of the document. If the program code is already present locally, it need only be downloaded for purpose of updating the local copy. Once a form is built into an ActiveX object and digitally signed, it can be downloaded to a client and run in a Web browser, such as Microsoft Internet Explorer.

Abstract: A system of the present invention includes a relational database management system (RDBMS). Methods are described for maintaining integrity between "design documents," which may be creating under different operating systems, and one or more information tables of the system. The system provides each field of a table with a unique ID ("field ID") for tracking the field regardless of restructuring changes which may be made to the table by various clients. Corresponding field IDs are stored with the fields of design documents, thereby permitting the system to maintain a link between a design document and its table. Upon a restructure of a table, the dependent design documents may be appropriately updated by their respective clients. Methods are also described for improved storage of free-form or "memo" data. In a preferred embodiment, memo data are stored in a separate file comprised of variable-length storage blocks.

Abstract: An object-oriented development system of the present invention includes a development system, which may include, among other features, a compiler, a linker, standard libraries, class libraries, and a debugger. Methods of the present invention include constructing C++ classes having response functions--C++ class methods which process specific system messages of interest. More particularly, a C++ class includes a registry object--an object which associates the message of interest with a particular response function. The registry object includes C++ template definition, whereby the object includes a "generic" function, that is, one which is not tied to any specific parameter type. In this manner, the message-response functions of the development system do not require compiler-specific extensions or unsafe casting operations.

Abstract: A development system providing methodology for improving system performance by decreasing recompilation of dependent source modules is described. During operation, the system keeps track of several pieces of information. From the outset, the system has kept track of the timestamps of sources (e.g., A.java file in a Java system) and compiled files thereof (e.g., A.class class file in a Java system). Examination of the timestamps leads to detection of those files which have been modified. The system will recompile A.java in the following circumstances: (1) A.class is not found, (2) A.java has a different timestamp, or (3) A.class has a different timestamp. Otherwise, the system does not invoke a recompile. If a recompilation in not required, the system then looks to the imports for determining whether the imports are consistent. Here, the system checks the timestamps of imports, possibly recompiling one or more of the modules providing the imports.

Abstract: A computer system having a facility for concurrently sharing objects or resources is described. The system includes a publish-and-subscribe facility or "Object Exchange," for facilitating sharing among workgroups. When a data object is "published" by a user ("publisher"), the object is sent from that user's computer to other computer users specified by the publisher. Those interested in the published data object (published pages) may elect to receive or "subscribe" to that data. From that point on, the publisher can choose to update the data, such as whenever the published version changes. The "subscribers" of the published pages automatically get updates. Subscribers of a spreadsheet notebook, for instance, would automatically receive pages as they are published. The Object Manager effects actions by posting messages or "forms" to either the local Object Exchange (assuming one is the publisher) or the Object Exchange of others (subscribers).

Abstract: Development system with visual designer tools (Designers) are described for generating and modifying program code. During system operation, a user employs the Designers to visually create an application program and generate a source file. Moreover, the user can proceed to edit the file with a text editor and then return to the Designers to edit the form visually. Each Designer is a bi-directional or "two-way" tool: the user can modify a form either visually with a Designer, or by editing the generated code in a source (text) file with a text editor. The user can use both techniques interchangeably--switching at will. All changes which occur in Designers are reflected in the generated code and vice versa.

Abstract: A development system having a compiler, a linker, and an interface for detecting invalid use of resource is generated. When the system is (optionally) operating in a "code guarded" mode, the linker links the object modules with a CodeGuard.RTM. Library to generate "code guarded" program(s). The API (Application Programming Interface) calls to the runtime libraries are "wrappered" by CodeGuard wrapper functions. Additionally in this mode, operation of the compiler is altered to insert calls from the user code (e.g., compiled code in object modules) to the CodeGuard Runtime Library, for checking runtime use of resources and memory. As a result, the system can identify a programming error at the location where it occurs that is, at the original line of code which gave rise to the problem in the first place. Errors are found immediately as they happen, so that the original offending site can be determined. In this manner, the task of creating computer programs is simplified.

Abstract: A development system having a compiler, a linker, and an interface is generated. When the system is (optionally) operating in a "code guarded" mode, the linker links the object modules with a CodeGuard.TM. Library to generate "code guarded" program(s). The API (Application Programming Interface) calls to the runtime libraries are "wrappered" by CodeGuard wrapper functions. Additionally in this mode, operation of the compiler is altered to insert calls from the user code (e.g., compiled user code in object modules) to the CodeGuard Runtime Library, for checking runtime use of resources and memory. As a result, the system can identify a programming error at the location where it occurs that is, at the original line of code which gave rise to the problem in the first place. Errors are found immediately as they happen, so that the original offending site can be determined. In this manner, the task of creating computer programs is simplified.