>
>
> On Tue, Jan 3, 2012 at 12:08 PM, Amandeep Singh wrote:
>
>> Hi, I have succesfully built the kde-source in a directory kde-devel.
>>
>> How can i checkout the effect of changes i make to the code.
>> I tried running a nested session using Xephyr, but i just get a blank
>> window. I followed t
Thats a feature (not a problem) that I quite like actually; to be able to
leaf through my windows with mouse wheel.
On Tue, Jan 3, 2012 at 12:08 PM, Amandeep Singh wrote:
> Hi, I have succesfully built the kde-source in a directory kde-devel.
>
> How can i checkout the effect of changes i make to
Hi, I have succesfully built the kde-source in a directory kde-devel.
How can i checkout the effect of changes i make to the code.
I tried running a nested session using Xephyr, but i just get a blank
window. I followed the steps given here :
http://techbase.kde.org/Getting_Started/Run/Nested_Sess
ed... as well as bug fixes, but once in
a while the scales should tip toward bug fixing, where most developers focus on
stabilizing what we have and making it concrete.
This is why I'm working mostly on bug fixing myself, because *I think* there
are more people working on new features and n
On Sat, Dec 11, 2010 at 11:35 AM, Felix Rohrbach wrote:
> Hi,
>
> first, thanks for your respose!
>
> Am Freitag, 10. Dezember 2010, 21:00:26 schrieb Aaron J. Seigo:
>> On Friday, December 10, 2010, Felix Rohrbach wrote:
>> > 1) With which project should I start?
>>
>> pick something that interest
On Sat, Dec 11, 2010 at 20:48, Felix Rohrbach wrote:
> @Lydia:
> I'll take a look at Choqok, but it seems to have all features I could think
> of...
You can check bugs.kde.org for feature requests for it. Or the
brainstorm section on forum.kde.org. Or you can email the main
developer. You should
Am Samstag, 11. Dezember 2010, 17:51:49 schrieb Daniel Nicoletti:
> Hey,
> Sure the first code is always the harder (not hello world :P ),
> I have a "junior" job that is not so junior and is not related to Internet
> or Multimedia but it might give you the feeling of working on KDE
> things. It re
> When I look at the applications I'm interested in they always seem to already
> have all the easy-to-implement features I can think of, and all the other
> things seem to hard for me as a starting point. But most likely I'm wrong
with
> that - I just don't have the experience to be able to sa
On Sat, Dec 11, 2010 at 17:35, Felix Rohrbach wrote:
> Hi,
>
> first, thanks for your respose!
>
> Am Freitag, 10. Dezember 2010, 21:00:26 schrieb Aaron J. Seigo:
>> On Friday, December 10, 2010, Felix Rohrbach wrote:
>> > 1) With which project should I start?
>>
>> pick something that interests y
Hi,
first, thanks for your respose!
Am Freitag, 10. Dezember 2010, 21:00:26 schrieb Aaron J. Seigo:
> On Friday, December 10, 2010, Felix Rohrbach wrote:
> > 1) With which project should I start?
>
> pick something that interests you. there are a lot of kde applications and
> all of them can use
power. While it may not be right to tell these things on
a development list, I would like to tell you a few shortcomings of the
KDE project which might help developers. Since I am on another FOSS
project, I wont be able to help but perhaps someone can! Here they
(shortcomings) are since then, till now
On Friday, December 10, 2010, Felix Rohrbach wrote:
> Hi,
>
> I'm a German student who would like to help developing KDE, but whose
welcome :)
> 1) With which project should I start?
pick something that interests you. there are a lot of kde applications and all
of them can use more attention a
Hi,
I'm a German student who would like to help developing KDE, but whose coding
skills are still limited. I've read the C++/Qt/KDE documentation and already
released my first own program, a todo list manager named DoBeeDo[1], but I
never coded on any bigger application.
Now, my questions:
1)
13 matches
Mail list logo
