[haiku-appserver] Re: investigating some bugs - Rudolf have a look at this please

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Wed, 30 Mar 2005 09:56:34 +0200 CEST

Adi Oanca <adioanca@xxxxxxxxxxxxxx> wrote:
> Axel Dörfler wrote:
> > Adi Oanca <adioanca@xxxxxxxxxxxxxx> wrote:
> >>    About the update code... I would like you to stay aside. As I 
> > > said,
> >>this is next on my list and I'm pretty sure you can find other 
> > > things 
> >>to do.
> >>
> >>    Please, don't touch that code.
> > How come?
> > If you will get to it "in the next few weeks" (as you said earlier) 
> > and 
> > Stephan can do it next, why would you want to hold up development? 
> > That 
> > doesn't make any sense to me.
>       I does to me. I wrote the clipping and invalidate code and made 
> update
> code to _show something_ knowing that this is not always correct, not 
> even talking
> about optimal. Because the window manager was not ready, and I needed 
> that for the
> update code to be complete, I went to write that too. I did some big 
> changes in
> app_server when adding the new window manager, and I will be done 
> shortly
> (a week, 2 max) and then resume work at update code. I don't really 
> see the point
> Stephan getting in my way! There are other things to be done in 
> app_server.

It's not about Stephan getting in your way; he would probably be done 
before you even get there. Anyway, this is a community effort, not a 
competition; you should be thankful for quality help.
Just consider how long you needed to write the window manager code. How 
long will it take you to write new update code given your time 

>       For you to be happy, let's change that into "the next couple 
> weeks".

For me to be happy you'd say: "if he hasn't yet done it in 'the next 
couple of weeks', I'll take over that job when I'm ready". There is 
plenty of other stuff left for you to do as well.


Other related posts: