8:35 a.m.
Dear NetSurf Developers,
I am responding to a message posted to csa.announce on August 9, which
may give you a fair indication of how much time I have to keep up with
developments online. :-(
However, I have been keeping up quite regularly with the NetSurf builds
via SVN. I have made changes to the RISC OS GUI code that I have never
tried to submit. These changes keep rolling over from one SVN update to
the next. For example, I prevent NetSurf from passing left/right
keypresses on because moving the cursor in (say) the address bar would
cause PCITV to change channels. Small stuff, but it does indicate that I
am quite familiar with C and the WIMP. My primary shortcoming as an
assistant would be in the amount of time I can commit.
So just how much work do you estimate will be required to align the WIMP
development with the core? And do you already have plenty of offers from
others with much time to spare?
--
Regards, Christopher Martin.
12:54 p.m.
On Sat, 2009-08-22 at 18:05 +0930, Christopher Martin wrote:
Thankyou for your offer.
So just how much work do you estimate will be required to align the
WIMP
development with the core?
This is difficult to estimate. The RISC OS frontend is currently
blocking a merge of some useful functionality into the trunk, which is
part of the problem -- it's actively getting in the way of core
development now. I'd estimate that fixing this is a few hours work for
someone with the appropriate knowledge.
And do you already have plenty of offers from others with much time
to
spare?
We've had a couple of offers. I've yet to see evidence of anyone doing
more than retrieving the existing sources from SVN and compiling them,
however.
J.
11:12 a.m.
On 26 Aug, John-Mark Bell wrote in message
<1251291254.25111.5.camel@duiker>:
On Sat, 2009-08-22 at 18:05 +0930, Christopher Martin wrote:
Thankyou for your offer.
> So just how much work do you estimate will be required to align the WIMP
> development with the core?
This is difficult to estimate. The RISC OS frontend is currently
blocking a merge of some useful functionality into the trunk, which is
part of the problem -- it's actively getting in the way of core
development now. I'd estimate that fixing this is a few hours work for
someone with the appropriate knowledge.
One thing that wasn't entirely clear to me was what was where in the various
SVN branches (although I may have missed something, as I haven't had
chance to spend long looking around what is on the NetSurf site). Which
branch(es) is the problem code in, and is there any priority as to what a RISC
OS maintainer should be concentrating on looking at?
(Apologies for not asking on IRC. I've so far not had long enough spare in
front of an internet-connected computer to make it worthwhile joining you on
the channel, whereas I do pick up email fairly regularly in between other
things.)
> And do you already have plenty of offers from others with much
time to
> spare?
We've had a couple of offers. I've yet to see evidence of anyone doing
more than retrieving the existing sources from SVN and compiling them,
however.
I'm my case, that's pretty much all I've managed to do so far, although I
have
spent a few hours here and there reading through some of the source code
from the trunk and trying to get my head around what goes where (the notes
which you and others posted here have been very helpful with that, BTW, so
thanks for them).
I'll need some spare time to spend at the computer when I don't have other
deadlines looming to do anything more concrete. All things being equal, I
might get some of that next week -- unless something else comes up in the
meantime.
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
1:38 p.m.
On Thu, 2009-08-27 at 12:12 +0100, Steve Fryatt wrote:
On 26 Aug, John-Mark Bell wrote in message
<1251291254.25111.5.camel@duiker>:
> On Sat, 2009-08-22 at 18:05 +0930, Christopher Martin wrote:
>
> Thankyou for your offer.
>
> > So just how much work do you estimate will be required to align the WIMP
> > development with the core?
>
> This is difficult to estimate. The RISC OS frontend is currently
> blocking a merge of some useful functionality into the trunk, which is
> part of the problem -- it's actively getting in the way of core
> development now. I'd estimate that fixing this is a few hours work for
> someone with the appropriate knowledge.
One thing that wasn't entirely clear to me was what was where in the various
SVN branches (although I may have missed something, as I haven't had
chance to spend long looking around what is on the NetSurf site). Which
branch(es) is the problem code in, and is there any priority as to what a RISC
OS maintainer should be concentrating on looking at?
The current issues are in branches/paulblokus/treeview. I don't think
any of the remaining active branches need fixing for RISC OS.
I've attached a diff of some changes I made that represent the
beginnings of making the treeview stuff in the RO frontend more sane. It
doesn't compile, however, as the menus code (at least) has tendrils
everywhere. It's also missing a bunch of functionality (like any Wimp
bindings for the RO treeview widget; a skeleton is there, but not much
else). It may be simpler to ignore this, although it does give some
indication of the kind of API I envisage for the RO treeview widget
wrapper.
(Apologies for not asking on IRC. I've so far not had long
enough spare in
front of an internet-connected computer to make it worthwhile joining you on
the channel, whereas I do pick up email fairly regularly in between other
things.)
That's no problem.
> > And do you already have plenty of offers from others with
much time to
> > spare?
>
> We've had a couple of offers. I've yet to see evidence of anyone doing
> more than retrieving the existing sources from SVN and compiling them,
> however.
I'm my case, that's pretty much all I've managed to do so far, although I
have
spent a few hours here and there reading through some of the source code
from the trunk and trying to get my head around what goes where (the notes
which you and others posted here have been very helpful with that, BTW, so
thanks for them).
Do shout if there's anything else that's unclear.
J.
4275
days inactive
4280
days old
netsurf-dev@netsurf-browser.org
3 comments
3 participants
participants (3)
-
Christopher Martin -
John-Mark Bell -
Steve Fryatt