Roassal2 browse examples from the ConfigurationBrowser fails

This is strange because for me Roassal was not dependent on Moose, but Moose was dependent on Roassal. The easiest solution would be to create a stable version on the versions of packages that were before the conversion to GTools, and make it be default for Pharo3. It’s better to be done by Roassal team as other people are not so fluent in the history of Roassal development

Uko

> On 09 Dec 2014, at 21:10, Alexandre Bergel <[hidden email]> wrote:
>
> Hi!
>
> This is a known problem, for which I have no solution / enough time to work on this.
> Everybody around us are using the Moose image for their daily development. We made the decision to use GT for browsing the example because of the significant improvements this brings. As such, Roassal example are not accessible from Pharo 3 anymore.
>
> Hernán, it would help if you could revise the old browser (a couple of months ago) which was purely made in Roassal. It works well.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>> On Dec 9, 2014, at 4:44 PM, Hernán Morales Durand <[hidden email]> wrote:
>>
>> Hello
>>
>> When I install Roassal2 from the ConfigurationBrowser in a fresh clean Pharo 3.0 image, and select Roassal -> Roassal examples GT, a MNU is raised (see the attached screenshot)
>>
>> Is this known issue?
>> Any fix?
>>
>> Cheers,
>>
>> Hernán
>>
>> <RoassalGT.jpg>_______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

But in that case, the examples will not be accessible within Pharo 3

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Dec 9, 2014, at 5:48 PM, Tudor Girba <[hidden email]> wrote:

The other solution is to package the example browser in the GT-InspectorExtensions-CoreRoassal.

Doru

On Tue, Dec 9, 2014 at 9:41 PM, Yuriy Tymchuk <[hidden email]> wrote:

This is strange because for me Roassal was not dependent on Moose, but Moose was dependent on Roassal. The easiest solution would be to create a stable version on the versions of packages that were before the conversion to GTools, and make it be default for Pharo3. It’s better to be done by Roassal team as other people are not so fluent in the history of Roassal development

Uko

> On 09 Dec 2014, at 21:10, Alexandre Bergel <[hidden email]> wrote:
>
> Hi!
>
> This is a known problem, for which I have no solution / enough time to work on this.
> Everybody around us are using the Moose image for their daily development. We made the decision to use GT for browsing the example because of the significant improvements this brings. As such, Roassal example are not accessible from Pharo 3 anymore.
>
> Hernán, it would help if you could revise the old browser (a couple of months ago) which was purely made in Roassal. It works well.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>> On Dec 9, 2014, at 4:44 PM, Hernán Morales Durand <[hidden email]> wrote:
>>
>> Hello
>>
>> When I install Roassal2 from the ConfigurationBrowser in a fresh clean Pharo 3.0 image, and select Roassal -> Roassal examples GT, a MNU is raised (see the attached screenshot)
>>
>> Is this known issue?
>> Any fix?
>>
>> Cheers,
>>
>> Hernán
>>
>> <RoassalGT.jpg>_______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi!

This is a known problem, for which I have no solution / enough time to work on this.
Everybody around us are using the Moose image for their daily development. We made the decision to use GT for browsing the example because of the significant improvements this brings. As such, Roassal example are not accessible from Pharo 3 anymore.

Hernán, it would help if you could revise the old browser (a couple of months ago) which was purely made in Roassal. It works well.

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

> On Dec 9, 2014, at 4:44 PM, Hernán Morales Durand <[hidden email]> wrote:
>
> Hello
>
> When I install Roassal2 from the ConfigurationBrowser in a fresh clean Pharo 3.0 image, and select Roassal -> Roassal examples GT, a MNU is raised (see the attached screenshot)
>
> Is this known issue?
> Any fix?
>
> Cheers,
>
> Hernán
>

> <RoassalGT.jpg>_______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev