Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 637 in moose-technology: VerveineJ should show an invocation to the default constructor

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 637 by tu...(a)tudorgirba.com: VerveineJ should show an invocation to the default constructor http://code.google.com/p/moose-technology/issues/detail?id=637 A call to the default constructor should be modeled like: - create a stub constructor in the target class - create an invocation to the constructor See the attached class for a sample. Attachments: DefaultConstructor.java 184 bytes

12 years, 1 month

Issue 636 in moose-technology: VerveineJ should set hasClassScope

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 636 by tu...(a)tudorgirba.com: VerveineJ should set hasClassScope http://code.google.com/p/moose-technology/issues/detail?id=636 Static fields or methods should be marked with hasClassScope=true: public static int attributeWithClassScope; public static void methodWithClassScope() {} See the attached sample class. Attachments: ClassScope.java 179 bytes

12 years, 1 month

moving petitparser to smalltalkhub

by Tudor Girba

Hi, I just discussed with Lukas, and he agrees to move PetitParser under the Moose team in SmalltalkHub. Who volunteers to do the moving? (I would like to do it myself, but the Glamour experience showed that it does not work from home) Cheers, Doru -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

12 years, 1 month

Fwd: [Esug-list] Release of the Pharo consortium web site

by stephane ducasse

Begin forwarded message: From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> Subject: [Esug-list] Release of the Pharo consortium web site Date: March 1, 2013 5:52:03 PM GMT+01:00 To: Association Pharo <association(a)pharo.org>, "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr>, A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr>, pharo-consortium(a)lists.gforge.inria.fr, ESUG Mailing list <esug-list(a)lists.esug.org> Cc: Sylvain Karpf <sylvain.karpf(a)inria.fr>, David Simplot-Ryl <David.Simplot-Ryl(a)inria.fr>, Marie-Agnes Enard <marie-agnes.enard(a)inria.fr> Hi guys After some efforts, we are proud to announce the consortium around Pharo. http://consortium.pharo.org With such consortium, companies and academic partners will be able to collaborate and sustain the development of the Pharo environment and ecosystem. Today we announce the release of the beta version of the official consortium website. Invest in your future, participate to the consortium! Our goal is to be able to pay a couple of full-time engineers to build a bright future for everyone. Thanks Esteban for the effort, lusy for the design, and our first members: Inria, VMWare, yesplan, 2denker, madEnvironment, BetaNine, Versus for their trust We wish you a lot of business and success! The Pharo Team _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

12 years, 1 month

creating a 4.7 release version in ConfigurationOfMoose

by Usman Bhatti

I am going to work on creating a release version of Moose 4.7, because for adapting Moose to pharo 2.0, we will start committing our changes/packages to the new repo and we will not be able to load a 4.7 config. I'll try to create a version with Stef's reloader and adapt it by hand, if need be. Stef, where can I find the latest version of the reloader? usman

12 years, 1 month

a job loading moose from STHub

by Usman Bhatti

https://ci.inria.fr/moose/job/Moose-latest-dev-4.7-ST/ The build is red because RPackage is spawning lots of halt windows at the end of load, otherwise it should be fine. Currently, its pointing to a baseline but we will have to make it load a version with new adaptations for Moose on pharo2.0. usman

12 years, 1 month

moose latest build failing

by Usman Bhatti

Is there something recently changed in Fuel that broke the build? [0m[0m[31m==== Startup Error: Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0mMetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: in Block: [^ self error: 'Name not found: ' , aString] MetacelloMCVersionSpec>>packageNamed:forMap:ifAbsent: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: in Block: [:req | (self... Set>>do: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpec>>resolveToLoadableSpecs: MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... [0m[31mGot startup errors: [0m[31m Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build.sh -i moose -s patch-inputsensor -s testrunner -s moose-tests -o moose-tests [31m[33m

12 years, 1 month

manual one click for 4.7

by Tudor Girba

Hi, I manually put together a one-click distribution. You can find it here: https://dl.dropbox.com/u/18323746/Moose/moose-suite-4.7.zip Please test it. In the future, we need to rebuild the automatic job for creating the distributions. This should be a priority for 4.8. Cheers, Doru -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

12 years, 1 month

model pool dictionaries in FAMIX

by Fabrizio Perin

Hi, Which would be the best way to model in FAMIX connections caused by poolDictionaries? For example: ArrayedCollection subclass: #Text instanceVariableNames: 'string runs' classVariableNames: '' poolDictionaries: 'TextConstants' category: 'Collections-Text' Text can access the class TextConstants becuse specified in its pool dictionary. where should I store the information that TextConstants is in the pool dictionary of Text? Thanks and cheers, Fabrizio

12 years, 1 month

PetitParser on SmalltalkHub

by Nicolas Anquetil

In the process of loading Moose on Pharo 2.0, we had to update the ConfigurationOfPetitSQLParser to add Pharo 2.0 ConfigurationOfPetitSQLParser>>development: spec <symbolicVersion: #development> spec for: #'pharo1.3.x' version: '1.0-baseline'. spec for: #'pharo1.4.x' version: '1.1-baseline'. spec for: #'pharo2.x' version: '1.1-baseline'. But I cannot commit the change ... Other solution would be to change the config Of moose to not load the developement version, but it's not the best solution nicolas -- Nicolas Anquetil -- RMod research team (Inria)

12 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