In typography, “small caps” refer to uppercase (capital) characters used in-lieu of lowercase (small) characters, where these uppercase characters are set at the same height as the lowercase characters.

Small caps are typically used for titles, headlines, column headings, etc. They are also good for any text that you would usually use all capitals. This is because the use of small caps makes the run of capital letters seem less jarring, and would also often require less space than all caps.

While many word processors and text formatting systems include an option to format text in small caps (which leaves uppercase letters as they are but converts lowercase letters to small caps), this is a feature that is lacking in most graphics editing software.

Some fonts have inherent small caps, ie they use smaller capital letters in place of the lowercase characters. These fonts are useful when you wish to use small caps to bring distinction to your designs.

Here are some fonts with inherent small caps:

Continue Reading »

If you are looking to compile SWFs into cross-platform desktop applications, leveraging powerful desktop-only APIs, you may want to consider MDM Zinc 3.0. Available for Windows & Mac OSX, Zinc™ 3.0 is the fastest, most powerful and most feature-rich Rapid Application Development Tool for Adobe® Flash® and Flex®. With Zinc 3.0, you can rapidly create stunning commercial Applications, Screensavers, Widgets, CD Roms, DVD’s, Kiosks and More.

Continue Reading »

The Trial Version of the Aspire UI library has been updated to v1.3.4 and is now available for download at
http://ghostwire.com/aspireui/download/

* The trial version is strictly for evaluation purposes.

* Compiled SWFs will stop working after a few minutes.

* This trial version is based off Aspire UI Standard Edition v1.3.4.

* Includes the assets for “classic”, “graylic” and “xp” themes.

* Aspire UI is an ActionScript 3.0 library – compiled SWFs must target Flash Player 9+.

Continue Reading »

The Aspire UI Components library, for pure ActionScript 3.0 development, now ships with four themes – “classic”, “graylic”, “vista” and “xp”. These themes are included to demonstrate the versatility of the skinning workflow; developers are not limited to these themes but can design their own themes via PNG images.

By default, components in the toolkit uses external PNG images loaded during run-time for component skinning. As of version 1.3, skin assets of the same theme can be compressed and packed into a single binary file, facilitating run-time loading and also making it easy to embed the skin assets if so desired.

As at the time of this post, the sizes of the compressed packed version of the themes are as follows:

Continue Reading »

This post is a supplement to “Serializing Bitmaps (Storing BitmapData As Raw Binary/ByteArray)”. In that article, we looked at how to convert BitmapData to a ByteArray, save that ByteArray, and re-construct the BitmapData from the saved ByteArray.

It is important to note that the technique saves the ByteArray “as is” in a flat binary file without any header or any block of metadata – this means that the file will in itself not be able to communicate its data structure and therefore, proper usage of the data requires prior knowledge of how the data has been packed (we used the first four bytes for storing the value of the width of the image). As a result, that method may be deemed as an “unorthodox” hack and unsuitable in team development.

In this post, we look at how you can employ the same basic idea while making the saved data more “consumable” by other developers.

Continue Reading »

The default behavior of the uiWindow container is to cast a drop shadow when it is active in the foreground, and not do so when it is inactive or when it is maximized to fill the stage. This behavior is determined by the component instance’s background property value.

Continue Reading »

The uiImage class is used to display an image, the source of which can either be a MovieClip symbol in the library, or an external SWF/GIF/JPG/PNG file.

When using external bitmap images (GIF/JPG/PNG), the uiImage class will load from the external source only once and use cached data if the same source is requested subsequently again by the same or other uiImage instances. This is efficient because the same BitmapData is used across different uiImage instances that use the same image source. This is why image icons in Aspire UI scrollable lists do not suffer from the “flickering” symptom (which you will experience when using Flash/Flex components).

Continue Reading »

This post is a supplement to “Saving XML As Binary”. I neglected to mention in that post that you can, if so desired, embed the binary XML within your SWF instead of loading it during run-time. That means you still get to keep the XML externally, not as part of your application code, so that the code and data can still be kept separate and maintained more easily.

However, it must be mentioned that embedding a text XML within SWF will get it compressed as part of the SWF compression anyway. Therefore, if compression is the only motivation, don’t convert the XML to binary and embed the binary version – it does not make sense. But if you wish to do some data encryption, then the additional work may be appropriate.

Continue Reading »

Whenever an application needs to save bitmap images to local storage or post them to a server script, a common practice is to encode the image as JPEG or PNG before sending that binary data off as the respective mimeType. However, if the intention is simply to save the bitmap image, ie to serialize the BitmapData, then converting the image to JPEG/PNG would actually be unnecessary.

Continue Reading »

The previous demo of the new “vista” theme featured mainly the uiWindow component.

Here is another demo featuring various UI components, including the checkbox, radiobutton, tabview, sliders and steppers (this is the same demo included in the library distribution but with the “vista” theme applied):

Continue Reading »