| |||||||||||||
|
| |||||||||||||
dcopdcopPosted Jul 7, 2007 0:24 UTC (Sat) by Richard_J_Neill (subscriber, #23093)In reply to: dcop by rfunk Parent article: Mandriva adds a semantic layer to the KDE 4 desktop
The reason I dislike dcop is that so few of the controls I want are actually implemented! That isn't always true; some applications provide everything one could want (eg amarok, klipper). For example this is a very useful shell script:
#!/bin/bash
However, the dcop commands that I really want to have are usually missing. For example, every option in kcontrol should be dcop-enabled. That way, I could write a shell script to automate KDE configuration every time I set up a new system. (copying ~/.kde brings too much cruft with it).
P.S. Amarok doesn't need dcop
(Log in to post comments)
dcop Posted Jul 7, 2007 19:52 UTC (Sat) by tzafrir (subscriber, #11501) [Link] > hat way, I could write a shell script to automate KDE configuration> every time I set up a new system. (copying ~/.kde brings too much > cruft with it).
Again, dcop needs the server to be up in order for it to be configured. You'd have ot run KDE first. Which is unlike what you can do with manipulation of configuration files.
(At least you can manipulate configuration files. With gnome you depend on gconf to be up even for mere configuration)
dcop Posted Jul 8, 2007 14:53 UTC (Sun) by tmg (guest, #46149) [Link] >That way, I could write a shell script to automate KDE configuration>every time I set up a new system. (copying ~/.kde brings too much cruft >with it). You may want to try kwriteconfig / kreadconfig, which seem to even work without KDE running. These commands probably do exactly what you want.
|
|
||||||||||||