Patents by Inventor Jack Greenfield
Jack Greenfield has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Publication number: 20050203960Abstract: The present invention provides systems and methods that synchronize modifications between electronic data and one or more associated data representations. Synchronization comprises translating modification made to the data or a representation to the representations or the data and other representations. A mapping engine is employed to facilitate modification translation, wherein the mapping engine utilizes data-representation relationships, which declaratively described the relationship between data and respective representations. Such relationships can be stored in markup language (e.g., xml) or as a memory string, for example. Modifications can be translated via a continuous technique, wherein translation occurs upon transaction commitment or via an explicit technique, wherein translation occurs upon an explicit request.Type: ApplicationFiled: March 9, 2004Publication date: September 15, 2005Inventors: Carlos Suarez, Niall McDonnell, Jack Greenfield, Ian Bavey, Jing Fan
-
Publication number: 20050114863Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: ApplicationFiled: September 28, 2004Publication date: May 26, 2005Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20050034132Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven t yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves. This delayed resolution of relationships occurs in two stages: the creation of a placeholder object for the data to be fetched,. and the fetching of that data only when it's needed.Type: ApplicationFiled: September 5, 2002Publication date: February 10, 2005Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 6820268Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: GrantFiled: August 29, 2002Date of Patent: November 16, 2004Assignee: NeXT Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 6704744Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: GrantFiled: September 18, 2000Date of Patent: March 9, 2004Assignee: NeXT Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20030212705Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: ApplicationFiled: March 5, 2003Publication date: November 13, 2003Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Danlel Willhite
-
Patent number: 6513072Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: GrantFiled: October 30, 2000Date of Patent: January 28, 2003Assignee: Next Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20020199029Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: ApplicationFiled: August 29, 2002Publication date: December 26, 2002Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 6466992Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: GrantFiled: February 2, 2001Date of Patent: October 15, 2002Assignee: Next Computer, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Publication number: 20010052032Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: ApplicationFiled: February 2, 2001Publication date: December 13, 2001Applicant: NEXT SOFTWARE, INC.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 6223227Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: GrantFiled: April 9, 1997Date of Patent: April 24, 2001Assignee: NeXT Software, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 6154786Abstract: The present invention comprises a method for allowing a controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a controlling object, regardless of the kind of user interface object with which the association object is associated.Type: GrantFiled: September 29, 1997Date of Patent: November 28, 2000Assignee: NeXT Software, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 6122641Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: GrantFiled: February 12, 1999Date of Patent: September 19, 2000Assignee: NeXT Software, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 5898871Abstract: The present invention provides a uniform method for dynamically determining an object's communication requirements. The invention provides the ability to determine the requirements for communicating with an object regardless of the object's implementation (i.e., whether keys were implemented as methods or instance variables). The invention is used in conjunction with the runtime description of an object to provide a technique for communicating with an object. The present invention uses "key-value coding" to represent data. Key-value coding uses a dictionary of key-value pairs to represent a property and a value of the property. For example, a data value, "Joe" stored in a column of a database table that contains employees' first names is represented in a key-value pair as: Key="firstName", Value="Joe". The property of the key in this key-value pair is "firstName". The method for loading data into an object is "takeValuesFromDictionary".Type: GrantFiled: May 27, 1997Date of Patent: April 27, 1999Assignee: NeXT Software, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 5873093Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: GrantFiled: May 28, 1997Date of Patent: February 16, 1999Assignee: NeXT Software, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 5709110Abstract: A security system (28) for a lap-top computer (30) with a monitor housing (32) hinged thereto. The system (28) comprises a low profile mounting plate (34). A component (36) is for affixing the low profile mounting plate (34) to the monitor housing (32). An elongated flexible retainment cable (38) is provided. A first assembly (40) is for locking in a swiveled manner, a first end of the cable (38) to a table/counter top (41). A second assembly (42) is for locking in a universal articulated manner a second end of the cable (38) to the low profile mounting plate (34). The monitor housing (32) of the lap-top computer (30) can be moved from a closed position to a vertical opened position, without interference from the cable (38) for full freedom of movement and positioning thereof.Type: GrantFiled: October 7, 1996Date of Patent: January 20, 1998Inventors: Jack Greenfield, David Monoson
-
Patent number: 5076079Abstract: An equipment housing is secured against removal from a clamping assembly which embraces two opposing sides of the equipment housing. Plates are affixed to said opposite sides of the housing by an adhesive means arranged in a unique manner to rely upon its shear strength to prevent unauthorized removal of the equipment or housing or both. The various types of adhesives which may be used in connection with this shear strength locking device may include single part adhesives which consist of liquids of various viscosity, as well as amorphous materials, films and layered films which include various types of double-sided tapes. Another category of adhesives is the multipart material which may consist of two-part epoxies or two-part acrylics. For the most part, high-tack adhesives, which cure at normal room temperatures, are the preferred material.Cyanoacrylates and similar matrials may be used where rapid cure and adhesion of dissimilar parts is required.Type: GrantFiled: January 22, 1990Date of Patent: December 31, 1991Inventors: David B. Monoson, Jack Greenfield