User interface framework
View Patent ↗Systems, methods and computer readable media for user interface frameworks are disclosed. In some implementations, the method can include detecting, at a dispatcher within a user interface framework, an event emitted from a user interface element contained within a document object model node associated with a controller. The method can also include requesting a module associated with the controller and instantiating the controller. The method can further include providing the event to the controller.
1. A method comprising:
detecting, at a dispatcher within a user interface framework, an event emitted from a user interface element contained within a document object model node associated with a controller, wherein the document object model node includes an attribute defining a module and specifying that the module be loaded prior to instantiating the controller;
requesting the module associated with the controller;
instantiating the controller, wherein instantiating the controller includes automatically constructing the controller in response to a first occurrence of the event; and
providing the event to the controller.
2. The method of claim 1 , wherein the controller is associated with the document object model node via a declaration in a mark-up language portion of document model object code containing the node.
3. The method of claim 1 , further comprising specifying the controller as optional, wherein when the controller is specified as optional and cannot be located by the user interface framework, the user interface framework does not raise an error based on the controller not being found.
4. The method of claim 1 , wherein the controller can include one or more arguments passed to the controller when it is called, the arguments including one or more of:
a statement in a declaration of the controller within code declaring the document object model node;
a shared object within a data model accessible by controllers within the document object model; and
a context.
5. The method of claim 1 , wherein an instance of the controller is cached in a root node of the controller.
6. The method of claim 1 , further comprising removing an instance of the controller when the document object model node is destroyed.
7. The method of claim 1 , wherein the controller is declared in a template using a mark-up language or scripting language attribute.
8. A system comprising:
one or more processors configured to perform operations including:
detecting, at a dispatcher within a user interface framework, an event emitted from a user interface element contained within a document object model node associated with a controller, wherein the document object model node includes an attribute defining a module and specifying that the module be loaded prior to instantiating the controller;
requesting the module associated with the controller;
instantiating the controller, wherein instantiating the controller includes automatically constructing the controller in response to a first occurrence of the event; and
providing the event to the controller.
9. The system of claim 8 , wherein the controller is associated with the document object model node via a declaration in a mark-up language portion of document model object code containing the node.
10. The system of claim 8 , wherein the operations further comprise specifying the controller as optional, wherein when the controller is specified as optional and cannot be located by the user interface framework, the user interface framework does not raise an error based on the controller not being found.
11. The system of claim 8 , wherein the controller can include one or more arguments passed to the controller when it is called, the arguments including one or more of:
a statement in a declaration of the controller within code declaring the document object model node;
a shared object within a data model accessible by controllers within the document object model; and
a context.
12. The system of claim 8 , wherein the operations further comprise removing a controller instance when the document object model node is destroyed.
13. The system of claim 8 , wherein the controller is declared in a template using a mark-up language or scripting language attribute.
14. A nontransitory computer readable medium having software instructions stored thereon that, when executed by a processor, cause the processor to perform operations comprising:
detecting, at a dispatcher within a user interface framework, an event emitted from a user interface element contained within a document object model node associated with a controller, wherein the document object model node includes an attribute defining a module and specifying that the module be loaded prior to instantiating the controller;
requesting the module associated with the controller;
instantiating the controller, wherein instantiating the controller includes automatically constructing the controller in response to a first occurrence of the event; and
providing the event to the controller.
15. The nontransitory computer readable medium of claim 14 , wherein the controller is associated with the document object model node via a declaration in a mark-up language portion of document model object code containing the node.
16. The nontransitory computer readable medium of claim 14 , wherein the operations further comprise removing an instance of the controller when the document object model node is destroyed.
17. The nontransitory computer readable medium of claim 14 , wherein the controller is declared in a template using a mark-up language or scripting language attribute.