From 2ecab1a194b0dc551b478820e1aaa3b8713354cc Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Wed, 16 Nov 2011 13:53:18 -0600 Subject: Additional renaming of kde to tde --- doc/kdevelop/kdevelop-scripting.docbook | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/kdevelop/kdevelop-scripting.docbook') diff --git a/doc/kdevelop/kdevelop-scripting.docbook b/doc/kdevelop/kdevelop-scripting.docbook index d9e59bb5..177a0b65 100644 --- a/doc/kdevelop/kdevelop-scripting.docbook +++ b/doc/kdevelop/kdevelop-scripting.docbook @@ -1,4 +1,4 @@ - + @@ -12,7 +12,7 @@ Running Scripts - To access a script that is available to &kdevelop; use the ToolsScripts menu. If there there is no such menu item then there are no installed scripts available to KDevelop. + To access a script that is available to &tdevelop; use the ToolsScripts menu. If there there is no such menu item then there are no installed scripts available to KDevelop. @@ -30,7 +30,7 @@ The next step is to create the actual script. For the above example the Type of One of the most useful tools in developing scripts for applications is the KDCOP application.
- KDCOP Browsing DCOP Interfaces in &kdevelop; + KDCOP Browsing DCOP Interfaces in &tdevelop; @@ -41,7 +41,7 @@ The next step is to create the actual script. For the above example the Type of Once the script is complete it is ready to be installed. Application developers should document the location that will be scanned for scripts. In the case of the above example for Kate the scripts are located in "$KDEDIRS/share/apps/kate/scripts".
- &kdevelop; Scripts on the Filesystem + &tdevelop; Scripts on the Filesystem -- cgit v1.2.3