Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

The Moldable Debugger - screencasts
by Andrei Chis 02 Jan '14

02 Jan '14

Hi, I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser. https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser There is also an older one for announcements (https://vimeo.com/83020584). The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger> Cheers, Andrei

3 2

moose: custom analyses made easy
by Tudor Girba 01 Jan '14

01 Jan '14

Hi, I would like to make more explicit what Moose is and how it is different than what you can find in the analysis tools space. I wrote a recent post that takes a quick tour around Moose: http://www.humane-assessment.com/blog/moose-custom-analyses-made-easy With this occasion, I am putting forward a new tagline to capture Moose's vision: "Custom analyses made easy" Being different is nice, but it is also a challenge given that we need to educate the audience that looks at Moose. That is why we need to present Moose more aggressively. And this is why having a more clear web presence is important at this point. As I said before, I hope to get a bit of help from you to reshape the current webpage. Perhaps you will notice that this message also matches the prerequisite for making humane assessment (http://humane-assessment.com): bringing the cost of analysis tools close to zero. That is because humane assessment actually promotes Moose, and I think we should use the synergies between the "process" world and the tool world. Now it's your turn. - First, please let me know what you think. Is it clear what I mean? Do you have a different opinion? - Second, I would kindly ask you to send stories of using Moose. Alex started to do this recently, and this is great. You can also see some examples on the humane assessment blog. It would be great to have these use cases described. Examples are the best teachers. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 0

Progress codebase analysis using Moose
by Alexandre Bergel 01 Jan '14

01 Jan '14

>From http://stackoverflow.com/questions/20828790/progress-codebase-analysis-usin… Has anyone used Moose to deal with a large legacy Progress ABL/4GL codebase, and if yes, what are the caveats, experiences, lessons learned you can share about this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

towards moose in the pharo ide (gtinspector / gtdebugger)
by Tudor Girba 31 Dec '13

31 Dec '13

Hi, Some of you asked how the GTInspector and GTDebugger are different from the existing infrastructure. They are quite different from the norm in that: they are tiny, and they are highly extensible. Here are some posts that describe what makes them different: http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… http://www.humane-assessment.com/blog/moldable-gtdebugger These tools are already the default development tools in the Moose image. As you can see, Moose is reshaping the Pharo IDE. I think this is exciting. This should be just the beginning. To make it better, we need your energy: - Apply and extend these tools for your context (this is what makes them unique). - Tell us what works and what does not work. - Ideally, start working with us on this topic. In particular, I am looking for people that would like to spend some time working on Morphic widgets. It's your turn now. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

2 2

working as a team
by Tudor Girba 28 Dec '13

28 Dec '13

Hi, I wish for the new year to find us working as a team in which ... we take the time to make explicit what works and what does not. ... we build common solutions. ... we strive towards a common vision. I think there is a great deal of potential in Moose, but we can only uncover it together. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 0

Scatterplot with Graph-ET
by Serge Stinckwich 28 Dec '13

28 Dec '13

Hi all, I try to use scatterplot with Graph-ET and nothing happens. Apparently generateIn method for GETScatterPlot is empty. Script I use: ==================================== |diag| diag := GETDiagramBuilder new. (diag scatterplot) x: [ :x | x ]; y: [ :y | y ]; models: (1 to:100). diag open. ==================================== Cheers, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1

[fun] Editing graphic vectorial content
by Alexandre Bergel 28 Dec '13

28 Dec '13

Just to share a 10 min coding session, just before lunch. Result here: https://www.facebook.com/photo.php?fbid=564129843673617&set=a.3411893793009… code: -=-=-=-=-=-=-=-= | view stack selected statusBar | stack := ROViewStack new. view := ROView new. selected := nil. statusBar := nil. view on: ROMouseClick do: [ :evt | selected == #line ifTrue: [ | ex1 ex2 line | ex1 := (ROBox new size: 10; color: (Color purple alpha: 0.2)) element. ex2 := (ROBox new size: 10; color: (Color purple alpha: 0.2)) element. ex1 translateTo: evt position. ex2 translateTo: evt position + (100 @ 60). ex1 @ ROLightlyHighlightable. ex2 @ ROLightlyHighlightable. ex1 @ RODraggable. ex2 @ RODraggable. line := (ROLine new width: 3; color: (Color blue alpha: 0.2)) elementFrom: ex1 to: ex2. view addAll: { ex1 . ex2 . line }. ]. selected == #circle ifTrue: [ | ellipse | ellipse := (ROEllipse new size: 40; color: (Color yellow alpha: 0.2)) element. ellipse translateTo: evt position. ellipse @ RODraggable. view add: ellipse. ]. selected == #rectangle ifTrue: [ | box | box := (ROBox new width: 40; height: 30; color: (Color blue alpha: 0.2)) element. box translateTo: evt position. box @ RODraggable. view add: box. ]. view signalUpdate. ]. view @ RODraggable. stack zoomInButton; zoomOutButton. stack addMenu: '+ line' callBack: [ :evt | selected := #line. statusBar model: 'line' ]. stack addMenu: '+ rectangle' callBack: [ :evt | selected := #rectangle. statusBar model: 'rectangle' ]. stack addMenu: '+ circle' callBack: [ :evt | selected := #circle. statusBar model: 'circle' ]. stack addMenu: 'Info' callBack: [ :evt | UIManager default inform: 'Vectorial editing is hyper cool' ]. stack addView: view. stack title: 'Vectorial edition'. "Status bar at the bottom of the window" statusBar := (ROElement new) + ROLabel + ROBox white. stack add: statusBar. ROConstraint stickAtTheBottomOfTheWindow: statusBar. stack open -=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

debugger in Moose: new important bug
by Alexandre Bergel 28 Dec '13

28 Dec '13

Hi! I am trying hard to use the debugger, and this is not easy. If I select code in the debugger, doing a right-click and selecting 'debug it’ is crucial. Opening a debugger from another debugger is a strong pilar of Smalltalk. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

system nesting map
by Tudor Girba 27 Dec '13

27 Dec '13

Hi, I created a little visualization using the TreeMapBuilder called the System Nesting Map: it shows the nesting of classes in namespaces. It's not much technically, but it can come in handy from time to time. You can see a description here: http://www.humane-assessment.com/blog/system-nesting-map/ And Merry Christmas! Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

2 1

Configuration for Roassal 3D
by Stephan Eggermont 25 Dec '13

25 Dec '13

Is there a configuration that works in Moose 5? Stephan

4 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev