You can run individual modules without running kcontrol using the command <command>kcmshell</command> from &konsole;. Type <userinput> <command>kcmshell</command><option> --list</option></userinput> to see a list of the available &kcontrolcenter; modules. You can also access individual &kcontrolcenter; modules through adding the <guilabel>Preferences</guilabel> button to either &kicker; or the &kmenu; through their respective configuration dialogs.
You can run individual modules without running kcontrol using the command <command>tdecmshell</command> from &konsole;. Type <userinput> <command>tdecmshell</command><option> --list</option></userinput> to see a list of the available &kcontrolcenter; modules. You can also access individual &kcontrolcenter; modules through adding the <guilabel>Preferences</guilabel> button to either &kicker; or the &kmenu; through their respective configuration dialogs.
<para>Allows you to access another computer's files using the SEcure Shell (<acronym>SSH</acronym>) protocol. The remote computer needs to be running the <acronym>SSH</acronym> daemon, but the remainder of the protocol uses standard commandline tools as discussed below.</para>
<para>You can use the fish kioslave like this:
<para>You can use the fish tdeioslave like this:
<userinput>fish://<replaceable>hostname</replaceable></userinput> or <userinput>fish://<replaceable>username</replaceable>@<replaceable>hostname</replaceable></userinput>.</para>
<note><para>You need to use double forward slashes.</para></note>
@ -117,7 +117,7 @@ properly in 800x600 (is it 800x600 or 1024x768?). For a start, someone needs to
* Tons of KCMs and applications have options for selecting binaries which they use(frontends etc.). We need to be a little consistent here and adopt a general policy in this issue.
If a binary is not in $PATH it is the distributors fault and not KDE. The reason we have a GUI is so people don't have to know about this kinds of internals. The options doesn't mean anything because users use KDE, they're not in run level 3("WTF? cdparanoia? diff? What's that?"). PATH options("Where to search for X") should be removed - it is up to the distributor. Options for selecting what binary to use should be moved out to KConfEdit - they have a use but are very rarely used.
* Rewrite kcmshell to the new TDECModuleProxy and fix bugs. Move it to tdelibs.
* Rewrite tdecmshell to the new TDECModuleProxy and fix bugs. Move it to tdelibs.
<string><b>WARNING:</b> This option may in rare cases lead to various problems. Consult the What's This? (Shift+F1) help for details.</string>
* Empty panel now has size>0, so user can still drop icons on it.
* Fixed gcc 3.4 incompatibilities in EasyVector
* Fixed Drag and Drop Bugs :
* Crash when non-url dropped on quicklauncher
* Crash panel button dropped on quicklauncher
* Able to drop objects when quicklauncher is locked
* Crash when non-url dropped on quictdelauncher
* Crash panel button dropped on quictdelauncher
* Able to drop objects when quictdelauncher is locked
* Add application context menu now inserts new app at current location
2004-06-14 Dan Bullok <dan.kde@bullok.com>
@ -28,7 +28,7 @@
* Spouts tons of debugging info to kdDebug (for now).
2004-06-12 Dan Bullok <dan.kde@bullok.com>
* Fixed bug #75351: Tooltips change to filenames after rearranging applications in quicklauncher.
* Fixed bug #75351: Tooltips change to filenames after rearranging applications in quictdelauncher.
* Moved the URL->(menuID,service,kurl) functionality from the QuickButton constructor to its own class: QuickURL. Very similar code is used elsewhere in kicker, and should eventually be merged.
* Renamed some methods in QuickButton (getId -> menuId, getURL -> url) This matches the predominant KDE naming style.