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
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
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 alexandre.bergel@me.com 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 hernan.morales@gmail.com 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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 yuriy.tymchuk@me.com 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 alexandre.bergel@me.com
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 <
hernan.morales@gmail.com> 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
But in that case, the examples will not be accessible within Pharo 3
Alexandre
Just the browser should be in GT. Not the examples.
Doru
On Tue, Dec 9, 2014 at 10:44 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
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 tudor@tudorgirba.com 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 yuriy.tymchuk@me.com 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 alexandre.bergel@me.com
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 <
hernan.morales@gmail.com> 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Alex,
I could take a look and fix, but any solution you can provide would be nice because is a starting point of Roassal and could be see as showstopper. Cheers,
Hernán
2014-12-09 17:10 GMT-03:00 Alexandre Bergel alexandre.bergel@me.com:
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 <
hernan.morales@gmail.com> 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Looks like you need to add a dependency on Glamour and GT for pharo3 to the configuration. You can probably just copy the relevant parts from the ConfigurationOfMoose.
Stephan
On Dec 9, 2014, at 20:44 , Hernán Morales Durand 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Hernán Morales Durand -
Stephan Eggermont -
Tudor Girba -
Yuriy Tymchuk