[Pharo-project] what do we do for OmniBrowser?

Dmitri Zagidulin dmitri at zagidulin.net
Thu Feb 3 16:01:01 CET 2011

Ah, excellent! I was just surprised to see it missing from the Seaside
one-click 1.2 pharo image out of the box (since, if I recall
correctly, it was there in Squeak and in previous Pharo builds). Since
it seems like a key piece of functionality. And I couldn't figure out
how to install it, and I saw a recent email thread on this list saying
that it was broken, so I gave up on it for a while.
But, I will try it again!

On Wed, Feb 2, 2011 at 5:37 PM, Johan Brichau <johan at inceptive.be> wrote:
>> (btw, I still
>> can't believe we as a community let SeasideTesting be broken in 1.2).
> Well, I just tested it in 1.2 for the first time and it works.... If something doesn't work for you, please send an email on the seaside mailinglist. I am actively using and maintaining SeasideTesting (whenever possible) and willing to help out if people experience problems. Mind that the external browser testing is a new feature that David included in his new version in VisualWorks but which I did not port to Pharo/Squeak (yet). However, the traditional simulated browser testing is working. We have over 300 tests in our application that use seaside testing.

More information about the Pharo-project mailing list