Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Limitation of Mondrian?
by Alexandre Bergel 30 Apr '11

30 Apr '11

Hi! I often bump into a problem having the following gist: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= view nodes: #( $a $b $a). view edgesFromAssociations: { $a -> $b . $b -> $a} -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= How can I express the the second $a and not the first when defining edges? I have the impression this limitation comes from the fact that two different nodes have the same model behind ($a), and there is no way to distinguish between them. An easy and backward compatible solution would be to permit to provide nodes: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= nodes := view nodes: #( $a $b $a). view edgesFromAssociations: { nodes first -> nodes second . nodes second -> nodes third } -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Opinion? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

Issue 541 in moose-technology: Create an initial Moose help :)
by moose-technology＠googlecode.com 30 Apr '11

30 Apr '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-MooseCore New issue 541 by tudor.gi...(a)gmail.com: Create an initial Moose help :) http://code.google.com/p/moose-technology/issues/detail?id=541 We should have a Moose help entry in ProfStef. The idea is to pick some existing pieces of text from the webpage and the book.

1 1

configuration question: package only in group
by Tudor Girba 30 Apr '11

30 Apr '11

Hi, ConfigurationOfFuelMooseExtensions has the following baseline and version definitions and I am not sure whether they are correct. The problem is that the baseline defines a package only in a group, and then the version defines the version for it. Loading seems to load just fine. If I simply load the version, it loads the two packages defined in the Core group as expected. However, my problem is that when I query version 1.1 for packages, it retrieves the extra FuelMooseExtensionBenchmarks package. Could someone look into this? baseline11: spec <version: '1.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'http://www.squeaksource.com/Fuel'. spec package: 'FuelFameExtension' with: [ spec requires: 'Fuel' ]; package: 'FuelMooseExtension' with: [ spec requires: 'FuelFameExtension' ]. spec group: 'default' with: #('Core'); group: 'Core' with: #('FuelFameExtension' 'FuelMooseExtension'); group: 'Tests' with: #('FuelFameExtension' 'FuelMooseExtension'); group: 'Benchmarks' with: #('FuelFameExtension' 'FuelMooseExtension' 'FuelMooseExtensionBenchmarks'). spec project: 'Fuel' with: [ spec className: 'ConfigurationOfFuel'; loads: #('CoreWithProgressBar' ); file: 'ConfigurationOfFuel'; repository: 'http://www.squeaksource.com/Fuel' ] ]. version11: spec <version: '1.1' imports: #('1.1-baseline') > spec for: #common do: [ spec blessing: #release. spec project: 'Fuel' with: '1.1'; package: 'FuelFameExtension' with: 'FuelFameExtension-MartinDias.28'; package: 'FuelMooseExtension' with: 'FuelMooseExtension-MartinDias.8'; package: 'FuelMooseExtensionBenchmarks' with: 'FuelMooseExtensionBenchmarks-MartinDias.2']. Cheers, Doru -- www.tudorgirba.com "Some battles are better lost than fought."

4 15

Issue 597 in moose-technology: Minimal doc necessary
by moose-technology＠googlecode.com 30 Apr '11

30 Apr '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 597 by alexandr...(a)gmail.com: Minimal doc necessary http://code.google.com/p/moose-technology/issues/detail?id=597 When I open a moose panel, it have several icons: MSE->, ST ->, FL-> Adding a one line description will be good. If this issue is accepted, I can add something like "UIManager default inform: 'MSE is a file format ...'" when pressing MSE->

1 4

Issue 605 in moose-technology: Glamour does not properly update the rendering of Magritte presentations
by moose-technology＠googlecode.com 30 Apr '11

30 Apr '11

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.4 New issue 605 by tudor.gi...(a)gmail.com: Glamour does not properly update the rendering of Magritte presentations http://code.google.com/p/moose-technology/issues/detail?id=605 If you send update to a Magritte presentation, the whole morph seems to disappear.

1 1

Issue 602 in moose-technology: Better help
by moose-technology＠googlecode.com 29 Apr '11

29 Apr '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hapao New issue 602 by alexandr...(a)gmail.com: Better help http://code.google.com/p/moose-technology/issues/detail?id=602 Help should be present, everywhere, all the time Thanks Laurent & Patrick

1 2

Issue 547 in moose-technology: integrate fuel in ConfigurationOfMoose
by moose-technology＠googlecode.com 29 Apr '11

29 Apr '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Milestone-4.4 New issue 547 by jannik.l...(a)gmail.com: integrate fuel in ConfigurationOfMoose http://code.google.com/p/moose-technology/issues/detail?id=547 Gofer new squeaksource: 'Fuel'; package: 'ConfigurationOfFuelMooseExtension'; load. (Smalltalk at: #ConfigurationOfFuelMooseExtension) perform: #load

1 3

Issue 593 in moose-technology: Fuel import/export should provide progress bar
by moose-technology＠googlecode.com 29 Apr '11

29 Apr '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.4 New issue 593 by tudor.gi...(a)gmail.com: Fuel import/export should provide progress bar http://code.google.com/p/moose-technology/issues/detail?id=593 Fuel import/export should provide progress bar.

1 2

Fuel?
by Alexandre Bergel 29 Apr '11

29 Apr '11

Hi! What is Fuel? By reading the unit test, it seems that it is a serializer. Is there a description somewhere? There is none on moosetechnology.org and almost nothing on squeaksource. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 7

Re: wrong meta model definition
by Tudor Girba 29 Apr '11

29 Apr '11

Thanks for reporting this. Indeed, we have to make the meta-model rules work again. I will see if I can refresh them in the context of the OnMoose report (this is in the Arki project). Cheers, Doru On 26 Apr 2011, at 13:38, Fabrizio Perin wrote: > Hi Doru, > I was looking with Raffael to the definition of the meta model i we might find an inconsistency: > > You define: > > FAMIXGlobalVariable>>>parentModule > <MSEProperty: #parentModule type: #FAMIXModule opposite: #globalVariables> > <MSEComment: 'Module (typically a file) defining the global variable.'> > ^ self privateState > attributeAt: #parentModule > ifAbsentPut: [ nil ] > > But the opposite globalVariable is not define in FAMIXModule but into FAMIXScopingEntity. So either the pragmas in FAMIXGlobalVariable>>>parentModule became like this: > <MSEProperty: #parentModule type: #FAMIXScopingEntity opposite: #globalVariables> > <MSEComment: 'Module (typically a file) defining the global variable.'> > > (In this case the property should be called parentScope not parentModule) > > or you move to FAMIXModule > > FAMIXScopingEntity>>>globalVariables > <MSEProperty: #globalVariables type: #FAMIXGlobalVariable opposite: #parentScope> <multivalued> <derived> > <MSEComment: 'Global variables defined in the scope, if any.'> > > I would go for the first. > > Thanks, > > Fabrizio and Raffael -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev