@djrikky
Yeah, that boing-ball stuff sucks hard. But that strange banner done not by fab, not by Mason, not by Deniil, not by me, not by anyone else who somehow works now/ in the past on project. Its just Xeno74 by some reassons draw such banner. I personally dislike it totally: because of boing-ball crap, because of bad font, because of wrong phrase at all (not for amigaos, but for amigaos4, that should be right, and not mui/owb but muiowb, and if put any logo there, then there should be butterfly , not the that crappy boing ball in the half of banner)
@Karlos
I expect that whilst compiling OWB for OS3.x is perfectly possible* (WebKit itself is pretty clean, you'd probably need to spend most time on the GUI side), the end user experience is likely to be a bit disappointing without a great deal of effort put into optimisation. And by that I don't mean changing a few, frequently called functions for inline assembler variants (as fun as it is), but a very detailed analysis of the overall flowgraph for the layout engine / renderer to see if any of the algorithms need to be changed.
*Caveat: the core WebKit code is largely written in C++ and makes a lot of use of abstractions and generics. It may prove difficult to compile for existing amiga m68K targets.
There is tons of other problems than only WebKit (and in webkit itself, there is still some morphos related parts was , and now some amigaos4 related parts, not many , but still). And even some mui parts are uses in WebKit itself, which done only in mui4 and mui3.9.
Other problems it porting of all the necessary libs (half of them can't be just plain ./configure ; make, and need to work on sources).
One more problem its MUI : our aos4's mui3.9 are pretty fixed in terms of many-many wellknown old bugs from mui3.8. I even can't describe them all, because its so many that make no sense to write about they here. Some classes of mui3.9 also was updated, so add those problems as well.
And not the latest problem, its the compiler/linker/targets, which for sure will happens at some point, and that all need to fix , workorounds and loose tons of time (dunno who will do that).
But in theory - porting of course possible and to aos3, and to aros (with aros need to fix zune in many places, but its open source, so that is pluse). Imho porting to aros is preferable, because zune can be backported to 68k and no need to stuck with mui3.8 anymore for those who stack with aos3.
@all
Related to sources : when we will done, we will release it as well. And if someone will in interest to port it to aros or aos3, fab already agree with that, and i can help with all the stuff (if , of course, someone brave enough will mantain it).
