[Ktutorial-commits] SF.net SVN: ktutorial:[373] trunk/ktutorial/ktutorial-editor/doc/en
Status: Alpha
Brought to you by:
danxuliu
From: <dan...@us...> - 2012-08-20 11:16:02
|
Revision: 373 http://ktutorial.svn.sourceforge.net/ktutorial/?rev=373&view=rev Author: danxuliu Date: 2012-08-20 11:15:55 +0000 (Mon, 20 Aug 2012) Log Message: ----------- Update English handbook. Modified Paths: -------------- trunk/ktutorial/ktutorial-editor/doc/en/index.docbook trunk/ktutorial/ktutorial-editor/doc/en/installation.docbook trunk/ktutorial/ktutorial-editor/doc/en/using.docbook Modified: trunk/ktutorial/ktutorial-editor/doc/en/index.docbook =================================================================== --- trunk/ktutorial/ktutorial-editor/doc/en/index.docbook 2012-08-20 10:59:41 UTC (rev 372) +++ trunk/ktutorial/ktutorial-editor/doc/en/index.docbook 2012-08-20 11:15:55 UTC (rev 373) @@ -35,6 +35,8 @@ <copyright> <year>2010</year> + <year>2011</year> + <year>2012</year> <holder>Daniel Calviño Sánchez</holder> </copyright> <!-- Translators: put here the copyright notice of the translation --> @@ -49,8 +51,8 @@ (V.MM.LL), it could be used by automation scripts. Do NOT change these in the translation. --> - <date>2010-03-23</date> - <releaseinfo>0.1</releaseinfo> + <date>2012-08-18</date> + <releaseinfo>0.5</releaseinfo> <!-- Abstract about this handbook --> @@ -92,11 +94,11 @@ &ktutorial-editor; </para> <para> - Program Copyright 2010 Daniel Calviño Sánchez <email>dan...@gm...</email> + Program Copyright 2010-2012 Daniel Calviño Sánchez <email>dan...@gm...</email> </para> <para> - Documentation Copyright 2010 Daniel Calviño Sánchez <email>dan...@gm...</email> + Documentation Copyright 2010-2012 Daniel Calviño Sánchez <email>dan...@gm...</email> </para> <!-- TRANS:CREDIT_FOR_TRANSLATORS --> Modified: trunk/ktutorial/ktutorial-editor/doc/en/installation.docbook =================================================================== --- trunk/ktutorial/ktutorial-editor/doc/en/installation.docbook 2012-08-20 10:59:41 UTC (rev 372) +++ trunk/ktutorial/ktutorial-editor/doc/en/installation.docbook 2012-08-20 11:15:55 UTC (rev 373) @@ -22,7 +22,7 @@ <sect1 id="requirements"> <title>Requirements</title> - <para>In order to successfully build and use KTutorial, you need &kde; (at least version 4.3) and, therefore, &Qt; (at least version 4.5.3).</para> + <para>In order to successfully build and use KTutorial, you need &kde; (at least version 4.3) and, therefore, &Qt; (at least version 4.6).</para> <para>To use the full feature set of &ktutorial-editor; you will also need the QtDBus module of Qt, only available in Unix systems. Without that module &ktutorial-editor; can not talk to the target application, for example to know the name of its objects.</para> Modified: trunk/ktutorial/ktutorial-editor/doc/en/using.docbook =================================================================== --- trunk/ktutorial/ktutorial-editor/doc/en/using.docbook 2012-08-20 10:59:41 UTC (rev 372) +++ trunk/ktutorial/ktutorial-editor/doc/en/using.docbook 2012-08-20 11:15:55 UTC (rev 373) @@ -223,7 +223,8 @@ <title>Objects with duplicated names</title> <para>Usually, the name of an object in the target application will identify that and only that object. However, sometimes there could be two or more objects with the same name. For example, if there are two or more dialogs opened, there will probably be two or more objects named <literal>Ok button</literal>.</para> <para>Therefore, when two or more objects have the same name, they can not be identified by their name alone. Instead, their name must be qualified with the name of one or more ancestor objects. For example, <literal>Configuration dialog/Ok button</literal>. When an object is chosen in the list, &ktutorial-editor; takes care of all this and gets a unique name for the object.</para> - <para>But note that a name and the object it represents depends on the state of the target application. For example, if there is a dialog named <literal>Configuration dialog</literal> with a button named <literal>Ok button</literal>, its unique name could be just <literal>Ok button</literal>. However, if another dialog named <literal>File information dialog</literal> were opened while the <literal>Configuration dialog</literal> was still opened, and <literal>File information dialog</literal> had a also button called <literal>Ok button</literal>, now the unique name of the first button would be <literal>Configuration dialog/Ok button</literal>. In this situation, <literal>Ok button</literal> would not represent a specific object in the target application.</para> + <para>Under some circumstances, an object may not have a unique name. When a name represents two or more objects, KTutorial applies a set of ambiguity solving rules. &ktutorial-editor; takes that into account too, and tries to get a name that identifies the chosen object, even if the name is not unique. But, if even after applying the ambiguity solving rules there is no name that identifies just the chosen object, a warning is shown.</para> + <para>However, note that a name and the object it represents depends on the state of the target application. For example, if there is a dialog named <literal>Configuration dialog</literal> with a button named <literal>Ok button</literal>, its unique name could be just <literal>Ok button</literal>. However, if another dialog named <literal>File information dialog</literal> were opened while the <literal>Configuration dialog</literal> was still opened, and <literal>File information dialog</literal> had a also button called <literal>Ok button</literal>, now the unique name of the first button would be <literal>Configuration dialog/Ok button</literal>. In this situation, <literal>Ok button</literal> would not represent a specific object in the target application.</para> <para>All that means that, when choosing an object from the target application, the target application should be in the same state as it would be when following the tutorial and getting to the current step.</para> </tip> </sect2> @@ -240,7 +241,7 @@ <title>Other less noticeable features</title> <para>Besides those already mentioned, &ktutorial-editor; uses a running target application to provide other small yet useful features.</para> - <para>The one-line text editors to set the name of an object have text completion, so if instead of choosing the object its name is written directly in the text editor it will suggest the name based on the objects in the target application.</para> + <para>The one-line text editors to set the name of an object have text completion, so if instead of choosing the object its name is written directly in the text editor it will suggest the name based on the objects in the target application. The completion will try to suggest unique names; however, two or more proposed names can be duplicated if the objects they represent do not have a unique name, even after applying the ambiguity solving rules.</para> <para>The one-line text editor to set the name of a signal also has text completion, so when the object name was set, the text editor will suggest the signal name based on the signals that can be emitted by that object. The same schema is used for the name of properties.</para> <para>The one-line text editors for step ids in the step data and reaction dialogs have text completion too. The first one will suggest the ids not assigned yet (from the <emphasis>change to step</emphasis> field of the reactions), and the second one will suggest the ids already set in the steps.</para> <para>The text completion uses the standard KDE text completion system, so all the standard keyboard shortcuts can be used (like <keycombo action="simul">&Ctrl;<keycap>T</keycap></keycombo> to show all the available completions).</para> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |