Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

application of Moose to other non-Smalltalk GSoC projects

by Ben Coman

I noticed that BRL-CAD has some GSoC ideas around code refactoring. I wonder if someone might get sponsored to apply Moose to their requirements. http://brlcad.org/wiki/Google_Summer_of_Code/Project_Ideas http://brlcad.org/d/about cheers -ben

12 years, 2 months

[EyeSee] Customize size & labels of charts

by roberto.minelli＠usi.ch

Hi, I'm doing a line chart with EyeSee and I didn't manage to find a way to do the following things: 1. change the overall size of the chart 2. have string labels on the y axis, i.e., I create the chart using 1, 2, 3 as y-values but I'd like to have a way to map those 1,2,3 to three strings. Is it possible? 3. related to (1), is it possible to change the yScale? I have only three different values on the yAxis but I'd like the chart to be displayed better (i.e., now it is really squeezed). I browsed the souce code of EyeSee and the examples but it seems that these three "features" are not clearly accessible. Thanks in advance, R

12 years, 2 months

Name cloud and Overview pyramid migrated into Roassal

by Juraj Kubelka

Hi! Name cloud and Overview pyramid has been migrated into Roassal. There are two new tests which explains fixes of ROLabel (ROAbstractLabel>>testSize2 and #testSize3). Cheers, Jura

12 years, 2 months

roassal-based blueprint review

by Tudor Girba

Hi, I looked over the Roassal blueprint implementation. We start to have a working solution. Good work. However, there is still some work left :) What is nice: - Edges are properly drawn below the nodes - The implementation layer shows a tree layout - The morph menus work - The layers do not capture the interaction What is not so nice: - Morph menus are shown even on left click. They should only appear on right click. I fixed this. - The size of the root node grows too large and we get a little gap at the bottom (see the first attached picture). This has likely something to do with the latest fix from Alex related to padding. - When dragging a method or attribute node outside of the bounds of the parent, the parent continues to grow (see the second picture). This is not good :). The problem is that the logic depends on setting the parent to have extensible size. Instead, in the case of the blueprint, it should be the responsibility of the layout to grow the parent as needed without actually making the parent to be extensible. This is why in Mondrian the layout could be set to stretch. - Right now, the edges start and end in the center of the nodes. The convention in the blueprint is to have edges drawn starting from the right side and end on the left side of nodes. In any case, I already added it to the MooseFinder (the blueprint tab). Cheers, Doru -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

12 years, 2 months

Some Roasal questions

by Yuriy Tymchuk

Started to promote Roasal on Stack Overflow :) Check there please: http://stackoverflow.com/questions/16318358/change-edge-name-that-appears-i… http://stackoverflow.com/questions/16318649/avoid-duplication-of-edges-in-r… -- View this message in context: http://moose-dev.97923.n3.nabble.com/Some-Roasal-questions-tp4027181.html Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 2 months

Videos: Selling Pharo-based solutions & Custom architectural assessment

by Stephan Eggermont

Selling Pharo-based Solutions https://www.youtube.com/watch?v=v65L07qR-w4 Custom architectural assessment of a large enterprise system https://www.youtube.com/watch?v=Zzkd2D_WiVY Stephan

12 years, 2 months

Metaceller

by Diego Lont

Hi all, Recently I have been working on some configurations, and I felt the need to have something better (more specific for configurations) to edit my configurations than the standard OB / Nautilus. On the PharoConf Doru told me about GTMetataceller, but this tool needed some work. So I did some work on it, and now I am looking for feedback how you like it. It is built in glamour, and you get it, when you download the latest Moose. Just type GTMetaceller open somewhere in the browser and you are ready to rock. If you know how Metacello works, the editor should be more or less self explaining. In case you run into trouble, there is a help button that explains the tool a bit. I also did a screencast: http://youtu.be/LaJF_dfGsD8. If you want to load this in your image, just do: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; package: 'ConfigurationOfGToolkit'; load. (Smalltalk at: #ConfigurationOfGToolkit) project development load. (Smalltalk at: #GTMetaceller) open. Note: I only tested this in Pharo 2.0, this loading does not work in Pharo 1.4. It should work in Pharo 1.4, since loading the GT-Metaceller package in Moose 4.7 works fine. I think I should create a stable version as well … that loads in Pharo 1.4 as well. Cheers, Diego

12 years, 2 months

roassal + athens

by Tudor Girba

Hi, I would like to start adopting Athens behind Roassal. I believe there already is a binding. The question is what keeps us from adding Athens as a dependency to RoassalMorphic? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years, 2 months

Jenkins build became unstable: moose-latest-dev-4.8 #379

by admin＠moosetechnology.org

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

12 years, 2 months

Jenkins build is back to normal : moose-latest-dev-4.8 #374

by admin＠moosetechnology.org

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

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