I can confirm that OmniBrowser works in Pharo 1.2 and Pharo 1.3 with refactoring tools, syntax highlighting and code completion. All tests pass in the latest versions of both images: 2131 run, 2130 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes The following two scripts load the necessary packages (and tests): https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st https://github.com/renggli/builder/blob/master/scripts/omnibrowser-tests.st Cheers, Lukas On 18 April 2011 19:25, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Mon, Apr 18, 2011 at 7:21 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Apr 18, 2011, at 7:18 PM, Mariano Martinez Peck wrote:
On Mon, Apr 18, 2011 at 7:05 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
Core     -> Nothing to be done.
Full: Â Â Â Â -> Build is broken: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/232/console
Hopefully someone will sit, spend a couple of hours and merge latest changes from Lukas OB and ours.
Why merge? Lukas maintains OB and I am sure his version is fine for 1.2...
So let's just load it. We just had to temporary fork to make it usable while 1.2 was not yet relased.
Yes, true. Sorry, I was thinking about 1.3. Yes, for Pharo 1.2.2 it should be easier, I guess almost the same we released for 1.2.1
    Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Mariano http://marianopeck.wordpress.com
-- Lukas Renggli www.lukas-renggli.ch