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

List:       kde-devel
Subject:    Re: Introducing into KDE programming
From:       "=?ISO-8859-1?Q?Rafael_Fern=E1ndez_L=F3pez?=" <ereslibre () gmail ! com>
Date:       2006-09-26 15:37:32
Message-ID: 93f85fee0609260837j6348df28ubd70b6c81acc3a31 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Taking a look to your responses (that are really productive and interesting=
,
I thank you) I wonder how do you develop for KDE. I mean... what strategy d=
o
you follow to have a running system and hack KDE without breaking yours or
whatever.

I know that a obvious response is that you may work in terminal with emacs
or something (as I do lots of times when programming), but I really like
KDE, so I use it for my personal window manager, file manager and so on...
despite the fact that I do use xemacs for programming.

The idea of having another tree (i.e ~/kde-devel) and play with KDEDIRS
variable could be interesting, but I DON'T want to compile kdebase any time
that I break kdesu for example when programming or something (i know that i=
s
not necessary, but having a unclean tree makes me crazy). For that reason I
thought in downloading only apps that I would like to improve (i.e. kate,
kmail, kdesu...) and compile them with the include dir in my root system an=
d
the libraries in my kde root directory.

Thank you very much for your time,
Rafael Fern=E1ndez L=F3pez.

[Attachment #5 (text/html)]

<div>Taking a look to your responses (that are really productive and intere=
sting, I thank you) I wonder how do you develop for KDE. I mean... what str=
ategy do you follow to have a running system and hack KDE without breaking =
yours or whatever.
</div>
<div>&nbsp;</div>
<div>I know that a obvious response is that you may work in terminal with e=
macs or something (as I do lots of times when programming), but I really li=
ke KDE, so I use it for my personal window manager, file manager and so on.=
.. despite the fact that I do use xemacs for programming.
</div>
<div>&nbsp;</div>
<div>The idea of having another tree (i.e ~/kde-devel) and play with KDEDIR=
S variable could be interesting, but I DON'T want to compile kdebase any ti=
me that I break kdesu for example when programming or something (i know tha=
t is not necessary, but having a unclean tree makes me crazy). For that rea=
son I thought in downloading only apps that I would like to improve (
i.e. kate, kmail, kdesu...) and compile them with the include dir in my roo=
t system and the libraries in my kde root directory.</div>
<div>&nbsp;</div>
<div>Thank you very much for your time,</div>
<div>Rafael Fern=E1ndez L=F3pez.</div>


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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