Odyssey 3.0 alpha has been available for several weeks but there are still very few bug reports on Github. I wonder why?! How can the developers 'polish' the program if people do not bother to report about issues...?
I would guess because it's an alpha and the important bugs are obvious. When it gets to a beta stage, then reporting more nuanced problems would fall on the community.
Please, feel free to add any bugs in github. Just first check if anyone mentioned the same bug. It is useful to have them in a place and tackle one by one.
Can they report it from Odyssey itself? Github needs the latest browser engine to work or it works faulty if it works at all. Bit off putting if you can't post a report on the machine with the bug but instead need to stuff around taking pictures and logs to transfer to another computer.
One thing that I can say is that appart from the known issues it's stable and I haven't had any issues.
One thing that I wonder about is something that happens with wayfarer too on some sites, that isn't a bug but it loads quickly, halts and sits there with 100% CPU-usage for quite some time (on some rare occation I waited for like 30 min and gave up) and I've seen that happen with some site here too but these aren't bugs so yeah, only bugs are the reported ones. It's really stable and works as expected, which must be considered being a very good thing.
Please, feel free to add any bugs in github. Just first check if anyone mentioned the same bug. It is useful to have them in a place and tackle one by one.
Is it useful for you to get a list of sites that simply do not work with Odyssey? It is difficult to know what is the reason for each site...
Can they report it from Odyssey itself? Github needs the latest browser engine to work or it works faulty if it works at all. Bit off putting if you can't post a report on the machine with the bug but instead need to stuff around taking pictures and logs to transfer to another computer.
I just tested with Odyssey 3.0 that log-in on Github and opening a new issue works... I did not try save the issue, though, as I have currently no new issues to report. But the old 1.23 cannot handle Github.
One thing that I can say is that appart from the known issues it's stable and I haven't had any issues.
I'm also positively surprised how well the first alpha already works... There are some tasks which I can do only with Odyssey 3.0, as both Wayfarer and ALL the PPC Linux (32-bit) browsers fail with them!
Quote:
One thing that I wonder about is something that happens with wayfarer too on some sites, that isn't a bug but it loads quickly, halts and sits there with 100% CPU-usage for quite some time (on some rare occation I waited for like 30 min and gave up) and I've seen that happen with some site here too but these aren't bugs so yeah, only bugs are the reported ones. It's really stable and works as expected, which must be considered being a very good thing.
Can you give an example of those sites, if the issue is regular?
@Rolar Having issues per site might be a good thing to have when the browser is more stable. Ususally, these kinds of issues are still part of the webkit version used.
"Odyssey 3.0 alpha has been available for several weeks but there are still very few bug reports on Github. I wonder why?! How can the developers 'polish' the program if people do not bother to report about issues...?"
To be honest, I see it exactly the other way around: Several bugs have been reported, but the response of the developer(s) was - at least up to now - a bit reserved.
Which is completely okay, since the developers are working on it in their spare time. I just find the opening thesis a bit odd...
Anyway, thanks a lot for this great project and good luck for the further steps!
For my g4 1ghz and 1Gb mem its too much, memory just fills and it is unusable. So when/if Odyssey gets lighter, I can test it. Maybe this is limiting factor to get reports, more generally?
Some sites text parsing is way off, layout allso, but this is probably used chromium version (?).
If someone from dev team pops up and tell what areas to test, people has some idea… Amigaland has been long out of modern browsing so what is considered as bug? As alpha development state, what is wanted real bugs, hangs, grims?
Layout, text parsing and so on, are they under development atm, so is that worth of report?
I agree with you. More than enough bug reports have already been filed simply because there is hope of getting a slightly more modern browser for AmigaOS 4.1.
Unfortunately, after the release of Odyssey Alpha, there was no further progress and development was halted.
Perhaps they realized how much work is involved in porting and that it cannot be done alone.
It's like Timberwolf. This project cannot be handled by a single developer.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Unfortunately, after the release of Odyssey Alpha, there was no further progress and development was halted.
Is that official? It's news to me.
Per this thread, I'm sorry but think many have unrealistic expectations. It's a huge codebase to tame, AFXGroup's work is totally volunteer, and it's the Christmas season. And Odyssey is unlikely to progress much beyond the underlying WebKit/Wayfarer code it's based on.
I think they can finish the port, but big (volunteer) projects take time.
News feed
OS4 Feedback forum
OS4Depot Feedback 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
Donate
