On Mar 12, 2013, at 5:31 PM, Tudor Girba <[email protected]> wrote:
> Hi, > > I understand and encourage the streamlining of efforts. And I have no problem > with dealing with the bumps of living on the latest version, be it the VM or > the image. > > But, please consider the point of view of the one that offers the feedback. > Right now, it sounds as if you are shooting down an unreasonable request from > Stephan, but in this case, Esteban suggested that we should use the Cog VM > instead of the Pharo VM to develop Moose, given that the Pharo VM is > basically broken for us. > > So, Stephan did exactly that: he used the Cog VM. He reported that the tests > do not crash the VM, which I think should be a relevant input, and he also > reported other problems while running on the Cog VM. These errors indeed seem > to be related to FileSystem, and this just shows that using the Cog VM as a > temporary solution does not work. So, we have to focus on the Pharo VM. doru do you have an idea of the tests that crash the vm? > > And now, I am back to the original question: What other tests or experiments > would you like us to do to help with identifying the problem? > > Cheers, > Doru > > > On Tue, Mar 12, 2013 at 4:53 PM, Camillo Bruni <[email protected]> wrote: > FileDialogs apparently make use of the new FileSystem values, so yes, > the update-our-VM-warning is there for a good reason! > > On 2013-03-12, at 16:47, Stephan Eggermont <[email protected]> wrote: > > > The problem is not just with the MOOSE image, > > Pharo 20598 and Cog.app 2071 doesn't allow a > > file dialog to be opened. > > > > FileDialogWindow new open > > > > Stephan > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"
