C4DT Installation Guide - Revision history

Pyrit: /* Prerequisites */

2014-09-06T16:08:40Z

Prerequisites

← Older revision		Revision as of 16:08, 6 September 2014
Line 1:		Line 1:
	==Prerequisites==		==Prerequisites==
	First you need to install Eclipse itself. This is relatively straightforward. Go to the [http://eclipse.org/downloads/ Eclipse Download Page] and download the ''Eclipse for Java Developers'' package. Eclipse does not require running an installer. Just unpack the folder somewhere and run the Eclipse program inside it. Unless you don't have Java installed Eclipse should boot although that might take a while. On first boot, Eclipse will usually ask you to provide a workspace location. That's the folder Eclipse will create projects in by default. Set it as you like.		First you have to have Java 8 installed in order for C4DT to work with Eclipse.

			Now you need to install Eclipse itself. This is relatively straightforward. Go to the [http://eclipse.org/downloads/ Eclipse Download Page] and download the ''Eclipse for Java Developers'' package. Eclipse does not require running an installer. Just unpack the folder somewhere and run the Eclipse program inside it. Unless you don't have Java installed Eclipse should boot although that might take a while. On first boot, Eclipse will usually ask you to provide a workspace location. That's the folder Eclipse will create projects in by default. Set it as you like.

	'''Note to Linux Users''': Download Eclipse from its website even if it is available from your distribution's repository. A number of Linux users have had [http://askubuntu.com/questions/282951/how-to-completely-uninstall-eclipse problems] when eclipse is installed from the repo.		'''Note to Linux Users''': Download Eclipse from its website even if it is available from your distribution's repository. A number of Linux users have had [http://askubuntu.com/questions/282951/how-to-completely-uninstall-eclipse problems] when eclipse is installed from the repo.

Domtron: /* Prerequisites */

2013-11-08T19:41:21Z

Prerequisites

← Older revision		Revision as of 19:41, 8 November 2013
Line 1:		Line 1:
	==Prerequisites==		==Prerequisites==
	First you need to install Eclipse itself. This is relatively straightforward. Go to the [http://eclipse.org/downloads/ Eclipse Download Page] and download the ''Eclipse for Java Developers'' package. Eclipse does not require running an installer. Just unpack the folder somewhere and run the Eclipse program inside it. Unless you don't have Java installed Eclipse should boot although that might take a while. On first boot, Eclipse will usually ask you to provide a workspace location. That's the folder Eclipse will create projects in by default. Set it as you like.		First you need to install Eclipse itself. This is relatively straightforward. Go to the [http://eclipse.org/downloads/ Eclipse Download Page] and download the ''Eclipse for Java Developers'' package. Eclipse does not require running an installer. Just unpack the folder somewhere and run the Eclipse program inside it. Unless you don't have Java installed Eclipse should boot although that might take a while. On first boot, Eclipse will usually ask you to provide a workspace location. That's the folder Eclipse will create projects in by default. Set it as you like.

			'''Note to Linux Users''': Download Eclipse from its website even if it is available from your distribution's repository. A number of Linux users have had [http://askubuntu.com/questions/282951/how-to-completely-uninstall-eclipse problems] when eclipse is installed from the repo.

	==Installing C4DT==		==Installing C4DT==

Newton: /* Installing C4DT */

2011-08-02T16:08:03Z

Installing C4DT

← Older revision		Revision as of 16:08, 2 August 2011
Line 11:		Line 11:
	[[File:Eclipse_InstallWindow.png\|left]]<br clear=all/>		[[File:Eclipse_InstallWindow.png\|left]]<br clear=all/>

	C4DT's Update Site is currently [http://www.openclonk.org/c4dt/]. Add the Update Site (the name you choose for the site is of no concern), select it if that didn't happen automatically and you should see two items for installation:		C4DT's Update Site is currently [http://www.openclonk.org/c4dt/ http://www.openclonk.org/c4dt/]. Add the Update Site (the name you choose for the site is of no concern), select it if that didn't happen automatically and you should see two items for installation:
	[[File:EclipseAvailableFeatures.png\|left]]<br clear=all/>		[[File:EclipseAvailableFeatures.png\|left]]<br clear=all/>
	The first one is the C4DT plugin itself that contains all the functionality. The second one is a German language pack you can optionally install as well. Note though that only functionality added by C4DT is translated. The rest of Eclipse stays in English. To change that, head over to the [http://www.eclipse.org/babel/downloads.php Eclipse Babel Project] and install language packs from there. After pressing "Next" quite a few times, accepting the license (which is supposed to be the same as the one OpenClonk uses), agreeing to install unsigned content and restarting Eclipse, C4DT should be installed. A sign of success would be having a Clonk menu item in the main menu.		The first one is the C4DT plugin itself that contains all the functionality. The second one is a German language pack you can optionally install as well. Note though that only functionality added by C4DT is translated. The rest of Eclipse stays in English. To change that, head over to the [http://www.eclipse.org/babel/downloads.php Eclipse Babel Project] and install language packs from there. After pressing "Next" quite a few times, accepting the license (which is supposed to be the same as the one OpenClonk uses), agreeing to install unsigned content and restarting Eclipse, C4DT should be installed. A sign of success would be having a Clonk menu item in the main menu.

Newton: /* Installing C4DT */

2011-08-02T15:18:04Z

Installing C4DT

← Older revision		Revision as of 15:18, 2 August 2011
Line 11:		Line 11:
	[[File:Eclipse_InstallWindow.png\|left]]<br clear=all/>		[[File:Eclipse_InstallWindow.png\|left]]<br clear=all/>

	C4DT's Update Site is currently [http://www.~~maltworld~~.~~de/clonk/c4dt/update http://www.maltworld.de/clonk~~/c4dt/~~update~~] ~~but that might change in the future~~. Add the Update Site (the name you choose for the site is of no concern), select it if that didn't happen automatically and you should see two items for installation:		C4DT's Update Site is currently [http://www.openclonk.org/c4dt/]. Add the Update Site (the name you choose for the site is of no concern), select it if that didn't happen automatically and you should see two items for installation:
	[[File:EclipseAvailableFeatures.png\|left]]<br clear=all/>		[[File:EclipseAvailableFeatures.png\|left]]<br clear=all/>
	The first one is the C4DT plugin itself that contains all the functionality. The second one is a German language pack you can optionally install as well. Note though that only functionality added by C4DT is translated. The rest of Eclipse stays in English. To change that, head over to the [http://www.eclipse.org/babel/downloads.php Eclipse Babel Project] and install language packs from there. After pressing "Next" quite a few times, accepting the license (which is supposed to be the same as the one OpenClonk uses), agreeing to install unsigned content and restarting Eclipse, C4DT should be installed. A sign of success would be having a Clonk menu item in the main menu.		The first one is the C4DT plugin itself that contains all the functionality. The second one is a German language pack you can optionally install as well. Note though that only functionality added by C4DT is translated. The rest of Eclipse stays in English. To change that, head over to the [http://www.eclipse.org/babel/downloads.php Eclipse Babel Project] and install language packs from there. After pressing "Next" quite a few times, accepting the license (which is supposed to be the same as the one OpenClonk uses), agreeing to install unsigned content and restarting Eclipse, C4DT should be installed. A sign of success would be having a Clonk menu item in the main menu.

Mortimer: Add "Getting OpenClonk content into Eclipse" section

2010-12-21T16:05:57Z

Add "Getting OpenClonk content into Eclipse" section

← Older revision		Revision as of 16:05, 21 December 2010
Line 29:		Line 29:
	<p>This is all you need to set in the preferences but of course you can configure other things to your liking. Specifying Syntax highlighting colours used in Clonk text editors (expand the Clonk item in the tree view on the right) or keyboard short cuts (General -> Keys) come to mind.</p>		<p>This is all you need to set in the preferences but of course you can configure other things to your liking. Specifying Syntax highlighting colours used in Clonk text editors (expand the Clonk item in the tree view on the right) or keyboard short cuts (General -> Keys) come to mind.</p>
	<p>When you're done, press OK.</p>		<p>When you're done, press OK.</p>

			==Getting OpenClonk content into Eclipse==
	<p>Now notice the Project Explorer view. It's glaringly empty. To fill it with OpenClonk content, open up the Clonk project wizard by pressing File -> New Clonk Project.</p>		<p>Now notice the Project Explorer view. It's glaringly empty. To fill it with OpenClonk content, open up the Clonk project wizard by pressing File -> New Clonk Project.</p>
	[[File:Eclipse_NewClonkProject.png\|left]]<br clear=all/>		[[File:Eclipse_NewClonkProject.png\|left]]<br clear=all/>
	<p>Choose the name of the project. "OpenClonk" is advisable but in the end it's up to your preference.</p>		<p>Choose the name of the project. "OpenClonk" is advisable but in the end it's up to your preference.</p>

	<p>The following steps differ based on whether you cloned the OpenClonk repository or downloaded an official release.</p>		<p>The following steps differ based on whether you cloned the OpenClonk repository or downloaded an official release.</p>

Mortimer: Clarify linking/importing a bit more

2010-12-21T16:00:58Z

Clarify linking/importing a bit more

← Older revision		Revision as of 16:00, 21 December 2010
Line 34:		Line 34:
	<p>The following steps differ based on whether you cloned the OpenClonk repository or downloaded an official release.</p>		<p>The following steps differ based on whether you cloned the OpenClonk repository or downloaded an official release.</p>

	~~==1.~~ Cloned from Repository==		* '''Cloned from Repository'''
	<p>Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.</p>		:<p>Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.</p>

	~~==2.~~ Downloaded official release==		* '''Downloaded official release'''
	~~<p>~~C4Groups in the official release are packed. C4DT can read packed c4groups, but not modify them. To access packed groups, you ~~need to "~~link" to those groups. For that purpose, there is a link tab in the Clonk Project Wizard that enables you to add groups to be linked to the new project. Add all the .c4d/.c4f/.c4g files from the OpenClonk installation.~~</p>~~		:C4Groups in the official release are packed. C4DT can read packed c4groups, but not modify them. To access the content of packed groups, you have two choices. You can
	~~<p>~~To actually edit stuff, you need to create a new project that references the project containing the linked c4groups. Actually, this is not strictly necessary but advisable to keep things clear.~~</p>~~		:* ''link to those groups.''
	~~<p>~~For referencing other projects (making stuff defined in that project known to the other project), use the Project References tab in the wizard. For changing project references later on, open the properties of a project (right click on the project in the Project Explorer, then select "Properties") and go to the Project References section.~~</p>~~		::For that purpose, there is a link tab in the Clonk Project Wizard that enables you to add groups to be linked to the new project. Add all the .c4d/.c4f/.c4g files from the OpenClonk installation. When you finish the wizard later on, the linked groups will be displayed like regular folders, except for a link sign on the icon ([[File:EclipseLinkedGroup.png]])
			::To actually edit stuff, you need to create a new project that references the project containing the linked c4groups. Actually, this is not strictly necessary but advisable to keep things clear.
	==Both==		::For referencing other projects (making stuff defined in that project known to the other project), use the Project References tab in the wizard. For changing project references later on, open the properties of a project (right click on the project in the Project Explorer, then select "Properties") and go to the Project References section.
	~~<p>~~Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.~~</p>~~		:* ''import the groups.''
	<p>Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.</p>		::The groups will be unpacked into the Eclipse workspace folder and modifying the unpacked files there won't be modify the original groups. Add groups to be imported from the Importing tab in the wizard.
			::If you plan on modyifing content from the releases you could think about whether it wouldn't be better to clone from the repository so you will be able to track your modifications using version control.
			* '''Both'''
			:Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.

	==The Result==		==The Result==

Mortimer: Add explanation on how to link to packed c4groups from releases

2010-12-21T02:47:54Z

Add explanation on how to link to packed c4groups from releases

← Older revision		Revision as of 02:47, 21 December 2010
Line 32:		Line 32:
	[[File:Eclipse_NewClonkProject.png\|left]]<br clear=all/>		[[File:Eclipse_NewClonkProject.png\|left]]<br clear=all/>
	<p>Choose the name of the project. "OpenClonk" is advisable but in the end it's up to your preference.</p>		<p>Choose the name of the project. "OpenClonk" is advisable but in the end it's up to your preference.</p>
	<p>~~Now, by default~~ Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.</p>		<p>The following steps differ based on whether you cloned the OpenClonk repository or downloaded an official release.</p>

			==1. Cloned from Repository==
			<p>Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.</p>

			==2. Downloaded official release==
			<p>C4Groups in the official release are packed. C4DT can read packed c4groups, but not modify them. To access packed groups, you need to "link" to those groups. For that purpose, there is a link tab in the Clonk Project Wizard that enables you to add groups to be linked to the new project. Add all the .c4d/.c4f/.c4g files from the OpenClonk installation.</p>
			<p>To actually edit stuff, you need to create a new project that references the project containing the linked c4groups. Actually, this is not strictly necessary but advisable to keep things clear.</p>
			<p>For referencing other projects (making stuff defined in that project known to the other project), use the Project References tab in the wizard. For changing project references later on, open the properties of a project (right click on the project in the Project Explorer, then select "Properties") and go to the Project References section.</p>

			==Both==
	<p>Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.</p>		<p>Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.</p>
	<p>Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.</p>		<p>Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.</p>

Mortimer: Paragraphs, although probably used wrongly

2010-04-19T12:20:31Z

Paragraphs, although probably used wrongly

Mortimer at 20:34, 18 April 2010

2010-04-18T20:34:51Z

← Older revision		Revision as of 20:34, 18 April 2010
Line 34:		Line 34:
	Now, by default Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.<br>		Now, by default Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.<br>
	Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.<br/>		Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.<br/>
	Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.		Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.<br clear=all/>

			==The Result==
			After creating the OpenClonk project and waiting a bit for Eclipse to analyze all the scripts you should be presented with a vista such as this:
			[[File:Eclipse_OpenClonkProjectCreated.png]]<br clear=all/>
			In its current state, C4DT should more or less be able to parse all the scripts and not litter the problems view with false positives. When new functions are added to the engine (which tends to happen quite a lot with an engine still in development) those functions will be unknown to Eclipse at first, hence its complaining. But fear not, as those gaping holes of ignorance will sooner or later be stuffed.

Mortimer at 20:23, 18 April 2010

2010-04-18T20:23:58Z

@@ Line 3: / Line 3: @@
 ==Installing C4DT==
-Installing C4DT (Clonk Development Tools) is the next step to tailor that generic Eclipse installation you now have for the purpose of editing C4Scripts and other OpenClonk files with it. It is a plugin that provides a number of improvements you might know from other IDEs. Among those are
+Installing C4DT (Clonk Development Tools) is the next step to tailor that generic Eclipse installation you now have for the purpose of editing C4Scripts and other OpenClonk files with it. It is a plug-in that provides a number of improvements you might know from other IDEs. Among those are
 * Content Assistance (similar to IntelliSense from Visual Studio)
 * Error recognition (to not have to boot up the engine for getting a list of syntax errors)
 * Navigation (clicking on identifiers, getting to their declaration locations)
 * Debugging scripts (suspending execution of scripts, executing them in single steps)
-To install C4DT, you first have to add its update site to the list of update sites Eclipse is maintaining. An update site is a location (usually on some web site although it can be local as well) Eclipse can download plugins from. Once downloaded, those plugins will also be updated from the same update site if Eclipse finds new versions of the plugin there. To add an update site, go to Help -> Install New Software and press the Add button in the Install window.
+To install C4DT, you first have to add its update site to the list of update sites Eclipse is maintaining. An update site is a location (usually on some web site although it can be local as well) Eclipse can download plug ins from. Once downloaded, those plug ins will also be updated from the same update site if Eclipse finds new versions of the plug-in there. To add an update site, go to Help -> Install New Software and press the Add button in the Install window.
-[[File:Eclipse_InstallWindow.png|left]]
+[[File:Eclipse_InstallWindow.png|left]]<br clear=all/>

← Older revision		Revision as of 12:20, 19 April 2010
Line 22:		Line 22:
	==Initial configuration==		==Initial configuration==
	What now needs to be done is setting some default preferences that C4DT will need to not completely screw up. Open up the preferences (Window -> Preferences) and go to the Clonk section:<br />		What now needs to be done is setting some default preferences that C4DT will need to not completely screw up. Open up the preferences (Window -> Preferences) and go to the Clonk section:<br />
	[[File:Eclipse_ClonkPreferences.png\|left]]		[[File:Eclipse_ClonkPreferences.png\|left]]<br clear=all/>
	The preferences are divided into preferences to control the general behaviour of the plug-in (below) and engine-specific preferences (on top).<br/>		<p>The preferences are divided into preferences to control the general behaviour of the plug-in (below) and engine-specific preferences (on top).</p>
	Set the game path for OpenClonk to the planet folder in your repository.<br/>		<p>Set the game path for OpenClonk to the planet folder in your repository.</p>
	The two fields "C4Group Executable" and "Engine" will be filled out automatically if suitable executables are contained in the planet folder. If those are to be found somewhere else in your case, select them manually.<br/>		<p>The two fields "C4Group Executable" and "Engine" will be filled out automatically if suitable executables are contained in the planet folder. If those are to be found somewhere else in your case, select them manually.</p>
	The repository field isn't exactly needed at the moment but you can set it to the path to your repository (not the planet folder) anyway.<br/>		<p>The repository field isn't exactly needed at the moment but you can set it to the path to your repository (not the planet folder) anyway.</p>
	This is all you need to set in the preferences but of course you can configure other things to your liking. Specifying Syntax highlighting colours used in Clonk text editors (expand the Clonk item in the tree view on the right) or keyboard short cuts (General -> Keys) come to mind.<~~br clear=all~~/>		<p>This is all you need to set in the preferences but of course you can configure other things to your liking. Specifying Syntax highlighting colours used in Clonk text editors (expand the Clonk item in the tree view on the right) or keyboard short cuts (General -> Keys) come to mind.</p>
	When you're done, press OK.		<p>When you're done, press OK.</p>
	Now notice the Project Explorer view. It's glaringly empty. To fill it with OpenClonk content, open up the Clonk project wizard by pressing File -> New Clonk Project.		<p>Now notice the Project Explorer view. It's glaringly empty. To fill it with OpenClonk content, open up the Clonk project wizard by pressing File -> New Clonk Project.</p>
	[[File:Eclipse_NewClonkProject.png\|left]]		[[File:Eclipse_NewClonkProject.png\|left]]<br clear=all/>
	Choose the name of the project. "OpenClonk" is advisable but in the end it's up to your preference.<br>		<p>Choose the name of the project. "OpenClonk" is advisable but in the end it's up to your preference.</p>
	Now, by default Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.<br>		<p>Now, by default Eclipse will create projects in its workspace folder. But in the case of OpenClonk this is not suitable since all the game content is contained in the planet folder. Luckily, Eclipse provides a mechanism for such situations. It allows you to create projects from folders arbitrarily located in the file system. To use that mechanism uncheck "Use default location" and provide the path to the planet folder. This might feel kind of redundant since you already specified that path in the preferences and well, it is.</p>
	Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.<br/>		<p>Next, you should set the engine to "Open Clonk". When leaving it set to "Default engine" the project's engine will always be equal to the one selected in the preferences which might be troublesome when mixing Clonk Rage and Open Clonk projects in one workspace.</p>
	Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.<~~br clear=all~~/>		<p>Don't let yourself be confused by the boxes at the bottom of the wizard. Those will only be useful in cases where you have multiple projects that build on each other or need to import some packed groups. All not the case in OpenClonk.</p>

	==The Result==		==The Result==
	After creating the OpenClonk project and waiting a bit for Eclipse to analyze all the scripts you should be presented with a vista such as this:		<p>After creating the OpenClonk project and waiting a bit for Eclipse to analyze all the scripts you should be presented with a vista such as this:
	[[File:Eclipse_OpenClonkProjectCreated.png]]<br clear=all/>		[[File:Eclipse_OpenClonkProjectCreated.png]]<br clear=all/></p>
	In its current state, C4DT should more or less be able to parse all the scripts and not litter the problems view with false positives. When new functions are added to the engine (which tends to happen quite a lot with an engine still in development) those functions will be unknown to Eclipse at first, hence its complaining. But fear not, as those gaping holes of ignorance will sooner or later be stuffed.		<p>In its current state, C4DT should more or less be able to parse all the scripts and not litter the problems view with false positives. When new functions are added to the engine (which tends to happen quite a lot with an engine still in development) those functions will be unknown to Eclipse at first, hence its complaining. But fear not, as those gaping holes of ignorance will sooner or later be stuffed.</p>