[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Remote accounts on KDE development workstations
From:       Gioele Barabucci <ml () gioelebarabucci ! com>
Date:       2005-06-25 12:54:45
Message-ID: 200506251454.45444.ml () gioelebarabucci ! com
[Download RAW message or body]

When I started to work on my own wishitem #107954 I said to my self: "it can't 
be that difficult, just one applet to modify". Then I remembered why I had to 
stop KDE hacking: most of the things in kdebase are just frontends to 
something that happens on kdelibs, and hacking/building kdelibs on my 700 G3 
is impossible.

So two questions came to my mind:
* now most of the code in kdelibs _does_ things instead of _asking specific 
plugins_ to implement the concrete actions. The classic "policy in the 
kernel" problem. IMO in KDE4 there should be more delegation, or at least 
notification, to external code.
For example the "Recent documents" menuext is a simple kicker applet that 
shows  files created and modified by KRecentDocument that resides in 
kio/kfile. So if I want to modify the way those files are created I have to 
hack and rebuild kfile, that is not a light task on my notebook.

* some time ago I read of a very nice application of NX: remote workstations 
with accoounts for KDE developers so they could work on the trunk without any 
fear. Is this project alive or dead? Who should I contact to request an 
account?


--
Gioele <dev@gioelebarabucci.com>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]