Abstract: Methods and systems for creating a webpage having different element orders for different webpage widths are disclosed. A computing device receives inputs specifying different layouts of elements in different orders for different webpage widths. The computing device creates markup code for the webpage that specifies separate subtrees of nodes for the different layouts and then modifies the markup code to replace duplicate nodes with placeholders in the subtrees. The computing device also creates script code for the webpage with instructions for modifying a live DOM created from the markup code based on current webpage width. Specifically, the script code modifies the live DOM to specify positioning the elements differently for different webpage widths by changing the visibility of nodes and swapping placehoders and content nodes in the subtrees.

Abstract: Methods and systems for creating a webpage having different element orders for different webpage widths are disclosed. A computing device receives inputs specifying different layouts of elements in different orders for different webpage widths. The computing device creates markup code for the webpage that specifies separate subtrees of nodes for the different layouts and then modifies the markup code to replace duplicate nodes with placeholders in the subtrees. The computing device also creates script code for the webpage with instructions for modifying a live DOM created from the markup code based on current webpage width. Specifically, the script code modifies the live DOM to specify positioning the elements differently for different webpage widths by changing the visibility of nodes and swapping placehoders and content nodes in the subtrees.

Abstract: A breadcrumb path for use in navigating a hierarchical data set may be supplemented with one or more supplemental breadcrumbs representing preferred locations within the hierarchical data set. The supplemental breadcrumb may represent a previously visited location within the hierarchical data set, and may be further limited to the previously visited locations that are subordinate to the currently selected location. The supplemental breadcrumb may also represent a frequently visited location within the hierarchical data set. For scoped hierarchical data sets, the preferred location may represent a previously visited location within the scope of the selected location, or a frequently visited location within the scope of the selected location. Several embodiments of user interface components featuring such supplemented breadcrumb lists and having various advantages are presented, as well as a few contexts for applying such supplemental breadcrumbs in a breadcrumb list.

Abstract: A brake mechanism (10) for an elevator (2) is activated in response to an electronic control signal to prevent movement of an elevator car (16) under predetermined conditions. The brake mechanism is preferably a safety mechanism (10) and does not require a governor sheave, a governor rope, or a tension sheave. The safety mechanism in one disclosed example utilizes a solenoid actuator (22b) and an electric motor (40) and gear box assembly (42) to move safety wedges (18) into engagement with a guide rail (20) to stop the elevator car (16). The safety wedges (18) are held in a non-deployed position during normal elevator operation. If there is a power loss or if elevator car speed exceeds a predetermined threshold, an electronic control signal activates the safety mechanism (10) causing the solenoid to release, which causes the safety wedges (18) move in a direction opposite to that of a safety housing (12) mounted for movement with the elevator car (16).

Abstract: One or more hierarchical scopes may be applied to various portions of a hierarchical data set to represent a logical grouping of various nodes in the hierarchy. Various user interfaces may be devised to navigate within such a scoped hierarchical data set, such as a scoped treeview that limits the viewed portion of the tree to the hierarchical scope and/or a scoped breadcrumb list containing an aggregated breadcrumb for the nodes sharing a scope to condense the breadcrumb list. Several embodiments of user interface components featuring such scoped treeviews and/or scoped breadcrumb lists and having various advantages are presented, as well as a few contexts for applying such scoped treeviews and/or scoped breadcrumb lists.

Abstract: A breadcrumb path for use in navigating a hierarchical data set may be supplemented with one or more supplemental breadcrumbs representing preferred locations within the hierarchical data set. The supplemental breadcrumb may represent a previously visited location within the hierarchical data set, and may be further limited to the previously visited locations that are subordinate to the currently selected location. The supplemental breadcrumb may also represent a frequently visited location within the hierarchical data set. For scoped hierarchical data sets, the preferred location may represent a previously visited location within the scope of the selected location, or a frequently visited location within the scope of the selected location. Several embodiments of user interface components featuring such supplemented breadcrumb lists and having various advantages are presented, as well as a few contexts for applying such supplemental breadcrumbs in a breadcrumb list.

Abstract: An editing application may allow a user to change a literal property value of an object in a conventional manner. The functionality of the editing application may be expanded to allow a user to access non-literal values for property values, by allowing the user to define a calculation based on one or more sources. To indicate that an associated property value of an object is a non-literal value, a non-literal cue may be presented to the user, such as through the display of the object, the associated property indicator, and/or the associated property value. To reduce the learning curve of the expanded functionality, the user interface for literal values of a property may remain minimally impacted, while, alternative gestures associated with the object, property indicator, and/or property value may be used to allow access to the non-literal value controls or information.

Abstract: A brake mechanism (10) for an elevator (2) is activated in response to an electronic control signal to prevent movement of an elevator car (16) under predetermined conditions. The brake mechanism is preferably a safety mechanism (10) and does not require a governor sheave, a governor rope, or a tension sheave. The safety mechanism in one disclosed example utilizes a solenoid actuator (22b) and an electric motor (40) and gear box assembly (42) to move safety wedges (18) into engagement with a guide rail (20) to stop the elevator car (16). The safety wedges (18) are held in a non-deployed position during normal elevator operation. If there is a power loss or if elevator car speed exceeds a predetermined threshold, an electronic control signal activates the safety mechanism (10) causing the solenoid to release, which causes the safety wedges (18) move in a direction opposite to that of a safety housing (12) mounted for movement with the elevator car (16).