@Deniil

The startup bug has never been fixed, as its never been reproduced by us - what appears to have fixed it, is the port to PPC and the elimination of Petunia from the equation.

The problem is the distribution of 2.5, as there are still people that apparently want to buy it, so when the update is released, we will be back to square one again.

I am not sure whats happening, but we have had some discussions recently about things, and I expect there will be some news in the not to distant future.

@padrino

Just ignore them dude, not worth the hassle.

@Lio

Failing that, do a fresh install of IBrowse in a new location and test that. If it works its likely a configuration problem, if it doesn't something on the site(s) has probably changed.

Those having problems with palettes, there are two known sources of palette problems iirc. Once is MUI, it royally screws the palettes up under OS4, but iirc this only effects MUI programs.

The other is the icon settings on WB. If its set to the max setting (Best?) it can steal pens and causes other problems, so the ideal setting is the one below (Good?) ... this problem was evident when using Wet, for example.

Thats all from memory, but its something along those lines and might point people in the right direction :)

@tonyw

Ooer that does sound a bit weird! Can you send me your ibrowse.prefs file and we'll see if we can reproduce it.

@Antique

Blue ones are milk chocolate, red ones are dark (plain) chocolate

@Hans

Quote:

Not sure tbh, I wasn't involved in the 3.0 branch so I don't know how much was changed.


Quote:

See above, but I know the layout engine is mid-rewrite. How much is left to do in that particular area, I have no idea. Seeing as IBrowse was my first experience with C and AmigaOS programming, a lot of it is out of my reach still - I tend to play about with the GUI and prefs, hence the Search Bar etc, while the others spend time on the important bits.

Quote:

That will be ... impressive

To the best of my knowlegde we are still planning something like bi-annual public betas for IB3.x, but thats subject to Stefans decision.

Quote:

Not really - the plugin is based on the NSAPI4 SDK, so to a degree there is some stuff available, but not Amiga/IBrowse specific. Its the next thing on Olivers list, along with a skeleton plugin and the source to the Flash plugin, but he is having a rest atm.

@hotrod

Quote:

I haven't spoken to Stefan for over a month, so no idea what he is doing atm. Meldon I spoke to a week or so ago for the first time in almost a year, and he is just busy working all the time. Not sure what Oliver is doing, I know he is having a break from programming atm - probably watching the million TV shows we both like that all started in January

Me ? I'm busy decorating, catching up with copious amounts of TV that I keep missing while decorating, and just having a rest from computing out of work hours.

I should get up to speed again soon.

@Raziel

Because, to the best of my knowledge, and this was done before my time so I might be wrong, but EDITOR is a standard variable used by various applications, so rather than changing the prefs for various apps, you set it once and they all work ... just don't ask me what other apps use the variable as I have no idea

@Arnie

Yes, RTFM

http://www.ibrowse-dev.net/documentation/html/windows.html#source

@AmigaPapst

Other than whats already been said a hundred times, no not really

IBrowse forked just prior to 2.3's release into two branches, IB2.4 and IB3.0.

The IB2.4 branch was, originally, just for some quick fixes and the plugin API.

The 3.0 branch was ported to GCC, built as PPC native and re-write work began.

The 2.4 branch was then to be back ported into IB3.0.

Oliver and Stefan were working on 2.4, Meldon and Stefan were working on 3.0, I was working where ever I could help.

With the delays and complications during 2.4, plans changed and 2.4 became slightly more than planned. Meldon got a full time job and Stefan had other commitments so development work on 3.0 slowed right up. Meanwhile Oliver and I concentrated on 2.4.

With the release of 2.4, the plans to back port 2.4 into the 3.0 branch changed due to the insane amount of changes in 2.4, so instead the 3.0 branch is being back ported into the 2.4 branch to form the new 3.0 branch. Then we can restart 3.0 development in earnest.

Currently we are all having a rest.

@Swoop

As always:

1) Does it happen with the default IBrowse prefs and default MUI prefs ?

2) Boot without Petunia and obtain a stack trace without JIT so that we can be 100% sure the offsets are valid.

3) Enable the 68k Stack trace for Grim Reaper, otherwise the trace is useless for 68K apps anyway Details are in a document somewhere - either kernel or grim reaper. I can't remember what the variable is called off the top of my head.

If you can reproduce it without JIT, using the default prefs (to eliminate a settings issue), then we might be able to draw some conclusions

@AmigaPapst

Nothing, which is why IB3 is PPC native. IB2.4 is a different source branch and is 68k.

@tonyw

Quote:

Fully default

Backup and rename the prefs file (ibrowse.prefs) in the IBrowse directory to something else, so that IBrowse uses its factory defaults.

Go into Envarc:MUI/ and backup and rename any ibrowse prefs located in there, and backup and rename <global>.prefs so that MUI is fully back to its own factory defaults.

Reboot and use IBrowse until it crashes again. If there are no further crashes, reinstate the <global>.prefs and use that for a while. If there are still no further crashes, reinstate any IBrowse MUI prefs. If there are still no further crashes or if you dont have any IBrowse specific MUI settings, then reinstate the ibrowse.prefs.

If at any point the crashes come back, its likely to be one of your settings, so then we have to work out which so we can see if its IB or MUI.

It may sound like a lot of work, but during beta testing (of 2.3 iirc) we had one crash bug which took forever to track down and in the end it was a bug in NewString (no suprise there!) which was only triggered when the cursor was set to flashing and the time delay was set to a certain value.

If the crashes are full reproducable with a clean default settings for MUI and IB, then we can simply reset to defaults to try and reproduce it. If its triggered by a setting and our settings are different to yours, then its a nightmare to track down.

@Swoop

Can't really comment as I don't print and don't use Postscript Oliver should be able to answer, I'll ask him to take a look when I see him if he hasn't before hand.

@Jurassicc

IF and only IF these are 100% reproducable using the default IBrowse config, the default MUI config, and with Petunia disabled (ie. booting without Petunia, not black listing IB), then yes, please e-mail me the crash logs.

The reason for saying that is, the first two give us a level playing field for reproduction. The latter is because Petunia can screw up the offsets and we spend ages chasing things that aren't there, plus it will indicate if there may be a bug in Petunia.

You can get my e-mail from various sources, but if you can't find it, send me a PM

Best Regards,
Dave Fisher

@keisangi

I have NO idea whats required for Japanese support in the OS or the apps, but if you want to do a Japanese locale translation for IBrowse aswell, drop me a line and we'll sort it out.

I would assume that as long as the OS supports whatever is required, that it will just be a matter of translating and creating the catalog, but I'm a total novice when it comes to all that as everything I use is in english anyway

@Futaura

Yep, the only requirement is its rendered indented, no other visual change is required (although the specs only being guidelines means its upto the browser impementation to handle it as it sees fit) - so technically speaking both AWeb and IBrowse are handling it just fine.

The main issue is the lack of border which is down to CSS (lack of).

@Outcast

Quoted replies are enclosed in both CSS and blockquote tags ie. <div class="xoopsQuote"><blockquote>.

The former not supported by either IBrowse2.4 nor AWeb yet, and the latter I guess only supported by AWeb if IBrowse is just displaying it as normal text.

I will check if IBrowse supports blockquote as I'm at work atm and can't remember.

@FuZion

Ok, spoke to Oliver IBrowse uses the graphics.library routines to draw the images, and those (at least for 68k programs) support only a 1-bit maskplane.

We will need to add support directly for the full 8-bit alpha channel of RGBA images.

The functions added to OS4.0 final to support 32-bit imagery were a) added right near the end which was too late for 2.4 as we were finalising more important issues (like crashes ) and b) were not sufficently documented at the time.

Hope that clears things up - and I will now go and add an FAQ