On Sun, 2009-09-27 at 12:59 +0100, Gavin Wraith wrote: > In message <1254051536.30649.2.ca...@duiker> you wrote: > > > As for whether it's intended behaviour or not, I can't recall, I'm > > afraid. I suspect it is intentional, otherwise I can't imagine why > > effort would have been expended implementing it. > > Perhaps "intend" covers a range of possibilities, incorporating > different levels of forethought ;). Does the core enforce an > upper bound on the number of windows opened?
No. There's no such artificial limit. > Unless rather unusual display facilities are to be catered for, I > cannot imagine anybody wanting more than, say, 32 windows open at > the same time. Well, on those platforms where tabbed browsing is supported, the core makes no distinction between a tab and a window. Many people have hundreds of open tabs in Firefox, for example. Thus artificially limiting the number of windows in NetSurf seems counterproductive. > > This is one of the things that has been moved into the core code, but we > > can't merge it because it will break the RISC OS frontend. > > Again, apologies if this has already been covered. Is it easy to deduce > from the core code what sort of API a new, more compliant, version (of > the RISC OS frontend) should expose? Is there a header file (or group > of header files) that constitute the common interface between the > core and the several platforms? The treeview is documented here: http://wiki.netsurf-browser.org/Documentation/Treeview The hotlist, cookies, global history, and ssl certificate display APIs can be found in the relevant header files in the desktop/ directory. You'll need to check out the following branch, as the relevant changes to the core are not on trunk, as already explained: svn://svn.netsurf-browser.org/branches/paulblokus/treeview J.
