Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Andre Hora

Hello, I would like to know if it is possible to import XML code to Moose. I saw in the Moose Book ( http://www.themoosebook.org/book/introduction/nutshell) that it is possible. thanks! -- Andre Hora

14 years, 2 months

Issue 524 in moose-technology: Importing from Monticello is not working

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MonticelloImporter New issue 524 by andreho...(a)gmail.com: Importing from Monticello is not working http://code.google.com/p/moose-technology/issues/detail?id=524 The Importing from Monticello is not working in the last version of moose-latest-dev: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… I got this messsage when I try to open a Monticello package with the importer using the Moose Panel: MessageNotUnderstood: MooseMonticelloMethodPopulator>>ensureImplicitVariable:inFamixMethod:

14 years, 2 months

Project version (Moose, DSM, RPackage, Glamour, SmallDude)

by Alexandre Bergel

Hi! I think I reached a first milestone in my quest to have consistent and traceable version in Moose. Version 4.3.3 is now defined. I produced the versions: - DSM 2.1 - RPackage 1.0 - Glamour 2.1 - SmallDude 2.1 I created version 4.3.2. and 4.3.3 of Moose. - 4.3.2 uses the 'default' version of SmallDude. It is not necessary, but it helped me to track down some problem. - 4.3.3 does not depend on any baseline. This is an important step since it means that we should be able to load 4.3.3 of Moose in 10 years from now, and so, whatsoever you will commit in the dependent packages. So, at the next commit of any packages, I will produce version 4.3.4 and so on. The configurations were full of problems (e.g., PetitJava that does not require PetitParser for example). This means that the validator of Metacello seriously needs to be improved. It took me some time to identify and fix all this. I worked with Pharo1.2OneClick image. I haven't tried with Core. Now, the question is, should we create a hudson project to try the stable version? To make my life simpler, I always assign the last version as the stable version. I hope this is ok with you. Comments are welcome Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 2 months

> 2500 tests

by Tudor Girba

Hi, I just wanted to let you know that the amount of tests in Moose Suite just passed the threshold of 2500. The next step is to improve the coverage :). Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

14 years, 2 months

configuration of moose is broken

by Tudor Girba

Hi, ConfigurationOfMoose is broken. I tried to introduce ConfigurationOfFame and somehow all the missing requirements are now exploding and I cannot load it anymore. It looks like it will take some hours of work. Please do not touch these configurations for now. I will get back with another status report later today. Cheers, Doru -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

14 years, 2 months

Issue 508 in moose-technology: Fix the random Fame tests

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Fame Milestone-4.3 New issue 508 by tudor.gi...(a)gmail.com: Fix the random Fame tests http://code.google.com/p/moose-technology/issues/detail?id=508 These tests randomly crash: Fame.Tests.FMSingleEdgeStrategyTest.testMarkBlue Fame.Tests.FMSingleEdgeStrategyTest.testMarkRed Fame.Tests.FMSingleEdgeStrategyTest.testPropagationGraph Fame.Tests.FMSingleEdgeStrategyTest.testSetupGraph I have no idea why, but on the other hand it seems that they do not test something that we really use.

14 years, 2 months

Project version (Moose, DSM, RPackage, Glamour, SmallDude)

by Alexandre Bergel

14 years, 2 months

how do I browse the famix metamodel using the dedicated metamodel browser

by Stéphane Ducasse

hi guys how do I browse the famix metamodel using the dedicated metamodel browser Stef

14 years, 2 months

MOViewRendered>>edges:from:toAll: ???

by Nicolas Anquetil

What is the purpose of the first argument of this method? MOViewRendered>> edges: aCollection from: aFromBlock toAll: aToBlock "aToBlock should return a collection, edges will be drawn from the element returned by aFromBlock to this collection" ^self edges: aCollection from: aFromBlock toAll: aToBlock using: self edgeShape nicolas

14 years, 2 months

Re: rpackage does not refresh on class rename

by Cyrille Delaunay

All work well with class refactoring, the problem is that when opening a moose image, RPackageOrganizer has not yet registered to system announcements. This should be done in the initialization of the class RPackageOrganizer. If I do myself a 'ConfigurationOfRPackage loadDefault' in a fresh pharo image, the organizer correctly register to announcements. Could it be a problem with metacello that does not correctly initialize classes ? 2011/2/15 Tudor Girba <tudor(a)tudorgirba.com> > Don't forget to write a test :) > > Doru > > > On 15 Feb 2011, at 11:36, Cyrille Delaunay wrote: > > > Indeed there is something wrong. I will try to fix that today > > > > 2011/2/15 Tudor Girba <tudor(a)tudorgirba.com> > > I did not try recently. But if I remembered correctly, I just performed a > rename refactoring and then checked the RPackage model. > > > > Cheers, > > Doru > > > > > > On 15 Feb 2011, at 11:14, Cyrille Delaunay wrote: > > > > > Do you still have this problem? > > > > > > 2011/1/31 Cyrille Delaunay <cy.delaunay(a)gmail.com> > > > Thanks, I will look at that > > > > > > 2011/1/31 Tudor Girba <tudor(a)tudorgirba.com> > > > > > > Hi Cyrille, > > > > > > I noticed a case in which the RPackage did not seem to refresh after > performing a class rename refactoring. > > > > > > I did not have a chance to write a test case for this, but I think it > probably affects the importing as well. > > > > > > Cheers, > > > Doru > > > > > > > > > -- > > > www.tudorgirba.com > > > > > > "No matter how many recipes we know, we still value a chef." > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > www.tudorgirba.com > > > > "Reasonable is what we are accustomed with." > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow." > > > > >

14 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev