Moose-dev June 2013

moose-dev@list.inf.unibe.ch

36 participants
163 discussions

Equivalence relation on FAMIX entities
by Serge Stinckwich 14 Jun '13

14 Jun '13

Hi all, I want to implement equivalence relation on FAMIX entities. For example, methods m1, m2 are equivalent if they have the same name, same signature and their classes have the same name. Any idea to introduce these relations in a customizable way in FAMIX ? I guess I have to introduce a new meta-model in the FAMIX family ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

4 4

Re: [Pharo-dev] Modification on CollectionsExtensions
by Guillaume Larcheveque 13 Jun '13

13 Jun '13

Ok so if everyone agree I will remove the flatCollect: method from CollectionExtensions since Sebastian made the correction in Pharo 3.0. 2013/6/12 Stéphane Ducasse <stephane.ducasse(a)inria.fr> > > On Jun 12, 2013, at 1:02 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > > ok, i understood, > > Discussing with Marcus we believe that it would be better to keep > Collecition>>gather: and add Collection>>flatCollect: (with the same > implementation) and put a comment in gather: saying that is kept for > compatibility purposes. > > flatCollect: will be included in Pharo and will be removed from > CollectionExtensions. > > > + 1 > > >> -- *Guillaume Larcheveque*

3 2

Jenkins build became unstable: moose-latest-dev-4.8 #569
by admin＠moosetechnology.org 12 Jun '13

12 Jun '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/569/>

1 0

FAME being built for an hour already
by Yuriy Tymchuk 12 Jun '13

12 Jun '13

So fame job is already taking 1hour when it usually took 48sec. It looks like stuck at Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save fame I haven't figured out the problem yet. Does anybody have some suggestion that can help? Uko -- View this message in context: http://moose-dev.97923.n3.nabble.com/FAME-being-built-for-an-hour-already-t… Sent from the moose-dev mailing list archive at Nabble.com.

4 6

Re: [Pharo-dev] Modification on CollectionsExtensions
by Guillaume Larcheveque 12 Jun '13

12 Jun '13

I think the simplest solution is to keep both and that flatCollect directly call gather: If you agree with that, I will correct the moose extension package 2013/6/11 Stéphane Ducasse <stephane.ducasse(a)inria.fr> > gather: sucks as a name. > flatCollect: is much better so do not remove it. > > On Jun 11, 2013, at 4:53 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > > If they are not different so a better way would be replace #flatenCollect: > by #gather: > but anyway, moose people should decide and commit the change since i am > not a moose developer. > > > 2013/6/11 Marcus Denker <marcus.denker(a)inria.fr> > >> >> On Jun 11, 2013, at 4:24 PM, Frank Shearar <frank.shearar(a)gmail.com> >> wrote: >> >> > On 11 June 2013 14:18, Sebastian Tleye <stleye(a)gmail.com> wrote: >> >> Hello, >> >> >> >> Fixing some bugs in Traits we realized that it would be good idea to >> use >> >> CollectionsExtensions package (it has some useful functions), also it >> would >> >> be great to include CollectionsExtensions in Pharo 3.0. >> > >> > Is this the HPI library? I seem to recall TraitClasses [1] using it. >> >> CollectionExtension is from Moose. >> >> the Trait based Stream refactoring was done some years ago but has not >> been used >> or maintained. >> >> Marcus >> > > > -- *Guillaume Larcheveque*

3 3

Re: #stable not defined
by Stephan Eggermont 12 Jun '13

12 Jun '13

Sean wrote >Thomas Worthington-2 wrote >>Regardless, what should I do to get SOME version of, say, Moose >>or CairoGraphics loaded up? >I tried to load Moose per the instructions on their website [1] and got and error, so I'm not sure. I forwarded the error to >their mailing list [2] Could it be a well known vm bug? https://pharo.fogbugz.com/default.asp?10395 The released version of Moose is 4.7, which is based on Pharo 1.4 Moose 4.8 is based on Pharo 2.0 and is very close to release, and perfectly useable. Installing Moose from Monticello packages takes a lot of time as it is large, so I recommend downloading a development build from http://www.moosetechnology.org/download/4.8 I fully agree that suggesting to install #stable versions of configurations where stable is not defined is not very useful. Stephan

1 0

Re: [Pharo-dev] Modification on CollectionsExtensions
by Sebastian Tleye 11 Jun '13

11 Jun '13

I don't know, i should see the implementation, i just want to remove the dependency between CollectionsExtensions and Nile and one way to do it is modifying #flatCollect: implementation. if they are the same #flatCollect: could be remove safely replaced. 2013/6/11 Camille Teruel <camille.teruel(a)gmail.com> > > On 11 juin 2013, at 15:18, Sebastian Tleye wrote: > > > Hello, > > > > Fixing some bugs in Traits we realized that it would be good idea to use > CollectionsExtensions package (it has some useful functions), also it would > be great to include CollectionsExtensions in Pharo 3.0. > > > > One "problem" we found is that CollectionsExtensions is depending on a > Nile Package (that's not a desired feature). > > In the method Collection>>flatCollect: there is a line refering to a > nile function "nsWriteStream". > > How this #flatCollect: is different from #gather: anyway? > > > > > If i change "nsWriteStream" for "writeStream" the dependency disapears. > > > > I also run all the tests and they are working, so i was wondering if it > would be possible to commit the change. > > > > Thanks. > > >

2 1

ConfigurationOfMoose Error in Pharo 2.0
by Sean P. DeNigris 11 Jun '13

11 Jun '13

In answering a question on the Pharo users list [1], I tried to load Moose based on the instructions at [2]: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDevelopment And got: SmallInteger(Object)>>doesNotUnderstand: #isEmpty MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: where the SmallInteger in question was 602151175 [1] http://forum.world.st/stable-not-defined-td4692873.html [2] http://www.moosetechnology.org/download/pharo ----- Cheers, Sean -- View this message in context: http://forum.world.st/ConfigurationOfMoose-Error-in-Pharo-2-0-tp4692881.html Sent from the Moose mailing list archive at Nabble.com.

1 0

Roassal, SVG export, padding
by mathieubmddehouck＠mailoo.org 11 Jun '13

11 Jun '13

Hi I'm sorry to come with my problems, but I'm writing my internship report and I need some picture so I went back to Roassal. - Why when exporting in SVG it does not export the whole canvas but only a small part ? I had problem with my Ubuntu so I upgrade to 13.04 and noticed some nice stuffs. - Athens does not work, there is a problem with font rendering with Cairo and Ubuntu 13.04. ( I have reproduced the problem with Damien and Erwan computer ) Igor had a look, but he didn't find the problem. Then I took a new image and load my code in it. - When the mouse go over a node I have a ROPermissiveParent >> padding: failure (assertion failed), it seems that the padding is nil, I thought it has been solved for a while. Regards Mathieu

2 3

Modification on CollectionsExtensions
by Sebastian Tleye 11 Jun '13

11 Jun '13

Hello, Fixing some bugs in Traits we realized that it would be good idea to use CollectionsExtensions package (it has some useful functions), also it would be great to include CollectionsExtensions in Pharo 3.0. One "problem" we found is that CollectionsExtensions is depending on a Nile Package (that's not a desired feature). In the method Collection>>flatCollect: there is a line refering to a nile function "nsWriteStream". If i change "nsWriteStream" for "writeStream" the dependency disapears. I also run all the tests and they are working, so i was wondering if it would be possible to commit the change. Thanks.

1 0

← Newer
1
...
9
10
11
12
13
14
15
16
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2013