There are now two versions 40 in the repo.
The one I updated is copied to the metarepos,
so the problem is not yet fixed.
I only changed the catalog methods,
they need to be at the class side.
I don't know if you saw this post in pharo-dev?
On 19-06-15 07:11, Alejandro Infante wrote:
> Hi,
> I did that because when using:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Gofer it
> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
> configurationOf: 'Roassal2';
> loadStable
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> It was installing 1.52 even though the stable version of Roassal was 1.12.
> Instead if I used:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Gofer new smalltalkhubUser: 'ObjectProfile'
> project: 'Roassal2';
> package: 'ConfigurationOfRoassal2';
> load.
> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> I was getting the right version (1.12).
Gofer>>loadStable does not use the
ConfigurationOfRoassal2 class>>loadStable
(which is undefined, but many configurations define as
self project load: #stable
but loadVersion: #stable, which uses the latest version marked #stable.
So yes, that is something you'd want to fix in place.
And warn about on the mailing list.
In this version 1.12 then we see that Roassal is tightly coupled to
an old version of GlamourCore. So either ConfigurationOfRoassal2
needs to add a new #stable version every time GlamourCore #stable
for Pharo 4 is updated, or it should depend on GlamourCore #stable.
And ConfigurationOfGlamourCore has actually the same problem, as
#stable currently depends on an old version of Rubric. So that
should have been one or two versions more. And please note that
this is for the released Pharo 4, where we are only supposed to
backport important fixes.
I strongly suggest to make ConfigurationOfGlamourCore #stable
depend on ConfigurationOfRubric #stable, and to make
ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable.
B.t.w. I'm not quite sure why there is an old ConfigurationOfGlamourCore
in Pharo5.
Depending on #stable instead of #release1 or so works out ok
here as long there is not supposed to be a new release for Pharo 4.
Stephan
Hi!
The build is red. It would be great to fix this.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
On Pharo 4.0, Rubric text highlighting does not seem to work well. In the
following example, all the text (blue color is added to the first two
only). I check it with Rubric-FranckWarlouzet.217.
RubEditingArea new
beWrapped;
width: 400;
updateTextWith: (('Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Integer nec odio. Praesent libero. Sed cursus ante dapibus diam. Sed nisi.
Nulla quis sem at nibh elementum imperdiet. Duis sagittis ipsum. Praesent
mauris. Fusce nec tellus sed augue semper porta. Mauris massa. Vestibulum
lacinia arcu eget nulla. Class aptent taciti sociosqu ad litora torquent
per conubia nostra, per inceptos himenaeos. ') asText addAttribute:
TextColor blue from: 1 to: 2); openInWorld
In the repo, some fixes are proposed for text attributes but they do not
seem to correct this problem. Is this a known issue?
usman
Hello.
As I understand, no one works on improving Roassal3d, so all people who work with 3d graphics need to use Woden.
I’m using Woden during the month. I like Woden. And I’m sorry, but and it seems to me that it creates more troubles with downloading after each next downloading.
At the beginning I could download it from CI server. Now I cannot.
Then I used long script from smalltalkhub and downloaded it into moose5 image. Now I cannot.
Then I used the same script to download it into pharo4 image and after a couple of tries I was successful. Now I am not.
I understand that Woden is complicated and huge, but please tell me how should I download it?
Sorry for so criticizing letter.
Best regards,
Natalia
Hi.
In my fresh (5 min after I started work with it) moose 5 image, something weird is happening. When I want to select ( click ) in system browser on any class this massage appear.
I can change the package. I don’t know about methods.
Any suggestion what is wrong?
Best regards,
Natalia
Hello,
I noticed, that sometimes Roassal 2D presentation builds view twice in Moose Panel. When it happens, it builds every Roassal presentation renders view twice in that Moose panel, however if I would open another Moose panel this mistake doesn’t happen.
When I was debugging it, I saw that #painting: [ ] renders new view, shows it in panel, and then evaluates #painting: [ ] with this view.
Does anybody knows where is the problem?
Best regards,
Natalia
Hello.
I noticed weird thing - when I’m asking famix package #isPackage it returns false, because for this famix package modifiers is empty.
Why this method not return just true? If it suppose to be like that - how can I get true?
Best regards,
Natalia
Name: ConfigurationOfFamixDiff-usmanbhatti.9
Author: usmanbhatti
Time: 17 June 2015, 4:54:09.270165 pm
UUID: 2a47e2b3-8c83-4b36-a10a-a8064c4b6680
Ancestors: ConfigurationOfFamixDiff-usmanbhatti.8
development version for pharo 4.0
