3D PLM Enterprise Architecture |
User Interface - Frame |
Creating a Product Line Visual IdentityDifferentiating your own product line from others |
Use Case |
AbstractA product line should be easily recognized from others using some visual features discerningly chosen, such as its launching icon or splash screen. This article shows you how to implement the visual identity components for your product line. |
This use case is intended to show you how to create a load module to launch the application and how to create the visual identity resources [1] for a fictitious product line named CAAProductLine.
[Top]
CAAAfrProductLine is a use case of the CAAApplicationFrame.edu framework that illustrates the ApplicationFrame framework capabilities.
[Top]
The CAAAfrProductLine use case creates the load module that launches the product line application CAAProductLine, and includes all the resources to customize this product line visual identity.
[Top]
To launch CAAAfrProductLine, you will need to set up the build time environment, then compile CAAAfrProductLine along with its prerequisites, set up the run time environment, and then execute the use case [2].
Do not type the module name on the command line, but type the product name.
[Top]
The CAAAfrProductLine use case is made of a single source file named CAAAfrProductLine.cpp located in the CAAAfrProductLine.m module of the CAAApplicationFrame.edu framework:
Windows | InstallRootDirectory\CAAApplicationFrame.edu\CAAAfrProductLine.m\ |
Unix | InstallRootDirectory/CAAApplicationFrame.edu/CAAAfrProductLine.m/ |
where InstallRootDirectory
is the directory where the CAA CD-ROM
is installed.
With Windows, other files are needed to launch the application from a desktop shortcut. These files are also located in CAAAfrProductLine.m.
[Top]
Creating the visual identity components is divided into the following steps:
Assume the product line is named CAAProductLine.
[Top]
To create this main program, you should first create its module directory, such as CAAAfrProductLine.m. This module directory should contain:
# # LOAD MODULE FOR CAAAfrProductLine # BUILT_OBJECT_TYPE=LOAD MODULE # LINK_WITH=CATApplicationFrame JS0FM JS0GROUP |
#include "CNext.h" CNext Product ("CAAProductLine"); |
You can choose to import an existing bit map file. Click Import and select this file.You can also choose to draw the icon. Click New, and the Graphics and Colors toolbars are displayed
When the icon is created, use Save As to save the icon in the src directory of your module. Microsoft Developer Studio has also created two files:
//Microsoft Developer Studio generated resource script. // #include "resource.h" #define APSTUDIO_READONLY_SYMBOLS ///////////////////////////////////////////////////////////////////////////// // // Generated from the TEXTINCLUDE 2 resource. // #include "afxres.h" ///////////////////////////////////////////////////////////////////////////// #undef APSTUDIO_READONLY_SYMBOLS ///////////////////////////////////////////////////////////////////////////// // English (U.S.) resources #if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU) #ifdef _WIN32 LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US #pragma code_page(1252) #endif //_WIN32 ///////////////////////////////////////////////////////////////////////////// // // Icon // // Icon with lowest ID value placed first to ensure application icon // remains consistent on all systems. IDI_ICON1 ICON DISCARDABLE "icon1.ico" // Add this line to have the icon on the desktop and by-pass a Windows bug IDI_ICON2 ICON DISCARDABLE "icon1.ico" #ifdef APSTUDIO_INVOKED ///////////////////////////////////////////////////////////////////////////// // // TEXTINCLUDE // 1 TEXTINCLUDE DISCARDABLE BEGIN "resource.h\0" END 2 TEXTINCLUDE DISCARDABLE BEGIN "#include ""afxres.h""\r\n" "\0" END 3 TEXTINCLUDE DISCARDABLE BEGIN "\r\n" "\0" END #endif // APSTUDIO_INVOKED #endif // English (U.S.) resources ///////////////////////////////////////////////////////////////////////////// #ifndef APSTUDIO_INVOKED ///////////////////////////////////////////////////////////////////////////// // // Generated from the TEXTINCLUDE 3 resource. // ///////////////////////////////////////////////////////////////////////////// #endif // not APSTUDIO_INVOKED |
//{{NO_DEPENDENCIES}} // Microsoft Developer Studio generated include file. // Used by Script1.rc // #define IDI_ICON1 101 // Next default values for new objects // #ifdef APSTUDIO_INVOKED #ifndef APSTUDIO_READONLY_SYMBOLS #define _APS_NEXT_RESOURCE_VALUE 102 #define _APS_NEXT_COMMAND_VALUE 40001 #define _APS_NEXT_CONTROL_VALUE 1000 #define _APS_NEXT_SYMED_VALUE 101 #endif #endif |
Move the resource.h file to the LocalInterfaces directory, and build the module file using mkmk -u.
[Top]
The graphic resources to provide should be copied into the CNext\resources\graphic directory or in its subdirectories of the framework used. They are:
For Windows with P1 look: CAALogoP1NT.bmp | ![]() |
For Windows with P2 look: CAALogoP2NT.bmp | ![]() |
For UNIX with P1 Look: CAALogoP1IX.bmp | ![]() |
For UNIX with P2 Look: CAALogoP2IX.bmp | ![]() |
[Top]
The resource file must have the name you choose for the product line, here CAAProductLine. This file is:
// .CATRsc of a product line // -------------------------------------- ApplicationFrame.Icon.Name = "CAAProduct"; SplashScreen.Name = "CAASplash"; // P1 Look ApplicationLogo.P1.NT = "CAALogoP1NT"; ApplicationLogo.P1.Unix = "CAALogoP1IX"; DialogBoxBottom.P1 = "CAADecorationP1"; // Available NT Only // P2 Look ApplicationLogo.P2.NT = "CAALogoP2NT"; ApplicationLogo.P2.Unix = "CAALogoP2IX"; DialogBoxBottom.P2 = "CAADecorationP2"; // Available NT Only BackgroundImage.NT = "CAABackgroundNT"; BackgroundImage.Unix = "CAABackgroundIX"; |
You can now launch your application using the shortcut in the desktop and see its different visual identity components.
[Top]
To provide a visual identity to your product line, you can, with Windows only, create an EXE to launch your application associated with an icon of your own that can also be used as a shortcut in the desktop. You can create with UNIX and Windows text and graphic resources to display with your applications.
[Top]
[1] | What Is the Product Line Visual Identity |
[2] | Building and Launching a CAA V5 Use Case |
[3] | Contextual Help |
[Top] |
Version: 1 [Jul 2000] | Document created |
[Top] |
Copyright © 2000, Dassault Systèmes. All rights reserved.