Odyssey 1.23 progress: r5 RC2

@khayoz

PayPal works for me until i need to send a confirmation to my smartphone

btw, welcome back trooper, long time no see

@Raziel

Thank you! Feels good to be back on the X5000 100%
(well 99% ;) )

@khayoz

I hope it will be a max of 90%...leave some time for soldering

...and Real Life(tm)...yes, i think with all those taxes, bills and alien people around it's worth 1% of our time...
...that stupid Corona Virus really brought things down...
...they should open-source RealLife asap, so that more modern security measures could be installed...

@kas1e

I read your change log, and it is a impressive work. Actually I thought development stoped and was surprised to see this progress. Great work!

But I have a question, I read the browser is based on an old WebKit core, what
are the technicals challenges/difficulties to upgrade it?

Sorry if I've missed this in an earlier post.

I downloaded the OS4Depot version and installed it to a fresh partition. I have copied my bookmarks.html file over from the previous installation but I don't see any of my old bookmarks.

Has the format changed? What have I done wrong?

@tonyw

Make sure the web browser is NOT open,
before copying the file,
(as the file will be overwritten when the web browser quits.)

@tonyw
I successfully copied my bookmarks, so probably what @LiveForIt said.

@kas1e
Thank you for your great work.

@all
Personally, I do not use QuickLinks. I have been a FireFox user for many years / PaleMoon when FireFox become too "trendy" for me. In that time, I have always had my Bookmarks to the left side. This works fine with Odyssey, but if I change the dimensions of the Bookmarks and/or remove the Address field then even if I snapshot (which I believe is not releveant anyway, since that just stores the Intuition window ordinates) and/or save all preferences, quit out and open up Odyssey again then my Bookmark window remains in the old dimensions and contains the address field. I also noticed that in the drop down if I unchecked QuickLinks, then a restart ignored this and QuickLinks were shown again. Easy to get around since I just deleted all QuickLinks.

Just thought I would report those things. Very minor, and perhaps something I am doing wrong.

Tried the RC1 and since a few of days i am using the version from OS4Depot. Works great! Thanks to all involved.

I downloaded the version from OS4Depot and put it in its own directory.

YouTube worked right out of the box! Cool. (Watched a Nightwish/Nemo live concert video. Never able to see that on the Amiga before.) And in general this is way faster on my X5000 than the older version was. Great work kas1e.

Paul

kas1e,

The binary for Odyssey is huge - some 36 MB. Because it is >32 MB, its PPC FP op-codes can't be translated into SPE op-codes and it will have to run under emulation on the A1222.

Can you split part of the browser off as a library, to keep the largest binary down below 32 MB?

@tonyw
Quote:

36? It is 60 when unstripped, and almost 50 when stripped.

Quote:

LibWebCore.a alone about 80MB when building happens. For granted that with debug info, but not sure if it will be less than 32MB.

I mean, of course, it is possible to make all the internal libs to be as shared/separate/etc, but not sure if we can go below 32, and more of it, it's huge-big-time-consuming work will be, that for sure.

But if anyone wants to do so, i can help with all info i know about it.

Perhaps Trevor should have thought of that before picking an awkward CPU chip or perhaps he can sponsor some work to bring an up to date web browser core to Amiga.

@NinjaCyborg

Quote:
I don't think it was Trevor's fault: the CPU was most likely recommended to him. Possibly by the same genius who advised him to put the useless Xena/Xorro stuff on the X1000/X5000.

@trixie

Advised by Varisys.. Good thing they have also pre-paid a 1000 CPU`s already At the same time we ordered and pre-paid for all the long lead time items including 1000 Freescale P1022 CPUs so we would have the key components available once we started the full manufacturing run.

Source: https://www.exec.pl/article.jsp?nid=18 ... iew_with_Trevor_Dickinson

I'm getting CPU spikes (100%) all the time with latest Odyssey (clean install) and Amigans.net loaded.

It's so bad that Odyssey misses my keystrokes when the spikes occurs.

Latest OS 4.1 on a Sam460ex@1.15 GHz

When I move the mouse over a link Snoopy says: FAIL: GetVar codeset_default etc.


1.23 r5_beta07 works fine on the same machine.

@kas1e

Quote:

What matters for whether LTE can be used or not isn't executable size but how big the code segment is (".text" section in ELF files).

Running "ppc-amigaos-readelf -e" on the Odyssey exe it reports that the .text section is just a little over 33 MiB.

@salas00
Quote:

For me, it reports 210713c, ~35MB.

Do we need exactly no more 32MB, i.e. 31.9 will fit well or do we need around 30 and no more to be on the safe side?

Basically all we need then, and to make some of the 3d party libs be shared. The biggest ones which inbuild staticaly are:
libicu libs : 11mbl
libxml2: 2mb
libjpeg: 1.5mb
libfreetype: 1mb
libsqllite3 : 1mb
libcurl : 0.8mb
libwebp : 0.5mb
libxstl : 0.35mb
libexpat: 0.3mb

While libicu ones looks as good case, they very hardcore crap and hard to build, etc and surely will be not very easy to make it be shared.

Imho the ones which should be not _that_ hard and which can be make as shared are:


libxml2: 2mb
libjpeg: 1.5mb
libfreetype: 1mb
libwebp : 0.5mb

that will give us in summary ~5mb less which should fit.

@kas1e

Quote:

Only if you use SI units where 1 MB = 1000000 bytes.

Using binary units it is ~33.028 MiB where 1 MiB = 1048576 bytes.

@salas00
Indeed!

So maybe for the test, we can build just libxml2 as shared. It will save us 2MB and we can see if SPE will deal with it. I do not have experience with creating true amiga libs. If it is easy enough and can be done fast, maybe you can grab the latest libxml2, make a shared library from it, and I can then build test odyssey binary and we will see how it goes?