very nice improvement! it runs nicely even on classic. (after installing the right fonts)

Congratulation to All involved!

_________________

take backup of 1.9, 1.10 gives me yellow gurus

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

RTFM!

_________________

hmm... loads much faster for me, but it throws lots of recoverable alerts and DSIs now (µA1, July Update) Besides that, it still gives hangs when accessing gmx.de (not all pictures are loaded, still hangs for pictures loaded from other sites).

But I think it is on a good way with faster loading and the font changes made

Regards

you have some missing fonts.

_________________

What, if the required fonts are installed completely? If the optional font missing throws the alerts and DSIs, it shouldn't be optional... btw. it would be a good style to give the corresponding error message then instead of throwing alerts and DSIs, I would think.

Last edited by whose on 16-Feb-2008 at 02:15 PM.

whatt about take a look at the docs? OR on a site where the authors are giving suggestions?

like here

Last edited by Framiga on 16-Feb-2008 at 02:22 PM.

_________________

@framiga:

You missed the point... I have installed all required fonts already, hence I followed the readme to the extend. If a font declared optional throws alerts and DSIs, it is clearly not optional, hence the FM is simply wrong. I intend to told Joerg, that it isn't a good style to release a program which don't give appropriate error messages and requires components declared optional to function properly.

I didn't write it to fuss Joerg's work, I did it to make his work better.

So, it should be told to all potential users that they should install all the fonts mentioned in the readme in order to use OWB without alerts and DSIs.

BTW., it is even worse style to pretend that users with a clean installation have messed it up and tell about it on one site only so users with problems have to search for the solution on many different sites. If the July Update installation isn't clean at all, autors should mention what exactly isn't clean with these installations, as documentation of e.g. July Update is lacking many points still. I installed OS4 cleanly and used the supplied installer scripts for it. After that, I didn't mess with fonts at all, how should I mess up my fonts installation then?

Regards

Last edited by whose on 16-Feb-2008 at 02:34 PM.
Last edited by whose on 16-Feb-2008 at 02:33 PM.

"BTW., it is even worse style to pretend that users with a clean installation have messed it up and tell about it on one site only so users with problem have to search for the solution on many different sites."

this is known as "amigaland" didn't you know?

What are you pretending from an more or less alpha app?

Joerg explained on amigans.et (which btw is the site that gives me the worse problem with OWB) that a reinstall of the required fonts (not ALL the system fonts) is required to achieve a DSI free installation.

_________________

the yellow gurus disapred after useing typemanager to install the common fonts.
(Arial and verdana fonts.)

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Framiga:

Quote:

"BTW., it is even worse style to pretend that users with a clean installation have messed it up and tell about it on one site only so users with problem have to search for the solution on many different sites." this is known as "amigaland" didn't you know?

I know it. But is that the reason not to speak about the fact that this is more than bad behaviour? If I release a program and tell the users: Well, you have to search for the information on your problem yourself, try site a, b or maybe c and you may eventually get the right answer (maybe not), I am right and users have to search on their own for a problem they simply cannot know about? I bet you would tell me much different things than "good work whose" then.

Btw., I have messed up my fonts installation with the (optional) corefonts archive now (all families set right etc.), on some sites all goes well, on other sites it still throws alerts and DSI and I have to install even more fonts than the system installation provides (e.g. Arial). That is not "RTFM", that is plain wrong manual. I don't expect miracles, but I would love to see a good manual and senseful development. Is that expected too much?

It is very nice of joerg to develop OWB further and I appreciate that very much. But it is of no sense, if he frustrates his users and people interested in OS4 with wrong manuals, makes false assumptions of documentation the users posses and scatters needed information around the internet only for the sake of version number inflation.

Quote:

What are you pretending from an more or less alpha app?

I require it to work better than the previous version, not worse. Yet it works not as good as the previous version, it works somehow different, but not very usable at all (some DSIs are not ignorable at all). I think that doesn't deserve an increased version number, that's all.

Regards

Last edited by whose on 16-Feb-2008 at 03:12 PM.

sorry but i don't agree! if it works "worse than the previous one" is for you.

As i said this is the first version useable EVEN on classic (above all memory wise).

_________________

@Framiga:

Quote:

sorry but i don't agree! if it works "worse than the previous one" is for you.

Yeah, that's the right spirit... let user "average joe" alone in the dark, tell him he's a bummer if the manual states "optional" instead of "required" and then worry about this user leaving the platform.

What is so hard about telling to the users the right font setup in the readme?

What is so hard about telling there how to achieve the right setup, as not all users can know about it, because the system's documentation lacks these points and standard installation may be faulty or missing vital parts?

What is so bad about users telling that the manual/readme is not sufficient for proper (and hence fun) operation?

Did anybody think about, that, for a real useable browser developed with sense and the user in mind, people would like to pay much money? I would, but not if I have to expect some piece of software working for specific (and non-standard) installations only, that I'm not in possesion of.

[irony]
Btw., 1.9 does run very well on OS4 Classic, if you don't plug in 128MB of RAM, it is your problem...[/irony]

Regards

Lovely

Works much better under os4 classic, but still freeze the pointer / system after some pages. I miss an installer who install all the needed fonts...

_________________
I´m back in 2023 on Classic Amiga with my A1200/Blizzard1230IB@50Mhz, 32MB RAM, AmigaOS3.2 and ROMs, Indivision AGA MK3, Author of Amiga-Flipclock (OS4)

@ shastar

Quote:

Lovely

Just Lovely is right!

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.

@fingus:

Install at least the Arial font family (copy it from your Windows system), as this font family is badly needed for proper function (I have installed it once again, using the font files from my Windows system this time and had no Alerts/DSIs/freezes so far) using the type manager. Do not install the corefonts from the archive there, if you don't have the TTF font files available for all the .otag files in this archive (most of them are not freely available). This will mess it up, e.g. links not working and such.

Regards

Thanks for all the updates.

Here, I finally got it working, but text doesn't show(!!!). I isntalled the core fonts, as sugested. No Grim Reaper, just "invisible" text.

Some positive things now:

After solving the fonts issue, it runs much better now. No hangs for gmx.de and gimy.de and loading is much faster. Good work, Joerg! But, please update the readme regarding the fonts issue.

Regards