Esteban wrote:
Pharo 2.0 does not work with Eliot builds (and it will not work in some scenarios). In this case, the main reason is that we rebuild (and use) FilePlugin and it is not incorporated in Eliot branch of the vm... so the FileDialogWindow will take years to open if opens at all. You need to use one of our VM builds (anyone from last 6 months to now should work)
Ah, I didn't know the differences were already so that we need a Pharo-specific vm.
nbcog-mac-latest.zip from 27-11-2012 doesn't crash. 15883 run, 15493 passes, 2 skipped, 88 expected failures, 207 failures, 95 errors, 0 unexpected passes
Would it be possible to have the vm warning more informative? Something like "expected FilePlugIn, ..."?
Stephan
Hi Stephan,
Thanks for your testing time :)
Cheers, Doru
On Mar 12, 2013, at 9:12 PM, Stephan Eggermont stephan@stack.nl wrote:
Esteban wrote:
Pharo 2.0 does not work with Eliot builds (and it will not work in some scenarios). In this case, the main reason is that we rebuild (and use) FilePlugin and it is not incorporated in Eliot branch of the vm... so the FileDialogWindow will take years to open if opens at all. You need to use one of our VM builds (anyone from last 6 months to now should work)
Ah, I didn't know the differences were already so that we need a Pharo-specific vm.
nbcog-mac-latest.zip from 27-11-2012 doesn't crash. 15883 run, 15493 passes, 2 skipped, 88 expected failures, 207 failures, 95 errors, 0 unexpected passes
Would it be possible to have the vm warning more informative? Something like "expected FilePlugIn, ..."?
Stephan
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
-
Stephan Eggermont -
Tudor Girba