Moose-dev April 2011

moose-dev@list.inf.unibe.ch

29 participants
180 discussions

Issue 587 in moose-technology: Add interaction announcements to EyeSee

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee Milestone-4.4 New issue 587 by tudor.gi...(a)gmail.com: Add interaction announcements to EyeSee http://code.google.com/p/moose-technology/issues/detail?id=587 EyeSee should announce mouse interactions with the data.

14 years, 2 months

Exploring subversion histories with Kumpel

by Matthias Junker

Hi, i would like to announce the first release of Kumpel for Moose. Kumpel is a tool for exploring the history of a software system. The history data can be extracted from any Subversion repository. It uses Java KumpelProjectLoader to connect to a repository using the subversion client library svnkit. The model is based on Hismo and therefore histories and versions are modeled as first class entities. Kumpel was originally called YellowSubmarine and was developed for Visualworks and now ported to Pharo. The performance of loading a model was much improved compared to the Visualworks version. You can find more information here: http://www.moosetechnology.org/tools/kumpel I'm glad about any kind of feedback. If there are any questions, don't hesitate to send them to me or the Moose mailing list. Cheers, Matt

14 years, 2 months

Moose Entity >> mmGetProperty: / mmSetProperty:to:

by Tudor Girba

Hi Cyrille, I see that you added the mmGetProperty: / mmSetProperty:to methods back in MooseEntity. They are not correct because they depend on the internals of the PropertyDescription, and they change the semantics of the method defined in Object: mmGetProperty: aFM3PropertyDescription (self class canUnderstand: aFM3PropertyDescription implementingSelector) ifTrue: [ ^ self perform: aFM3PropertyDescription implementingSelector ] ifFalse: [ ^ self propertyNamed: aFM3PropertyDescription name ]. mmSetProperty: aFM3PropertyDescription to: value (self class canUnderstand: aFM3PropertyDescription implementingSelector asMutator) ifTrue: [ self perform: aFM3PropertyDescription implementingSelector asMutator with: value ] ifFalse: [self propertyNamed: aFM3PropertyDescription name put: value]. This breaks Metanool and it is not nice. The comment of your commit says that you are using it in Menssana. I am sure we can find another solution. So, could you describe the scenario you are using it in? Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

14 years, 2 months

Hudson crashes on VerveineJ :-(

by Nicolas Anquetil

Hi, Back after ICSM submissions :-) I noticed that Hudson is consistently crashing on the LAN Model tests. This is a shame because there are 19 _green_ tests in this suite :-) This would certainly improve the look of the project in the summary page :-) Anything I can do to help? --- Error Message Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit. Stacktrace junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit. --- nicolas

14 years, 2 months

system complexity with labels

by Tudor Girba

Hi, Thanks to the improved drawing of ComplexShapes in Mondrian, I updated the SystemComplexity to display the names for each hierarchy, like we had it in VW. Take a look at the attachment. Cheers, Doru -- www.tudorgirba.com "Value is always contextual."

14 years, 2 months

Issue 592 in moose-technology: System complexity should offer the name of hierarchies and an empty background

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Milestone-4.4 New issue 592 by tudor.gi...(a)gmail.com: System complexity should offer the name of hierarchies and an empty background http://code.google.com/p/moose-technology/issues/detail?id=592 Each hierarchy should be labelled. Each hierarchy should have an empty background.

14 years, 2 months

Issue 591 in moose-technology: ComplexShape blocks are executed also on children

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-High Component-Mondrian Milestone-4.4 New issue 591 by tudor.gi...(a)gmail.com: ComplexShape blocks are executed also on children http://code.google.com/p/moose-technology/issues/detail?id=591 Take the following example: view shape form: [:builder | builder column; pref; center; row; fill; row; fill. builder x:1 y:1 add: (MORectangleShape new text: [:col | (col first + 100) asString ]). builder x:1 y:2 add: MOChildrenShape new]. view node: #(10 20) forIt: [ view nodes: #(a b) ]. You will get a DNU due to Character not understanding +. It looks like the defined shape is also somehow run for the children, which is wrong.

14 years, 2 months

Issue 510 in moose-technology: Introduce Port>>transientValue:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 510 by tudor.gi...(a)gmail.com: Introduce Port>>transientValue: http://code.google.com/p/moose-technology/issues/detail?id=510 We should be able to set the value of a port only temporarily. This would be useful for triggering other transmissions. For example, to implement a search like behavior we could use the code from below. The problem is that if you press the search icon once, then change the selection manually, and then press the button again, the selection will not change because the #focusOne port did not change the value. |browser | browser := GLMTabulator new. browser act: [:b | (b pane port: #focusOne) value: 3 ] icon: MooseIcons mooseSearch entitled: 'Search'. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a | a tree display: [:x | 1 to: x]]. browser transmit to: #two; from: #one; andShow: [ :a | a tree display: [:x | 1 to: x*2]]. browser transmit to: #one port: #selection; fromOutsidePort: #focusOne. browser openOn: 3

14 years, 2 months

Issue 577 in moose-technology: ChildrenShape does not get centered

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.4 New issue 577 by tudor.gi...(a)gmail.com: ChildrenShape does not get centered http://code.google.com/p/moose-technology/issues/detail?id=577 I am trying to align a ChildrenShape to the center of a column, but it does not work. On the other hand, a simple rectangle looks like it works fine. In the below example, both the top row and the bottom one should be centered: view shape form: [:builder | builder column; pref; center; fill; row; fill; row; fill. builder x:1 y:1 add: (MORectangleShape new text: #asString). builder x:1 y:2 add: (MORectangleShape new). builder x:1 y:2 add: (MOChildrenShape new) ]. view nodes: #('label longer than the children' 'smal') forEach: [ :each | view nodes: #(1 2 3 4) ].

14 years, 2 months

Re: Fwd: nouvelle version de moose

by Tudor Girba

Hi Karine, I took a look at your MSE file. The problem is that VerveineJ used to not export ImplicitVariables correctly. It should be fixed in the meantime. Please, try with the latest VerveineJ and let us know if you still encounter the problem. Cheers, Doru On 15 Apr 2011, at 10:59, Karine Mordal-Manet wrote: > Hi Doru, > > >> Since a week, we changed the look and feel, and your screenshot still shows the older look, so I know that your version is older :). Please try again, and let's see if you still get the same problem. > > > I have downloaded the latest version: >>>> http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… >>> > > and I have open my MSE file with moose and I have the same issue. > > I think that I should create a new MSE file from source file of eclipse to resolve this issue. But if you want download the MSE file which I work actually it is possible via dropbox ? > > > Karine. > > > > Le 14 avr. 2011 à 22:10, Tudor Girba a écrit : > >> Hi Karine, >> >> Version 4.4 is under development, and you will get a new build every night :). >> >> Since a week, we changed the look and feel, and your screenshot still shows the older look, so I know that your version is older :). Please try again, and let's see if you still get the same problem. >> >> In the meantime, would it be possible to provide the MSE file somewhere for download? >> >> Cheers, >> Doru >> >> >> On 14 Apr 2011, at 14:12, Karine Mordal-Manet wrote: >> >>> Hi, >>> >>> The MSE file used was generated by VerveineJ. It's a MSE from eclipse application, source files in java. >>> I use the moose_suite-4_4_dev from http://www.moosetechnology.org/download/4.4. It is exactly the same or not ? >>> >>> >>> >>> Karine. >>> >>> >>> >>> Le 14 avr. 2011 à 13:54, Tudor Girba a écrit : >>> >>>> Hi Karine, >>>> >>>> The problem seems to be related to the information from the MSE file. What did you use to create this file? >>>> >>>> Would it be possible to redo the experiment using the latest development image? >>>> http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 14 Apr 2011, at 12:55, Stéphane Ducasse wrote: >>>> >>>>> Hi >>>>> >>>>> guys can one of you help karine >>>>> >>>>> Stef >>>>> >>>>> Begin forwarded message: >>>>> >>>>>> From: Karine Mordal-Manet <kmordal(a)gmail.com> >>>>>> Date: April 14, 2011 11:10:50 AM GMT+02:00 >>>>>> To: Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr>, Stéphane Ducasse <stephane.ducasse(a)inria.fr> >>>>>> Subject: nouvelle version de moose >>>>>> >>>>>> Hello, >>>>>> >>>>>> j'ai telechargé la dernière version de moose et j'ai exactement les mêmes erreurs et les memes soucis : >>>>>> les sloc sont à 0 >>>>>> certaines méthodes entrainent des erreurs lorsque j'essaie d'obtenir des metriques. >>>>>> Je te met une copie d'écran. >>>>>> >>>>>> >>>>>> >>>>>> K. >>>>> <Capture díÈcran 2011-04-14 ‡ 11.08.11.png> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Relationships are of two kinds: those we choose and those that happen. They both matter." >>>> >>>> >>>> >>>> >>>> >>> >> >> -- >> www.tudorgirba.com >> >> "What we can governs what we wish." >> >> >> > -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

14 years, 2 months

← Newer
1
...
9
10
11
12
13
14
15
...
18
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 April 2011