[haiku-development] Re: R1/a4 initial planning

Why not conzentraition on the basic from haiku
- Network settings
- package manager
- GUI cleanups
- Mediaplayer
- Stable API
- etc ...

I Think a webrowser stuffs need a team of developers to continue working ,
a port of a browser are nice but not realy effective when the developer
stop or paused the work.

stargater

PS: in the futures cames new browser engine smaller of code (after html5),
i see in the plan9 world a webfs. good idear i think.
http://en.wikipedia.org/wiki/Abaco_(web_browser)


Am 22. Februar 2012 22:07 schrieb Ryan Leavengood <leavengood@xxxxxxxxx>:

> On Wed, Feb 22, 2012 at 2:56 PM, Adrien Destugues
> <pulkomandy@xxxxxxxxxxxxx> wrote:
> >
> > Anyway, webkit seems to be the way to go now. It does need a lot of work,
> > but other solutions do as well.
> > Unless we can get someone else than the Haiku devs working on a browser,
> > with more allocated resources ?
>
> I'm pretty motivated to work on this again and with other personal
> projects easing up I should have the time. I think once we are over
> the hump of updating our WebKit and getting the WebPositive source
> into the Haiku repo things will become much easier. I intend to make
> working on Web+ and even WebKit as easy as possible so that there
> isn't just a special group of us who can do it. Eventually I can see
> any Haiku dev popping into the WebPositive code to add something small
> or fix a bug. Now it is incredibly hard to do that because there is a
> huge barrier to entry.
>
> I also think that with Git, some workflow guidelines, maybe some other
> tools we can make it much easier to keep our WebKit up-to-date. I did
> already undo the removing of the Haiku port in my copy of the WebKit
> repo, I just need to fast forward that to the latest version, fix all
> the issues and get it building. Easy peasy ;)
>
> --
> Regards,
> Ryan
>
>

Other related posts: