If you want to install new plugin system-wide, root, use:
</para>
<screen>
su -c "cp libmykomplugin.so $KDEDIR/lib"
su -c "cp libmykomplugin.so $TDEDIR/lib"
</screen>
<note><para>If you use the KDevelop project generator, you will not need to do the above, but instead adapt the Makefile.am to link against extra libraries. By default, it will link to &Qt; and &kde; libraries and generate all the needed object files. Just run <command>make</command> to build, and <command>su -c make install</command> to install.</para></note>
@ -34,7 +34,7 @@ Here is a short description about the needed steps to make a dialog translatable
<listitem><para>How to extract the messages and create the .po file?</para>
<para>
Use the <command>kmdr2po</command> script to extract the strings. The script is inside the <emphasis>working</emphasis> directory of the source release tarball and should be installed to <command>$KDEDIR/share/apps/kommander/translating</command> as well.
Use the <command>kmdr2po</command> script to extract the strings. The script is inside the <emphasis>working</emphasis> directory of the source release tarball and should be installed to <command>$TDEDIR/share/apps/kommander/translating</command> as well.
</para>
<para>
Just run:
@ -52,7 +52,7 @@ An appropriate <your-kommander-dialog.po> file will be created.
<listitem><para>How to install the translation?</para>
<para>Put the compiled *.mo file either to</para>
<para><command>$KDEDIR/share/locale/<your language>/LC_MESSAGES/</command> (will be available globally for all users)</para>
<para><command>$TDEDIR/share/locale/<your language>/LC_MESSAGES/</command> (will be available globally for all users)</para>
<para>or to </para>
<para><command>$HOME/.kde/share/locale/<your language>/LC_MESSAGES/</command> (will be available only for the current user)</para>
These examples reflect the most recent development state of &kommander;. In its current state &kommander; has few limitations for developing small to medium applications. It certainly is not suitable for building a KWord clone, but for a simple editor, database frontend, GUI for commandline programs or any application in the spirit of Unix/Linux small applications it is a good choice. The examples presented here are intended to show the potential as well as how to work around limitations. There are some useful tricks included in these if you want to do a more capable small application with &kommander;. Remember &kommander; is not intended to do everything, but to do most things. For this concession you should be able to build something in &kommander; faster than other alternatives ad add GUI to scripting languages not otherwise supported in KDE.
</para>
<note><para>
The examples are installed to <command>$KDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
The examples are installed to <command>$TDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
@ -113,7 +113,7 @@ The place to define abbreviations (some kind of templates), that can be expanded
<itemizedlist>
<listitem><para><guilabel>Name:</guilabel> the user visible name</para></listitem>
<listitem><para><guilabel>Output window:</guilabel> plugins can appear in a tab of the editor area or in a separate toolview at the bottom</para></listitem>
<listitem><para><guilabel>Location:</guilabel> the path to the plugin, if it is not located in the standard locations, like <filename class="directory">$<envar>KDEDIR</envar>/lib</filename> .</para></listitem>
<listitem><para><guilabel>Location:</guilabel> the path to the plugin, if it is not located in the standard locations, like <filename class="directory">$<envar>TDEDIR</envar>/lib</filename> .</para></listitem>
<listitem><para><guilabel>File name:</guilabel> the relative path and the filename to the plugin's libtool file, like <filename class="libraryfile">trinity/libcervisiapart.la</filename></para></listitem>
<listitem><para><guilabel>Input:</guilabel> the plugin will get this information on startup, so it can open the <guilabel>Current File</guilabel>, the folder of the current file (<guilabel>Current File Path</guilabel>) or the <guilabel>Project Folder</guilabel>.</para></listitem>
<listitem><para><guilabel>Read only part:</guilabel> check if the plugin refuses to load. Read-only KParts usually refuse to load without this option checked.</para></listitem>
@ -1195,8 +1195,8 @@ First you have to enter the name of your script with the interpreter as well. Ex
<para>
Although you can use full paths, the recommended way is to use the <command>%scriptdir</command> variable in the command line, like <command>sh %scriptdir/myScript.sh</command>. This way &quantaplus; will try to locate your script in the following places:
for local or global use respectively. Then create a folder (the one
specified in your <filename>docrc</filename> file) in the same folder
as your <filename>docrc</filename> file and copy your &HTML; pages in
@ -1771,7 +1771,7 @@ After a resource was downloaded, but before it is installed, &quantaplus; verifi
</para>
<para>The entries are:</para>
<itemizedlist>
<listitem><para><guilabel>Target directory name:</guilabel>the newly created &DTEP; will go under this name to the <filename><envar>$KDEHOME</envar>/share/apps/quanta/dtep</filename> folder.
<listitem><para><guilabel>Target directory name:</guilabel>the newly created &DTEP; will go under this name to the <filename><envar>$TDEHOME</envar>/share/apps/quanta/dtep</filename> folder.
</para>
</listitem>
<listitem><para><guilabel>Name:</guilabel>the name (definition string) of the DTD</para></listitem>
<p>An assumption is made that you have the knowledge and ability to find and install any missing libraries that you may encounter. Basically, you need the headers from KDE, Qt, and GCC. If you don't know what was just said, then try the steps below and, if it doesn't work for you, then find yourself a Linux geek that can help.</p>
<p>Type the following in a shell and see what you get:</p>
<p>If you don't get two yes answers, then you need to find the location of the one that failed and export it to your current shell environment.</p>
@ -145,7 +145,7 @@
<divclass="fltop"><ahref="#top">Top</a></div>
<divclass="minihdr">2.4 I get error <i>X</i> when running ./configure</div>
<divclass="indent">
<p>Please read 2.3 carefully again and make certain that you have exported the $KDEDIR and $QTDIR environment variables. This is the most likely cause. Aside from that, if you are missing something very important, then configure will tell you what it needs.</p>
<p>Please read 2.3 carefully again and make certain that you have exported the $TDEDIR and $QTDIR environment variables. This is the most likely cause. Aside from that, if you are missing something very important, then configure will tell you what it needs.</p>
<string>The name of the folder where the toolbars are stored</string>
</property>
<property name="whatsThis" stdset="0">
<string>The name of the folder where the toolbars are stored. This is a relative name to <br><i>$KDEDIR(&nbsp;or&nbsp;$KDEHOME)/share/apps/quanta/toolbars</i> .</string>
<string>The name of the folder where the toolbars are stored. This is a relative name to <br><i>$TDEDIR(&nbsp;or&nbsp;$TDEHOME)/share/apps/quanta/toolbars</i> .</string>
<string>The name of the folder where the toolbars are stored</string>
</property>
<property name="whatsThis" stdset="0">
<string>The name of the folder where the toolbars are stored. This is a relative name to <br><i>$KDEDIR(&nbsp;or&nbsp;$KDEHOME)/share/apps/quanta/toolbars</i> .</string>
<string>The name of the folder where the toolbars are stored. This is a relative name to <br><i>$TDEDIR(&nbsp;or&nbsp;$TDEHOME)/share/apps/quanta/toolbars</i> .</string>
//creates an entry string in quantarc if it does not exist yet
config->setGroup("General Options");
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
TQStringListautosavedFilesEntryList=QuantaCommon::readPathListEntry(config,"List of autosaved files");//the list of actual backup files inside $TDEHOME/share/apps/quanta/backups
if(!autosavedFilesEntryList.contains(backupPathValueURL))//not yet backed up, add an entry for this file
Timothy Pearson
13 years ago