It seems like netsurf is a great candidate for providing HTML based UI in apps. Is this something anyone has tried from a technical point of view?
Does the current licensing support this for paid for apps or is netsurf licensable for such purposes?
I was trying to run the netsurf source code. I got an error saying
libnsbmp library not installed. I downloaded it's package and tried to
run the make file in the package but it is also giving an error
"Makefile.top : no such file or directory". What should I do?
I am a student developer from New Delhi, India. I just went through the GSoc ideas page of NetSurf and would like to start my contribution journey by submitting a few patches. I went through the list of bugs and I wish to submit a patch to the bug 0002078: Slow shutdown.
Which emulator should I prefer for RISC OS or are there any other solutions as well?
I noticed the Haiku build fails:
In file included from
error before `new'
Can someone change this argument to "nw" or anything else so I don't
have to do ugly things like #define new new_ #include ... #undef new ?
Please reply to the list and not directly to me. Thanks.
On Wed, Feb 12, 2014 at 06:05:28PM +0100, Ralf Junker wrote:
> On 12.02.2014 17:01, John-Mark Bell wrote:
>> On Tue, Feb 11, 2014 at 05:10:35PM +0100, Ralf Junker wrote:
>>> Hence I believe that the "has_children" callback could (and should?) be
>>> removed from the hubbub_tree_handler.
>> That would be an ABI break, which we strive to avoid. However, the next
>> release of Hubbub already breaks the ABI in other areas, so I'm inclined
>> to take the opportunity to remove that treebuilder callback entry.
> I am all for it, unless ...
>> Of course, it might resurface later, should we ever get around to
>> bringing Hubbub's implementation back in line with the specification.
>> Somewhat embarrassingly, it's nearly 5 years out of date.
> ... Hubbub requires the has_children callback to meet the specification.
> If so, I would prefer to leave it in now to avoid ABI breaks in the
Well, fundamentally, I don't think we're anywhere near a position where
the Hubbub's ABI can be called stable, regardless of this specific case.
5 years of specification changes will have a great deal of impact. Until
Hubbub is updated, it's almost impossible to know what will change.
> Since documentation is somewhat scarce, could you name parts of the
> specifications Hubbub currently does not conform to? I am not asking for
> an exhaustive list, just some clues to give me a rough idea.
The only part of the HTML specification which is relevant to Hubbub is
the chapter on parsing (and anything it references). I'm not going to
quote the section numbers, as that's liable to change as the
As docs/Updated states, the last time Hubbub matched the specified
behaviour was 2009-03-10. The specification has changed a great deal
since then (and no, we have not done a gap analysis to see where the
I've finally managed to get a working patch for libcurl's threaded DNS
resolver, so I've updated the ppc-amigaos toolchain.
If somebody can give Jenkins a prod so it rebuilds the ppc-amigaos
toolchain that'd be great. :)
In Hubbub, the "has_children" tree callback is never used.
It is defined in hubbub\include\hubbub\tree.h, line 286.
With that line commented out, Hubbub still compiles fine and tests pass
Hence I believe that the "has_children" callback could (and should?) be
removed from the hubbub_tree_handler.
What do NetSurf developers think?
On Sat, 08 Feb 2014 23:06:56 +0000, Commit Mailer wibbled on for an age:
> + /* Front end /really/ should not be doing this. */
> - bw->history = history_create();
> + bw->history = history_create(bw);
Yes, I know. But this is the only way to convince a new (blank) tab
to have new history.
I did have a nose around in the core at the time but it didn't look
like an easy thing to add/fix there (although I forget why not).
Can anyone who has an open bugs in our tracker  please go and review
We have almost 200 outstanding bugs and it is very hard keeping on top
of them. An number of older bugs are awaiting feedback from the
reporter or no longer apply to current versions.
If you have a bug like this please, please assist us by replying with
requested feedback or adding a note that simply says if the issue is
still reproducible. We are trying to get on top of the bugs for the
next release bug your assistance is appreciated.
As previously mentioned all old accounts and bugs have been imported
from sourceforge but if you no longer remember your user name, have
access to your sourceforge email or other issues logging in just
contact us  (please no direct email as it will just add work for us
forwarding it to the role address).
 http://bugs.netsurf-browser.org/mantis/my_view_page.php (select "Reported by Me" link)
On Mon, 3 Feb 2014 00:14:26 +0000, Vincent Sanders wibbled on for an age:
> It should *only* be used by front ends when using the gui tables,
> probably only from the modules actually implementing them. Currently
> there are a number of frontend headers which it appears include
> desktop/gui.h unnecessarily, these are:
I tried to remove it, but it needs desktop/gui.h for the gui_drag_type