Moose-dev September 2014

moose-dev@list.inf.unibe.ch

42 participants
134 discussions

Issue 1085 in moose-technology: tool tip in the Playground

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 1085 by alexandr...(a)gmail.com: tool tip in the Playground http://code.google.com/p/moose-technology/issues/detail?id=1085 Describe the problem: what do you get? what do you expect? If I put the mouse above the play icon, top right of a window. The keybinding (cmd-o) may be indicated no? -- 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, 6 months

Issue 1044 in moose-technology: Can't debug block local variables in GT debugger

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1044 by v.blonde...(a)gmail.com: Can't debug block local variables in GT debugger http://code.google.com/p/moose-technology/issues/detail?id=1044 Describe the problem: what do you get? what do you expect? In the GT Debugger, when you debug a block with a local variable; you can't read its value because the variable is unknown... How to reproduce the problem: step by step if necessary Write in a Workspace : 1 = 1 ifTrue: [ |local | local := 1 ] Debug It! Use the through button to go into the block. Try to inspect the local variable. Additional information: platform, context which may impact the problem Moose 5.0 latest - Ubuntu 13.10 - x64 Please fill in the labels with the following information: * Type-Defect * Component-GT-Debugguer * Milestone-5.0 -- 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, 6 months

Date on the X-axis with Charter

by Alexandre Bergel

Hi! Here is a post that describe how to have dates on the X-axis. This has been a recurrent problem, which is why I would like to share it with you. Dates are particular values that requires an adequate control over what is being displayed on X-axis. The julianDayNumber converts a date into a number. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= methods := RTObject withAllSubclasses flatCollect: #methods. methods := methods reject: [ :m | m numberOfLinesOfCode > 150 ]. oldestMethod := methods minFor: #date. b := RTCharterBuilder new. b extent: 800 @ 200. b shape circle size: 5; color: (Color blue alpha: 0.1). b interaction popup. b points: methods. b allY: #numberOfLinesOfCode. b allX: [ :m | m date julianDayNumber - oldestMethod date julianDayNumber ]. b axisConfiguration noDecimals; title: 'LOC'. b axisY. b axisConfiguration title: ''; labelRotation: -30; numberOfTicks: 10; numberOfLabels: 10; labelConvertion: [ :v | (Date julianDayNumber: v + oldestMethod date julianDayNumber) ]. b axisX. b build -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 6 months

roassal 1->2: please test your changes

by Tudor Girba

Hi, I am going through the changes made to Moose-RoassalPaintings and some of the are just broken. For example: viewBlueprintOn: was not migrated, but viewBlueprintComplexity was changed to use Roassal2. This makes it crash. Please test these changes by trying to generate actual visualizations. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 6 months

Issue 1034 in moose-technology: Glamour easel and GTDebugger

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Critical New issue 1034 by alexandr...(a)gmail.com: Glamour easel and GTDebugger http://code.google.com/p/moose-technology/issues/detail?id=1034 Hi! I have spotted an important bug. If I enter the following in the Glamour Roassal easel: view nodes: (1 to: 20). self halt. A debugger is open, but I cannot step in. Apparently the code source is not accessible. This is a major regression... -- 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, 6 months

help wanted for class blueprint

by Tudor Girba

Hi, I would need help for reimplementing the Class Blueprint. The challenge here is to get the ability to set the height of the boxes to be based on the maximum height of any of the sybling boxes. Who can help? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 6 months

[ANN] Test Coverage with Hapao

by Alexandre Bergel

Dear all, We are happy to release Hapao2 for Pharo. Ricard Jacas and Alejandro Infante put quite some work on Spy2 (an über cool profiling framework for Pharo) and Hapao2. Hapao2 is about assessing the test coverage of your code and is a major revamp of Hapao1, which was presented a couple of years ago by Vanessa. Hapao2 does not only list covered and uncovered methods, as most test coverage tool on Earth will do. Hapao gives a great visualization to easily navigate in your code, assess its complexity, and give you a great visual output telling its coverage. You need Roassal in your image: Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. (Smalltalk at: #ConfigurationOfRoassal2) load and you need S2py: MCHttpRepository location: 'http://smalltalkhub.com/mc/ObjectProfile/S2py/main' user: '' password: '' New entries will appear in the world menu: You can run the test coverage on : - the class classes you have modified, - on a particular - on a particular class category - on the last class categories you have modified - on the last packages you have modified Here is a portion of a large coverage: A technical description of Hapao may be found on http://bergel.eu/download/papers/Berg12c-HapaoSCP.pdf We are daily using Hapao to help us understand our tests. Cheers, Ricardo, Alejandro & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 6 months

GTInspector

by Alexandre Bergel

Hi! Soon, we will face the problem of having too many tabs. E.g., Any idea how to fix this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 6 months

roassal2 support for menus

by Tudor Girba

Hi, We need a simple way to add the Moose menu to any Roassal element or edge. We either - add RTInteractionBuilder>>menu: or, - add Object>>roassalMenuFor: aBuilder What do you think? Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 6 months

integrating gt in pharo and releasing moose 5.0

by Tudor Girba

Hi, As you might has seen, GT (inspector+playground for now) is now integrated in Pharo 4. This means that the target we set one year ago of building a Moose-based IDE is becoming a reality. I think this is a great milestone. With these tools the "market" for Roassal visualizations or other analyses opens up widely and the philosophy of Moose becomes more pervasive. This is just the beginning of the story. The only problem is that in order to fix issues that might occur in Pharo 4 we might impact Moose as it still relies on Pharo 3. In order to fix this, we have to release Moose 5.0. That is why I am asking here for help. The greatest problems are the Roassal visualizations. It would be ideal to release in 2 weeks. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 6 months

← Newer
1
2
3
4
5
6
7
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2014