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.

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