Abstract: An example non-transitory machine-readable storage medium includes instructions to analyze a unit of real property to facilitate generation of a scope of work for working the unit of real property. When executed, the instructions cause a processor of a computing device to obtain real property data describing the unit of real property, identify a workable feature of the unit of real property based on the real property data, determine a quantitative factor describing the workable feature, and provide an indication of the workable feature and the quantitative factor to another computer device. A consumer user interface and a provider user interface are described.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to place client-side validation rules on user interface components using a desktop integration framework. The validation rules can be tied to translatable resources or model metadata. In one aspect, the validation rules metadata is provided separately from the document to which the validation rules will eventually be tied.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to place tooltips on components and columns headers using a desktop integration framework. The tooltips can be tied to translatable resources or model metadata. In one aspect, the tool tip metadata is provided separately from the document to which the tool tip will eventually be tied.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers working within desktop applications to create application-specific documents that integrate with web-based applications. Using a desktop integration framework, a developer can design documents having components that provide user interfaces to data associated with data models of the web-based applications. In one aspect, how a component looks and is configured can be dynamically driven at runtime based on metadata of its underlying data model.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to place tooltips on components and columns headers using a desktop integration framework. The tooltips can be tied to translatable resources or model metadata. In one aspect, the tool tip metadata is provided separately from the document to which the tool tip will eventually be tied.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to place tooltips on components and columns headers using a desktop integration framework. The tooltips can be tied to translatable resources or model metadata. In one aspect, the tool tip metadata is provided separately from the document to which the tool tip will eventually be tied.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to place client-side validation rules on user interface components using a desktop integration framework. The validation rules can be tied to translatable resources or model metadata. In one aspect, the validation rules metadata is provided separately from the document to which the validation rules will eventually be tied.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers to place tooltips on components and columns headers using a desktop integration framework. The tooltips can be tied to translatable resources or model metadata. In one aspect, the tool tip metadata is provided separately from the document to which the tool tip will eventually be tied.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow developers working within desktop applications to create application-specific documents that integrate with web-based applications. Using a desktop integration framework, a developer can design documents having components that provide user interfaces to data associated with data models of the web-based applications. In one aspect, how a component looks and is configured can be dynamically driven at runtime based on metadata of its underlying data model.