INFORMATION WORKER CREATING COMPONENT APPLICATION WITHOUT WRITING CODE TO CREATE THE APPLICATIONS

1 . A data processing system for data exchange across application boundaries, comprising:

a canvas memory in which to open multiple applications; and

a transform component to generate data structures across the canvas memory in at least one application form and to automatically transform the data structures to at least one other application form to mitigate application boundaries between disparate applications.

2 . The system of claim 1 , the canvas memory functions as a background buffer component in a computer system.

3 . The system of claim 2 , the canvas memory exists inside of at least one application that can be accessed by at least one other application.

4 . The system of claim 1 , further comprising a rules and policies component for manipulating data on the canvas memory.

5 . The system of claim 1 , further comprising a wrapper to exchange data between applications.

6 . The system of claim 1 , further comprising at least one layout type and at least one data type that is associated with the canvas memory.

7 . The system of claim 6 , further comprising a binding component to map layout type and the binding type.

8 . The system of claim 1 , a state component to share state information between an application and the canvas memory.

9 . The system of claim 1 , further comprising a monitor component to automatically determine rules and policies for the canvas memory.

10 . The system of claim 9 , the monitor component includes a learning component to automatically determine the rules and policies for the canvas memory, where learning is associated with native data or an application, or where learning is associated on a canvas that supports pre-fetching based on history.

11 . The system of claim 1 , further comprising one or more links that are embedded regarding the source of data.

12 . The system of claim 11 , further comprising a tool that allows a user to drill down to bring up portions of an application to process a selected data structure.

13 . The system of claim 12 , further comprising a tagging component to indicate where data originated.

14 . The system of claim 13 , further comprising a component to provide multiple data views.

15 . The system of claim 14 , further comprising a component that provides data to a user that is most likely to be the next piece of data needed via pre-fetching user interface.

16 . The system of claim 15 , further comprising a filter component that hides data that is not relevant to a current context.

17 . A method to share data across a common memory, comprising:

providing a memory surface to enable data structures to be placed on the surface;

defining one or more layout types for the data structures;

determining one or more binding rules to associate the layout types with the data structures; and

automatically exchanging data across the memory surface between data structures associated with at least two disparate applications.

18 . The method of claim 17 , further comprising a state component to exchange application states between the at least two disparate applications.

19 . The method of claim 17 , further comprising automatically transforming data to a different form across the memory surface.

20 . A data communications system, comprising:

means for providing a layout of one or more data structures;

means for defining a type for one or more data structures;

means for binding the layout and the type for the one or more data structures; and

means for exchanging data between the data structures, where the data structures are associated with at least two different applications.