Abstract: Disclosed are various embodiments of variable transform systems for three-dimensional engines. In some aspects, a custom transform editor interface overrides a user interface included with a 3D engine to enable interactions according to a non-native coordinate system that is different from a native coordinate system of the 3D engine. An initial mesh that specifies a initial vertex positions is intercepted. The initial mesh is modified into a modified mesh with polygons that are aligned to the non-native coordinate system. The custom transform editor interface renders the modified mesh as polygons that are aligned to the non-native coordinate system rather than the native coordinate system of the 3D engine.

Abstract: Disclosed are various embodiments of variable transform systems for three-dimensional engines. In some aspects, transform data is identified for an object. The object is associated with a base transform class of a three-dimensional engine. A variable transform class generates global transform data using the transform data. The global transform data is expressed according to a cartesian coordinate system used by the three-dimensional engine. The variable transform class provides the global transform data to the base transform class of the three-dimensional engine to position the object in world space.

Abstract: Disclosed are various embodiments of variable transform systems for three-dimensional engines. In some aspects, transform data is identified for an object. The object is associated with a base transform class of a three-dimensional engine. A variable transform class generates global transform data using the transform data. The global transform data is expressed according to a cartesian coordinate system used by the three-dimensional engine. The variable transform class provides the global transform data to the base transform class of the three-dimensional engine to position the object in world space.

Abstract: A workflow is expressed as an arrangement of a set of executable tiles. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tile. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tile. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tile. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tile. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tiles. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tile. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: A workflow is expressed as an arrangement of a set of executable tile. In some embodiments, the tiles include operations expressed in different programming languages. A tile can include a declarative specification of datatypes so that external agents, e.g., workflow services, can identify the datatypes and schemas required as arguments and produced as result; this simplifies the defining of a workflow, e.g., by a workflow coder. A tile can have zero, one, or plural user interfaces; selection of a user interface from plural user interfaces can be based on a user selection, on user roles, or on tile lifecycle stage. Workflow services can communicate with each other so that workflows can be distributed and shifted among processor nodes.

Abstract: The current document is directed to cloud-based cloud-management systems and subsystem components of the management systems that store, retrieve, use, and manipulate artifacts. In the described implementations, artifacts are represented by artifact descriptors, referred to as “artifact specs,” which are instantiated, at run time, as corresponding artifact models. The artifact models include full descriptions of the artifacts as well as references to locally stored instances of the artifacts that can be used to access the artifacts. In the case of automated-application-release-management subsystems, artifacts include executables, program code, files containing input and/or output data, and other stored data used in provisioning virtual machines, deploying application executables, testing application executables, and carrying out other subtasks of application development, testing, and release.

Abstract: Methods and systems for processing graphical data received at a computing system from a remote source are described. One method includes decoding received graphical content, the received graphical content including an image being compressed using a plurality of codecs, wherein decoding the received graphical content includes creating a decoded image. The method also includes, based on quality of the received graphical content, selecting from among a plurality of filters to apply to the decoded image. The method further includes applying a plurality of filters to at least a portion of the decoded image.

Abstract: Methods and systems for processing graphical data received at a computing system from a remote source are described. One method includes decoding received graphical content, the received graphical content including an image being compressed using a plurality of codecs, wherein decoding the received graphical content includes creating a decoded image. The method also includes, based on quality of the received graphical content, selecting from among a plurality of filters to apply to the decoded image. The method further includes applying a plurality of filters to at least a portion of the decoded image.