Moose-dev March 2015

moose-dev@list.inf.unibe.ch

42 participants
102 discussions

by Sean P. DeNigris

How do I get the example browser working (i.e. drawing the visualizations instead of inspecting them) in Pharo 4.0? I loaded Roassal2 stable per https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/QuickStart/… . Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Roassal-Example-Browser-in-Pharo-tp4813039.html Sent from the Moose mailing list archive at Nabble.com.

9 years, 9 months

GTInspector and string search

by phil＠highoctane.be

I've loaded GTPlayground and GTInspector in my 3.0 image. Works nice. Now, I needed to search a string in a string show in the String tab. There seemed to be no way to do that. Is there a shortcut key? I have a large piece of text and I missed that feature. Got away by copy/pasting to an old workspace and searching from there. TIA for the pointer. Phil

9 years, 9 months

Moose-Algos. Why Moose?

by Christophe Demarey

Hi, Packages in MooseAlgos are quite independent of Moose. I wonder if it would be good to have them as an independent project. In fact, they are not far from being independent (some dependencies to break) but the name of the project does not reflect that. Maybe it is something that prevents other developers to use these algorithms. I personally think MooseAlgos will benefit from a name without Moose. 'Algos' is not a good name and it is difficult to find a good one because there are algorithms for graphs (mostly), clustering, and matrix. There is also a package with code under the BSD license. Need to split? Name ideas? Here are the dependencies (only static analysis, I do not know if there are some runtime dependencies not detected) : Moose-Algos-Graph has a dependency on Moose-Core because Moose-Algos-Graph defines an extension method cyclesToAll: for MooseGroup. It is very strange. #cyclesToAll: is only called by FAMIXNamespaceGroup>>#cyclesToAllProviderNamespaces in the Famix-Extensions package. This methods has no senders. Either MooseGroup>>#cyclesToAll and FAMIXNamespaceGroup>>#cyclesToAllProviderNamespaces should be removed or moved MooseGroup>>#cyclesToAll should be moved to #FAMIXNamespaceGroup. WDYT? Moose-Algos-Clusturing depends on Moose-Core because MalClusterEngine>>performClusteringShowProgress: references MooseCustomTask. I don't know how to break this dependency. Best regards, Christophe.

9 years, 9 months

moose at the breathing code conference

by Tudor Girba

Hi, My talk on Moose was accepted at the Breathing Code conference to be held on May 5 in Frankfurt: http://breathing-code.de/program.html#data-analysis-moose It's an interesting setup that fits both Pharo and Moose like a glove. However, this being the first edition of the conference, the organizers are a bit in trouble as there are not enough registrations. They need to reach 35 participants until April 1, and they urge people to spread the word. Now, I kindly ask you to spread the word the best you can about this conference. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 9 months

Issue 1117 in moose-technology: Cleanup in Moose-Algos-Graph + add GraphReducer + add TopologicalSorting

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1117 by christop...(a)inria.fr: Cleanup in Moose-Algos-Graph + add GraphReducer + add TopologicalSorting https://code.google.com/p/moose-technology/issues/detail?id=1117 Cleanup in Moose-Algos-Graph -- 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

9 years, 9 months

loading Glamour in Pharo 4

by Peter Uhnák

After loading Glamour dev in Pharo 40 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamour'; load. (Smalltalk at: #ConfigurationOfGlamour) perform: #loadDevelopment ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ when I try opening Playground I get AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: And Spotter throws GLMHintableActionButtonBrick(Object)>>doesNotUnderstand: #addUpAction: Am I missing some extra dependency? Thanks, Peter

9 years, 9 months

[ANN] Quality Assistant: live code critics feedback

by Yuriy Tymchuk

Dear Moose developers, As you already know I am working on providing better code quality support in Pharo. You can use Code Critics in Pharo to detect bad practices and potential bugs. But launching the Critics Browser and running it on your code every now and then requires additional effort which demotivates many people in doing it. I want to present you a compact tool called Quality Assistant https://github.com/Uko/QualityAssistant#quality-assistant-𝑏𝑒𝑡𝑎- It runs SmallLint rules on the code that you save and provides you with a critic feedback directly in the place where you code: the Nautilus Browser. Quality Assistant is available for Pharo 4 from the Configuration browser. Please read about how to set it up here: https://github.com/Uko/QualityAssistant#set-up I plan to introduce more features in the future and your feedback is much appreciated. Cheers! Uko

9 years, 9 months

Roassal tip: Blinking elements

by Alexandre Bergel

Hi! Maybe some of you are not are not aware of the RTBlink class. RTBlink is an interaction to make element blink. You simply need to invoke "RTBlink on: aRoassalElement” Here are two examples: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. v @ RTDraggableView. shape := RTBox new width: [ :cls | cls numberOfVariables * 5 max: 5 ]; height: [ :cls | cls numberOfMethods sqrt * 2 ]. es := shape elementsOn: Collection withAllSubclasses. v addAll: es. RTFlowLayout on: es. RTMetricNormalizer new elements: es; normalizeColor: #numberOfLinesOfCode. es when: TRMouseClick do: [ :event | RTBlink new color: Color blue; on: event element ]. v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Simply click on an element to make it blink. A slightly more elaborated example: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Set here the classes you wish to visualize" classes := Collection withAllSubclasses. v := RTView new. v @ RTDraggableView. shape := RTBox new width: [ :cls | cls numberOfVariables * 5 max: 5 ]; height: [ :cls | cls numberOfMethods sqrt * 2 ]. es := shape elementsOn: classes. v addAll: es. RTFlowLayout on: es. RTMetricNormalizer new elements: es; normalizeColor: #numberOfLinesOfCode. "Set here the classes you wish to visualize" labels := (RTLabel new height: 8) elementsOn: classes. RTFlowLayout new gapSize: 0; on: labels. v addAll: labels. TRConstraint move: labels onTheRightOf: es. labels translateBy: 20 @ 0. labels @ RTHighlightable. labels when: TRMouseClick do: [ :event | RTBlink new color: Color blue; on: (es elementFromModel: event element model) ]. es @ RTHighlightable. es when: TRMouseClick do: [ :event | RTBlink new color: Color blue; on: (labels elementFromModel: event element model) ]. v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 9 months

merlin change

by Usman Bhatti

Name: Merlin-usmanbhatti.148 Author: usmanbhatti Time: 27 March 2015, 2:20:45.694933 pm UUID: b77314f3-7b8e-49b8-a0a6-3c6a1b7f5034 Ancestors: Merlin-TudorGirba.147 adding format block for radiobutton items.

9 years, 9 months

moose bug tracker

by Christophe Demarey

Hi, Is there a new bug tracker for Moose? As google code will close in 2016, but in read only mode from August, 24th 2015 I wanted to know if the migration is already done, forecasted? Christophe.

9 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2015