Re: Atari build

V V ned., 31. dec. 2023 ob 00:40 je oseba John-Mark Bell <jmb@netsurf-browser.org> napisala:

> However, the last few versions I had tried would timeout before
> rendering anything.
>
> That was why I was still using build 5366 from 2022.
>
> Yesterday I installed 6637 and it still gives Timeouts. The only page
> that would work was http.  I increased the curl timeout to 300 with no
> change.

All of the support libraries have been upgraded in the last year,
including migrating to OpenSSL 3. These are significant changes so may
have introduced some brokenness at some point.

Sadly, the Atari frontend has no maintainer (any changes are mostly to
make it build after changes to other parts of the code) so, although CI
continues to spit out binary builds, these are never tested (and none of
the core developers has any specific Atari knowledge or any appropriate
hardware/emulator so cannot test them, either).

As ever, if someone is able to work out a fix, we'll happily take a
patch containing it!

 

About Atari release.

Latest nightly build works normally on the FireBee browsing https pages included. It takes some time but it renders them nicely!

So I guess the problem with Atari 68060@60MHz is that it timeouts as it is too slow. @Peter, maybe you can try it in Aranym how NetSurf is working?

As the GUI for Atari builds is not updated can someone point me to the description of the options in choices fill so we can edit it with a text editor?

I would like to know mostly how to enable/disable javascript and CSS rendering? I believe those two options would make page rendering faster.

Vido

Brez virusov.www.avast.com

Re: Atari build

On 29/12/2023 12:02, pslegg@scubadivers.co.uk wrote:
> Hi all,
>
> I hadn't updated Netsurf on my Atari 68060@60MHz) since before January.
>
> I have always found the Atari build to be extremely slow, 5-10 minutes
> or more to render a page being normal and I think it's the ssl that
> hurts it most. So it's not greatly usable but I do use it download
> FreeMint OS updates.

60MHz is not very much to work with, tbh, so I am not entirely surprised
that things are slow, particularly given the ever-increasing complexity
of the modern web.

> However, the last few versions I had tried would timeout before
> rendering anything.
>
> That was why I was still using build 5366 from 2022.
>
> Yesterday I installed 6637 and it still gives Timeouts. The only page
> that would work was http.  I increased the curl timeout to 300 with no
> change.

All of the support libraries have been upgraded in the last year,
including migrating to OpenSSL 3. These are significant changes so may
have introduced some brokenness at some point.

Sadly, the Atari frontend has no maintainer (any changes are mostly to
make it build after changes to other parts of the code) so, although CI
continues to spit out binary builds, these are never tested (and none of
the core developers has any specific Atari knowledge or any appropriate
hardware/emulator so cannot test them, either).

As ever, if someone is able to work out a fix, we'll happily take a
patch containing it!


John-Mark.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Re: NetSurf 3.11 Released

In article
<CAEEy9dZqxm9OK5GEy75=uxu5f5a=7UHmW10jOb6q+tf1VoSrEA@mail.gmail.com>,
Michael Drake <tlsa@netsurf-browser.org> wrote:
> NetSurf 3.11 is now available to download from

> https://www.netsurf-browser.org/

> The biggest change to the core is improved CSS support, including
> support for the "display: flex" property value, which improves the
> layout of some web pages. There is also a new option in the Choices
> to disable CSS.

> A huge number of other changes have also been made including
> new features, significant performance optimisations, stability
> improvements, and other fixes.

[Snip details]

Many thanks, much appreciated.
B

--
_____________________________________________________________________

Brian Jordan
brian.jordan9@btinternet.com
RISC OS 5.28 (16-Dec-20) on Raspberry Pi
_____________________________________________________________________
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Atari build

Hi all,

I hadn't updated Netsurf on my Atari 68060@60MHz) since before January.

I have always found the Atari build to be extremely slow, 5-10 minutes or more to render a page being normal and I think it's the ssl that hurts it most. So it's not greatly usable but I do use it download FreeMint OS updates.

However, the last few versions I had tried would timeout before rendering anything.

That was why I was still using build 5366 from 2022.

Yesterday I installed 6637 and it still gives Timeouts. The only page that would work was http.  I increased the curl timeout to 300 with no change.

Peter

NetSurf 3.11 Released

NetSurf 3.11 is now available to download from

https://www.netsurf-browser.org/

The biggest change to the core is improved CSS support, including
support for the "display: flex" property value, which improves the
layout of some web pages. There is also a new option in the Choices
to disable CSS.

A huge number of other changes have also been made including
new features, significant performance optimisations, stability
improvements, and other fixes.

Change Log
==========

NetSurf 3.11
------------

### Core / All platforms

* HTML: Fixed failure to reflow SVGs if fetched and ready before layout.
* HTML: Support for `display: flex` layout.
* HTML: Improved minimum/maximum sizes in box layout.
* HTML: Improved handling of percentages.
* HTML: Minor cleaning up of layout code.
* HTML: Use new LibCSS API for unit conversion.
* HTML: Improved ordered list handling.
* CSS: Updated selection callbacks to latest LibDOM API.
* Options: Added core option to disable CSS.
* Options: Added core option to prefer dark mode.
* Options: Improved user choices file processing.
* Bitmap: Opaque testing now implemented in core.
* Bitmap: Added core support for premultiplied-alpha.
* Bitmap: Format logged on startup.
* Bitmap: Added support for pixel colour component order configuration.
* Bitmap: Added colour component order conversion functions.
* Bitmap: Generally more optimal on all platforms for all image formats.
* Image: JPEGXL image handler.
* Image: Compatibility with latest rSVG version.
* Image: Improved handling for broken GIF images.
* Image: Updated to new LibNSGIF API.
* Image: Updated all image format handlers to use new core bitmap capabilities.
* Fetch: Updated to new libcurl API.
* Fetch: Disabled TLS1.0 and TLS1.1.
* Fetch: Improved handling of bad SSL connections.
* Fetch: Change to libcurl to optimise HTTPS connections (upstreamed).
* Local history: More robust rendering.
* Resources: Updated certificate bundle.
* JavaScript: Minor updates to DOM bindings.
* JavaScript: Updated to Duktape 2.7.0 release.
* JavaScript: Console: Don't log through closed window.
* Utility: Cleaned up UTF8 handling.
* Utility: Improved recursive directory removal.
* Utility: Add support for xx_YY format language codes.
* CI: Various improvements to build automation and testing.
* General: Various warning fixes.
* General: Aligned UserAgent with compatibility spec.
* Documentation: Updated URLs to https.
* Documentation: Added front-end development guide.
* Text areas: Clear selection on word left/right.
* Buildsystem: Fixed handling of removed header files.
* Disc cache: Minor fixes.
* Debug: Added generated charts to image cache stats page.
* Debug: Added descendant bounding boxes to HTML box tree dumps.
* Built in: Cleaned up generated `about:` pages.

* LibParserUtils library 0.2.5 (parser building utility functions):
- Optimised consuming from buffer.
- Optimised endian detection.
- Added new API to append vector to buffer.

* Hubbub library 0.3.8 (HTML parser):
- Massively optimised element type detection using perfect hash.
- Optimised and updated performance tester.
- Fixed bitrot in tests.
- Improved example client code.
- Buildsystem improvements.

* LibCSS library 0.9.2 (CSS parser and selection engine):
- Added support for SVG `fill-opacity` property.
- Added support for SVG `stroke-opacity` property.
- Added support for CSS property wide `revert` value.
- Added support for CSS property wide `unset` value.
- Added support for CSS property wide `initial` value.
- Added support for CSS `position` property `sticky` value.
- Added support for CSS `display` property "grid" values.
- Added support for `prefers-color-scheme` media query.
- Added new public API for CSS unit conversion.
- Added support for predefined counter styles.
- Optimised media query handling.
- Made selection code generator deterministic.
- Various selection code generator improvements.
- Squashed leak of system font names.
- Improved internal handling of property units.
- Improved internal string map.
- Minor buildsystem improvements.
- Improved example code.
- Added new tests.

* LibDOM library 0.4.2 (Document Object Model):
- Fixed XML parser error handling.
- Fixed XML parser empty document handling.
- Added DOMTokenList implementation.
- Added DOM tree walking function.
- Improved example code.
- Fixed HTML Element int32 attribute getter to handle signed values.
- Various stability improvements.
- Buildsystem improvements.

* LibNSGIF library 1.0.0 (GIF support):
- Complete rewrite.
- New API that doesn't expose internal state.
- Much better handling of bad or broken GIFs.
- Support for decoding to client's choice of pixel colour component order.
- Many fixes.
- Faster decoding.
- Updated documentation.

* LibSVGTiny library 0.1.8 (SVG support):
- Fixed X11 example utility build.
- Implemented path arc correctly.
- Updated documentation.

### RISC OS-Specific

* Removed last vestiges of plugin support.
* Added Choices option to disable CSS.
* Updated licence information.
* Updated links to use https in documentation.
* Fixed broken links in documentation.
* Support for building with `arm-riscos-gnueabi` toolchain.
* Updated bundled resources.
* Improved bitmap rendering.
* Fixed EX0 EY0 "high DPI" rendering.
* Text selection support in URL bar (RO5.28 onwards).
* Dragging favicon saves whole URL.
* Updated to new RUfl API.
* Fixed font scanning on startup behaviour.
* Unified redraw code for browser windows and other core-rendered windows.
* Fixed auto-scroll crash when pointer leaves core window.
* Allow drag and drop loading of WEBP image format.

* RUfl library 0.1.0 (RISC OS Unicode support):
- Added astral character support.
- RUfl_cache version now in filename.
- Support for multiple versions of RUfl_cache coexisting.
- Substitution table reworked for astral characters and heavily optimised.
- Render 6-digit replacements for codepoints outside Basic Multilingual Plane.
- Refactoring and many code improvements.
- Support for UCS-aware Encoding files.
- Various API changes.
- Detect overlong and invalid UTF-8 sequences.
- Improved compatibility with different Font Manager versions.
- Fixed menu building to cope with system with no fonts.
- Ignore UCS fonts if using a non-UCS Font Manager.
- Remove assumption that pointers are 32-bit.
- Added test infrastructure and many tests.
- Buildsystem improvements.

### GTK-Specific

* Cleaned up initialisation.
* Various build warning fixes.
* Fixed crash when destroying scaffolding.
* Don't create zero-sized bitmaps.
* Configure core to use Cairo's bitmap format.
* Added support for cursor word left/right key bindings.
* Added support for delete word left/right key bindings.
* Added back/forward mouse button processing.
* Fixed path plotter.
* Made UI resources more consistent.

### Amiga-Specific

* Added page theme option.
* Improved bitmap handling.
* Improved and optimised Unicode handling.
* Stability improvements.

### Windows-Specific

* Buildsystem: Use pkg-config.
* Support Ctrl+A in address bar.

### Framebuffer-Specific

* Minor internal font fixes.
* Improved documentation.

Also included are many smaller bug fixes, improvements and
documentation enhancements.


Best regards,
The NetSurf Team
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

[Rpcemu] Real floppy support

RPCEmu is a very good program but I miss real floppy support.


Micky

_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Re: [gccsdk] GCCSDK 10 for older cores

On 22/04/2022 17:29, Steffen Huber wrote:
> Hi,
>
>> Rob Kendrick <rjek@rjek.com> wrote:
> [snip]
>> Is building code for ARMv3 (or v4?) supported and I'm being an idiot, or
>> is this totally out of scope of the endeavour?
>
> No idea about the GCCSDK details, but from a GCC-ARM-backend perspective,
> ARMv4 and everything-non-Thumb-before-ARMv6 was deprecated I think in
> GCC 6, so I guess it was removed from the ARM backend in one of the
> later versions.

Certainly, ARMv4 (no T) is still deprecated in GCC 13. Support remains,
however (my understanding is that removing it will necessitate removing
support for various StrongARM variants and there was push-back against
that when all the other non-Thumb architecture variants were removed in
2018). So, in practice, it's still there, is understood, and produces
the code you would expect.

[Aside: you could still probably get away with using ARMv4T here anyway
and building all the compilation units in ARM mode as no interworking is
actually necessary].

[...]

> So unless you re-add the support to the ARM backend, I guess you
> are out of luck and need to go back to GCC 4.7.x for old ARM
> architecture compatibility.

There is still one gotcha if you want to support Acorn hardware: the
RiscPC bus doesn't support halfword (16bit) accesses, so LDRH/STRH do
not work. Teaching the compiler not to emit these instructions turns out
to be fairly trivial, however.

Some time ago, we put all of this together to produce a GCC10-based
toolchain that will build for ARMv4 (using softfloat) and using EABI
calling conventions. The resulting binaries (whether statically or
dynamically linked) require ARMEABISupport and so require RISC OS 5
(unless I've misinterpreted ARMEABISupport's use of the PMP dynamic area
APIs). In terms of hardware compatibility, StrongARM RiscPCs are the
minimum thing supported (as ARMv4 is the minimum supported architecture,
all ARM610/710/7500(FE)-based systems are ruled out but all other
post-Acorn systems should be fine).

The full set of changes can be found at:

https://git.netsurf-browser.org/toolchains.git/tree/arm-riscos-gnueabi/

and the commit messages are probably reasonably instructive as to what
is changing and why:

https://git.netsurf-browser.org/toolchains.git/log/arm-riscos-gnueabi

(The squash-merge introducing the toolchain is disaggregated here:
https://git.netsurf-browser.org/toolchains.git/log/?h=jmb/arm-riscos-gnueabihf
in case that's of use to anyone)

As implied by the directory name, the system triplet
(arm-riscos-gnueabi) differs from the arm-riscos-gnueabihf used by the
GCC10 in the autobuilder (as the ABIs are *not* compatible -- the "hf"
one requires ARMv7 and VFP hard float). This is reasonably analogous to
the Debian armel/armhf architecture split, so should not be unreasonably
confusing.

John Tytgat's original GCCSDK makefile was resurrected as part of this
work, so it builds in pretty much the same way as the GCC 4-based GCCSDK
does (which much better fits the NetSurf toolchain requirements than the
rules in the autobuilder).

Most of the other patches should be fairly obvious (the POSIX locales
one was upstreamed aeons ago, so is already in UnixLib proper). There
are probably two items that deserve special mention:

1. elf2eif has had some significant surgery to ensure that static
binaries using EABI work properly:
a: enabling ARMEABISupport's abort handling at process start
b: ensuring that the GOTT_BASE pointer at &8038 is filled in

2. UnixLib's stack unwinding has been reworked significantly for the
EABI case (and refactored in the APCS case). Successful EABI unwinding
requires the presence of unwind tables (i.e. building with
-funwind-tables), however.

Hopefully this is of use to somebody!


John-Mark.

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [Rpcemu] Linux Home driretory next to my HostFS drive

On 18/11/2023 12:55, riscos@markerdesign.be wrote:
> Hello,
>
> I have two versions of RPCEmu running on my Linux laptop and have
> created Symlinks to access my USB drives. So far, so good, so happy.
>
> Now I would like the Linux Home directory to appear next to my HostFS
> drive on the taskbar, and or is there a way to make symlinks appear on
> the taskbar (either as a folder or as a drive).
>
> Does anyone have any experience with this?
>
Just noticed this, dunno if you worked it out yet? You don'd say what
RISC OS you are running or indeed which RPCEmu .

Using RISCOS 3.7 here and 0.9.4.  To achieve what it sounds like you are
after, you could create a symbolic link inside your HostFS directory,
pointing to your home directory. Then use 'AddTinyDir'.

From the command line, something like;

AddTinyDir HostFS::HostFS.$.Home

where home is the symbolic link you created. Create an obey file and
have it run on each boot to make it persistant.

I think pinboard in RISC OS 5 can do that.

--
Michael Howard.

_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Re: allocator_claim_pages:449

On 1 Dec 2023 as I do recall,
John-Mark Bell wrote:

> On 01/12/2023 09:57, Martin Avison wrote:
> > In article <8e67b10b5b.harriet@bazleyfamily.co.uk>,
> > Harriet Bazley <lists@bazleyfamily.co.uk> wrote:

[snip]


> >> allocator_claim_pages:449 - Unknown dynamic area
> >
> >> Reporter 2.72 (15 Aug 2020) Listed 10 lines
> >
> > They do not look like messages caused by a RISC OS error being raised,
> > but more like messages produced by a specific Reporter call within
> > the program.
>
> These appear to emitted by the ARMEABISupport module. There is, to my
> knowledge, no "official" release build of this, so we made sure to
> provide the same binary as was being shipped by other applications to
> ensure that everything was consistent. That may well mean that it's
> actually a debug build of the module, hence the logging.

Yes, I got 'unknown dynamic area release'-type messages later, when I
had to Alt-Break Netsurf. (Doesn't seem to happen on a normal quit.)

--
Harriet Bazley == Loyaulte me lie ==

The saddest words in the English language are 'Too' and 'late'
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Re: allocator_claim_pages:449

On 01/12/2023 09:57, Martin Avison wrote:
> In article <8e67b10b5b.harriet@bazleyfamily.co.uk>,
> Harriet Bazley <lists@bazleyfamily.co.uk> wrote:
>> Since downloading v6511 of Netsurf I keep seeing "Unknown dynamic
>> area" errors pop up in my Reporter window. These are 'silent'
>> errors that don't generate a WIMP error box, so presumably the user
>> is not supposed to be aware of them, but it gives the impression
>> that the app is running out of memory....
>
>> Reporter 2.72 (15 Aug 2020) List Fri 1st Dec 2023 01:11
>
>> 01:06:46.54 ** Clear ** from Menu
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>> allocator_claim_pages:449 - Unknown dynamic area
>
>> Reporter 2.72 (15 Aug 2020) Listed 10 lines
>
> They do not look like messages caused by a RISC OS error being raised,
> but more like messages produced by a specific Reporter call within
> the program.

These appear to emitted by the ARMEABISupport module. There is, to my
knowledge, no "official" release build of this, so we made sure to
provide the same binary as was being shipped by other applications to
ensure that everything was consistent. That may well mean that it's
actually a debug build of the module, hence the logging.


John-Mark.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Re: allocator_claim_pages:449

In article <8e67b10b5b.harriet@bazleyfamily.co.uk>,
Harriet Bazley <lists@bazleyfamily.co.uk> wrote:
> Since downloading v6511 of Netsurf I keep seeing "Unknown dynamic
> area" errors pop up in my Reporter window. These are 'silent'
> errors that don't generate a WIMP error box, so presumably the user
> is not supposed to be aware of them, but it gives the impression
> that the app is running out of memory....

> Reporter 2.72 (15 Aug 2020) List Fri 1st Dec 2023 01:11

> 01:06:46.54 ** Clear ** from Menu
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area
> allocator_claim_pages:449 - Unknown dynamic area

> Reporter 2.72 (15 Aug 2020) Listed 10 lines

They do not look like messages caused by a RISC OS error being raised,
but more like messages produced by a specific Reporter call within
the program.

Martin
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org