Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: Moose on pharo 1.2
by Stéphane Ducasse 22 Sep '10

22 Sep '10

On Sep 21, 2010, at 9:43 PM, Laval Jannik wrote: > > On Sep 20, 2010, at 18:52 , Simon Denier wrote: > >> >> On 20 sept. 2010, at 17:14, Laval Jannik wrote: >> >>> Hi guys, >>> >>> It is not so easy to load Moose on Pharo1.2 :) >>> There are two deprecated call during the loading. This is due to FileSystem, we cannot change the source code on the repository. >> >> What's the licence? Can we copy the package in Moose repo until fixes are integrated? MIT and I hope that colin will change it slightly and that we can integrate it in Pharo. > > I don't know, it is on wiresong. > >> >>> ==== >>> >>> For now our fixes are on files attached to the mail. >>> Cheers, >>> Jannik >>> >>> <Mondrian-jl.581.mcz><Moose-MonticelloImporter-jl.12.mcz><ShoutWorkspace.1-jl.7.mcz><Glamour-Morphic-Renderer-jl.6.mcz> >> >> >> Do the fixes break in Pharo 1.1? Could we integrate them and still run in 1.1? > > Only Mondrian seems to be broken with my changes. > So tomorrow, I will commit the rest. > > Cheers, > Jannik > >> >> >>> >>> On Sep 20, 2010, at 16:43 , Laval Jannik wrote: >>> >>>> ===== >>>> >>>> With Cyrille, we fix a part of error tests. Now, I'm not sure that it can work on Pharo1.1. >>>> So we do not save our work on moose repository. >>>> >>>> What do we do for next steps ? >>>> Do we change our Pharo system and go to 1.2 or working on 1.1 ? >> >> >> Check the status of 1.2 dev. If there is a good enough stable version, we can move. Until that, I would prefer to stay with 1.1 right now, just to enjoy a nice stable fast environment for a while, and also so that we can still integrate fixes in 1.1, benefiting to the users who can't/won't move to 1.2 right now. >> >> Actually the best plan is to check whether we could maintain the compability for a while. >> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > --- > Jannik Laval > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

1 0

MAVector
by Alexandre Bergel 21 Sep '10

21 Sep '10

Hi! I analyzed a bit the presence and usage of abstract methods in Moose. MAVector>>initializeSize: is abstract. MOClusteringVector is a subclass of MAVector. MOClusteringVector does not override initializeSize: and is not subclassed. MOClusteringVector is therefore abstract without subclasses. Something has to be fixed somehow. I found a similar situation in Mondrian, and I fixed it. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

cog or no cog?
by Tudor Girba 20 Sep '10

20 Sep '10

Hi, Just out of curiosity, is anyone still working with a non-cog vm? I am asking because I was thinking of releasing 4.1 one click with a Cog VM. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

5 4

Glamour and Magritte validation
by François Tanguy 19 Sep '10

19 Sep '10

Hi, I have built a Glamour browser that uses magritte descriptions. The underlying data model is very simple. There are only integers to be displayed. When I click the save button, I get some validation errors stating that the input entered in the text field is invalid. If I deal with strings that is ok. So I think that the input is not converted into integer and therefore magritte does not like it because an integer is expected but a string is provided. Anybody already tried this use case ? Francois

2 1

About a real solution for analysing Pharo in Moose
by Stéphane Ducasse 16 Sep '10

16 Sep '10

Hi guys I think that we should leverage the pharo infrastructure to be able analyze pharo unstable. We should make sure that we can - load code in a separate system dictionary - perform analysis of code in that separate namespace this way we can use Moose 4.1 in pharo 1.1 to load pharo 1.2 unstable. It will be shaky the first time but it should work. wat do you think? Stef

4 4

Using MouseEnter events from a Mondrian presentation in Glamour
by Simon Denier 15 Sep '10

15 Sep '10

I'm wondering how to use MouseEnter events from Mondrian (when I just move the mouse over an element) in a Glamour presentation. I am not sure how to use it actually. There is an example in MoosePanel when the mouse overs a class in system complexity, class name is displayed in the status bar. It seems like I could perhaps read from the #status port? My idea is that I would like to be able to update a presentation in another pane when I just hover over an element. For example, I could use it to display the source code in a separate pane when discovering a mondrian presentation. I don't like to have too much popup with source code (it hides the visualization), and the benefit to have it in a separate pane is that you always now where to look. (rambling from esug) -- Simon

4 5

+ and - buttons in the easel
by Alexandre Bergel 15 Sep '10

15 Sep '10

Hi! The color of the background of the + and - buttons is different than the color of the window when the window is not selected. http://code.google.com/p/moose-technology/issues/detail?id=457 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

MooseCustomTask and Glamour rendering
by Simon Denier 15 Sep '10

15 Sep '10

Hi It seems I have some problems to mix progress bars (using MooseCustomTask) and Glamour browser (it's related to Arki more precisely). I mean, I select some items in a browser, which then compute lazily their state. Some long computations are done in a Moose custom task to give feedback. But it gives errors or incorrect results in Glamour/Arki when it is done this way, generally because some data are incomplete when the browser is rendering the widget. I'm puzzled by how this happens, because it seems it should be managed by the UI thread. Any hacker willing to take a look at Esug? -- Simon

2 2

Glamour: removed windowFor:
by Veronica Isabel Uquillas Gomez 15 Sep '10

15 Sep '10

Hi Doru, Can't find this method that Torch is using? Is there any reason for the removal? Veronica

1 1

Moose release 4.1
by Laval Jannik 15 Sep '10

15 Sep '10

I am preparing release 4.1. I have a small failure due to XMLParserTest>>testDecodingCharacters --- Jannik Laval

5 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev