Abstract: A lighting apparatus includes an anchored base comprising a bollard configured to slide onto an anchor plate and a first extrusion configured to mate the bollard with the anchor plate at a bottom end of the bollard, a cap attachment comprising a second extrusion configured to mate with the bollard at a top end of the bollard, a fixture head comprising a third extrusion disposed on an LED optical chamber and a front cap, wherein the third extrusion is configured to mate with the front cap, and a first fixture head attachment disposed on an exterior surface of the bollard at a top end, wherein the first fixture head attachment includes a fourth extrusion configured to mate with the fixture head and operatively connect the fixture head with the anchored base, wherein the first, second, third, and fourth extrusions are configured to respectively mate at four regions of contact to flushly visually obscure one or more screws.

Abstract: A lighting apparatus includes an anchored base comprising a bollard configured to slide onto an anchor plate and a first extrusion configured to mate the bollard with the anchor plate at a bottom end of the bollard, a cap attachment comprising a second extrusion configured to mate with the bollard at a top end of the bollard, a fixture head comprising a third extrusion disposed on an LED optical chamber and a front cap, wherein the third extrusion is configured to mate with the front cap, and a first fixture head attachment disposed on an exterior surface of the bollard at a top end, wherein the first fixture head attachment includes a fourth extrusion configured to mate with the fixture head and operatively connect the fixture head with the anchored base, wherein the first, second, third, and fourth extrusions are configured to respectively mate at four regions of contact to flushly visually obscure one or more screws.

Abstract: Examples are disclosed herein that relate to sharing of depth-referenced markup in image data. One example provides, on a computing device, a method comprising receiving image data of a real world scene and depth data of the real world scene. The method further includes displaying the image data, receiving an input of a markup to the image data, and associating the markup with a three-dimensional location in the real world scene based on the depth data. The method further comprises sending the markup and the three-dimensional location associated with the markup to another device.

Abstract: A data provider application programming interface (API) is configured for use with a game content editing application. An asset relationship management file, which is generated with the data provider API, includes information such as relationship references and annotations and is updated by the data provider API when a digital asset is edited. The asset relationship management file is then stored in a data store. An asset relationship graph is generated, based on the asset relationship management file in the data store. The asset relationship graph includes asset graph nodes that map dependency relationships between asset files. A graph API is also described. The graph API is configured for accessing the relationship graph through a server process to expose dependency relationships and annotations to a client process, such as an application. Thus, the effect of changes to one asset on other assets can readily be evaluated.

Abstract: A data provider application programming interface (API) is configured for use with a game content editing application. An asset relationship management file, which is generated with the data provider API, includes information such as relationship references and annotations and is updated by the data provider API when a digital asset is edited. The asset relationship management file is then stored in a data store. An asset relationship graph is generated, based on the asset relationship management file in the data store. The asset relationship graph includes asset graph nodes that map dependency relationships between asset files. A graph API is also described. The graph API is configured for accessing the relationship graph through a server process to expose dependency relationships and annotations to a client process, such as an application. Thus, the effect of changes to one asset on other assets can readily be evaluated.

Abstract: Methods, systems, and software products are described that display relationships between game assets in a game development environment. In one implementation, a selection of a particular game asset is received, and a selection of a particular type of relationship is received to display for the selected game asset. The type of relationship may be a parent relationship, a child relationship, a category relationship, etc. Other game assets are then identified that have the selected relationship with the selected game asset. The other game assets that are identified are displayed to a user.