(void)newKAction(i18n("&Save Strings List to File..."),"filesaveas",0,TQT_TQOBJECT(this),TQT_SLOT(slotStringsSave()),actionCollection(),"strings_save");
(void)newKAction(i18n("&Load Strings List From File..."),"unsortedList",0,TQT_TQOBJECT(this),TQT_SLOT(slotStringsLoad()),actionCollection(),"strings_load");
constTQStringlvStringsWhatthis=i18n("Shows a list of strings to search for (and if you specified it, a list of strings to replace with). Use the \"add strings\" dialog to edit your string list or double click on a string.");
//KNewProjectDlg messages
constTQStringcbLocationWhatthis=i18n("Base folder for operations of search/tqreplace. Insert path string here by hand or use the search button.");
constTQStringcbLocationWhatthis=i18n("Base folder for operations of search/replace. Insert path string here by hand or use the search button.");
<ul type="disc"><li>detect incorrect path at shebang, allow user to choose correct one and remeber that pair</li>
<div></div>
<div></div></ul>
<p><span style="font-weight:600">If we keep the old parser.<br /><br /></span><br />Make it possible to use any language with Kommander. The idea is to replace Kommander specials with language specific code in a way that it will not break conditions and loops, like now. example:<br />#!/bin/bash<br />array="1 2 3 4 5"<br />for i in $array do<br /> @Label.setText($i)<br />done<br /><br />This does not work now. The idea is to tqreplace @Widget.method() with a language specific DCOP call.<br />If the language has DCOP bindings, use those bindings to execute the dcop call. If not, use the command line<br />DCOP application. This is slower, but always works. In the above case, Kommander would tqreplace <br />@Label.setText($i) <br />with<br />dcop kmdr-executor-PID KommanderIf setText Label $i<br /><br />Kommander will have description files for each supported language about how to execute DCOP calls.<br />If the language has DCOP bindings, this description tells the syntax of the bindings. If it doesn't have, the description gives a way how to execute external applications. This should always exists, as all languages can execute external applications.<br /><br />In KDE4, of course use DBUS instead of DCOP.<br /><br /></p>
<p><span style="font-weight:600">If we keep the old parser.<br /><br /></span><br />Make it possible to use any language with Kommander. The idea is to replace Kommander specials with language specific code in a way that it will not break conditions and loops, like now. example:<br />#!/bin/bash<br />array="1 2 3 4 5"<br />for i in $array do<br /> @Label.setText($i)<br />done<br /><br />This does not work now. The idea is to replace @Widget.method() with a language specific DCOP call.<br />If the language has DCOP bindings, use those bindings to execute the dcop call. If not, use the command line<br />DCOP application. This is slower, but always works. In the above case, Kommander would replace <br />@Label.setText($i) <br />with<br />dcop kmdr-executor-PID KommanderIf setText Label $i<br /><br />Kommander will have description files for each supported language about how to execute DCOP calls.<br />If the language has DCOP bindings, this description tells the syntax of the bindings. If it doesn't have, the description gives a way how to execute external applications. This should always exists, as all languages can execute external applications.<br /><br />In KDE4, of course use DBUS instead of DCOP.<br /><br /></p>
@ -1302,7 +1302,7 @@ Example: <b>Tags=style(type[text/css])</b> means that both <b>
<string>Comma separated list of the local scope defining keywords</string>
</property>
<property name="whatsThis" stdset="0">
<string>Comma separated list of the local scope defining keywords. Other structure group elements found under a structure node that was created based on a keyword from this list are treated as local elements. For example if this list tqcontains <b>function</b>, it means that elements, like variables found under a <b>function</b> are local, relative to the node that holds the <b>function</b>.</string>
<string>Comma separated list of the local scope defining keywords. Other structure group elements found under a structure node that was created based on a keyword from this list are treated as local elements. For example if this list contains <b>function</b>, it means that elements, like variables found under a <b>function</b> are local, relative to the node that holds the <b>function</b>.</string>
@ -1313,7 +1313,7 @@ Example: <b>Tags=style(type[text/css])</b> means that both <b>
<string>Comma separated list of the local scope defining keywords</string>
</property>
<property name="whatsThis" stdset="0">
<string>Comma separated list of the local scope defining keywords. Other structure group elements found under a structure node that was created based on a keyword from this list are treated as local elements. For example if this list tqcontains <b>function</b>, it means that elements, like variables found under a <b>function</b> are local, relative to the node that holds the <b>function</b>.</string>
<string>Comma separated list of the local scope defining keywords. Other structure group elements found under a structure node that was created based on a keyword from this list are treated as local elements. For example if this list contains <b>function</b>, it means that elements, like variables found under a <b>function</b> are local, relative to the node that holds the <b>function</b>.</string>
This will match strings like <b>$fooObj=new foo;</b>. Now this string is searched and it will tqfind <b>new foo;</b>, where <b>foo</b> is the first captured text (the regular expression matching <b>foo</b> is between brackets).<br>
This will match strings like <b>$fooObj=new foo;</b>. Now this string is searched and it will find <b>new foo;</b>, where <b>foo</b> is the first captured text (the regular expression matching <b>foo</b> is between brackets).<br>
So the type of <b>$fooObj</b> is <b>foo</b>.</string>
This will match strings like <b>$fooObj=new foo;</b>. Now this string is searched and it will tqfind <b>new foo;</b>, where <b>foo</b> is the first captured text (the regular expression matching <b>foo</b> is between brackets).<br>
This will match strings like <b>$fooObj=new foo;</b>. Now this string is searched and it will find <b>new foo;</b>, where <b>foo</b> is the first captured text (the regular expression matching <b>foo</b> is between brackets).<br>
So the type of <b>$fooObj</b> is <b>foo</b>.</string>
KMessageBox::error(this,i18n("<qt>There is already an abbreviation group called <b>%1</b>. Choose an unique name for the new group.</qt>").tqarg(groupName),i18n("Group already exists"));
d->tqreplace(name,newTQString(m_dtd->booleanTrue));//it seems that browsers don't like <input disabled="false">, so if a checkbox is false, don't put in the tag at all
d->replace(name,newTQString(m_dtd->booleanTrue));//it seems that browsers don't like <input disabled="false">, so if a checkbox is false, don't put in the tag at all
TQStringListbackedupFilesEntryList=QuantaCommon::readPathListEntry(config,"List of backedup files");//the files that were backedup
TQStringListautosavedFilesEntryList=QuantaCommon::readPathListEntry(config,"List of autosaved files");//the list of actual backup files inside $KDEHOME/share/apps/quanta/backups
if(!autosavedFilesEntryList.tqcontains(backupPathValueURL))//not yet backed up, add an entry for this file
if(!autosavedFilesEntryList.contains(backupPathValueURL))//not yet backed up, add an entry for this file
KMessageBox::warningYesNo(0L,i18n("<qt>Do you want to replace the existing <b>%1</b> DTD?</qt>").tqarg(nickName),TQString(),i18n("Replace"),i18n("Do Not Replace"))==KMessageBox::No)
KMessageBox::warningYesNo(0L,i18n("<qt>Do you want to replace the existing <b>%1</b> DTD?</qt>").tqarg(nickName),TQString(),i18n("Replace"),i18n("Do Not Replace"))==KMessageBox::No)
KMessageBox::Yes==KMessageBox::questionYesNo(0,i18n("<qt>Do you want to add the<br><b>%1</b><br>file to project?</qt>").tqarg(saveUrl.prettyURL(0,KURL::StripFileProtocol)),TQString(),KStdGuiItem::add(),i18n("Do Not Add"))
tpearson
13 years ago