Startup script - Revision history

Mandrav: Updated info for latest changes

2006-12-15T12:29:54Z

Updated info for latest changes

Mandrav: Added example

2006-12-10T20:17:55Z

Added example

Artojon: removed extra category

2006-11-11T17:40:57Z

removed extra category

Artojon: wikify

2006-07-07T19:02:02Z

wikify

Mandrav: /* Startup */

2006-07-03T09:44:47Z

Startup

Mandrav: /* Startup */

2006-07-03T09:43:32Z

Startup

Mandrav: Initial

2006-07-03T09:42:28Z

Initial

New page

== Startup ==

When Code::Blocks finishes loading, it tries to load a script named ''startup.script''. If it is found it then tries to execute the ''"function main()"'' inside it (if there). The user can edit this script to run arbitrary customization commands on application startup.
The shipped ''startup.script'' just logs its presence in the application's debug log.

function main()
{
Log(_T("Running startup script"));
}

See also: [[scripting commands]].
[[Category:Documentation]]

@@ Line 1: / Line 1: @@
 [[Category:Scripting Code::Blocks]]
-When Code::Blocks finishes loading, it tries to load a script named ''startup.script''. If it is found it then tries to execute the ''"function main()"'' inside it (if there). The user can edit this script to run arbitrary customization commands on application startup.
+When Code::Blocks finishes loading, it tries to load a script named ''startup.script''. If it is found it then executes it (no need for ''"function main()"'' inside it anymore). The user can edit this script to run arbitrary customization commands on application startup.
-The shipped ''startup.script'' just logs its presence in the application's debug log.
+The shipped ''startup.script'' demonstrates a couple of the newest scripting features.
-  function main()
+  Log(_T("Running startup script"));
-−
-     Log(_T("Running startup script"));
+ // #include any script plugins; this will register them too
+  // un-comment the line below to register a pointless sample plugin
 == Example ==
-As an example, you could register some scripts you have written and bind them to Code::Blocks' menus.
+An example script is now shipping with Code::Blocks. Please read the last line of the startup.script above:
-All you have to do now, is create the "sample.script" file in the same folder. Here's an example:
+ // add a menu entry to edit this script
- // A sample script
+This actually binds the script named <tt>edit_startup_script.script</tt> to the menu entry <tt>"Settings/-Edit startup script"</tt>.
-And don't forget that Code::Blocks conveniently allows you to edit the "sample.script" at any time. All you have to do is keep SHIFT pressed while clicking on the "Sample script" menu item ;).
+And don't forget that Code::Blocks conveniently allows you to edit the <tt>edit_startup_script.script</tt> at any time. All you have to do is keep SHIFT pressed while clicking on the <tt>"Edit startup script"</tt> menu item ;).

@@ Line 8: / Line 8: @@
       Log(_T("Running startup script"));
+  }
 == See also ==
 * [[Scripting commands]]

← Older revision		Revision as of 17:40, 11 November 2006
Line 1:		Line 1:
−	~~[[Category:Code::Blocks_Documentation]]~~
	[[Category:Scripting Code::Blocks]]		[[Category:Scripting Code::Blocks]]

@@ Line 1: / Line 1: @@
 When Code::Blocks finishes loading, it tries to load a script named ''startup.script''. If it is found it then tries to execute the ''"function main()"'' inside it (if there). The user can edit this script to run arbitrary customization commands on application startup.
 The shipped ''startup.script'' just logs its presence in the application's debug log.
@@ Line 7: / Line 10: @@
+  }
-See also: [[scripting commands]].
+== See also ==
-[[Category:Code::Blocks_Documentation]]
+* [[Scripting commands]]

← Older revision		Revision as of 09:43, 3 July 2006
Line 10:		Line 10:

	See also: [[scripting commands]].		See also: [[scripting commands]].
−	[[Category:~~Documentation~~]]	+	[[Category:Code::Blocks_Documentation]]