One of the conveniences of CSS is that you easily can set a style for all views of a certain type. However, there are times when you wish to style all of a given element type except for certain instances. The :not pseudo-class can be used to handle this scenario. This article discusses :not and how it can be used to prevent the styling of views and their children.
CSS provides a number of ways of defining colors. The Pixate Engine supports these CSS syntaxes and provides extensions to them. The Engine even provides a way to extend colors with user-defined names and values. This article discusses the supported color syntaxes and the color extensions provided by the Pixate Engine.
With the introduction of retina displays, it became necessary for iOS developers to create multiple versions of image assets: one for retina displays and another for non-retina displays. Pixate allows you to return to using single files via its support for SVG images; however, there are times when you simply have to use images. This article briefly discusses the Pixate Engine's support for 2x images and how that relates to URL fallback.
This article discusses custom schemes added by the Pixate Engine that can be used in your styling URLs. These schemes allow you to specify files independently of where you run your app: on the Simulator or on device. Additionally, URLs without a scheme activate a fallback mechanism that can be useful for changing content in an application, even after it has been deployed.
iOS comes with a rich selection of default fonts; however, typography, being an important aspect of design, oftentimes requires the use of fonts outside of the iOS defaults. Fortunately, it's fairly straight forward to include new fonts in your application. This post goes into those details along with a discussion of the CSS used to select an included font and its variants.