[haiku-development] Re: Ticket #820 (Network preflet)

  • From: Barrett <barrett666@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 21 Apr 2010 14:04:27 +0200

> the whole Network preflet development is a bit unfortunate. Besides your own 
> efforts, there was another effort to resurrect yet another preflet from the 
> src/test/ area of the tree. At the time, it wasn't clear how all this would 
> unfold. Myself and a few others have tried to give feedback on the Network 
> preflet development in general, but it appears no one, including the people 
> who have worked on the code, is persistent enough with this issue to push it 
> to be finally resolved. I absolutely can see how this may be frustrating to 
> you, but sometimes you have to stubbornly find your way into the project. 
> When I first became involved with Haiku, I thought I can drop the drawing 
> backend code for the app_server and people would be all over it to get it 
> integrated into the app_server. This wasn't at all what happened and so I had 
> to become much more involved and take matters into my own hands, so to speak.
>

I understand, i'm trying to find my way in the project : )
unfortunately the previous (6 months ago) discussion was a little
disheartening for me. But it is my own personality.

Looking at trac seems that anyone committed some code from the actual
preflet to the one in tests, you (or anyone) know the current state?

>
> Most important is a preflet which works, at least as good as the current one, 
> and is easy to grasp for the user. Improvements can be iterative. I still 
> have a Haiku trunk on one of my machines where I have included your preflet 
> into the build. But I never got arround to actually giving it a good testing 
> and a good look at the code. I hope it's a consolation that things are not 
> only frustrating for you, but also for me (and I presume other core 
> developers) when we don't find the time to work off all the stuff that piled 
> up on our TODO lists.
>
> Just try to keep at it. Eventually, when you have something that works well 
> (just announce when it's ready for testing) and the code is decent and 
> follows the coding style, I am sure that you can get this into SVN.

My priority is to exclude a duplicate work, i have also other things
in mind and i'm restarting to work on this only to don't delete my
code with the idea that maybe my code was not so bad.

Thanks for help ; )

Other related posts: