Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

How to only import in a MooseModel the selected packages in the MooseBrowser?

by Romain PEIRS

Hi, I would know if there is a mean to only import in a MooseModel the selected packages in the MooseBrowser? For example, when I import the bundle Moose in Moose Browser, I would only have in the MooseModel the packages of the bundle. I hope it was clear. Romain

16 years, 11 months

How to load automatically packages on which depend packages which I want to publish?

by Romain PEIRS

Hi, I would know how to load automatically packages on which depend packages which I want to publish? Anyone knows how to do that? Thanks J Romain

16 years, 11 months

About a model of changes on top of famix

by Stéphane Ducasse

let us imagine that we would like to see what would happen if we would move a class A from package P1 to P2, without changing the source code and may be been able to undo the change Solution A: We could copy the complete model, modify it. (and keep somewhere an history) Solution B: We could change the model and keep an history of the changes (move A P1 P2). Solution C: I could cache in each model a timestamp similar to what frederic pluquet did and know at which version modification we are. then for a given changes I could get the model by getting entity at the same level or lower. Any thoughts on that. I have the impression that solution B is easier. stef

16 years, 11 months

Moose Dojo at ESUG

by stephane ducasse

Hi doru I anounced a Moose Dojo at ESUG. Could you update the moose.unibe.ch web pages. Alex it would be good to improve the description and to announce it in other forums. http://www.esug.org/conferences/16thinternationalsmalltalkjointconference20… Stef

17 years

Re: famix and fame

by Adrian Kuhn

A word about addTo* methods and slots vs links Fame offers two implementations for properties. If you use links instead of slots, you do not need addTo* methods because the collection returned by a getter is "hot". As far I know the current code generation uses slots, whereas the hand-written code of FM3 uses links. So what is the difference? In short: slots implement the "end" of each property, where as links model the "association" established by the property. For a large project, as eg Moose, I personally suggest to use links instead of slots! Why? Links are less code (not *slot method) Links are less memory (not wrapper objects at 1-end) Links are hot (add and remove on returned collection) Links are more debuggable (no wrapper in the way) @Toon ... this is your call to arms, what are the advantages of slots? :) But first a general issue, why slots or links at all? To automatically update the opposite of an association. A half-only established association is one of the worst bugs in a data-model, it is, to say so, the blink dog of software engineering. Half of the time it works, half of the time not. Hence we decided to make associations a first-level citizen in Fame. Considering Library and Book as an example of a multivalued, ie ( 1 : n ) property, an implementation using slots looks like this Library >> initialize books := FMManySlot new on: self; oppInstVar: #library; youself Library >> books <MSEProperty: #books type: Book opposite: #library> <multivalued> ^books values Library >> books: allBooks books set: allBooks Libary >> booksSlot ^books Library >> addToBooks: aBook aBook libary: self Library >> removeFromBooks: aBook aBook library: nil Book >> initialize library := OneSlot new owner: self; oppInstVar: #books; yourself. Book >> library <MSEProperty: #library type: Library opposite: #books> ^library value Book >> library: newLibrary library set: newLibrary Book >> librarySlot ^library And code to add / remove a book to / from a library like aLibrary addToBooks: newBook aLibrary removeFromBooks: aBook And an implementation using links looks like this Library >> initialize books := FMMultivalueLink on: self opposite: #library Library >> books <MSEProperty: #books type: Book opposite: #library> <multivalued> ^books Library >> books: allBooks books value: allBooks Book >> initialize library := nil Book >> library <MSEProperty: #library type: Library opposite: #books> ^library Book >> library: newLibrary library := FMMultivalueLink on: self update: #books from: self library to newLibrary And code to add / remove a book to / from a library like aLibrary books add: newBook aLibrary books remove: aBook Please note, this is not a violation of the Law of Demeter, since accessing the elements of a container class (ie collection) does not account as "talking" in the sense of the law's "never talk to strangers". As you can see, using links there is no special need for those notorious add / remove methods. cheers, AA > Hi, > > Today, Toon and me worked on Fame and FAMIX in Squeak. We regenerated > FAMIX and the results are: > > - Added addTo* like methods (for example, FAMIXClass>>addToMethods: > aMethod). The reason why it's not just addMethod: is due to us being > unable tofind a simple and robust algorithm for producing English > singular. Also, just taking the type into account is not enough > because of cases like incomingInvocations and outgoingInvocations. > > - Changed the names of parameters to reflect whether they are > collections or not. > > - Made the Smalltalk superclass to be MooseEntity. > > > We also worked on creating the meta-repository for FAMIX and we also > have MSE files with FAMIX models loading. There still some work to be > done to populate the MooseModel. > > I also fixed the loading error related to FMBookMock and fixed some . > I will continue with working on the Moose Finder over the next days. > > Doru > > -- > www.tudorgirba.com > www.tudorgirba.com/blog > > "Value is always contextual."

17 years

Symbols not define

by Menanteau Jannick

Hello, I'm beginning with moose and I've a problem with Mondrian I want to generate visualization with this code : view newShape rectangle; height: #numberOfMethods; width: #numberOfAttributes; linearFillColor: #numberOfLinesOfCode within: classes; withBorder. view nodes: classes. view edges: classes from: [:each | each superclass] to: [:each | each]. view treeLayout. I think it's correct because I've found it on http://moose.unibe.ch/tools/mondrian/tour?_s=LrcZtOGEBQIygSJg&_k=RnnrLpmU&_… But I've problem with symbols (like #numberOfMethods) : they are not defined. Maybe there is a special manipulation to do ? I've done this : - open Moose - "Open in Mondrian Easel" - inset this code in the window - "generate view" Thanks to help me

17 years

Re: Tests Mondrian

by Alexandre Bergel

Hi Jannick! Glad to hear that you jump on the boat! Best would be to ask the moose mailing list. You may want to register the mailing list for this. I do not have the answer right now. Cheers, Alexandre On 27 Jun 2008, at 14:51, jannick.menanteau.gmail wrote: > J'essai de générer des visualisations dans Mondrian: > > view newShape rectangle; height: #numberOfMethods; width: > #numberOfAttributes; linearFillColor: #numberOfLinesOfCode within: > classes; withBorder. > view nodes: classes. > view edges: classes > from: [:each | each superclass] > to: [:each | each]. > view treeLayout. > > C'est un code trouvé sur http://moose.unibe.ch/tools/mondrian/tour?_s=LrcZtOGEBQIygSJg&_k=RnnrLpmU&_… > > Le problème est que les symboles (#numberOfMethods par exemple) ne > sont pas définis... > Y a-t-il une manipulation spécifique à faire ? > > Voici comment j'ai procédé : > - ouverture de Moose > - "open in Mondrian Easel" > - insertion du code dans la fenêtre au centre bas > - "generate view" > > Merci > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

17 years

google code

by Orla Greevy

Hi, did someone set up the google code for Moose? If so can you send the link... Orla ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

17 years

group?

by stéphane ducasse

Hi doru in Squeak I started to get some green tests :) Now if you load and try to run testClassSides you get an error because allClasses does not return a model but a collection. classSide ^self isClassSide ifFalse: [self mooseModel allClasses entityNamed: (self mooseName , '_class') asSymbol] ifTrue: [self] can you have a look? Stef

17 years

Layering in moose

by stéphane ducasse

Hi Doru There are several methods in MooseFamixModel that depend on MooseFamixExtensions. I suggest to move them there. Do we agree? - la méthode hasSubclasses dans FAMIXClass (Root::Smalltalk::SCG::Moose::FAMIXClass.hasSubclasses()- >numberOfChildren()) - la méthode hasSuperclasses dans FAMIXClass (Root::Smalltalk::SCG::Moose::FAMIXClass.hasSuperclasses()- >numberOfParents() ) - la méthode hasEmptyBody dans FAMIXAbstractBehaviouralEntity (2 invocations: Root ::Smalltalk::SCG::Moose::FAMIXAbstractBehaviouralEntity.hasEmptyBody()- >numberOfAccesses() et Root ::Smalltalk::SCG::Moose::FAMIXAbstractBehaviouralEntity.hasEmptyBody()- >numberOfOutgoingInvocations() ) Then in MooseUI mooseKill <menuItem: 'Kill' nameKey: nil menu: #(#menuBar #tools #mooseUtilities) position: 1> SCG.Moose.MooseModel kill depends on MooeUIExtensions So may be we should move it there. Stef

17 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev