Understand, just do you know what is the current state of the salass libs ? I mean, is everything accelerated already in his implementation and if not everything accelerated yet, atleast does we have already some simple test of his implementation compared to a "plain" one ? As you say that OWB need to be rewrite in various area for Amiga surface, having a simple test could atleast suggest us if in end the work will worth or not
So " It is just solid coloured shapes though, and if you enable anti-alias only drawing of rectangles is h/w accelerated.".
But i do not know what it mean from Odyssey's side. I mean how much Odyssey use "anti-aliased drawing of rectangles" and "solid coloured shapes".
As for tests, he have on his github page and tests as well, all can be downloaded and compiled easy with supplied makefiles (i tried few days ago). And it have some tests too. But once i see that those tests are "too much have amigaos4 native code", i understand that i can't simply replace old cairo with his one.
If only we can redirect somehow image-surfaces to amiga-surfaces, without needs to rewrite odyssey's code
I guess it's too much to ask to make the Search engines list at least "sortable"? So, that one can drag the wanted entry to the top? Or some change to make an entry "default" so it gets used on a fresh start? Right now, the first entry will always be used on a fresh start of Odyssey.
Same goes for the "Spoof as..." setting, it always goes back to "Default Setting" on a fresh start...or do i have to save the settings somewhere?
Many thnaks for taking up this work. Already some nice small improvements. The font rendering is much better with this version. Much easier on my eyes.
I did notice that is the beta02 release the $Ver:: isn't set although the version in the about box is correct.
When I right click on Odyssey beta02 and select version it shows the old version: "Odyssey Web Browser 1.23 (12/25/2013)"
@kas1e Spoofing as iphone 13 works great with youtube. ;)
A "little thing" you should add that I find annoying is in the "Download Fonts" script in the Odyssey folder, everytime I make an fresh install and "install" Odyssey I run the Download Fonts script, and it always fail until I add --no-check-certificate.
I do get a lot of LIBS:muimaster.library:GroupDispatcher lately (since the updates) but that might be only me and i also don't have a reproducable case yet.
It surely can be rewriten on amigaos4 native probabaly, as we can expect that today's DOS should do it all what asyncio do. Its just for MorphOS and AmigaOS that all used offten, and it just works for os4 port as well, without needs to tinkering with "if our public DOS can do that all already what asyncio do, and if it worth to worry about at all".
Quote:
I do get a lot of LIBS:muimaster.library:GroupDispatcher lately (since the updates) but that might be only me and i also don't have a reproducable case yet.
Be sure you use beta02, and be sure you use latest mui. But if both are meet, then it probabaly that one:
So try to save crashlogs , and compare if they the same, as well as take latest debug version Thore attach to the ticket and try to follow his steps he ask to provide more usefull crashlogs.
Found a general bug in address bar, it's not a new one as i can reproduce it in every versions of owb
To reproduce it, do this step passages:
1) Identify your browser as IPad 6.1 2) Open Google, and type something to search, for example: "Odyssey Web Browser aros" 3) Now in Google search, choose "image" (so to search for images the text you typed) 4) When thumbnails will be loaded, right click into any of that image and select --> open image in new tab
Have the debug versions installed now for some time, can't get the crash anymore. Either because of the slowdown due to the debug builds or there was some "fix" which, well "fixed" it.
Seems that it loads the picture from a stored database or something like that. Url start with data:image/jpeg;base6 ... and contains more than 16000 characters!
Indeed you are right .. just selected with copy and paste one of that line-url and got a crazy quantity of 12304 chars ! Means Odyssey seems not able to manage such extra long urls and go mad :)
However it doesn't seems a limitation in other Amiga browsers as just tried the same with NetSurf and everything worked with no glitch at all, so only OWB seems affected to ,,, i'll report it as MUI bug eventually
Seems that it loads the picture from a stored database or something like that. Url start with data:image/jpeg;base6 ... and contains more than 16000 characters!
The URL literally has a JPEG image base64 encoded in it. That's what "data:image/jpeg;base64=..." means (where ... is the image data). No wonder it's ridiculously long!
That's a very silly way of submitting an image to a server. Odyssey should still be able to handle it, though.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
