Hi!
I tried to load moose in a fresh 1.2 image: ConfigurationOfMoose loadDefault
I just can't. The following is printed in the transcript:
-=-=-=-=-=-=-=-=-=
Loading Moose configuration ...
--------
Loading default of ConfigurationOfMoose...
...RETRY->ConfigurationOfPetitParser
...RETRY->ConfigurationOfPetitParser
gofer repository error: 'GoferRepositoryError: Cannot connect to 77.57.193.217:80'...ignoring
...FAILED->ConfigurationOfPetitParser
-=-=-=-=-=-=-=-=-=
Am I the only one? How comes that Jenkins does not bump into the same problem.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Doru,
When I use #sendTo:from:with: the panel update is not refreshing the selected item in a list.
My scenario:
A GLMStacker with two panes working as an inner browser.
- when I send a external value to this inner browser the value is assigned but the item does not appear as selected.
- when I select a value in one of its panes I send nil to the selected value in the other pane... The same: the value changes to nil but if it was a selected item it remains selected.
The panes allowDeselection.
Regards,
Veronica
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 586 by cy.delau...(a)gmail.com: Compute invocation candidates with
different strategies seems to be broken
http://code.google.com/p/moose-technology/issues/detail?id=586
When you try to import a smalltalk model and select a another strategy than
the default one, you get some errors
I created myself a parser that has quite some rules. Now I discovered that in the format there are comments possible. The type of comments is quite common. One format for single line comment and one for multiline comments.
The comments are not described as part of the format. So now I'm trying to get a solution how to parse the comments. Basically the can appear anywhere in the text. I could do it by first removing the comments and then parsinf the format. But hopefully there is something more smart.
thanks,
Norbert
Hi,
I created a mse file of Pharo1.1Core.
I removed the Implicit Variable to fit with moose 4.4.
The mse file is here (20 Mb):
http://dl.dropbox.com/u/7739334/mse/pharo1.1.zip
Cheers,
---
Jannik Laval
Hi,
I would like to export a model without the implicit variables.
This is a generated model with an old version of FAMIX and the implicit variable are attached to a class, whereas now it is attached to a method.
Is there an easy way to export without implicit variable ?
Cheers,
Jannik
Hi,
On 12 May 2011, at 16:44, Marcus Denker wrote:
>
> On May 12, 2011, at 4:42 PM, Tudor Girba wrote:
>>
>> I did not mean that someone should look into the posted code. I was in a hurry and I simply asked a direct question if anyone has any idea of why 4096 would be a limit for highlighting text in TextMorph. The question had nothing to do with Glamour, but I am sorry if the form of the mail made you waste your time.
>>
>> In any case, I will look into this in more details.
>>
>
>
> maybe this is relevant? We should release 1.2.2....
>
> http://code.google.com/p/pharo/issues/detail?id=4157
Hmm. Sounds similar, but I am too ignorant.
I could reproduce the problem outside of Glamour. The issue is indeed not with TextMorph, but with PluggableTextMorph:
string := ''.
1 to: 1000 do: [:i | string := string, 'abcde'].
text := ((string asText addAttribute: TextColor red), ('xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' asText)).
(PluggableTextMorph on: text text: #yourself accept: #value) openInWindow
Cheers,
Doru
>
> --
> Marcus Denker -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
--
www.tudorgirba.com
"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."
For nested types, I am setting the containing class to be the container
entity of the nested class. I am trying to create a Tree View for my Moose
entities. So, I have
Namespace
Namespace
Class
Method ....
(Just to see my results are correct...)
Earlier I was using downcast to change container entity into a Namespace.
That allowed me to navigate from a parent namespace to a child namespace
using Namespace.getChildScope(). However, Container entity does not allow me
to perform this navigation as the only thing available with ContainerEntity
is belongsTo. My question is: Why cannot we ascertain the containing
elements of a ContainerEntity?
thanx in advanace,
Usman