KDE->TDE branding cleanup.

pull/1/head
Darrell Anderson 11 years ago
parent a448241e2c
commit 9a6a1370a0

@ -351,7 +351,7 @@ the database and reopen the project.</string>
</property>
<property name="toolTip" stdset="0">
<string>Try to locate all included files and preprocess them.
This makes macros and imported namespaces work correctly, and allows KDevelop
This makes macros and imported namespaces work correctly, and allows TDevelop
to know what code-items are visible from within which file.
Note: Parsing may become very slow when this is enabled
(It will become faster after some time).</string>
@ -1110,13 +1110,13 @@ This option only applies to QMake projects.</string>
<cstring>m_kdevembedded</cstring>
</property>
<property name="text">
<string>&amp;Use KDevelop's embedded designer</string>
<string>&amp;Use TDevelop's embedded designer</string>
</property>
<property name="toolTip" stdset="0">
<string>Start KDevelop's own designer embedded within KDevelop</string>
<string>Start TDevelop's own designer embedded within TDevelop</string>
</property>
<property name="whatsThis" stdset="0">
<string>KDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to integrate the UI designer into KDevelop.</string>
<string>TDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to integrate the UI designer into TDevelop.</string>
</property>
</widget>
<widget class="TQRadioButton">
@ -1124,13 +1124,13 @@ This option only applies to QMake projects.</string>
<cstring>m_kdevexternal</cstring>
</property>
<property name="text">
<string>Run &amp;KDevelop's designer as a separate application</string>
<string>Run &amp;TDevelop's designer as a separate application</string>
</property>
<property name="toolTip" stdset="0">
<string>Start KDevelop's own designer externally</string>
<string>Start TDevelop's own designer externally</string>
</property>
<property name="whatsThis" stdset="0">
<string>KDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to run KDevelop's UI designer as a separate program.</string>
<string>TDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to run TDevelop's UI designer as a separate program.</string>
</property>
</widget>
<widget class="TQRadioButton">
@ -1144,7 +1144,7 @@ This option only applies to QMake projects.</string>
<string>Use Qt Designer externally</string>
</property>
<property name="whatsThis" stdset="0">
<string>Check this button if you wish to use Qt Designer rather than KDevelop's integrated designer.</string>
<string>Check this button if you wish to use Qt Designer rather than TDevelop's integrated designer.</string>
</property>
</widget>
<widget class="TQLayoutWidget">

@ -178,11 +178,11 @@ Otherwise leave it unchecked.</string>
</property>
<property name="whatsThis" stdset="0">
<string>Use the floating toolbar. This toolbar always stays
on top of all windows so that if the app covers KDevelop
on top of all windows so that if the app covers TDevelop
you have control of the app through the small toolbar. It
can also be docked into the panel.
This toolbar is in addition to the toolbar in KDevelop.</string>
This toolbar is in addition to the toolbar in TDevelop.</string>
</property>
</widget>
<widget class="TQCheckBox" row="0" column="0">
@ -197,7 +197,7 @@ This toolbar is in addition to the toolbar in KDevelop.</string>
</property>
<property name="whatsThis" stdset="0">
<string>Displaying static members makes GDB slower in
producing data within KDE and Qt.
producing data within TDE and TQt.
It may change the "signature" of the data
which TQString and friends rely on,
but if you need to debug into these values then

@ -21,19 +21,19 @@
<cstring>textLabel1_2</cstring>
</property>
<property name="text">
<string>KDE include directories:
<string>TDE include directories:
Only the selected entry will be used</string>
</property>
</widget>
<widget class="TQComboBox" row="3" column="1">
<item>
<property name="text">
<string>KDE Libs Headers</string>
<string>TDE Libs Headers</string>
</property>
</item>
<item>
<property name="text">
<string>All KDE Headers</string>
<string>All TDE Headers</string>
</property>
</item>
<property name="name">
@ -43,7 +43,7 @@ Only the selected entry will be used</string>
<string></string>
</property>
<property name="whatsThis" stdset="0">
<string>Decide if you want to restrict the Code Completion database to only the base tdelibs API or the entire KDE include structure</string>
<string>Decide if you want to restrict the Code Completion database to only the base tdelibs API or the entire TDE include structure</string>
</property>
</widget>
<widget class="TQLabel" row="3" column="0">
@ -62,7 +62,7 @@ Only the selected entry will be used</string>
<bool>true</bool>
</property>
<property name="whatsThis" stdset="0">
<string>If none of the directories KDevelop found is what you want,you can enter a directory of your choice here</string>
<string>If none of the directories TDevelop found is what you want,you can enter a directory of your choice here</string>
</property>
</widget>
<widget class="TQPushButton" row="2" column="3">

@ -197,7 +197,7 @@
<cstring>select_label</cstring>
</property>
<property name="text">
<string>Please select how KDevelop should execute your scripts.</string>
<string>Please select how TDevelop should execute your scripts.</string>
</property>
</widget>
<widget class="TQButtonGroup">

@ -210,7 +210,7 @@ Indent Switch=false</string>
</property>
<property name="toolTip" stdset="0">
<string>Use the global defaults. See the menu:
Settings/Configure Kdevelop/Formatting.</string>
Settings/Configure TDevelop/Formatting.</string>
</property>
</widget>
</vbox>

@ -81,7 +81,7 @@
</widget>
<widget class="TQLabel">
<property name="name">
<cstring>KDevelopGraphic</cstring>
<cstring>TDevelopGraphic</cstring>
</property>
<property name="sizePolicy">
<sizepolicy>

@ -330,7 +330,7 @@
<cstring>useAssistant_box</cstring>
</property>
<property name="text">
<string>Use KDevelop &amp;Assistant to browse documentation</string>
<string>Use TDevelop &amp;Assistant to browse documentation</string>
</property>
</widget>
<widget class="TQGroupBox" row="2" column="0">

@ -24,7 +24,7 @@
<string>PartExplorer</string>
</property>
<property name="toolTip" stdset="0">
<string>This is a front-end to KDE's TDETrader: search your KDE documentation for more information about KDE services and TDETrader</string>
<string>This is a front-end to TDE's TDETrader: search your TDE documentation for more information about TDE services and TDETrader</string>
</property>
<vbox>
<property name="name">
@ -43,7 +43,7 @@
</sizepolicy>
</property>
<property name="text">
<string>KDE service &amp;type:</string>
<string>TDE service &amp;type:</string>
</property>
<property name="buddy" stdset="0">
<cstring>typeCombo</cstring>

@ -208,7 +208,7 @@
<string>&amp;KRegExp syntax</string>
</property>
<property name="whatsThis" stdset="0">
<string>A description of this syntax can be found in the KDE API documentation.</string>
<string>A description of this syntax can be found in the TDE API documentation.</string>
</property>
</widget>
</vbox>

@ -38,7 +38,7 @@
<cstring>textLabel2</cstring>
</property>
<property name="text">
<string>&lt;b&gt;NOTE&lt;/b&gt; These are directories to search in that are found in your KDE resource directories. So if you add the string "kate/scripts" to the list then KScript will look in "$TDEDIRS/data/kate/scripts" for scripts. This will allow you to get scripts in your home directory as well as system wide ones.</string>
<string>&lt;b&gt;NOTE&lt;/b&gt; These are directories to search in that are found in your TDE resource directories. So if you add the string "kate/scripts" to the list then KScript will look in "$TDEDIRS/data/kate/scripts" for scripts. This will allow you to get scripts in your home directory as well as system wide ones.</string>
</property>
</widget>
</vbox>

@ -211,7 +211,7 @@
</sizepolicy>
</property>
<property name="text">
<string>Note: Changes will take effect after KDevelop is restarted</string>
<string>Note: Changes will take effect after TDevelop is restarted</string>
</property>
<property name="alignment">
<set>WordBreak|AlignCenter</set>

@ -40,7 +40,7 @@
</sizepolicy>
</property>
<property name="text">
<string>KDevelop could not open</string>
<string>TDevelop could not open</string>
</property>
</widget>
<widget class="KSqueezedTextLabel">
@ -108,7 +108,7 @@
<cstring>open_with_kde</cstring>
</property>
<property name="text">
<string>Let KDE find a suitable program</string>
<string>Let TDE find a suitable program</string>
</property>
<property name="checked">
<bool>true</bool>
@ -119,7 +119,7 @@
<cstring>open_as_text</cstring>
</property>
<property name="text">
<string>Open it in KDevelop as plain text</string>
<string>Open it in TDevelop as plain text</string>
</property>
</widget>
<widget class="TQLayoutWidget">

@ -13,7 +13,7 @@
</rect>
</property>
<property name="caption">
<string>Profile Editor for The KDevelop Platform</string>
<string>Profile Editor for The TDevelop Platform</string>
</property>
<grid>
<property name="name">

@ -30,10 +30,10 @@
<string>Lo&amp;ad last project on startup</string>
</property>
<property name="toolTip" stdset="0">
<string>Check this if you want KDevelop to load the last opened project on startup</string>
<string>Check this if you want TDevelop to load the last opened project on startup</string>
</property>
<property name="whatsThis" stdset="0">
<string>Mark this checkbox if you want to continue to work with the last project you worked on. This will cause KDevelop to automatically load this project on start-up. It will usually be shown in the state you left work so you can readily proceed.</string>
<string>Mark this checkbox if you want to continue to work with the last project you worked on. This will cause TDevelop to automatically load this project on start-up. It will usually be shown in the state you left work so you can readily proceed.</string>
</property>
</widget>
<widget class="TQLabel" row="0" column="0" rowspan="1" colspan="4">
@ -55,10 +55,10 @@
<string>Line wrappin&amp;g</string>
</property>
<property name="toolTip" stdset="0">
<string>By default, KDevelop will wrap long lines around in the Messages Output View window</string>
<string>By default, TDevelop will wrap long lines around in the Messages Output View window</string>
</property>
<property name="whatsThis" stdset="0">
<string>By default, KDevelop will wrap long lines around in the Messages Output View window so that valuable information will not be easily overlooked. In some cases this will clutter long message lists. Remove the checkbox mark if you do not want the lines wrap around.</string>
<string>By default, TDevelop will wrap long lines around in the Messages Output View window so that valuable information will not be easily overlooked. In some cases this will clutter long message lists. Remove the checkbox mark if you do not want the lines wrap around.</string>
</property>
</widget>
<widget class="TQLayoutWidget" row="5" column="2" rowspan="1" colspan="2">
@ -111,7 +111,7 @@
<string>Choose what sort of output you want from the build process</string>
</property>
<property name="whatsThis" stdset="0">
<string>KDevelop preprocesses the messages the Messages Output View window receives during the build processes in order to filter superfluous information. You can control the level of detail KDevelop will display using the dropdown box in this field.
<string>TDevelop preprocesses the messages the Messages Output View window receives during the build processes in order to filter superfluous information. You can control the level of detail TDevelop will display using the dropdown box in this field.
&lt;b&gt;Very Short&lt;/b&gt; Displays only warnings, errors, and the filenames which are compiled.
&lt;b&gt;Short&lt;/b&gt; Suppresses all compiler flags and formats the output to be more readable.
&lt;b&gt;Full&lt;/b&gt; Displays all output messages unmodified.</string>
@ -163,7 +163,7 @@
<string>Set the directory where you want your projects in.</string>
</property>
<property name="whatsThis" stdset="0">
<string>By default, KDevelop uses a common parent directory for all new projects. Enter the absolute path of this common directory in the box or select it from your directory structure. KDevelop will place the any new project here as a subdirectory.</string>
<string>By default, TDevelop uses a common parent directory for all new projects. Enter the absolute path of this common directory in the box or select it from your directory structure. TDevelop will place the any new project here as a subdirectory.</string>
</property>
</widget>
</hbox>
@ -267,7 +267,7 @@
<string>Use the terminal as set in KControl</string>
</property>
<property name="whatsThis" stdset="0">
<string>If checked, KDevelop will use the default terminal as set in KControl in KDE components, Component Chooser.</string>
<string>If checked, TDevelop will use the default terminal as set in KControl in TDE components, Component Chooser.</string>
</property>
</widget>
<widget class="TQLayoutWidget" row="1" column="0">
@ -294,7 +294,7 @@
<string>&amp;Other:</string>
</property>
<property name="toolTip" stdset="0">
<string>Set a different terminal than the KDE default one</string>
<string>Set a different terminal than the TDE default one</string>
</property>
<property name="whatsThis" stdset="0">
<string>Choose some other terminal different from the default one.</string>
@ -393,13 +393,13 @@
<cstring>embeddedDesignerRadioButton</cstring>
</property>
<property name="text">
<string>&amp;Use KDevelop's embedded designer</string>
<string>&amp;Use TDevelop's embedded designer</string>
</property>
<property name="toolTip" stdset="0">
<string>Start KDevelop own designer embedded within KDevelop</string>
<string>Start TDevelop own designer embedded within TDevelop</string>
</property>
<property name="whatsThis" stdset="0">
<string>KDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to integrate the UI designer into KDevelop.</string>
<string>TDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to integrate the UI designer into TDevelop.</string>
</property>
</widget>
<widget class="TQRadioButton" row="1" column="0">
@ -407,13 +407,13 @@
<cstring>seperateAppRadioButton</cstring>
</property>
<property name="text">
<string>Run KDevelop's &amp;designer as a separate application</string>
<string>Run TDevelop's &amp;designer as a separate application</string>
</property>
<property name="toolTip" stdset="0">
<string>Start KDevelop own designer externally</string>
<string>Start TDevelop own designer externally</string>
</property>
<property name="whatsThis" stdset="0">
<string>KDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to run KDevelop's UI designer as a separate program.</string>
<string>TDevelop comes with its own UI designer that can either be embedded or be run as a separate program. Check this button if you wish to run TDevelop's UI designer as a separate program.</string>
</property>
</widget>
<widget class="TQRadioButton" row="2" column="0">
@ -427,7 +427,7 @@
<string>Use Qt Designer externally</string>
</property>
<property name="whatsThis" stdset="0">
<string>Check this button if you wish to use Qt Designer rather than KDevelop's integrated designer.</string>
<string>Check this button if you wish to use Qt Designer rather than TDevelop's integrated designer.</string>
</property>
</widget>
</grid>
@ -446,7 +446,7 @@
<string>Check this if you want to know what directory make is in</string>
</property>
<property name="whatsThis" stdset="0">
<string>The make tool usually will display messages like “Entering directory”, or “Leaving directory” when it switches the directories it currently works in. As this clutters the messages list in the Messages Output View window, KDevelop suppresses those messages by default. Mark the checkbox if you want to protocol which directories make worked in.</string>
<string>The make tool usually will display messages like “Entering directory”, or “Leaving directory” when it switches the directories it currently works in. As this clutters the messages list in the Messages Output View window, TDevelop suppresses those messages by default. Mark the checkbox if you want to protocol which directories make worked in.</string>
</property>
</widget>
<spacer row="4" column="0" rowspan="5" colspan="1">

Loading…
Cancel
Save