Who likes manga?

I’d ask you what version of AcornSSL you’re using,

AcornSSL 1.04 (26 Jan 2019). To my surprise I found within !System.350.Modules.Network.URL a module called HTTP (0.91) and another called AcornHTTP (0.92). I deleted the former and renamed the latter to HTTP.
All of these, including AcornSSL, I retrieved from an archive old software. They were not there in my working !Boot for some reason.

Gavin,

The latest HardDisc image via downloads has AcornHTTP as 1.03 and also AcornSSL 1.05 (09 Sep 2019) mbedTLS 2.16.4.

I would suggest not changing file names as they are different fetchers etc and this may cause issues with Secure fetches and things like Sine Nomine’s !Recce supporting application for !RiscOSM.

Doug

AcornSSL 1.04 (26 Jan 2019). To my surprise I found within !System.350.Modules.Network.URL a module called HTTP (0.91) and another called AcornHTTP (0.92). I deleted the former and renamed the latter to HTTP.
All of these, including AcornSSL, I retrieved from an archive old software. They were not there in my working !Boot for some reason.

How do you update your !Boot when a new HardDisc zip appears on the downloads page?

I would suggest not changing file names as they are different fetchers etc

I would second that. If you rename the file, then Manga will stop working correctly as it won’t be able to load the fetcher.

It appears that this module might have used to have been called HTTP (WebServe’s Run file), but the version supplied now is called AcornHTTP, perhaps in keeping with AcornSSL? Together with the URL module (wot, no AcornURL? :-p) they implement http and https fetching.

If you want to be old school and call it HTTP, you’ll need to edit the utility supplied with Manga (if you use it) that loads the modules. It’s BASIC, easy enough to read. Oh, and probably the !Run file of everything that loads the modules in the future… ;-)

How do you update you !Boot when a new HardDisc zip appears on the downloads page?

With difficulty, I would imagine, especially if using a system where the DOS partition is within !Boot, so you can’t swap one out for the other, not to mention configuration and settings. The mess within !Boot and the issue of updating isn’t one of the platform’s strong points.

My !Boot is roughly the vintage of the Beagleboard xM from when I got back into RISC OS (what was that, 2013 or so?) with bits copied in as and when. It’s probably a mess but it works (or, at least, appears to).

It appears that this module might have used to have been called HTTP (WebServe’s Run file), but the version supplied now is called AcornHTTP

I noticed that too when fiddling with Browse. I note in the StrongHelp Internet SWIs manual there’s an HTTP listed, but it’s not the Acorn one, so my theory is someone at Acorn forgot to register the name and subsequently discovered a clash and had to rename it.

How do you update you !Boot when a new HardDisc zip appears on the downloads page?

With difficulty, I would imagine, especially if using a system where the DOS partition is within !Boot, so you can’t swap one out for the other, not to mention configuration and settings.

I was expecting an answer involving use of the Merge function in !Configure

My !Boot contains a Backup folder that contains the old versions of the named modules, now if that’s not a function of the normal build I’m left wondering what made it because it wasn’t manual intervention on my part.

The mess within !Boot and the issue of updating isn’t one of the platform’s strong points.

Tempting to pull apart and rebuild, but where to start?

My !Boot contains a Backup folder that contains the old versions of the named modules

My pi !Boot has two backup folders. One atthe top level of !Boot and one in !System as well with even older modules.

I was expecting an answer involving use of the Merge function in !Configure

Automatic things… Hmm…

It’s worth pointing out, by the way, that Installer is capable of updating AcornSSL. If the module versions match, it’ll then look at datestamps. That ought to work, but really… different modules ought to have different versions. ;-)

My !Boot contains a Backup folder that contains the old versions of the named modules,

Installer does that.

I wonder what happens if you update a module more than once, does the more recent backup overwrite the older backup?

Tempting to pull apart and rebuild, but where to start?

I guess first by splitting it into “system stuff” and “user stuff”, which will cause a hundred message thread where everybody argues over what counts as what. Like whether !Scrap really belongs with the system, or does it belong with the user? ;-)

but really… different modules ought to have different versions. ;-)

Elsewhere there’s a post where I sympathise with Nemo.

I’m voting for using version 0.00 as a marker, then you know it’s¹ not worth taking notice of in any fashion.

Like whether !Scrap really belongs with the system, or does it belong with the user? ;-)

SystemScrap, SystemTemp, UserScrap, UserTemp
Scrap shouldn’t persist beyond the current boot session at most, Temp can persist until a defined time has elapsed.

And NetSurf² can discontinue its nasty habit and Cache things like fonts in a more appropriate Application cache.

¹ It’s total bollox is what it is.

And NetSurf can discontinue its nasty habit and Cache things like fonts in a more appropriate Application cache.

If you’re thinking of the RUfl_cache file, it’s accessed by other applications that use the RUfl font library also, so it would need to be in a system temporary directory.

If you’re thinking of the RUfl_cache file, it’s accessed by other applications that use the RUfl font library also, so it would need to be in a system temporary directory.

I seem to recall this coming up many times before, and the developers being clear that they considered the data to be transient and not requiring retention: making Scrap a legitimate place for it to live.

It is transient to the extent that it can easily be rebuilt by rescanning the fonts. The scanning process does take time, though, especially if you have a lot of fonts, so it is preferable if the RUfl_cache survives reboots etc.

Just put version 0.44 in the usual places.

Fixes a couple of bugs in the parsing of What’s New (also Suggestions and Search) related to manga with long titles and oddities in chapter scanning in some circumstances.

Also hidden some test code to “scale the current page”. It isn’t linked into Manga, it’ll run stand-alone and scale down by a factor of 1.36 (odd number chosen on purpose). It’s just a test, but it does in under half a second what the same algorithm (and code) takes BASIC about half a minute. That’s a vast difference, don’t you think? ;-)
I don’t know if I’ll take this further. The scaling works but it isn’t that good, ChangeFSI is only a little bit slower on most pages. But, since scroll wheel now works, I don’t bother with scaling at all, just scroll up and down. That works better for the really-long-page manga that would likely scale weird.

[note: if you find this, be aware that if you have precaching on (you probably will) then the “current” page will be the next one, not the one you’re looking at]

Now, I had planned to watch some films yesterday but I got sidetracked, so I’m going to brew a nice cup of tea, get into bed with the heated blanket, and watch ’em all right now. ;-)

Version 0.45 now available.

V0.44 had a small whoopsie in that I forgot to bump the version, so it thought it was 0.43 (and would thus keep reminding that an update was available when started).

Otherwise, played around with the test scaling code, I think it’s much better now but then it does process 11 pixels each time instead of 5; and you can press + and – to try different scalings.
[note, though, that going to 2x can easily swallow 20MiB for a normal page]

Usual places.

Version 0.46 now available, in the usual places.

• SecureSockets support removed.
• New “Surprise me” option to pick a random manga you’ve not yet read.
• Manga URIs now support chapter and page references (try this); and won’t trash any previously remembered reading position of a manga you’re actually reading unless you go to a new page (and if you do, your original position was automatically bookmarked so you can jump back to it).
• Some other fixes and enhancements.

Version 0.47 now available, either off my private server (manually or auto-update) or from !Store.

• Fixed cache tidy to actually tidy the cache. ;-)

• Moved cache operations to a submenu off the main menu. Tidier, less clutter.

• History editor now shows you how much space in the cache/library each manga is taking. Yup, Azumi is over a gigabyte. And it’s just as well I don’t read Naruto or One Piece, they’d be a lot more…

• Some other tweaks and enhancements.

Note – home server is off today (thunderstorm warning). It’s always on !Store. ;-)

By the way -is there a option of accessing store from a Android device?

Just to let you know – using AcornHTTP 1.04 and AcornSSL 1.06 and some code tweaks to make Manga “look like NetSurf”, Manga is now able to fetch content from the MangaReader site again.

Unfortunately, Cloudflare has optimised the page by removing all whitespace and newlines, which completely breaks my parsing. I’ll have to have a think about how best to fix this…

[Update: Epic cheating – if it’s not an image, then I scan through the HTML byte by byte looking for certain tags (like </tr> and when found, I output a newline afterwards! It’s a lot easier to fix the HTML than the parser!]

Okay. Normality resumed, so you have something to do on a “don’t dare go outside OR YOU WILL DIE!” weekend other than staring out the window… ;-)

Manga 0.48 has arrived. It now works with all the nonsense that’s been done to the mangareader.net site (and note, since it’s now infested with scripting, it no longer works with NetSurf…).

It’s on Store, it’s on the auto-updater thingy, or you can get it from http://heyrick.ddns.net/manga/

The changes (and note the stuff not working):

0.48  2020/08/29

      Changes to the fetcher to "look like NetSurf".
      This, when combined with AcornHTTP v1.04 and
      AcornSSL v1.06 are enough to make !Manga look
      like a browser to the Cloudflare system.
      
      Many *many* internal changes to the parser to
      support the new "optimised" and condensed
      markup.
      PLEASE REPORT BACK ANY TITLES THAT DON'T WORK.
      
      Currently "What's new?", "Suggestions", and
      "Search" are disabled; because of how completely
      different the markup is now.
      This will be fixed soon. But I thought it better
      to get a working Manga out, than hold back for
      fixing everything. ;-)
      
      Known bugs:
        * Sometimes the description is blank or something
          like "</p></".
        * Sometimes the little cover picture is missing.
        * The genres are all run together, like
          "AdventureComedyFantasy".

        * The menu options for What's New and search are
          greyed out. There are other ways to call these;
          and - of course - they don't work...

Have fun, and thanks to everybody who voted for it to have a second ribbon this year. :-)

Thanks! :)

Version on PlingStore seems to be 0.47 still, though described on the list/details as 0.48. Shows on ‘My software’ as 0.47 though did its flashy green thing.

oops! Forget to upload the zip as I was doing a dozen things at the same time. Should be fixed now.

Unexpected HTTP response 301 – cannot fetch file.

Dropping out to examine file

Exit

Beagleboard -xM, 27-Aug-20 ROM, latest disc image.

Unexpected HTTP response 301 – cannot fetch file.

Ah… <facepalm>

It’s because your settings file specifies not using SSL.

Three fixes:

FIX ONE

Download v0.48b from http://heyrick.ddns.net/manga/manga_0-48b.zip or from !Store.
(the auto-updater won’t see this as the main program has not been changed)

FIX TWO

Find the file Boot → Choices → Manga → settings and delete it. Rerunning Manga and applying the configuration again should resolve the program as the default is for SSL to be used.

FIX THREE

Run the following program to switch to using SSL:

ON ERROR END
f% = OPENUP("<Choices$Dir>.Manga.settings")
PTR#f% = 17
b% = BGET#f%
b% = b% OR (1 << 4)
PTR#f% = 17
BPUT#f%, b%
CLOSE#f%
END

(aside: this is the change in v0.48b, the !Run file runs the above program at start to force SSL mode)