My colleague, Rob, suggested that one streamlining possibility was to leave !Qupzilla outside of our !ZillaRAM app – as long as it had been seen by the filer, it would load fairly quickly anyway. This was then copied to a RAMDisc on the machine (the amount of memory available these days means RAMDiscs are easy to utilise) along with the supporting files that are needed.Īfter a bit of experimentation, I realised that the browser itself didn’t need to be run from the RAM Disc to achieve a noticeable speed increase, as long as the Unix support files were located there. One of the things I’d done was to embed !Qupzilla deep in my application sandwich. In discussions online with another RISC OS user who had infinitely better coding skills than me, we thought that he could make some streamlined changes to the multi-layered way I’d originally achieved what I’d wanted for myself – but also a useful RISC OS browser for configuring Wispy V.

And it might have been a good start for someone to take a hold of it, modify it and make it so much better! This “application sandwich” was primarily due to a distinct lack of coding skills. It wasn’t neat, tidy, or clever, but it was functional. QupZilla, as ported to RISC OS by Chris Gransden, is a nice browser for RISC OS, but it lacks a few of the basics that RISC OS users have come to expect: an iconbar icon some indicator of it doing something during the long pause when loading and a little bit more speed! Even as is, it still feels faster than Otter.īeing frustrated by many of these shortfalls, it wasn’t impossible, even for me, to cludge something together that manages all this.

Qupzilla brouser