It's down since don't remember when, what happen to this portal ??
Utilitybase.com is a very important site for developers so atleast some words that saying why it's off-line and when it will be availible again would be welcome !
Good question. The ongoing infection was really annoying, but it was a huge and comprehensive well of knowlegde incl. all those talented and knowing programmers who shared their wisdom with newbie people like me.
Yep but having no words about it's a bit annoying, I'm looking for a question about SDK but old threads are not accessible, hope they have a backup atleast
I think using ancient forum engines being able to support ancient web browsers like IBrowse is really showing now. Ancient engines are full of ancient vulnerabilities.
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
Maybe but to be compatible with IBrowse disabling CSS can be enough i think, altrough i can't find one single reason to support such museum browser ...
I disgree totally. I much prefer using IB to that dreadful OWB, CSS capable or not.
In fact I find it disgusting when AMIGA sites now use so much CSS that they look strange in IB
Incidentally OWB fails to log into a couple of the bank sites I use but IB2.5 beta has no problems - even if the resulting layout looks a bit strange, at least IB works whereas OWB doesn't !
Ideally IB should be CSS capable by now but sadly it isn't. It is however functional, and no way obsolete. I often use it purely because sites load a lot quicker (important if BT restricts your access to 512kbps) than OWB or other CSS enabled browsers.
Maybe but to be compatible with IBrowse disabling CSS can be enough i think, altrough i can't find one single reason to support such museum browser ...
The old browsers can be useful for some things. I've been able to capture/download files that I couldn't get with OWB. For example, I tried to D/L some pictures from a camera review page and all I got with OWB was a "Forbidden" message. IBrowse downloaded the images from the links. I was able to access some otherwise inaccessible files with AWeb because they were in the disk cache. I can also save some Flash files (that I can't save with OWB) by setting up a MIME in AWeb with a "download" setting.
I hope Timberwolf will have an option for disk-caching. Disk caches aren't really that useful anymore, unless you want to access files that can't normally be saved directly from the Internet. Sorry for the OT post but maybe someone will speak up with some UtilityBase info if the topic stays on the recent page for a day or 2.
IB is of no use here. I have it installed but never use it... really. i dont fint it fun to switch between browsers just because IB cant cope most of non amiga pages. Someday i will change my homepage to CSS. Cant be limitied just because some people still uses IB.
Ideally IB should be CSS capable by now but sadly it isn't. It is however functional, and no way obsolete. I often use it purely because sites load a lot quicker (important if BT restricts your access to 512kbps) than OWB or other CSS enabled browsers.
Even though I was thrilled by the speed increase when I recently switched from dialup to a fast cable connection, I still get impatient with long pages full of useless jpeg images. Sometimes operating IB with image loading disabled (and sometimes even javascript disabled) can get to the information I want much faster than with newer browsers.
IB is of no use here. I have it installed but never use it... really. i dont fint it fun to switch between browsers just because IB cant cope most of non amiga pages.
I have both AWeb and IBrowse installed but rarely use them. However, until we get get a modern browser with the configurability (image loading, disk chching, MIME settings, D/L manager etc.) of the old browsers I'm keeping them installed and available.
Well for downloading files and do all the other things (not possible on Reaction OWB yet) you can switch to NetSurf 2.7 and when needed using it side by side with OWB.
About homebanking and other Javascript issues i think that problem are quite delimited to the WebKit version used in that specific OWB release rathen then real limitation of the browser, for example did you try to switch to version 3.30 or 3.31 and retry your homebanking ?
I know this isn't so good but various OWB release have this kind of "little bug", but mostly it can work only better than IBrowse in all areas.
OWB support all modern web standard, modern Javascript, modern HTML 4 and 5, CSS 3 while IBrowse is limited to an incomplete Javascript 1.5 support, an incomplete HTML 4.01 standard and no CSS at all
Aniway to turn on topic IMHO there is no reason to use IBrowse on UtilityBase,as there are no file to download, Flash to use (also very limited too) and so on and even that there not worth to use it ...
At the end don't forget that MUI OWB is on the way, they just need the update 3