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

List:       kde-devel
Subject:    Re: kdeui again
From:       Chris Schlaeger <cs () alpha ! tat ! physik ! uni-tuebingen ! de>
Date:       1999-06-08 2:21:13
[Download RAW message or body]

I totally agree with you, so let me explain what I meant. "don't have
time" means I am at work right now and I'm not getting paid to work on
KDE. It also means that my changes cause some apps to crash and that
KOffice has a very ugly layout. Given the complexity of the changes
this was expectable as much as I like to avoid these situations. I
cannot compile and test each and every KDE app before commiting
stuff. Having just a few hours in the evening this is just not
practical.

So if someone finds something that my changes broke, tell me about
it. I very much appreciate this and will put it on my list and fix it,
no question. If you want it fixed right away, fix it yourself or
check-out an ealier version. That's what CVS is for.

In this particular case it takes about 5 minutes to fix it. I posted
the workaround yesterday and today on this list and it is documented
in KDE2PORTING. The source contains an appropriate comment as well.

Don't get me wrong. I hate it as much as everybody else when I
checkout stuff and it does not compile or segfaults before you even
see a window. KDE2 is alpha software. If we want to improve it we
potentially break it. KTMainWindow and KToolBar were in not too good
shape when I started the work. I hope my work will improve this
situation and make a good base for new features (Sven will be
adding ;) ). Working on the core piece of nearly every KDE app any
problem has a high visibility. I pretty much know what I'm doing here,
so bare with me and expect the new features that are about to come.

Now let's do some real work again!
Chris


On Tue, Jun 08, 1999 at 10:57:11AM -0400, pbrown@redhat.com wrote:
> On Tue, 8 Jun 1999, Chris Schlaeger wrote:
> 
> > view_* public variables do no longer exist. There is really no reason
> > for an app to use this information. If you do need it anyway, use
> > mainViewGeometry() instead.
> > 
> > Can you or someone else fix this, please. I don't have time right now.
> 
> PLEASE do not break things and then ask someone else to fix them because
> you are "out of time."  You are allowed to slowly ADD features when you
> are short on time, but never BREAK things when you have time and then fail
> to eitiher 
> 
> 1) document how to fix someone's code
> 
> 2) provide an alternative implementation
> 
> because you are short on time.  It is COMPLETELY CRIPPLING to other
> developers and puts us on YOUR SCHEDULE, which really isn't fair when it
> can be avoided.
> 
> We all appreciate your efforts of fixing geometry management in the
> MainWindow class.  But when you are programming in the libraries, you must
> always keep in mind that your changes affect many other programmers, and
> work accordingly.
> 
> ---
>   Preston Brown                                    Systems Engineer
>   pbrown@redhat.com                                Red Hat, Inc. 

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