Hi!
Moose is able to process code written in Smalltak, a dynamically typed languages. Is there other platform that would work with python, ruby or groovy?
I did some googling, but nothing apparent emerged.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I updated Pharo to the latest version.
It looks like multiple tests fail because something changed in the computation of allRecursiveTypes.
Cheers,
Doru
On 15 Mar 2012, at 22:48, Alexandre Bergel wrote:
> How comes there are so many failed tests ?
>
> Alexandre
>
>
> On 15 Mar 2012, at 16:46, admin(a)moosetechnology.org wrote:
>
>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/886/>
>>
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
Hi,
I used it for various forms of dates. What is the question?
Cheers,
Doru
On 14 Mar 2012, at 16:24, Friedrich Dominicus wrote:
> I wonder if anyone has used PetitParser to parse dates in diverse
> formats.
> e.g
> 01/01/2012
> 07/31/2012
>
> And with failures on things like
> 2012-07-32 or
> 2012-13-01 or
> 2012-02-30 or
> 2011-02-29
>
> Regards
> Friedrich
>
>
>
>
>
> --
> Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim
> Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus
>
--
www.tudorgirba.com
"One cannot do more than one can do."
Thanks a lot. I just needed to set the author before compiling and it worked! Now we have 3 tests that fail. I
I guess this is a pharo issue. Could you report it?
Cheers,
Doru
Sent from my iPhone
On Mar 14, 2012, at 17:21, Alexandre Bergel <abergel(a)dcc.uchile.cl> wrote:
> Apparently, this will also fix the Fame failing tests :-)
> Today is a good day :-)
>
> Alexandre
>
>
> On 14 Mar 2012, at 10:07, Alexandre Bergel wrote:
>
>> I lunched a headless image and checked what happened. Apparently instances of InputEventSensor are not properly initialized in a headless mode. This seems to solve the Glamour failing tests.
>>
>> Can you try something? In the script you use to lunch the tests, can you add before running the tests?
>> -=-=-=-=-=-=-=-=-=-=-=-=
>> InputEventSensor compile: 'initialize
>> super initialize.
>> eventQueue := WaitfreeQueue new.
>> mouseButtons := 0.
>> mousePosition := 0 @ 0.
>> modifiers := 0 '.
>> InputEventSensor allInstances do: #initialize.
>> -=-=-=-=-=-=-=-=-=-=-=-=
>>
>> I suspect this will help. No idea whether this will solve the Fame problem or not.
>>
>> Cheers,
>> Alexandre
>>
>>
>>
>> On 14 Mar 2012, at 07:55, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> This is the only test that is like this. The other failures I cannot
>>> reproduce locally.
>>>
>>> It would be great if you could take a look and see if you can reproduce them.
>>>
>>> Cheers,
>>> Doru
>>>
>>> On Wed, Mar 14, 2012 at 1:42 PM, Alexandre Bergel
>>> <alexandre.bergel(a)me.com> wrote:
>>>> We have those 12 failing test since a long time already.
>>>> I checked some of the tests, and apparently they are due to the underlying Morph. For example:
>>>> | browser |
>>>> browser := GLMExpander new.
>>>> browser show: [ :a | a text ].
>>>> window := browser openOn: #(#a #b #c).
>>>>
>>>> testCreation expect to have "window submorphs last class == MorphTreeMorph", however it gets GeneralScrollPane. Shouldn't the test be simply updated?
>>>>
>>>> Is there anything I could do to help?
>>>>
>>>> Cheers,
>>>> Alexandre
>>>>
>>>> On 14 Mar 2012, at 06:15, admin(a)moosetechnology.org wrote:
>>>>
>>>>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/881/>
>>>>>
>>>>>
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
We wanted to open a DistributionMap with a given windows size. Any idea how
to do it?
We looked with stef in the MOViewRenderer class but nothing jumps to our
eyes.
Thanks.
--
*Guillaume Larcheveque*
Hi,
I used inFamix to create an .mse File of Jython <http://www.jython.org/>.
All works well except the namespacing seems to be a bit off in the model,
e.g. there is a namespace called jython and another one called jython::util
but the first is not defined as parentPackage of the latter. I think they
should be thought - at least for Java systems.
Mircea Lungu told me there was a class floating around somewhere which
fixes this for moose models. Could anyone point me to it? I'd like to use
it for testing.
Also, is inFamix maybe capable of doing that but I haven't found it? Or are
there other tools which do the importing with namespaces linked in this way?
Cheers,
Dennis
Hi all,
I am trying to import an MSE file [1] generated by Verveine-J into the
latest moose-latest-dev image [2].
My image is basically the same you find in the Jenkins build and I am
running it on MacOS 10.7.3.
When the parsing of the file is almost completed I get this dialog:
"Space is low
Warning! Pharo is almost out of memory!
Low space detection is now disabled. [...]"
By simply closing all the windows and restarting the image, I have no luck:
The message still appears.
The message also suggests to "restart the Pharo VM with a larger memory
allocation." Unfortunately I have no idea on how to do this in general, and
on a Mac in particular. I looked at previous threads in the mailing list,
but I was not able to find any solution.
Can anyone help me with this problem, please?
Thank you in advance.
Cheers,
Alberto
[1] http://www.inf.usi.ch/phd/bacchelli/svn_2011_06_30.mse.zip
[2]
http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti…
--
View this message in context: http://moose-dev.97923.n3.nabble.com/Space-is-low-tp3823370p3823370.html
Sent from the moose-dev mailing list archive at Nabble.com.
I've had some trouble with email. I'm not sure if this one made it out
or if I just didn't get it back from the list.
I would have missed any responses.
Ben Coman wrote:
8<----cut-------
> So in the end I added 'self update' to the start of
> GLMMagrittePresentation>>reactOnAnswerFor: as follows...
> reactOnAnswerFor: aValue
> self update.
> ^ answerBlock glamourValue:
> (aValue asGlamorousMultiValue,
> self asGlamorousMultiValue,
> self entity asGlamorousMultiValue)
>
> and now the <cancel> button works as expected. However I still don't
> know what reactOnAnswerFor is meant to do, or if there
> is a more appropriate way of achieving this. Please let me know.
>
> I also haven't had any success getting the #list pane to refresh when
> a change is saved on the #detail pane. Any assistance will be greatly
> appreciated.
>
> cheers, -ben
>
Phew! That was a lot to take in. Upon further investigation I retract
modifying GLMMagrittePresentation.
The solution to both the <save> and <cancel> buttons can be encompassed
entirely within the user code with one additional line 'onAnswer:'
magritteParentPrototype := a magritte.
magritteParentPrototype "these are the essential parts"
title: 'Details';
description: [:person | person magritteDescription] ;
onAnswer: [ :ignore | browser update ] .
I have uploaded this as Glamour-Examples-BenComan.230
Note that I think this only worked for me last time when I had
MagritteMagic loaded onto Moose 4.6.
cheers, Ben
Hello,
I have a one-click moose image downloaded around first week of Feb 2012.
The problem with the image is that it's windows vm that does not launch the
image file. In fact, when I execute the vm, it creates a process (visible
in windows task manager) but nothing happens. We tried to debug it with
Igor but we couldn't (as there is no entry point). The image in the bundle
can be launched with latest windows vm (from pharo server) [meaning that
the problem comes from the vm which we cannot debug].
I downloaded another moose image today and executed its windows vm, and its
working fine.
It would be good to have a jenkins process to run moose on windows vm. Do
we have such a setup? If not, I can create one in the coming weeks.
thanx,
usman