On Tue, 2009-09-01 at 14:00 -0700, WP Blatchley wrote:

> Many thanks for posting that diff - I've been studying it, and it's
> made a few things clearer to me.
> 
> I have some very basic questions, if anyone's got time to answer them:
> 
> 1) How can I check out from SVN a different branch to the main one? 

Specify the branch URL instead of trunk. For Paul's treeview branch,
this would look something like:

svn co svn://svn.netsurf-browser.org/branches/paulblokus/treeview

> I've only used CVS up to now. Would the best way to tackle getting the
> treeview core stuff to work with the RISC OS front end be to check out
> the treeview branch and work on that until it compiles and runs on
> RISC OS, and then merge that back into the trunk?

Yes. The rest of that branch needs merging to trunk, too. Thus, you'll
need to work with that branch to get the RO treeview stuff working.

> 2) I'm right in thinking that at the moment, the RISC OS version uses
> its own tree view code for the history and cookies displays, but that
> you've created target-independent treeview code in the core now and
> RISC OS needs to ditch its own code and just use the core code.

That's about right, yes. Frontends have enough to implement without
duplicating such functionality.

> 3) If so, is there more detail about the interface to the core's new
> treeview code?

Besides doxygen commentary, there's:

http://wiki.netsurf-browser.org/Documentation/Treeview

Beyond that, ask here :)

> 4) Is there any form of debug build for RISC OS?

Not really, no. The best that's currently achievable is:

a) LOG(())
b) Build with GCC4.1 and CFLAGS=-g -O0, then use gdbserver in
conjunction with another machine.

The latter approach isn't all that great right now so I don't recommend
it tbh. GDBServer could do with some love, for starters.


J.


Reply via email to