Moose-dev December 2013

moose-dev@list.inf.unibe.ch

36 participants
148 discussions

Start a nNew thread

Jenkins build became unstable: moose-5.0 #333

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/333/>

11 years

Issue 1029 in moose-technology: Roassal Easel crashed

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1029 by rob...(a)pergl.org: Roassal Easel crashed http://code.google.com/p/moose-technology/issues/detail?id=1029 Ubuntu 13.10 MooseSuite 4.9 Go to Browse - In Roassal Easel - eg - Adding Name - hover with mouse around the tree * Type-Defect -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years

Issue 1031 in moose-technology: smalltalk import doesn't work (moose5)

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1031 by rainbowt...(a)gmail.com: smalltalk import doesn't work (moose5) http://code.google.com/p/moose-technology/issues/detail?id=1031 moose 5 from pharo launcher - open moose panel - press import famix model from image - select any package(s) >>> - press next, finish I get the debugger, closing it cancels import Please fill in the labels with the following information: * Type-Defect * Component-Moose -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years

Re: [Pharo-dev] [ANN] traversal-enabled objects with DeepTraverser

by Tudor Girba

Hi, I looked a bit at the existing hardcoded traversal methods in a Pharo/Moose image. To detect it, I used a traversal. Perhaps this can also be useful for people that want to teach what a traversal is, or what an analysis is, so I wrote a blog post about it: http://www.humane-assessment.com/blog/looking-for-hardcoded-traversal-metho… Cheers, Doru On Sat, Dec 14, 2013 at 3:44 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > > On Wed, Dec 11, 2013 at 12:21 PM, Tudor Girba <tudor(a)tudorgirba.com>wrote: > >> Hi, >> >> I put together a little implementation for traversals. It is inspired by >> an original implementation from Mariano. >> > > Wow... my memory is sooo bad I don't remember ;) > > > >> Using DeepTraverser, you can traverse arbitrary graphs by describing the >> traversal and by specifying the actions you want to perform on the nodes >> and relations. >> >> > Once (or even more times) we thought with Martin 2 things: > > 1) Reify the traversal in Fuel so that we could plug a different one. > 2) Use Fuel only for traversing and allowing user a hook to plug the what > to do with each node. > 3) Use the same traversal of 2) for deepCopying > 4) Use the same traversal of 2) to get an approximate memory consumption > of the transitive closure of an object > > But as always happened we run out of time. > > Anyway...I think this is a nice area to explore. There are many uses for a > nice traverser. > > Also, did you see we wrote a Rossal extension to print the fuel traversal? > > http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.9/Documentation/… > > > The code is available in the Moose image as part of the MooseAlgos >> subproject, but can also be loaded separately in a Pharo image via: >> >> Gofer new >> url: 'http://www.smalltalkhub.com/mc/Moose/DeepTraverser/main'; >> package: ‘ConfigurationOfDeepTraverser’; >> load. >> (Smalltalk globals at: #ConfigurationOfDeepTraverser) loadDevelopment. >> >> >> Just to give you an idea, here are some representative examples: >> >> Number >> deep: #subclasses >> do: [:each | Transcript show: each; cr]. >> >> Number deepCollect: #subclasses. >> >> Number >> deep: #subclasses >> collect: #name. >> >> Number >> deep: #subclasses >> do: [:each | Transcript show: each; cr] >> relationDo: [ :from :to | Transcript show: from; show: ' <-- '; show: >> to; cr ]. >> >> >> >> More details about the usages and a little description of the >> implementation can be found here: >> http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects/ >> >> >> Cheers, >> Doru >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- www.tudorgirba.com "Every thing has its own flow"

11 years

Jenkins build is back to stable : moose-5.0 #324

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/324/>

11 years

Failing test in Moose

by Alexandre Bergel

Hi! I had a look at the failing test in Moose. I have found the reason: -=-=-=-=-=-=-=-= FAMIXPackageGroup>>browsePackageBlueprints <menuItem: 'Browse Package Blueprints' category: 'Visualize'> PackageBlueprint openBlueprintBrowserOn: self -=-=-=-=-=-=-=-= The class PackageBlueprint is undefined. I remember that Doru moved it somewhere? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years

Issue 1030 in moose-technology: VerveineJ does not export local variables

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 1030 by anquetil...(a)gmail.com: VerveineJ does not export local variables http://code.google.com/p/moose-technology/issues/detail?id=1030 Some local variables are not exported in the mse file even when we don't specify the -summary option -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years

Fwd: [Pharo-dev] GTDebugger...

by Alexandre Bergel

wrong mailing list… Alexandre Begin forwarded message: > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: [Pharo-dev] GTDebugger... > Date: December 15, 2013 at 5:21:35 PM GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > Apparently it does not recognizes variables in a workspace. > This is really annoying... > > Try this: > var := 5. > self halt > > in the debugger, select var and print it > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years

[Spy] Deprecated #methodDict

by Roberto Minelli

Hi, I’ve seen that in Pharo 3.0 the #methodDict has been deprecated and Spy (and myself) are actually using it. I will find a solution for myself, but please fix this in Spy as well. Cheers, R

11 years

one day - moose challenge

by Tudor Girba

Hi, I would like to propose as a topic for the following Moose Dojos to focus on building tools. The challenge is to take an analysis problem and build a tool to support that problem. Let me give you some examples: - Problem: browse the Fame meta-descriptions - Solution: the Meta Browser - Problem: browse&search pragmas in Pharo - Solution: ? - Problem: ? - Solution: ? You got the idea. We could create demos for these tools and use them as showcases for how Moose enables such scenarios. Who is up for the challenge? Would you tackle this at the next Moose Dojo? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years

← Newer
1
...
6
7
8
9
10
11
12
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2013