Re: Not enough application memory to start Basic

On 14/06/14 13:48, David Pitt wrote:

> > All the NetSurf needs to run its cache is a value for Cache$Dir
> > pointing to the chosen location.

Indeed. The original proposal for Cache by Rob Kendrick[1] simply set
two variables in its !Run file. These were:

Caches$Write - Expands to where you should write new cache data
Caches$Path - Expands to where you should read cached data

We recently decided to make use of "!Cache" as we assumed it would be
suitable and correct. (None of the core developers are actually using
RISC OS at the moment, so we hadn't checked it actually worked.)

Looking at the content of the supplied "!Cache" it seems to contain a
lot of extra stuff and unexpected complexity.

As shipped, it currently looks like this:

!Cache/
!Cache/!Boot,feb
!Cache/!Help,feb
!Cache/!Run,feb
!Cache/!RunImage,ffb
!Cache/!Sprites22,ff9
!Cache/!Sprites,ff9
!Cache/Caches
!Cache/Caches/Blank
!Cache/Caches/Single
!Cache/Caches/Single/MimeMan
!Cache/Caches/Single/MimeMan/MimeBase,ffd
!Cache/Caches/Single/MimeMan/PluginMime,ffd
!Cache/Resources
!Cache/Resources/MultiError,ffb
!Cache/Resources/ResFind,ffb
!Cache/Resources/UK
!Cache/Resources/UK/Help
!Cache/Resources/UK/Messages
!Cache/Resources/UK/!Meta
!Cache/Resources/UK/Templates,fec

While we'd expect something like:

!Cache/
!Cache/!Boot,feb
!Cache/!Help,feb
!Cache/!Run,feb
!Cache/!Sprites,ff9
!Cache/!Sprites22,ff9
!Cache/Caches

We can either create our own "!Caches" that behaves as we expect, or we
can try to get the upstream "!Cache" fixed and continue to use that.
Although "!Cache" does seem over-complex; I'm not sure why it needs a
!RunImage, for example.

Also, whichever we choose, we should move the RUfl cache to the
persistent cache, rather than storing it in Scrap.


[1] See this thread:

http://vlists.pepperfish.net/pipermail/netsurf-users-netsurf-browser.org/2006-June/005356.html

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