Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

SciSmalltalk
by Serge Stinckwich 28 Mar '12

28 Mar '12

Dear all, we already discuss about that in the moose and pharo mailing-list. Maybe this is too late, but please find a small proposal for gsoc 2012 below. ================================================================ Name: SciSmalltalk Level: Intermediate Possible mentor: Serge Stinckwich Possible second mentor: ? Description Smalltalk has at that time no equivalent to mathematical libraries like NumPy, SciPy (Python) or SciRuby (Ruby). The goal of the SciSmalltalk project is to develop an open-source library of mathematical for the Smalltalk programming language (MIT Licence). Technical Details The development of this project is to be done in Pharo Smalltalk, but the code should be portable to other Smalltalk flavors. Numerous Smalltalk projects provide already some basic functionalities (complex and quaternions extensions, random number generator, fuzzy algorithms, LAPACK linear algebra package, Didier Besset's numerical methods, ...). A first task will be to do an audit of all the existing projects that provide some mathematical stuff and build a Pharo Configuration to load them in a fresh Pharo Smalltalk image. After that, the student help by his/her mentors will decide what are the numeric algorithms to develop in priority. The student will need to know some basic numeric algorithms usually found in such libraries. Units tests should also be provided. Benefits to the Student The student will help the Smalltalk community in a very concrete way. The student will learn to design well-designed code with tests. Benefits to the Community Having a package providing more elaborate numeric libraries is really important to develop the use Smalltalk in new domains (robotics, high performance computing, computer vision, bio-computing, ...). The lack of numeric librairies hamper the use of the Smalltalk in a scientific context at the moment. An another goal of this project is to develop a community of people interested by these topic. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

3 4

InFamix do not import correctly FAMIXLocalVariable parentBehaviouralEntity
by Fabrizio Perin 28 Mar '12

28 Mar '12

Hi, I imported a Model generated with InFamix and i tried to navigate the model with the MooseFinder. Once I click on class the debugger opens with a MNU: receiver of "classScope" is nil. In fact FAMIXLacalVariable>>belongsTo returns nil. Anybody have the same problem? Cheers, Fabrizio

2 3

how to embed a MooseFinder in another browser?
by Fabrizio Perin 28 Mar '12

28 Mar '12

Hi, I was wondering how to open a MooseFinder on an element selected in another browser. I tried something like this: browser := GLMTabulator new. browser column: #functions; column:#finder. browser transmit to: #functions; andShow: [ :a | a list title: 'Functions'; display: [:each | each ]]. browser transmit to: #finder; from: #functions; andShow: [ :a | a finder title: [:each | each mooseName]; ..... ^ browser but I don't know how to proceed (this is why I added the dots). Any suggestion? Am I doing it the wrong way? Cheers, Fabrizio

3 4

Mondrian saving and reloading a layout
by Ben Coman 28 Mar '12

28 Mar '12

In Mondrian I can drag nodes around the layout to make a more pleasing graph. Is there a mechanism built in to facilitate saving and later reloading the layout of a graph ? Or where should I look into to system to implement this? -cheers, Ben

3 7

Re: Jenkins build is still unstable: moose-latest-dev #906
by Alexandre Bergel 27 Mar '12

27 Mar '12

I fixed the two Mondrian failing tests. All these problems stems from the recent changes in the collection hierarchy. Somehow, the order of elements are not preserved. Here is an example: Consider the script: view nodes: (1 to: 4). view edgesFromAssociations: {1 -> 2 . 1 -> 3 . 3 -> 4}. view treeLayout It displays this: or this: Before the recent collection changes, it was always the same layout, one of the two. So the tests need to be updated... The build should be green again Cheers, Alexandre On 27 Mar 2012, at 02:17, admin(a)moosetechnology.org wrote: > See <http://hudson.moosetechnology.org/job/moose-latest-dev/906/> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Stable Moose Configuration
by Dennis Schenk 27 Mar '12

27 Mar '12

Hi, Im currently using the dev version of Moose. For some parts it is still very unstable. For example when using the Mondrian Easel examples, it always crashes after a short while. Also autocomplete does not seem to work at the moment. I looked at ConfigurationOfMoose to see if I could use the stable version for some of the development, but there the stable version currently points to version 4.3.4 as far as I can tell. Would it be possible to create a configuration for the latest stable version of Moose, i guess that would be 4.6.x? Cheers, dennis

4 16

Updating a browser with Glamour
by Santiago Vidal 27 Mar '12

27 Mar '12

Hi, I implement a browser with glamour. To provide data to the browser I use the Hismo models that are installed in the Moose Panel: browser openOn: MooseModel root allModelHistories How can I refresh the data shown by the browser when a new Hismo model is added to the Moose Panel? Thanks. Cheers, -- Santiago Vidal

2 2

8 failing tests remaining
by Tudor Girba 26 Mar '12

26 Mar '12

Hi, After fixing Collection>>union: in Pharo, the Moose tests are better. We now have only 8 failing tests. Any help to fix these would be appreciated :) Cheers, Doru -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

3 8

Issue 783 in moose-technology: hidden 'Name already defined' tempvar & ivar clash
by moose-technology＠googlecode.com 26 Mar '12

26 Mar '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 783 by google....(a)ben.coman.com.au: hidden 'Name already defined' tempvar & ivar clash http://code.google.com/p/moose-technology/issues/detail?id=783 Moose 4.6 has some hidden clashes between instance variables and method temporary variables. In order to observe the operation of #forNode:do: in Mondrian, I went to add only 'self halt' to MOViewRendererTest>>testEdgesAndInteractiveExpansion. When I tried to <Accept> this, it complained temporary variable 'view' was 'Name already defined' and indeed MOViewRendererTest does have a clashing instance variable 'view' which prevents me from saving my change. Similar has happened to me previously a few times, so I thought I would flag it in case anyone was curious to determine how this got past the compiler into the system, and also might be able to do some automated sweep of the code to detect any similar occurances. cheers, Ben

1 1

Mondrian - display of text within ellipse
by Ben Coman 26 Mar '12

26 Mar '12

In Moose 4.6, World > Moose > Mondrian Easel > Examples > basic > edges + tiled nodes has this code... | nodes | view shape rectangle width: 40; text: #yourself. nodes := view nodes: (1 to: 20). view shape arrowedLine. view edges: (2 to: 20) from: 1 to: #yourself. view layout: (MOCircleLayout forNodes: nodes allButFirst) which displays text inside each rectangular node. If I change the second line to... view shape ellipse then nodes do appear as ellipses but the text disappears. That is not what I expected. How can text be made to display within an ellipse? cheers, Ben

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev