Since the old treeview was inefficient, a bit flaky, and difficult to
maintain, we've been planning to replace it for some time.
I have a treeview rewrite in progress which is quite advanced, and I've
just pushed what I have done so far. Currently this is a new generic
treeview module, a partial new global history module, and a hack in the
old treeview for testing the new one.
To see the new treeview in action, either set temp_treeview_test:1 in the
Chocies file, or pass --temp_treeview_test=1 when you execute NetSurf.
With this option set, the global history treeview test can be found in the
hotlist/bookmarks/favourites window. You can have the old and new global
history treeviews open side-by-side.
Any feedback welcome.
A few more notes follow.
On a 600MHz XScale, the new global history treeview builds much faster
with my current 326kB of URL file.
(2.440000) desktop/global_history.c global_history_init 657: Loading
(2.600000) desktop/global_history.c global_history_init 709: Loaded
(2.690000) desktop/history_global_core.c history_global_initialise 281:
Building history tree
(4.020000) desktop/history_global_core.c history_global_initialise 288:
History tree built
That's 0.16s vs. 1.33s. The new one is probably fast enough that we could
get away with making the global history treeview when the global history
window is opened, rather than generating on startup.
RISC OS treeview drags
Seems that the RISC OS front end doesn't pass the mouse coordinate to the
core during drags in the treeview window, which is making the drag
behaviour there a bit peculiar.
Single click on the expand/contract arrow toggles its expansion.
Single click on text/icon selects it.
Double click on a directory toggles its expansion.
Double click on an entry will "launch" it.*
Drag from an empty area starts a selection.
Drag from text/icon region will start a move drag.
Drag from anywhere in a selection will start a move drag.
First mouse button creates new selection.
Second mouse button modifies a selection.
Keyboard shortcuts for select all, clear selection, and delete selection
* Global history doesn't implement the launch callback msg yet.
Global history TODO
- Need to implement launch message handling
- Need to implement node deletion message handling (so the delete actually
- Need to make browser window update the new global history code as you
1. Get some feedback.
2. Address feedback.
3. Finish new global history.
4. Change global history to use new treeview, removing temp test option.
5. Implement bookmarks, ssl cert chain viewer and cookie manager
with new treeview. Need to add various features to the treeview,
such as read-only mode, node movement drags, etc.
Up to and including step 5, there will be no changes in the front ends...
the old tree stuff will be wrapper layers for the new stuff.
6. Change front ends to use new treeview stuff directly.
Somewhere before step 6, I intend to change the interface for the using
the new treeview features a bit (core_window stuff).
Michael Drake (tlsa) http://www.netsurf-browser.org/
I hope that this is not a waste of the list's time ....
I have successfully installed Enlightenment 17 for my build and I have
chosen Netsurf as the web browser.
However, when trying to install Netsurf under the command of "*make install
[PREFIX=/usr]*" the process stops at "*gtk/Makefile.target:25. *** unable
to find library for : BMP libnsbmp. Stop.*" But the *libnsbmp* library has
How can I overcome this?
I'm sure that I'm gonna look stupid against what is probably an easy fix.
Would be really grateful if someone can help me out :)
In my opinion Mozilla is not the organzation it used to be. It doesn't
listen to either users or developers. It makes arbitrary changes and
requires web developers to cope. This attitude reflects an abberant power
imbalance felt by Mozilla between them and their users.
Rather than hope for a change in attitude at Mozilla, I think the org
should be replaced with a project which more accurately incarnates
progressive ideals. I think NetSurf could well be it. I must say, I am
impressed with its project breadth: Amiga and even Atari... that's
impressive. I remember that there were ports of Firefox to the GP2X
handheld, before Gecko became too obfusticated to port, and looking at
these home computer ports I think I see that same spirit. I also like how
you are using libraries, as opposed to IBM's XP-COM unqualified disaster. I
notice that you are lacking in areas, however, which Mozilla dealt with
long ago, with C-based libraries that have been successfully implemented.
engine, as they were in SphereRPG, which used SDL and SpiderMonkey side by
side. With respect to HTML 5, I think you may want to question your
dependence on it, because with few exceptions the standards process has
been taken over by Google and is being biased towards its interests. These
interests are not necessarily accessory to a "better web".
I think standardization compliance is a red herring; rather, I think the
future lies in passion and leverage of popular values. However it would be
a mistake to engage in "browser war" -- people who use Firefox do so
because they detest Microsoft, Google, and Apple all. What we want is an
alternative to Mozilla and its modus operandi... if the sites and apps we
make won't run on other browsers, then they should use ours. Google's
aggressive adherents are the real secret to its success... responding to
their attitude in kind could pay dividends for Netsurf.
Thanks to the Secretary and Treasurer for their continued work in
these roles this past year.
Year in review
During last year we launched NetSurf 3.0, the first release to
incorporate our DOM library.
We migrated the project's version control from Subversion to Git,
and changed the core buildsystem.
The project's old autobuilder has been completely replaced with a
Jenkins based Continuous Integration system, which automatically
builds NetSurf and our libraries for various platforms. It also
does automated testing, produces test coverage data, and static
The new CI system now reports build failures in our IRC channel.
With the discontinuation of the CIA.vc service, we have lost commit
notifications on IRC.
The big change in NetSurf 3.0 was the use of our new Document Object
Model library, LibDOM. This new library is a foundation that paves
the way for us to implement a fully dynamic layout engine in the
Other improvements included in the release included new textarea
support, ability to fetch and parse CSS in parallel with HTML
documents, extensive behind-the-scenes refactoring, and a host of
smaller changes and fixes.
Since NetSurf 3.0 was released several areas have been developed.
Background image handling has been revamped to minimise redraw area,
to handle animated background images, and to cope with image
conversion failure. Textarea redraw has been optimised to minimise
redraw area. Visited links are now styled correctly. A bloom
filter utility module has been added which is currently used to
optimise urldb lookups. The handling of user options has been
rewritten to better support changes to the default values and the
system colour settings.
Since the existing treeview is plagued by bugs and poor performance,
it is in the process of being rewritten. The new treeview code is
largely finished, with the the new global history and cookie manager
modules already completed.
The main plan for NetSurf's development since NetSurf 1.x has
been shared widely before. Here it is again:
| 1. New HTML parser (hubbub)
| 2. New CSS engine (libcss)
| 3. New DOM implementation (libdom) < We are here now
| 4. New layout engine
|  was introduced with NetSurf 2.0
|  was introduced with NetSurf 2.5
|  was introduced with NetSurf 3.0
|  is intended for NetSurf 4.0
|  is intended for NetSurf 5.0
support has already been started, NetSurf 4.0 will have both
we could combine step  into step .
The next 12 months
We are planning a NetSurf 3.1 release once the HTML forms handling
has been rewritten as opaque DOM driven widgets. The treeviews will
be transitioned over to the new implementation soon, so this feature
is also likely to make NetSurf 3.1.
As for LibDOM, there remain many interfaces that are unimplemented,
especially for the HTML element specialisations. Some parts of
LibDOM can also be removed.
Long term there are two main areas of focus for future development:
engine needs planning.
+ Improving/fixing what we've already got. There are various
issues that we have. The most striking being our CSS selection
performance, which has dominated profiling reports for the last
Thanks to everyone involved in the project for their contributions over
the last 12 months!
Michael Drake (tlsa) http://www.netsurf-browser.org/
NetSurf Society Financial Report, August 2013
This is a summary of the society's financial status as of 2013-08-04.
The sole source of income since the last report (2012-06-16) has been
the takings from sales of NetSurf at the Wakefield 2013 show.
All outgoings have been in the form of reimbursements for
project-related activities or show stand bookings.
As resolved at the 2010 AGM, the society will now pay up to 15 pence per
mile for mileage.
Balance carried forward: 1651.28
2013 Wakefield Show sales 290.00
Michael Drake -- train tickets:
EDB->WKF->EDB Wakefield 2013 (70.00)
415 miles RDG->WKF->RDG Wakefield 2013 (62.25)
Hosting for CI system (114.82)
Wakefield 2013 stand + chairs (46.00)
Remaining Funds: 1648.21