Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4. This means that, at this point, in the Moose image Nautilus does not get updated anymore. Cheers, Doru On 11 May 2012, at 08:52, Tudor Girba wrote:

I can reproduce the problem.

Nautilus is loaded from its own repository like: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work.

But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: Gofer new squeaksource:'MetaRepoForPharo14'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4.

Cheers, Doru

On 10 May 2012, at 15:01, Fabrizio Perin wrote:

...

Hi, I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code.

I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else.

Any idea?

Cheers, Fabrizio

-- www.tudorgirba.com

"Sometimes the best solution is not the best solution."

-- www.tudorgirba.com "It's not how it is, it is how we see it."

Could you please point me where I can download the image and the exact way to reproduce the issue ? Because it clearly sounds weird to me, and I am proud that Moose use Nautilus :) Thanks in advance, Ben On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote:

If we don't use the latest version of Nautilus what about to load the working version of Omnibrowser?

Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load.

(ConfigurationOfOmniBrowser project version: #stable) load: #( 'Dev' 'Dev Tests').

Cheers, Fabrizio

2012/5/11 Tudor Girba <tudor@tudorgirba.com> Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4.

This means that, at this point, in the Moose image Nautilus does not get updated anymore.

Cheers, Doru

On 11 May 2012, at 08:52, Tudor Girba wrote:

...

I can reproduce the problem.

Nautilus is loaded from its own repository like: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work.

But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: Gofer new squeaksource:'MetaRepoForPharo14'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4.

Cheers, Doru

On 10 May 2012, at 15:01, Fabrizio Perin wrote:

...

Hi, I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code.

I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else.

Any idea?

Cheers, Fabrizio

-- www.tudorgirba.com

"Sometimes the best solution is not the best solution."

-- www.tudorgirba.com

"It's not how it is, it is how we see it."

Hi, just download the Moose build of May the 8th http://ci.moosetechnology.org/job/moose-latest-dev/972/artifact/moose/ and open Nautilus. You will notice that the browser is empty. I think that either in Moose is loaded the latest version of Nautilus, so we can report bugs or suggest improvements (and we benefit from the on going work), or it pointless to load Nautilus. If we have to rely on a fix version of a development environment than I believe it is better to rely on an old version of a mature development environment such as OB. This is why I suggested to use OB instead of Nautilus. Cheers, Fabrizio 2012/5/12 Tudor Girba <tudor@tudorgirba.com>

Hi,

The problem is reproducible in the latest Pharo 1.4.

Just download it, and then run: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Cheers, Doru

On 12 May 2012, at 14:20, Benjamin wrote:

...

Could you please point me where I can download the image and the exact way to reproduce the issue ?

Because it clearly sounds weird to me, and I am proud that Moose use Nautilus :)

Thanks in advance, Ben

On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote:

...

If we don't use the latest version of Nautilus what about to load the working version of Omnibrowser?

Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load.

(ConfigurationOfOmniBrowser project version: #stable) load: #( 'Dev' 'Dev Tests').

Cheers, Fabrizio

2012/5/11 Tudor Girba <tudor@tudorgirba.com> Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4.

This means that, at this point, in the Moose image Nautilus does not get updated anymore.

Cheers, Doru

On 11 May 2012, at 08:52, Tudor Girba wrote:

...

I can reproduce the problem.

Nautilus is loaded from its own repository like: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work.

But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: Gofer new squeaksource:'MetaRepoForPharo14'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4.

Cheers, Doru

On 10 May 2012, at 15:01, Fabrizio Perin wrote:

...

Hi, I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code.

I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else.

Any idea?

Cheers, Fabrizio

-- www.tudorgirba.com

"Sometimes the best solution is not the best solution."

-- www.tudorgirba.com

"It's not how it is, it is how we see it."

-- www.tudorgirba.com

"Not knowing how to do something is not an argument for how it cannot be done."

Thanks. It works now. Cheers, Doru On 12 May 2012, at 18:05, Benjamin wrote:

Thank you guys :)

It was a stupid mistake when posting versions :) So I fix it, and push the latest 2.0 fixes in the 1.4 version :)

So now it seems to work properly :)

Could you try and confirm please ?

Thanks in advance,

Ben

On May 12, 2012, at 3:38 PM, Fabrizio Perin wrote:

...

Hi, just download the Moose build of May the 8th

http://ci.moosetechnology.org/job/moose-latest-dev/972/artifact/moose/

and open Nautilus. You will notice that the browser is empty.

I think that either in Moose is loaded the latest version of Nautilus, so we can report bugs or suggest improvements (and we benefit from the on going work), or it pointless to load Nautilus. If we have to rely on a fix version of a development environment than I believe it is better to rely on an old version of a mature development environment such as OB. This is why I suggested to use OB instead of Nautilus.

Cheers, Fabrizio

2012/5/12 Tudor Girba <tudor@tudorgirba.com> Hi,

The problem is reproducible in the latest Pharo 1.4.

Just download it, and then run: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Cheers, Doru

On 12 May 2012, at 14:20, Benjamin wrote:

...

Could you please point me where I can download the image and the exact way to reproduce the issue ?

Because it clearly sounds weird to me, and I am proud that Moose use Nautilus :)

Thanks in advance, Ben

On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote:

...

If we don't use the latest version of Nautilus what about to load the working version of Omnibrowser?

Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load.

(ConfigurationOfOmniBrowser project version: #stable) load: #( 'Dev' 'Dev Tests').

Cheers, Fabrizio

2012/5/11 Tudor Girba <tudor@tudorgirba.com> Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4.

This means that, at this point, in the Moose image Nautilus does not get updated anymore.

Cheers, Doru

On 11 May 2012, at 08:52, Tudor Girba wrote:

...

I can reproduce the problem.

Nautilus is loaded from its own repository like: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work.

But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: Gofer new squeaksource:'MetaRepoForPharo14'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4.

Cheers, Doru

On 10 May 2012, at 15:01, Fabrizio Perin wrote:

...

Hi, I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code.

I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else.

Any idea?

Cheers, Fabrizio

-- www.tudorgirba.com

"Sometimes the best solution is not the best solution."

-- www.tudorgirba.com

"It's not how it is, it is how we see it."

-- www.tudorgirba.com

"Not knowing how to do something is not an argument for how it cannot be done."

-- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

Good! Thanks Benjamin. Fabrizio 2012/5/12 Benjamin <benjamin.vanryseghem.pharo@gmail.com>

Cool :)

Ben

On May 12, 2012, at 10:11 PM, Tudor Girba wrote:

...

Thanks. It works now.

Cheers, Doru

On 12 May 2012, at 18:05, Benjamin wrote:

...

Thank you guys :)

It was a stupid mistake when posting versions :) So I fix it, and push the latest 2.0 fixes in the 1.4 version :)

So now it seems to work properly :)

Could you try and confirm please ?

Thanks in advance,

Ben

On May 12, 2012, at 3:38 PM, Fabrizio Perin wrote:

...

Hi, just download the Moose build of May the 8th

http://ci.moosetechnology.org/job/moose-latest-dev/972/artifact/moose/

and open Nautilus. You will notice that the browser is empty.

I think that either in Moose is loaded the latest version of Nautilus, so we can report bugs or suggest improvements (and we benefit from the on going work), or it pointless to load Nautilus. If we have to rely on a fix version of a development environment than I believe it is better to rely on an old version of a mature development environment such as OB. This is why I suggested to use OB instead of Nautilus.

Cheers, Fabrizio

2012/5/12 Tudor Girba <tudor@tudorgirba.com> Hi,

The problem is reproducible in the latest Pharo 1.4.

Just download it, and then run: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Cheers, Doru

On 12 May 2012, at 14:20, Benjamin wrote:

...

Could you please point me where I can download the image and the exact way to reproduce the issue ?

Because it clearly sounds weird to me, and I am proud that Moose use Nautilus :)

Thanks in advance, Ben

On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote:

...

If we don't use the latest version of Nautilus what about to load the working version of Omnibrowser?

Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load.

(ConfigurationOfOmniBrowser project version: #stable) load: #( 'Dev' 'Dev Tests').

Cheers, Fabrizio

2012/5/11 Tudor Girba <tudor@tudorgirba.com> Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4.

This means that, at this point, in the Moose image Nautilus does not get updated anymore.

Cheers, Doru

On 11 May 2012, at 08:52, Tudor Girba wrote:

...

I can reproduce the problem.

Nautilus is loaded from its own repository like: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work.

But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: Gofer new squeaksource:'MetaRepoForPharo14'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4.

Cheers, Doru

On 10 May 2012, at 15:01, Fabrizio Perin wrote:

...

Hi, I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code.

I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else.

Any idea?

Cheers, Fabrizio

-- www.tudorgirba.com

"Sometimes the best solution is not the best solution."

-- www.tudorgirba.com

"It's not how it is, it is how we see it."

-- www.tudorgirba.com

"Not knowing how to do something is not an argument for how it cannot be done."

-- www.tudorgirba.com

"There are no old things, there are only old ways of looking at them."