Re: NetSurf 3.8 release

On 2018-07-30 11:32, Vincent Sanders wrote:
> I intend to make the 3.8 release on Friday the 3rd of August 2018
>
> If any developers have pending bugfix or features they intend to merge
> for the 3.8 release and need additional time please let me know as
> soon as possible.
>
> This release will primarily be to incorporate all the bug fixes from
> the developer weekends and does not contain any major feature updates.

I've only just started looking at the RISC OS bugs so am not in a
position to contribute this time around--maybe next time!

--
xsltpro.co.uk
Technical Writing and Programming Solutions for RISC OS or UNIX

NetSurf 3.8 release

I intend to make the 3.8 release on Friday the 3rd of August 2018

If any developers have pending bugfix or features they intend to merge
for the 3.8 release and need additional time please let me know as
soon as possible.

This release will primarily be to incorporate all the bug fixes from
the developer weekends and does not contain any major feature updates.

--
Regards Vincent
http://www.kyllikki.org/

Plotting to bitmaps

There are a few reasons we want to plot to bitmaps:

1. Plotting to thumbnails (which we do already).
2. Plotting Canvas elements.
3. Optimising tiled SVGTiny rendering by pre-rendering SVG to bitmap.

So the plan is:

1. Make NetSurf core depend on libnsfb for its memory backend.
2. Rip the plotter implementation out of the NetSurf framebuffer
front end, and make it a core plot_bitmap plotter interface.
The core can use this, and front ends can choose to use it too.
3. Adjust the rendering pathways so they can take a bitmap to plot
into.

We might consider putting these features behind compile time options.

--
Michael Drake http://www.netsurf-browser.org/

Re: How up to date are NS's CA certs?

On 27 July 2018 16:22:04 BST, David Higton <dave@davehigton.me.uk> wrote:
>A topic that came up recently on csa.apps made me question how up to
>date NetSurf's CA certificate bundle is. A secondary question is if
>there is a well defined process for anybody to maintain such a bundle.
>
>So, devs, what are the answers?
>

They are updated periodically. I think it's in the release preparation now to update them, so they should always be up-to-date for release versions.

Chris

How up to date are NS's CA certs?

A topic that came up recently on csa.apps made me question how up to
date NetSurf's CA certificate bundle is. A secondary question is if
there is a well defined process for anybody to maintain such a bundle.

So, devs, what are the answers?

Dave

Re: m68k Amiga + RISCOS patches

Le 23/07/2018 à 19:47, Chris Young a écrit :
>> Would you mind merging those so they don't get lost?
>>
>> I don't know if I'll get the time to work more on this this summer.
>
> Merged the Amiga one. I can't test the RISC OS changes so I'll leave
> that to others.

Thanks.

I've rebased my other branches.

Btw, it seems like the list rejects my mails now due to my ISP's SMTP
being in the spamcop database :-(

François.

Re: m68k Amiga + RISCOS patches

On Sat, 21 Jul 2018 17:35:37 +0200, François Revol wrote:

> Le 09/07/2018 à 17:05, Chris Young a écrit :
> >
> >
> > On 9 July 2018 16:02:01 BST, "François Revol" <revol@free.fr> wrote:
> >> Le 09/07/2018 à 15:22, Chris Young a écrit :
> >>>
> >>> I thought I'd fixed that but I probably only changed it in my
> >>> gcc6 branch, and actually I thought there was more wrong with the
> >>> 3.4 toolchain than just that!
> >>>
> >>> Unfortunately OpenSSL is still completely broken with Curl* on
> >>> m68k-amigaos and I have no further ideas why.
> >>>
> >>> Chris * By which I mean, OpenSSL itself generally seems to work,
> >>> as does Curl, but accessing secure sites with Curl fails.
> >>>
> >>
> >> Ah, I didn't really try it, just made sure it built completely, as
> >> I'm more on the atari side currently.
> >>
> >> I already rewrote the OpenSSL patch for atari because they changed
> >> their build system, by looking at the Amiga stuff, but didn't try
> >> it yet.
> >>
> >
> > It'll be interesting to see if that works. We have AmiSSL here which
> > is a wrapper for OpenSSL and that works on 68k, so I'm at a loss as
> > to what might be wrong with our build.
>
> Would you mind merging those so they don't get lost?
>
> I don't know if I'll get the time to work more on this this summer.

Merged the Amiga one. I can't test the RISC OS changes so I'll leave
that to others.

Chris