Moose-dev June 2013

moose-dev@list.inf.unibe.ch

36 participants
163 discussions

Issue 943 in moose-technology: Integrate Rubric in Glamour
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 943 by tu...(a)tudorgirba.com: Integrate Rubric in Glamour http://code.google.com/p/moose-technology/issues/detail?id=943 Rubric can be found at: Gofer new url: 'http://www.smalltalkhub.com/mc/AlainPlantec/Rubric/main'; package: 'Rubric'; load. In particular, we should integrate RubScrolledTextMorph and RubTextFieldMorph. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 3

an stable Moose version for pharo2 ?
by Guillermo Polito 23 Jun '13

23 Jun '13

Hi guys, I was building a simple CI job to run an acceptance test for the pharovm. Now, as we talked with Esteban and Camillo, we want to: - take an stable pharo20 - load an stable freezed version of moose - load an stable freezed version of seaside - run tests as a first attempt. However, I find the configuration of moose has no 4.8 version as I was expecting, and loading the latest development version does not really do it (we want to test the vm, not moose :). How can I get a freezed version of moose working on 2.0? Tx!! Guille

3 3

moose 4.8
by Tudor Girba 23 Jun '13

23 Jun '13

Hi, As soon as all tests are green, we will release 4.8. The target would be end of next week at the latest. Afterwards, we move to Moose 5.0 on top of Pharo 3.0. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

5 6

What is the relevence of referenceVersion in Hismo?
by badja 23 Jun '13

23 Jun '13

In the description of Girba, 2005, "Modeling History to understand Software Evolution", there is a small statement on "referenceVersion" in the Hismo metamodel: "Each Version has a reference to the so called referenceVersion which provides a fixed point in the historical space." This is implemented in Moose Hismo, but there is little description of its relevence to modelling. What is meant by "fixed point in the historical space"? In fact, there is an interface to set it to easily set it to nil!! (HismoEntityVersion class >> with:inHistory:) Can Tudor or someone else able to describe why referenceVersion would be important in time based analysis? Could this be, for example, the "baseline" to which other copies are compared? Can we have a different referenceVersions in different HismoHistoryGroups? Can we change the referenceVersion on the fly during analysis? I can see hints in the names of methods (e.g. isBornPriorToOrInReferenceVersion), but I can't quite catch the semantics. Can you give some guidelines on which version should be selected as the referenceVersion, and why? As I've described earlier, I'm trying to analyse different versions of system development schedules. I'm trying to use the Hismo framework to its best advantage, so I'm trying to understand the semantics as well as the code. Alan. -- View this message in context: http://forum.world.st/What-is-the-relevence-of-referenceVersion-in-Hismo-tp… Sent from the Moose mailing list archive at Nabble.com.

5 11

Issue 829 in moose-technology: Roassal Label Text does not scale with Zoom Out
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 829 by google....(a)ben.coman.com.au: Roassal Label Text does not scale with Zoom Out http://code.google.com/p/moose-technology/issues/detail?id=829 Actions 1. Open Roassal Easel > Example > #arrowed edges > umlLike 2. Click the <Zoom out> button multiple times Expected Behaviour Text gets smaller so as to stay within the border as the label box gets smaller. Observed Behaviour Only the border of the label gets smaller. The text gets the same size until it all overlaps.

1 4

Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Summary: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736 (No comment was entered for this change.)

4 15

Issue 647 in moose-technology: Integrate torch package visualization
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 647 by cy.delau...(a)gmail.com: Integrate torch package visualization http://code.google.com/p/moose-technology/issues/detail?id=647 Maybe it would be a good idea (?) to use / integrate the torch packages visualization in moose ? http://hal.archives-ouvertes.fr/docs/00/53/15/08/PDF/Uqui10a-Torch-WCRE10.p…

2 4

Re: Issue 469 in moose-technology: integrate Kontractor
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Labels: Milestone-4.3 Comment #4 on issue 469 by tudor.girba: integrate Kontractor http://code.google.com/p/moose-technology/issues/detail?id=469 What is the status of this?

1 3

Re: Issue 437 in moose-technology: Text is not affected by zooming in Mondrian
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Comment #1 on issue 437 by alexandre.bergel: Text is not affected by zooming in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=437 Situation has been slightly improved, but this is clearly not satisfactory

1 4

Re: Issue 401 in moose-technology: fromPositions: and toPositions:
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Status: WontFix Comment #2 on issue 401 by tu...(a)tudorgirba.com: fromPositions: and toPositions: http://code.google.com/p/moose-technology/issues/detail?id=401 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2013