The Portable Network Graphics ( png ) image encoding standard was recently designed to be a successor to the popular gif standard. One of the reasons the gif standard still prevails is that many different kinds of software need to display images - drawing programs, document editors, stand-alone image viewers, user interface design tools, web browsers - and each imposes its own packaging requirements on the image-handling component. Creating a png viewing component for each of these niches takes time. Here too is a natural opportunity for Flexible Packaging. We would like to capture the functionality of parsing and displaying a png image once and reuse it in many different contexts.
The second case study involved creating three different components for displaying png images: a Netscape (version 4 ) plug-in; an ActiveX control; and a stand-alone Windows application. As with the previous example, all three programs share an identical ware but use different packagers, generated from UniCon descriptions.