Abstract: Techniques to performing sub-configuration of components of an entity. In one method, the entity is configured via a parent model and each sub-configurable component is configured via one of a number of sub-models. Initially a selection to configure a particular sub-configurable component of the entity is received, and a sub-model for the selected component is identified. One or more values for one or more features of the selected component are received (e.g., from the parent model or via the sub-model) and form a configuration for the component, which is then validated based on the associated sub-model and the received values. Configuration of the entity is also validated based on the parent model and the validated configuration for the selected component. Feedbacks may be provided for each configuration of the parent model and sub-models. The data for the parent model and sub-models may be localized or globalized.

Abstract: Techniques to performing sub-configuration of components of an entity. In one method, the entity is configured via a parent model and each sub-configurable component is configured via one of a number of sub-models. Initially a selection to configure a particular sub-configurable component of the entity is received, and a sub-model for the selected component is identified. One or more values for one or more features of the selected component are received (e.g., from the parent model or via the sub-model) and form a configuration for the component, which is then validated based on the associated sub-model and the received values. Configuration of the entity is also validated based on the parent model and the validated configuration for the selected component. Feedbacks may be provided for each configuration of the parent model and sub-models. The data for the parent model and sub-models may be localized or globalized.

Abstract: Techniques to support user interaction in a browser environment, “capture” certain user actions, and perform appropriate defined actions. In a first scheme, “setup” pages are used to detect user actions. Each setup page is associated with a respective script that is executed when the page is activated (e.g., via a Back or Forward button). The script performs the defined actions to obtain the proper behavior for dependent pages. The scripts for the setup pages keep track of the state of these pages, and further maintain a local history stack for the URLs of the dependent pages. In a second scheme, each dependent page includes a hidden history frame having a script that performs a set of defined actions for the page. The script further keeps track of whether or not the dependent page has been loaded previously.

Abstract: Techniques to support user interaction in a browser environment, “capture” certain user actions, and perform appropriate defined actions. In a first scheme, “setup” pages are used to detect user actions. Each setup page is associated with a respective script that is executed when the page is activated (e.g., via a Back or Forward button). The script performs the defined actions to obtain the proper behavior for dependent pages. The scripts for the setup pages keep track of the state of these pages, and further maintain a local history stack for the URLs of the dependent pages. In a second scheme, each dependent page includes a hidden history frame having a script that performs a set of defined actions for the page. The script further keeps track of whether or not the dependent page has been loaded previously.