Component based design time architecture

• US 20050160400A1
• Filed: 03/09/2005
• Published: 07/21/2005
• Est. Priority Date: 02/20/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Pepin, Brian K.
• Granted Patent: US 7,676,787 B2
• Time in Patent Office: Days
• US Class Current: 717/107
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/41 Compilation

Abstract

The invention includes an architecture in which components associate their design time functionality independent of a design tool. The design time functionality includes code generators, compilers, parsers and editors. The architecture includes interfaces for components and designers to communicate. The architecture includes attributes in metadata that describe the functionality associated with the instance of a component.

Claims

1. An application development architecture, comprising:

at least one component;

at least one designer associated with the at least one component; and

a design tool that populates itself with the at least one designer associated with the at least one component.

2. The architecture of claim 1, wherein the designer provides design time functionality to its associated component.

3. The architecture of claim 2, wherein the design time functionality includes at least one of a code generator, a compiler, a parser and an editor.

4. The architecture of claim 1, wherein the component and the designer are associated via metadata.

5. The architecture of claim 1, wherein the component provides information to identify the component'"'"'s associated designer.

6. The architecture of claim 1, wherein the component dynamically alters an association of its associated designer.

7. The architecture of claim 1, wherein the component provides a plurality of associated designers.

8. The architecture of claim 7, wherein a developer selectively determines which of the plurality of associated designers to associate with an instance of the component.

9. The architecture of claim 1, wherein the design tool provides an interface to facilitate communication between the designer, the component and the design tool.

10. An application development architecture, comprising:

a design tool that populates itself with a designer associated with a component; and

a designer host interface that creates an instance of the component and creates an instance of the designer associated with the component.

11. The architecture of claim 10, wherein the designer host interface destroys the instance of the component and destroys the instance of the designer associated with the component.

12. The architecture of claim 10, wherein the designer filters information before it is received by its associated component.

13. The architecture of claim 10, wherein the designer and the component are provided separately from each other.

14. The architecture of claim 10, wherein the designer host interface provides utility tasks to the designer and the component.

15. The architecture of claim 14, wherein the utility tasks include at least one of editing, parsing of source code of a text file, compiling, code generating, memory management and disk transfers.

16. The architecture of claim 10, further comprising a selection service to facilitate communication among a plurality of selected objects.

17. The architecture of claim 16, wherein the plurality of selected objects is at least one of the component, the designer and the designer host interface.

18. The architecture of claim 10, wherein the design tool provides an interface to facilitate communication between the designer and the design tool.

19. In a component based environment, a method for developing an application, comprising:

loading a designer host interface;

obtaining a request from a developer for a component;

loading the component;

identifying a designer associated with the component;

loading a designer associated with the component;

initializing the designer;

manipulating information received by the component; and

invoking the designer host interface to coordinate utility tasks requested by at least one of the component and the designer.

20. The method of claim 19, wherein the designer host interface provides at least one of a parser, a compiler, a code generator and an editor.