Hey guys. If you have OWB installed, and if you run AmiUpdate, you will find that OWB 1.9 is now available.
This version is simply fantastic. (I'm posting this message using it.) If you've been disappointed with previous versions, you have got to give this one a try.
On a related topic, I'd like to show my appreciation to the guys who are working on OWB by donating some money to them. Does anyone know who is doing most of the work? (I know that both Andrea and Joerg are working on this project together, but I'm not sure if one or the other is dedicating more time to it.)
Edit: 1.10 is now available. Get it while its hot!
Yes, it is a lot better now. It's progressing well. However, I've already hit a few hiccups (documented in the news article comments over on AW.net). And, I've had my first crash too.
Normally I wouldn't post a crashlog here, but I'm rather tired right now, so here's the log: Crash log for task "OWB" Generated by GrimReaper 52.3 Crash occured in module OWB at address 0x7F5B6318 Type of crash: DSI (Data Storage Interrupt) exception
l have to say it starting to work great on my modest blizzard ppc looks really great thanks for this l never thought see the day when had os 4 and a decent web browser.
The WebCore/WebKit and the Sand-Labs OWB developers
Andrea did the initial changes required to build OWB for AmigaOS4 and he ported some of the libraries required for OWB like libcurl to OS4, other libraries OWB needs were ported to OS4 by Edgar Schwan, and of course without the SDL port from Richard Drummond the OS4 OWB wouldn't have been possible either.
Except for the ARexx port from Andrea I implemented all OWB 1.x changes, but that's at least partially my fault since I didn't add everything to the SVN server yet, which is unfortunately very problematic since I build OWB on OS4 itself and the OS4 SVN client can't be used for the OWB sources.
Great work to both you and andrea, Its appreciated by all.
Wasnt their talk of webkit being used for Aweb in the past as its engine? Perhaps it would be an easier job for the AWeb team to throw the OWB engine into Aweb now?
A1XE G4 800mhz,512mb,Radeon9200,SonyDRU-510A and 800a, Esi Juli@,Sil680,WiFi.
yea the aweb guy(s) should be able to benefit from this i guess. lets hope joerg and andrea turns it into something that makes it easy to include in amiga apps. a mui class would be cool, dunno if it's possible though.
I agree to use MUI if possible, it is so much more user configurable than reaction. You can choose to use custom screens easier than you can with reaction, and you can also snaphot all your windows to where you want them which Reaction still seems unable to do. You can also choose what fonts you use in MUI and fonts do seem to be OWBs weakness at the moment, some look decidedly Topazish.
A web browser not using MUI does just not seem quite right
Why don't the OWB guys and IBrowse guys join forces.
OWB certainly has the better layout engine and IB already has the GUI. Combining forces would certainly save both teams a lot of effort.
No. Make it datatypes class so you can use it with both MUI and Reaction GUIs (and everything else + Multiview) f.ex. we have already simplehtml datatype.
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
AmiUpdate is an UPDATE mechanism, which means you must have something to update first. If you haven't got 1.8+ installed, then as far as AmiUpdate is concerned, theres nothing to update.