我思,我想

记录人生痕迹

Subscribe to RSS feed

Posts tagged with "kde"

让KDE中的GTK程序使用Human Theme [updated]

UPDATE: 昨天去问了一下HUAHUA, 最简单的方法就是直接编辑配置文件, 加上ICON的设定就好了...

修改 .gtkrc-2.0, 或者.gtkrc-2.0-kde, evn | grep gtk 看看那个是起作用的就修改哪个.

修改如下:
  gtk-theme-name="Human"
  gtk-font-name="Sans Serif 9"
  gtk-icon-theme-name="Human"

注意后面指定了icon的名称.


=========================================
kde里面安装gtk-engines-qt可以在系统设置里面让gtk程序使用qt风格, 看起来和qt程序差不多, 但是实际上有时候gtk风格看起来会挺难看的. 特别是文件对话框, 超级难看, 图标也超级丑陋.

这个时候我们可以让gtk程序使用gtk的style, 比如ubuntu的Human Theme, 感觉还不错.

第一步, 在kubuntu的 系统设定--外观--颜色, 把左下角的 *将颜色应用到非KDE应用程序* 前面的勾去掉, 这样让gtk程序使用我们将来要设定的style的配色.

第二步, 安装Human Theme 和 gnome控制台. ::

    sudo apt-get install gtk2-engines-ubuntulooks human-cursors-theme  human-icon-theme human-theme gnome-control-center


如果喜欢别的style如clearlooks, 可以安装相应的engine.

安装了Human 主题之后, 在kubuntu的 系统设定--外观--GTK Style and Fonts ,里面选择Human Style.

然后再运行 gnome-control-center, 主题里面选择Human.

第三步, 这个其实是很关键的, 再做了前面两步的时候gtk程序的风格应该已经变化了(要新打开的程序), 但是当你注销, 或者重启之后, 风格就会变得很丑, 特别是图标. ::

  ln -s /usr/bin/gnome-settings-daemon ~/.kde/Autostart/gnome-settings-daemon


这一步是让登录系统的时候自动启动gnome的daemon程序, 保持gnome的某些设置, 这样还有一个好处, 如果你会经常使用某些gnome下面的程序,可能会提高启动速度. 同样如果在gnome经常会使用某些kde程序, 可以在启动的时候把kdeinit自动启动起来, 这样也能够提高kde程序的性能.

kubuntu and kde4

,

摘要:
kubuntu将紧密跟进kde的下一代版本kde4,由于kde4的第一个版本预计在今年10月发布,所以我们无法在kubuntu7.10中使用kde4,而kubuntu8.04将是下一个LTS版本,因为这个时候kde4还是第一个发行版本,稳定性和可用性不一定能够满足LTS版本的需要,估计也不会成为kubuntu8.04的default desktop.但是kubuntu也许会发布kde4的包,方便大家使用kde4.

The announcement of a releaseplan for KDE 4 silenced all the previous discussions wether or not the completely new KDE will appear. KDE 4 is based on Qt4 and all applications have to be ported to it. The release of KDE 4.0 is planned for October 2007. kubuntu-de.org held an interview with Jonathan Riddell, project lead of kubuntu about KDE 4 and future kubuntu releases.
q: Jonathan, many kubuntu users seem to be eager to get KDE 4 a soon as possible. Can you give us a look behind the set?''

Jonathan Riddell: At the last Ubuntu Development summit we looked at KDE 4 and made plans for introducting it into the archives. kde4libs and kde4base are now in, the rest are sitting in the NEW queue waiting for an admin to approve them for the archive. Some of the packages have already been rejected because of licence problems (nothing major, just a missing file), so it's good that we are doing this early to get such problem out the way.
You can install these packages alongside the current KDE 3 and run them under KDE 3 or in their own session.
However they're very unstable, and not usable for every day work at all. Also the packages do not currently have any dependencies on them, so you need to install these manually.
q: Kubuntu 6.10 contains packages for KDE 4 for developers. Do you think there will be soon test versions for common users, too?

Jonathan Riddell: Our main focus is to make the tools necessary available to developers. So we have the latest CMake (the new build system for KDE
4) in feisty and coming into backports. We also have the latest strigi and decibel libraries which are now needed by KDE 4.
Users are welcome to try out the packages but I really don't recommend them for use except as a good way to find bugs and start fixing them.
q: Recently, there were reports in the press that sounded like the publication or discussion of milestones for a release plan. When do you
estimate KDE 4 might be released?
Jonathan Riddell: Previously I had hoped for last October which would be KDE's 10th birthday. I was obviously well off, so maybe I should guess a release around our 11th birthday smile
Even once KDE 4 is released we will still have KDE 3 around for a while until all the applications are ported. We've started the porting already for Kubuntu with Ubiquity and other apps now using Qt 4 but many apps such as Adept and Guidance depend on KDE functionality so it is not possible to port them until KDE 4 becomes more stable.
q: When KDE 4 will be released, which Kubuntu would likely contain it, 7.10 or rather 8.04?
Jonathan Riddell: I suspect KDE 4 won't be stable enough to be default desktop for 7.10. 8.04 it should be but it's possible that 8.04 will be our next LTS release and I don't want our first KDE 4 as default release to also be an LTS release. Either way we'll have packages and ISOs of KDE 4 available as soon as sanely possible for everyone to try.
Thank you for the Interview

调整ktorrent参数,降低cpu占用率

,

我一直用ktorrent下载bt,下载速度和功能让我很满意。但是有时候如果连上的源多的话会占用大量的cpu,导致机器很慢。看看top的信息,ktorrent和Xorg占用了很多cpu,基本上ktorrent 70%,Xorg 20%,基本占用了所有的cpu资源。

看到这样的情况,分析应该是ktorrent频繁刷新界面导致的。于是在设置里面把ktorrent的界面刷新时间加长,设置到2秒,ktorrent的cpu占用立即下降到30,40%左右,不错。但是还是较高。再分析界面上显示几百个连接上的下载者信息,和下载块的信息,也在不断刷新,估计这个也有问题,于是把选项中的 这两个选项也去掉了,结果cpu占用就下降到了7%左右,效果令人非常满意。

如果有用ktorrent的朋友,感觉占用cpu过高的话,不妨试试这个方法。

KDE 4.0 Roadmap

,

十月二十三,KDE4发布. 还有大半年时间. 慢慢等吧.


KDE 4.0 Roadmap
===============

Milestone: Subsystem Freeze
Date: 1 April 2007
Goals:
* From this date forward, no major KDE subsystem can be committed to kdelibs.
* The location of all classes are fixed within kdelibs
* Trunk is expected to contain KDE4 code only now. This effectively means
that all scripts processing translations for KDE3 in trunk will cease.
* Extragear applications that want to release based on KDE3 are expected
to move to /branches/stable and work from there.
* The buildsystem requirements are fixed; i.e, must not require a
version of cmake greater than 2.4.5.

Milestone: Alpha Release + kdelibs soft API Freeze
Date: 1 May 2007
Goals:
* Qt 4.3 is required from here until release.
* The kdelibs API is frozen. This means that the classes and interfaces are
not allowed to change, except with permission of the core developers.
* To make an API change, post a kdelibs API exception request to the
kde-core-devel mailinglist with an explanation and the code. If there
are no objections after a week, the change can be committed.
NOTE: all affected modules must continue to compile and work as expected.


Milestone: Feature Freeze
Date: 1 June 2007
Goals:
* The KDE main modules are frozen for new features.
* No new features are allowed, the focus is on stabilizing the applications
and fixing all bugs.
* The main module maintainers must indicate if they will follow the release
schedule or will divert and not be released together with KDE 4.0.

Milestone: Beta Cycle, Full kdelibs API Freeze
Start: 25 June 2007 End: 24 September 2007 Duration: 3 months (estimated)
Goals:
* From this date forward, a Beta Version will be published every month
until most grave bugs are resolved.
* The kdelibs API is now frozen solid.
* Translations are included starting with the second Beta, thus beginning
a string freeze. Exceptions can be requested on the kde-i18n mailinglist.

Milestone: Release Candidate Cycle
Start: 25 September 2007 End: 22 October 2007 Duration: 4 weeks (estimated)
Goals:
* From this date forward, a Release Candidate will be released every
two weeks until *all* grave bugs are resolved.
* After the first Release Candidate there is a total release freeze.
This means only regressions (breakage caused due to the KDE4 port)
or grave bugs can be fixed, but nothing else.
* With the first Release Candidate, a list of languages which will be
included with the KDE 4.0 release will be made available, based on the
usual rules.

Milestone: KDE 4.0 Released
Date: 23 October 2007
Goals:
* This date is based on an estimated 3 Beta's and 2 Release Candidates.

今天KDE-CN筹备大会第一次会议开幕了

,

我有幸旁听了一会儿.期待KDE-CN开张.