diff options
Diffstat (limited to 'tde-i18n-en_GB/docs/tdesdk/kcachegrind/index.docbook')
| -rw-r--r-- | tde-i18n-en_GB/docs/tdesdk/kcachegrind/index.docbook | 56 |
1 files changed, 28 insertions, 28 deletions
diff --git a/tde-i18n-en_GB/docs/tdesdk/kcachegrind/index.docbook b/tde-i18n-en_GB/docs/tdesdk/kcachegrind/index.docbook index 71ff8f42cef..443be3d40cd 100644 --- a/tde-i18n-en_GB/docs/tdesdk/kcachegrind/index.docbook +++ b/tde-i18n-en_GB/docs/tdesdk/kcachegrind/index.docbook @@ -1,6 +1,6 @@ <?xml version="1.0" ?> <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [ - <!ENTITY kcachegrind '<application + <!ENTITY tdecachegrind '<application >KCachegrind</application >'> <!ENTITY cachegrind "<application @@ -18,7 +18,7 @@ <!ENTITY oprofile "<application >OProfile</application >"> - <!ENTITY kappname "&kcachegrind;"> + <!ENTITY kappname "&tdecachegrind;"> <!ENTITY package "tdesdk"> <!ENTITY % addindex "IGNORE"> <!ENTITY % British-English "INCLUDE"> @@ -30,7 +30,7 @@ <bookinfo> <title ->The &kcachegrind; Handbook</title> +>The &tdecachegrind; Handbook</title> <authorgroup> <author @@ -80,7 +80,7 @@ <abstract> <para ->&kcachegrind; is a profile data visualisation tool, written using the &kde; environment. </para> +>&tdecachegrind; is a profile data visualisation tool, written using the &kde; environment. </para> </abstract> <keywordset> @@ -197,24 +197,24 @@ </sect1> </chapter> -<chapter id="using-kcachegrind"> +<chapter id="using-tdecachegrind"> <title ->Using &kcachegrind;</title> +>Using &tdecachegrind;</title> <sect1 id="using-profile"> <title >Generate Data to Visualise</title> <para ->First, one wants to generate performance data by measuring aspects of the runtime characteristics of an application, using a profiling tool. &kcachegrind; itself does not include any profiling tool, but is good in being used together with &callgrind;, and by using a converter, also can be used to visualise data produced with &oprofile;. Although the scope of this manual is not to document profiling with these tools, the next section provides short quickstart tutorials to get you started. </para> +>First, one wants to generate performance data by measuring aspects of the runtime characteristics of an application, using a profiling tool. &tdecachegrind; itself does not include any profiling tool, but is good in being used together with &callgrind;, and by using a converter, also can be used to visualise data produced with &oprofile;. Although the scope of this manual is not to document profiling with these tools, the next section provides short quickstart tutorials to get you started. </para> <sect2> <title >&callgrind;</title> <para ->&callgrind; is available from <ulink url="http://kcachegrind.sf.net" -> http://kcachegrind.sf.net</ulink +>&callgrind; is available from <ulink url="http://tdecachegrind.sf.net" +> http://tdecachegrind.sf.net</ulink >. Note that it previously was called &calltree;, but that name was misleading. </para> <para @@ -228,7 +228,7 @@ ></blockquote > At program termination, a file <filename >callgrind.out.pid</filename -> will be generated which can be loaded into &kcachegrind;. </para> +> will be generated which can be loaded into &tdecachegrind;. </para> <para >More advanced use is to dump out profile data whenever a given function of your application is called. E.g. for <command @@ -241,7 +241,7 @@ > callgrind --dump-before=KonqMainWindow::slotReload konqueror </command ></para ></blockquote -> This will produce multiple profile data files with an additional sequential number at the end of the filename. A file without such an number at the end (only ending in the process PID) will also be produced; by loading this file into &kcachegrind;, all others are loaded too, and can be seen in the Parts Overview and Parts list. </para> +> This will produce multiple profile data files with an additional sequential number at the end of the filename. A file without such an number at the end (only ending in the process PID) will also be produced; by loading this file into &tdecachegrind;, all others are loaded too, and can be seen in the Parts Overview and Parts list. </para> </sect2> @@ -263,13 +263,13 @@ >opcontrol -d</command >. This will write out the measurement results into files under directory <filename >/var/lib/oprofile/samples/</filename ->. To be able to visualise the data in &kcachegrind;, do in an empty directory: <blockquote +>. To be able to visualise the data in &tdecachegrind;, do in an empty directory: <blockquote ><para ><command > opreport -gdf | op2callgrind </command ></para ></blockquote -> This will produce a lot of files, one for every program which was running on the system. Each one can be loaded into &kcachegrind; on its own. </para> +> This will produce a lot of files, one for every program which was running on the system. Each one can be loaded into &tdecachegrind; on its own. </para> </sect2> </sect1> @@ -279,7 +279,7 @@ >User Interface Basics</title> <para ->When starting &kcachegrind; with a profile data file as argument, or after loading one with File/Open, you will see a sidebar containing the function list at the left; and, on the right the main part, an area with visualisations for a selected function. This visualisation area can be arbitrarily configured to show multiple visualisations at once. </para> +>When starting &tdecachegrind; with a profile data file as argument, or after loading one with File/Open, you will see a sidebar containing the function list at the left; and, on the right the main part, an area with visualisations for a selected function. This visualisation area can be arbitrarily configured to show multiple visualisations at once. </para> <para >At first start, this area will be divided into a top and a bottom part, each with different visualisations selectable by tabs. To move visualisation views, use the context menu of the tabs, and adjust the splitters between visualisations. To quickly switch between different visualisation layouts, use View/Layouts/Duplicate, change the layout and switch between layouts with View/Layout/Next (or, even better, use the corresponding keyboard shortcuts). </para> @@ -290,9 +290,9 @@ > in the left list, and look at the call graph visualisation; there, you see calls happening in your program. Note that the call graph view only shows functions with high event count. By double-clicking a function in the graph, it will change to show the called functions around the selected one. </para> <para ->To explore the GUI further, in addition to this manual, also have a look at the documentation section on the web site <ulink url="http://kcachegrind.sf.net" -> http://kcachegrind.sf.net</ulink ->. Also, every widget in &kcachegrind; has <quote +>To explore the GUI further, in addition to this manual, also have a look at the documentation section on the web site <ulink url="http://tdecachegrind.sf.net" +> http://tdecachegrind.sf.net</ulink +>. Also, every widget in &tdecachegrind; has <quote >What's this</quote > help. </para> </sect1> @@ -300,12 +300,12 @@ </chapter> -<chapter id="kcachegrind-concepts"> +<chapter id="tdecachegrind-concepts"> <title >Basic Concepts</title> <para ->This chapter explains some concepts of the &kcachegrind;, and introduces terms used in the interface. </para> +>This chapter explains some concepts of the &tdecachegrind;, and introduces terms used in the interface. </para> <sect1 id="concepts-model"> <title @@ -611,9 +611,9 @@ <title >Command Reference</title> -<sect1 id="kcachegrind-mainwindow"> +<sect1 id="tdecachegrind-mainwindow"> <title ->The main &kcachegrind; window</title> +>The main &tdecachegrind; window</title> <para ></para> @@ -847,11 +847,11 @@ <qandaentry> <question> <para ->What is &kcachegrind; for? I have no idea. </para> +>What is &tdecachegrind; for? I have no idea. </para> </question> <answer> <para ->&kcachegrind; is a helpful at a later stage in software development, called Profiling. If you don't develop applications, you don't need &kcachegrind;. </para> +>&tdecachegrind; is a helpful at a later stage in software development, called Profiling. If you don't develop applications, you don't need &tdecachegrind;. </para> </answer> </qandaentry> @@ -974,13 +974,13 @@ <title >Installation</title> -<sect1 id="getting-kcachegrind"> +<sect1 id="getting-tdecachegrind"> <title ->How to obtain &kcachegrind;</title> +>How to obtain &tdecachegrind;</title> <para ->&kcachegrind; is part of the &package; package of &kde;. For less supported interim releases, &callgrind; and further documentation, see the homepage at <ulink url="http://kcachegrind.sf.net" -> http://kcachegrind.sf.net</ulink +>&tdecachegrind; is part of the &package; package of &kde;. For less supported interim releases, &callgrind; and further documentation, see the homepage at <ulink url="http://tdecachegrind.sf.net" +> http://tdecachegrind.sf.net</ulink >. Look there for further installation and compile instructions. </para> </sect1> @@ -989,7 +989,7 @@ >Requirements</title> <para ->In order to successfully use &kcachegrind;, you need &kde; 3.x. For generating profile data, &cachegrind; or &calltree;/&callgrind; is recommend. </para> +>In order to successfully use &tdecachegrind;, you need &kde; 3.x. For generating profile data, &cachegrind; or &calltree;/&callgrind; is recommend. </para> </sect1> <sect1 id="compilation"> |