Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.
Example Application GUI Composer
GUI Composer Runtime ships with an example application that will be used to explain critical components of a GUI Composer created application.
You will need to install GUI Composer Runtime, please refer to Getting Started section.
Example application is located in GCInstallRoot\guicomposer\webapps\modem_m3 directory. It is using a modem project that simulates processing of a modem signal. The target that is used in this example is CortexM3 (LE) simulator. The project and its source files are located in above mentioned directory in a zip file. You may import this project into CCSv5.3 to build/debug it. The example is quite simple it has a single dial that allows to control a g_ModemData.carrierFreq variable that can be used to adjust wavelength of the g_ModemData.OutputBuffer which is graphed in the top graph. A spinner control is also tied to the same CarrierFreq variable showing that mutliple widgets may be used to control the same target variable. This might be useful where coarse/fine grained control is required. Second graph is included purely for illustration purposes and it graphs g_ModemData.Idelay array.
Example Application Generated Files
Files listed below have been created with CCS GUI Composer Designer feature. They explain detailed implementation information that may be useful when attempting to edit/adjust generated application by editing files.
app.html : This is the main html page containing applications layout. This file is generated when GUI Composer is used to design the application by dragging and dropping widgets onto a page. Actual widgets included in this application are between <body> </body> tags. Below is an example of a single widget, in this case the dial widget. All widgets need to have a unique id and then specify data-dojo-type attribute which defines the type of widget. Remainder of parameters specify optional settings such as size, position, colors, min, max values, etc)
<canvas id="widget_915" data-dojo-type="gc.dijit.Dial" title="CarrierFreq" size="225" maxValue="50" labelNumberFormat="standard" fractionalScaleDecimals="1" frameDesign="tiltedBlack" dialDesign="anthracite" style="z-index: 9999; position: absolute; left: 20px; top: 23px;"></canvas> app.json: This is a json file that is automatically loaded by GUI Composer Runtime. Its file name needs to match its corresponding html filename. Json file contains specification information for widgets that interact with target data. Below is an example of a json entry that matches the dial definition. json entries are used to bind widgets to target applications global variables. widgetid needs to match the id from html file. In this case Dial widget mentioned above is bound to g_ModemData.carrierFreq variable from our target application.
All widgets that GUI Composer supports have code snippet examples shown in GCInstallRoot\bind_examples. Each widget has a html file showing html code and its corresponding .json file.
appConfig.ccxml : This is an optional file that is used to configure a simulator. In most cases when HW is used, this file will not be necessary as the information provided during Export Application stage will be used to auto generate configuration information.
appProgram.out: This is the target application program that will be loaded when a GUI Composer application is started.
index.html: This is auto generated page that is part of default template. It is the default page that gets loaded when GUI Composer App is launched. It's main purpose is to show target initialization/connection status and then automatically load app.html upon succesful connection.
modem_m3_gc_app.exe : This is a generic executable that is used to start a particular GUI Composer application. This launcher may be renamed and its icons adjusted to match branding requirements of an application.