Frictional Game Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<h1>CodeLite - How to get started</h1> <div class="level1"> <p> <em>Alternate community created guide with images can be found here </em> <em><a href="https://wiki.frictionalgames.com/hpl3/community/scripting/codelite_setup_with_pictures" class="urlextern" title="https://wiki.frictionalgames.com/hpl3/community/scripting/codelite_setup_with_pictures" rel="nofollow">wiki.frictionalgames.com/hpl3/community/scripting/codelite_setup_with_pictures</a></em> </p> <ol> <li class="level1"> <a href="http://codelite.org/support.php" class="urlextern" title="http://codelite.org/support.php" rel="nofollow">Download the latest CodeLite release.</a></li> <li class="level2 node"> Launch CodeLite and configure: <br/> &lt;nowiki>&#42;&lt;/nowiki> Settings→Code Completion→Display and Behavior: Activate "Keep function signature un-formated".<ul> <li class="level3"> Settings→Code Completion→ctags→Search Paths: Click Add.. and navigate to the SOMA game folder and select the script/ folder.</li> <li class="level3"> Settings→Code Completion→ctags→Advanced: Add&lt;nowiki> &#42;&lt;/nowiki>.hps to file types list.</li> <li class="level3"> Settings→Code Completion→Colouring: Enable colour local variables.</li> <li class="level3"> (optional) Settings→Code Completion→Colouring: Enable colour workspace tags, also enable enumerator but leave the rest with default setting.</li> <li class="level3"> (optional) Settings→Code Completion: Configure the rest to your liking. For example, auto-show & case sensitive enabled.</li> <li class="level3"> Settings→Colours and Fonts→Customize, select C++ and in Global Settings add &lt;nowiki> &#42;&lt;/nowiki>.hps to the File Extension list.</li> </ul> </li> <li class="level2"> Create a new workspace. Do this by going to Workspace menu and select "New Workspace…". Pick C++ Workspace. Name is as you like and set the workspace path as you like <b>as long as it is on the same drive as SOMA.</b></li> <li class="level2"> Create a new project in the workspace. Do this by right-clicking on the workspace in the list to the left and choose the Create New Project option. Select others → Non-code project. Name as you like and leave rest as default.</li> <li class="level2"> Add one folder to the project. Right-click on the project folder and choose New Virtual Folder. Name it _api (you can create others later when you know more).</li> <li class="level2 node"> Time to add files to the project. <br/> &lt;nowiki>&#42;&lt;/nowiki> Right-click on _api and Add An Existing File, add the file "SOMA GAME FOLDER LOCATION/hps_api.hps" (might need to launch the game executable one time to have this file created).<ul> <li class="level3"> Right-click on the <b>project</b> in the list to the left, pick Import Files From Directory. Navigate to the SOMA GAME FOLDER and select it. In the next window, check the boxes for maps and scripts and make sure that the &lt;nowiki>&#42;&lt;/nowiki>.hps file extension is present in the list of extentions to import. Click OK.</li> </ul> </li> </ol> <p> That should be it, you should now have three top folders in your project and a lot of sub-folders with various script files. Hps files should be color coded and parsed for completion as you open them in the project. If they do not, you can re-tag the workspace, project or the single file to see if it helps. </p> <p> Start typing something, for example Entity (depending on configuration this can be case sensitive!) and a drop down should appear showing all the functions that begin with Entity and the documentation for each selected function. You can force things to appear using these shortcuts: </p> <ul> <li class="level1"> ctrl-space will bring up the completion drop down.</li> <li class="level2"> ctrl-shift-space will bring up hints when inside the () of a function.</li> </ul> </div> <h2>Issues & Info</h2> <div class="level2"> <ul> <li class="level1"> Write Class@ object and not Class @object, the later will screw up coloring.</li> <li class="level2"> A bug currently can make some words loose coloring when you launch codelite. Open the Tags settings, click OK and the re-tag the file or project to fix it.</li> <li class="level2"> If you loose all coloring and can't get it back, delete the .tags file saved in the same folder as your workspace. Then relaunch codelite and re-tag workspace, save file to get it working.</li> <li class="level2"> Parameters with &in will break coloring of parameter, but will have no other side-effects.</li> </ul> </div> <h3>Extra Info</h3> <div class="level3"> <p> Info about Settings→Colours and Fonts→Customize→Styles→Edit Lexer keyword sets, Set 0 to Set 4: </p> <ul> <li class="level1"> Set 0 User configured list of keywords not already parsed. Can be edited.</li> <li class="level2"> Set 1 Unknown.</li> <li class="level2"> Set 2 Doxygen keywords, words here will be colored in comments using /&lt;nowiki>&#42;&lt;/nowiki>&lt;nowiki>&#42;&lt;/nowiki> codeblocks when prepended with @ ie @var int myInt. Can be edited.</li> <li class="level2"> Set 3 Used for the setting "Colour workspace tags", automatically created (not visibly). Can NOT be edited.</li> <li class="level2"> Set 4 Used for the setting "Colour local variables", automatically created (not visibly). Can NOT be edited.</li> </ul> </div>