Composite values for declarative language applications
First Claim
1. In a declarative application with composites organized hierarchically, including composites in the same hierarchy, but not directly related by direct intervening child/parent relationships, a method executable by a processor of providing a link between composites unrelated by direct intervening child/parent relationships, the method comprising:
- rendering data at a user interface, the data being associated with a first composite in the declarative application;
detecting, at the user interface, user interaction with the rendered data,as a result of detecting user interaction with the rendered data, defining a composite path to the first composite;
providing the path as a local variable to a second composite such that the second composite can interact with the data;
wherein the second composite is in the same declarative application hierarchy as the first composite but is not related to the first composite by any direct intervening child/parent relationships such that the first and second composites are in different sub-trees of the same hierarchical declarative application;
registering dependencies on the composite path with a listener, by registering a configuration builder with the listener;
receiving at the configuration builder a notification from the listener that dependencies in the path have changed; and
as a result of dependencies in the composite path changing, updating the observed value of the path.
2 Assignments
0 Petitions
Accused Products
Abstract
One embodiment is directed to a method that may be practiced in a declarative application with composites organized hierarchically, including composites in the same hierarchy, but not directly related by direct intervening child/parent relationships. The method includes acts for providing a link between composites unrelated by direct intervening child/parent relationships. The method includes rendering data at a user interface. The data is associated with a first composite in a declarative application. The method further includes detecting, at the user interface, user interaction with the rendered data. As a result of detecting user interaction with the rendered data, the method further includes defining a composite path to the first composite. The method further includes providing the name of the path as a local variable to a second composite such that the second composite can interact with the data.
20 Citations
18 Claims
-
1. In a declarative application with composites organized hierarchically, including composites in the same hierarchy, but not directly related by direct intervening child/parent relationships, a method executable by a processor of providing a link between composites unrelated by direct intervening child/parent relationships, the method comprising:
-
rendering data at a user interface, the data being associated with a first composite in the declarative application; detecting, at the user interface, user interaction with the rendered data, as a result of detecting user interaction with the rendered data, defining a composite path to the first composite; providing the path as a local variable to a second composite such that the second composite can interact with the data; wherein the second composite is in the same declarative application hierarchy as the first composite but is not related to the first composite by any direct intervening child/parent relationships such that the first and second composites are in different sub-trees of the same hierarchical declarative application; registering dependencies on the composite path with a listener, by registering a configuration builder with the listener; receiving at the configuration builder a notification from the listener that dependencies in the path have changed; and as a result of dependencies in the composite path changing, updating the observed value of the path. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. In a declarative application with composites organized hierarchically, including composites in the same hierarchy, but not directly related by direct intervening child/parent relationships, a method executable by a processor of using a link between composites unrelated by direct intervening child/parent relationships, the method comprising:
-
accessing a first composite that can interact with data; evaluating a local variable at the first composite, the local variable comprising a composite path to a second composite, and to data associated with the second composite, the data associated with the second composite being the data that can be interacted with by the first composite, wherein the second composite is in the same declarative application hierarchy as the first composite but is not related to the first composite by any direct intervening child/parent relationships, using the first composite, interacting with the data associated with the second composite; registering dependencies on the composite path with a listener, by registering the dereference configuration builder with the listener; receiving, at the dereference configuration builder, a notification from the listener that dependencies in the path have changed; and as a result of dependencies in the composite path changing, updating the observed value of the path. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15)
-
-
16. In a declarative application with composites organized hierarchically, including composites in the same hierarchy, but not directly related by direct intervening child/parent relationships, a computer program product comprising a computer readable memory comprising computer executable instructions that when executed by a processor cause the following to be performed:
-
rendering data at a user interface, the data being associated with a first composite in the declarative application, wherein the first composite includes functionality including an interface which allows other agents to query the first composite, using a primary return value of the first composite, about objects in the composite; detecting, at the user interface, user interaction with the rendered data, as a result of detecting user interaction with the rendered data, defining a composite path to the first composite; providing the path as a local variable to a second composite such that the second composite can interact with the data; wherein the second composite is in the same declarative application hierarchy as the first composite but is not related to the first composite by any direct intervening child/parent relationships such that the first and second composites are in different axis of the same hierarchical declarative application; registering dependencies on the composite path with a listener, by registering the dereference configuration builder with the listener; receiving, at the dereference configuration builder, a notification from the listener that dependencies in the path have changed; and as a result of dependencies in the composite path changing, updating the observed value of the path. - View Dependent Claims (17, 18)
-
Specification