- Moose-dev - INF Mailman

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, 4 months

2
3
0 0

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, 4 months

1
4
0 0

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, 4 months

1
0
0 0

> 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, 4 months

2
1
0 0

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, 4 months

1
1
0 0

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, 4 months

1
3
0 0

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, 4 months

2
1
0 0

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, 4 months

2
3
0 0

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, 4 months

4
7
0 0

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, 4 months

1
1
0 0

Issue 530 in moose-technology: Glamour: highlighting source code does not work anymore

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 530 by vuqui...(a)vub.ac.be: Glamour: highlighting source code does not work anymore http://code.google.com/p/moose-technology/issues/detail?id=530 Text presentations do not highlight Smalltalk methods' source code anymore. All the content appears in red. This happens with the last changes of PharoCore 1.2. I am using both #forSmalltalk #forSmalltalk: * Type-Defect * Component-Glamour

14 years, 4 months

1
2
0 0

Issue 538 in moose-technology: inFusion should recover the references between classes

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 538 by tudor.gi...(a)gmail.com: inFusion should recover the references between classes http://code.google.com/p/moose-technology/issues/detail?id=538 When a class name appears in the source code (not in the type declaration), it should be modeled as a FAMIX.Reference.

14 years, 4 months

1
0
0 0

Issue 535 in moose-technology: inFusion should export isTransient for attributes

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 535 by tudor.gi...(a)gmail.com: inFusion should export isTransient for attributes http://code.google.com/p/moose-technology/issues/detail?id=535 private transient String middleName;

14 years, 4 months

1
0
0 0

Issue 534 in moose-technology: inFusion should export the initialization of attributes in Java static constructs

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 534 by tudor.gi...(a)gmail.com: inFusion should export the initialization of attributes in Java static constructs http://code.google.com/p/moose-technology/issues/detail?id=534 static { RATE_CODES = new HashSet<String>(3); RATE_CODES.add(RATE_ASSITANT_SERVICE); RATE_CODES.add(RATE_MEDICAL_SERVICE); RATE_CODES.add(RATE_TECHNICAL_SERVICE); }

14 years, 4 months

1
0
0 0

Glamour - text presentations - highlighting

by Veronica Isabel Uquillas Gomez

Hi, Showing a method' source code in text presentations does not highlight anymore. All appear in red. Indeed, this happens with the last actualizations of PharoCore 1.2. I just noticed that this was already fixed in Mondrian-easel. Could you also fix it in Glamour? thanks :) Regards, Veronica

14 years, 4 months

2
1
0 0

blue vs green bullet in hudson

by Alexandre Bergel

Hi! Just wondering why a success is represented as a blue bullet and not a green one? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

3
4
0 0

Version numbering, question <provocative email>

by Alexandre Bergel

if I want to be a bit provocative. Why are we in 4.3.X and not in 5.X ? When will we switch to version 5? Are we sure we do not give a "bad" image to be in version 4.X for a couple of years? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

3
2
0 0

Tool tip & transparency

by Alexandre Bergel

Hi! The theme of Pharo 1.2 has changed over the last few weeks. I like the transparency effect. But I feel it is a bit inefficient time to time (cf. screenshot). Is there something that we could do about it? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

3
3
0 0

Adding RPackage>>packageName

by Alexandre Bergel

Hi! Would it be possible to add the method RPackage>>packageName ^ name asString packageName is defined on PackageInfo Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

1
0
0 0

Issue 529 in moose-technology: Mondrian Easel does not offer highlighting anymore

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.3 New issue 529 by tudor.gi...(a)gmail.com: Mondrian Easel does not offer highlighting anymore http://code.google.com/p/moose-technology/issues/detail?id=529 This is due to the changes in Pharo. When using the PluggableShoutMorph we have to set the styler. Something like this: editor := PluggableShoutMorph ... . styler: (SHTextStylerST80 new view: editor; yourself)

14 years, 4 months

1
1
0 0

MOEasel>>method?

by Tudor Girba

Hi Alex, I just noticed this method: MOEasel>>method ^ MOEasel >> #method Obviously you need it for something because you just changed it, but I cannot figure out what its role is :). Could you explain it? Cheers, Doru -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

14 years, 4 months

2
1
0 0

Problem loading JNIPort

by Matthias Junker

Hi, i was trying to load JNIPort as described on squeaksource on my Macbook (OS X 10.6.6). I downloaded the latest Pharo 1.2 from Hudson ( https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/) and opened it using SqueakVM 5.8b12. I was able to load Alien using the following command: Gofer it squeaksource:'MetacelloRepository' ; package: 'ConfigurationOfAlien'; load. ((Smalltalk globals classNamed: 'ConfigurationOfAlien') project version: 'Pharo 1.2') load: 'Core'; load: 'LibC Then i loaded the JNIPort Configuration: Gofer it squeaksource: 'JNIPort'; package: 'ConfigurationOfJNIPort'; load. But when i load the actual project with this: ConfigurationOfJNIPort project latestVersion load I get the following error in the class StandardLibInterface(AlienLibrary)>>load libraryName: '/System/Library/Frameworks/System.framework/System' errorCode: #'not found' When i check on the file system i find a symbolic link which points to /usr/lib/libSystem.B.dylib (which also exists there). Any hints to what i'm doing wrong? Cheers, Matt

14 years, 4 months

3
6
0 0

Issue 525 in moose-technology: Mondrain: when edges are present #draggable is raising an error

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 525 by vuqui...(a)vub.ac.be: Mondrain: when edges are present #draggable is raising an error http://code.google.com/p/moose-technology/issues/detail?id=525 The use of #draggable is raising an error: MOEdge does not understand #translateBy:bounded: Previously it was working without problems. * Type-Defect

14 years, 4 months

1
4
0 0

Cool logo

by Alexandre Bergel

I just download the oneclick. I like the new logo on the top left corner. Speaking about logo, I have never get a feedback of the Mondrian logo. What do you feel about it? Shall I try to produce a new one? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 4 months

1
0
0 0

Fwd: [Pharo-project] Call for Pharo Support **important**

by Tudor Girba

Hi, Pharo is critical for Moose. If you want to support it, please distribute or respond to the below message. Cheers, Doru Begin forwarded message: > From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Date: 15 February 2011 14:02:56 CET > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [Pharo-project] Call for Pharo Support **important** > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Please distribute this message around > > > Dear Pharoers > > We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. > > We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) > > Thanks for your support > > The Pharo Board > > M. Denker, S. Ducasse, and A. Lienhard > > -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

14 years, 4 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev