[Libreoffice-commits] help.git: source/text

Libreoffice Gerrit user logerrit at kemper.freedesktop.org
Tue Feb 26 12:04:15 UTC 2019


 source/text/sbasic/python/python_ide.xhp |    9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

New commits:
commit 45899930d0fc91724fba403a2429b9863d32247c
Author:     LibreOļ¬ƒciant <LibreOfficiant at sfr.fr>
AuthorDate: Tue Feb 26 11:48:38 2019 +0100
Commit:     Olivier Hallot <olivier.hallot at libreoffice.org>
CommitDate: Tue Feb 26 13:03:51 2019 +0100

    Name tag updates in links
    
    Change-Id: I88cdf6ea514ba98d45d90d59bc170f4c59938df6
    Reviewed-on: https://gerrit.libreoffice.org/68382
    Tested-by: Jenkins
    Reviewed-by: Olivier Hallot <olivier.hallot at libreoffice.org>

diff --git a/source/text/sbasic/python/python_ide.xhp b/source/text/sbasic/python/python_ide.xhp
index b6cc64544..e6d715630 100644
--- a/source/text/sbasic/python/python_ide.xhp
+++ b/source/text/sbasic/python/python_ide.xhp
@@ -8,7 +8,6 @@
     * file, You can obtain one at http://mozilla.org/MPL/2.0/.
     *
     -->
-
     <meta>
         <topic id="pythonidesetup" indexer="include" status="PUBLISH">
             <title id="tit" xml-lang="en-US">IDE for Python</title>
@@ -27,13 +26,11 @@
         <h1 id="hd_id151543348965464"><variable id="pythonideh1"><link href="text/sbasic/python/python_ide.xhp" name="Python IDE Setup">Setting up an Integrated Development Environment (IDE) for Python</link></variable></h1>
         <paragraph id="par_id541543348965465" role="paragraph" xml-lang="en-US">Writing Python macros requires extra configuration steps to set an IDE of choice.</paragraph>
     </section>
-    <paragraph role="paragraph" id="N0106">Unlike Basic language macros development in %PRODUCTNAME, developing Python scripts for %PRODUCTNAME requires to configure an external Integrated Development Environment (IDE). Multiple IDEs are available that range from beginners to advanced Python coders. While using a Python IDE programmers benefit from numerous features such as syntax highlighting, code folding, class browsing, code completion, coding standard enforcement, test driven development, debugging, version control and many more. You can refer to <link href="https://wiki.documentfoundation.org/Macros/Python_Design_Guide" name ="external">Designing & Developing Python Applications</link> on the Wiki for more in-depth information about the setup of a bridge between your IDE and a running instance %PRODUCTNAME.</paragraph>
-
+    <paragraph role="paragraph" id="N0106">Unlike Basic language macros development in %PRODUCTNAME, developing Python scripts for %PRODUCTNAME requires to configure an external Integrated Development Environment (IDE). Multiple IDEs are available that range from beginners to advanced Python coders. While using a Python IDE programmers benefit from numerous features such as syntax highlighting, code folding, class browsing, code completion, coding standard enforcement, test driven development, debugging, version control and many more. You can refer to <link href="https://wiki.documentfoundation.org/Macros/Python_Design_Guide" name="Designing & Developing Python Applications">Designing & Developing Python Applications</link> on the Wiki for more in-depth information about the setup of a bridge between your IDE and a running instance %PRODUCTNAME.</paragraph>
     <h2 id="hd_id761544698669786">The APSO Extension</h2>
-    <paragraph role="paragraph" id="N0104">The <link href="https://extensions.libreoffice.org/extensions/apso-alternative-script-organizer-for-python" name ="external">Alternative Python Script Organizer (APSO)</link> extension eases the edition of Python scripts, in particular when embedded in a document. Using APSO you can configure your preferred source code editor, start the integrated Python shell and debug Python scripts. Extensions exist that help inspect arbitrary UNO objects, refer to <link href="https://wiki.documentfoundation.org/Macros/Python_Design_Guide" name ="external">Designing & Developing Python Applications</link> for additional details on such extensions.</paragraph>
+    <paragraph role="paragraph" id="N0104">The <link href="https://extensions.libreoffice.org/extensions/apso-alternative-script-organizer-for-python" name="Alternative Python Script Organizer (APSO)">Alternative Python Script Organizer (APSO)</link> extension eases the edition of Python scripts, in particular when embedded in a document. Using APSO you can configure your preferred source code editor, start the integrated Python shell and debug Python scripts. Extensions exist that help inspect arbitrary UNO objects, refer to <link href="https://wiki.documentfoundation.org/Macros/Python_Design_Guide" name="eDesigning & Developing Python Applications">Designing & Developing Python Applications</link> for additional details on such extensions.</paragraph>
     <section id="relatedtopics">
         <embed href="text/sbasic/python/main0000.xhp#pythonscriptshelp"/>
     </section>
-
 </body>
-</helpdocument>
+</helpdocument>
\ No newline at end of file


More information about the Libreoffice-commits mailing list