Translating objects between software applications which employ different data formats

• US 7,711,527 B2
• Filed: 01/07/2005
• Issued: 05/04/2010
• Est. Priority Date: 05/14/1998
• Status: Expired due to Fees

• Current Assignee: Autodesk, Inc.
• Original Assignee: Autodesk, Inc.
• Inventors: Hutchinson, John, Sabadell, Stewart
• Primary Examiner(s): Rodriguez; Paul L
• Assistant Examiner(s): Rodriguez; Carlos Ortiz
• Application Number:
  US11/031,115
• Publication Number:
  US 20050131938A1
• Time in Patent Office: 1,943 Days
• Field of Search: 345/672, 345/420, 703/2, 703/7, 703/13, 703/6, 703/23, 707/100, 707/103.R, 709/223, 715/866, 717/105
• US Class Current: 703/2
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A mechanism for translating objects between applications that use different formats is described. As described, a source object is generated using a source application. The source object is then translated to a target object in a target application. The target application having a format that is not supported by the source application. A first modification, which is not supported by the source application, is then performed to the target object. A second modification is also performed to the source object in the source application. Based on the modifications, the target object in the target application is revised to reflect the second modification to the source object without removing the first modification to the target object.

Claims

1. A computer-implemented method for inserting a leaf object associated with a source object generated using a source application executing on a processor into a hierarchical tree structure used for organizing one or more properties of the source object, the method comprising:

reading the source object from a memory, wherein the source object is developed using the source application and is associated with a source object geometry and the one or more source object properties;

generating a compare key object associated with the source object based on a filter object, wherein the filter object is associated with a first source object property, and the compare key object has a first key value equal to a value of the first source object property;

determining that the first key value matches a first collection key value associated with a first collection object in the hierarchical tree structure;

creating the leaf object, wherein the leaf object is linked to the first collection object in the hierarchical tree structure;

translating the source object geometry into a target object geometry, wherein the target object geometry is associated with a target application executing on the processor;

storing the target object geometry in the leaf object; and

storing a first modification to the target object geometry in a modifier stack in the memory, wherein the modifier stack is linked to the first collection object and is developed using the target application,

wherein the format of the target application is not supported by the format of the source application.

2. The method of claim 1, wherein the step of determining that the first key value matches the first collection key value includes determining whether the first collection object linked to a model space collection object and, if so, whether the first collection key associated with the first collection object has been compared to the first key value.

3. The method of claim 1, further comprising the step of determining whether a second collection object having a second collection key is linked to the first collection object and, if so, determining whether the second collection key matches a second key value associated with the compare key object and associated with a second source object property.

4. The method of claim 3, wherein the second collection object is not linked to the first collection object.

5. The method of claim 4, further comprising the step of inserting the second collection object into the hierarchical tree structure, wherein the second collection object is linked to the first collection object and is linked to the leaf object.

6. A computer-readable medium storing instructions that, when executed by a processor, cause the processor to insert a leaf object associated with a source object into a hierarchical tree structure used for organizing one or more properties of the source object, by performing the steps of:

reading the source object, wherein the source object is developed using a source application and is associated with a source object geometry and the one or more source object properties;

generating a compare key object associated with the source object based on a filter object, wherein the filter object is associated with a first source object property, and the compare key object has a first key value equal to a value of the first source object property;

determining that the first key value matches a first collection key value associated with a first collection object in the hierarchical tree structure;

creating the leaf object, wherein the leaf object is linked to the first collection object in the hierarchical tree structure;

translating the source object geometry into a target object geometry, wherein the target object geometry is associated with a target application;

storing the target object geometry in the leaf object; and

storing a first modification to the target object geometry in a modifier stack, wherein the modifier stack is linked to the first collection object and is developed using the target application,

wherein the format of the target application is not supported by the format of the source application.

7. The computer-readable medium of claim 6, wherein the step of determining that the first key value matches the first collection key value includes determining whether the first collection object linked to a model space collection object and, if so, whether the first collection key associated with the first collection object has been compared to the first key value.

8. The computer-readable medium of claim 6, further comprising the step of determining whether a second collection object having a second collection key is linked to the first collection object and, if so, determining whether the second collection key matches a second key value associated with the compare key object and associated with a second source object property.

9. The computer-readable medium of claim 8, wherein the second collection object is not linked to the first collection object.

10. The computer-readable medium of claim 9, further comprising the step of inserting the second collection object into the hierarchical tree structure, wherein the second collection object is linked to the first collection object and is linked to the leaf object.