NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Directory layout of GUI Composer

From Texas Instruments Wiki
Jump to: navigation, search

 

GUI Composer directory layout is important to help in deployment options of applications. Below is an explanation of directory layout and potential deployment options. 


Gui Composer Standalone application. 

High level directory structure

- guicomposer

    - ccs_base (JTAG drivers, debugger engine and symbol manager, flashing tools)

    - eclipse (eclipse runtime, web browser, javascript libraries, gui composer runtime)

    - webapps (individual applications )

          - applicationA (each application exists in its own folder, this is where .html and .json files that render the user interface and connect widgets to target variables exist)

          - applicationB



GUI Composer integrated with Code Composer Studio

High level directory structure

For clarity only relevant directories have been shown below. Depending on your installation of Code Composer Studio you may see addtional directories. 

- CCSInstallationRoot

     - ccsv5

          - ccs_base

          - eclipse

          - webapps

                 - applicationA (each application exists in its own folder, this is where .html and .json files that render the user interface and connect widgets to target variables exist)
                 - applicationB