Status: New
Owner: ----
Labels: Type-Defect Priority-Critical
New issue 1102 by anne.et...(a)gmail.com: Error in GlamourRenderer
configuration Moose 5.0
https://code.google.com/p/moose-technology/issues/detail?id=1102
Load a brand new Moose 5.0 image.
Execute some code from a playground.
There is an issue since the WorkspaceVariable class does not exist in Pharo
3.0 but only in Pharo 4.0.
I think that the issue comes from the fact that the
ConfigurationOfGlamourRenderer load version 304 and not 303. We should do a
ConfigurationOf for Pharo 3.0 and an other one for Pharo 4.0
Moose 5.0 should not evolve anymore.
Anne
--
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
Hi!
RTGraphBuilder went through major improvements.
- min and max may be specified.
- plugins to add some decoration (average line, standard deviation range, ticks lines, …)
Here are some examples, with some examples, which should illustrate these points:
Is obtained with:
-=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-=
| b ds |
b := RTGrapherBuilder new.
ds := RTDataSet new.
ds points: (0 to: 100 by: 0.1).
ds y: [ :x | (0.1 * x) sin ].
ds noDot.
ds interaction popupText: 'sinus'.
ds connectColor: Color blue.
b add: ds.
ds := RTDataSet new.
ds points: (0 to: 100 by: 0.1).
ds y: [ :x | (0.2 * x) cos * 2 ].
ds noDot.
ds interaction popupText: 'cosinus'.
ds connectColor: Color red.
b add: ds.
b minY: -4.
b maxY: 4.
b minX: -25.
b build.
-=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-=
-=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-=
b := RTGrapherBuilder new.
ds := RTStackedDataSet new.
ds interaction popup.
ds points: #(600 470 170 430 300).
ds barShape width: 20; color: Color lightGreen.
b add: ds.
b axisX noLabel; noTick.
b axisY noDecimals.
b addPlugin: RTMeanDevVarPlugin new.
b build
-=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-=
Another example:
-=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-=
b := RTGrapherBuilder new.
b extent: 300 @ 200.
5 timesRepeat: [
ds := RTStackedDataSet new.
ds noDot.
ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum.
ds connectColor: Color green.
b add: ds.
].
b addPlugin: RTMeanDevVarPlugin new.
b build.
-=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-=
The plugin framework exposes to a plugin all the necessary to define a whole range of decorations. For example, variable average lines, linear regression should be trivial to add...
Happy new year!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
Reading the list, I remember some mail about a message to update the
whole browser, but I can't find it again. Which message I have to send
for that?
Cheers,
Offray
Hello,
I'm student from France. I would like to participate in an open source
project in Pharo.
Moose project looks interesting. I'm noob in Pharo.
How can I start to help you ?
Thank you,
Best regards,
Jonathan Wadin.
Hi,
In order to do two new pages on the website, with respectively the users and the contributors of Moose, we need to update the data we previously got.
You are using Moose or contribute to its development, so can you please fill in the sheets available here (https://docs.google.com/spreadsheets/d/1tadFC96gi8hXuc4WZ4fEikredbz_1nKff5_… There are two sheets pages, one for users, one for contributors. We don’t need individual names, but entity (academic or industrial one). To give an example I filled in the sheet with the RMod team.
The Moose Days have shown us that we don’t all use Moose for the same reasons (and that is really great) so I put a column to briefly described what you are using and what you are contributing. It can help us to find new ways to use Moose ;o)
Thank you in advance for your help. It is really important that you put information, even if it is finished. It is to help us to build new projects, get money and show to the world that Moose is largely used and not only an academic prototype.
Cheers,
Anne
Hi Jan,
The PPPrediateTest>>testStartOfWord is failing after your last commit.
Could you check it, please?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi guys,
I don't know if anybody still counts, but I would like to announce another
Masters thesis that was written while contributing to Moose:
Dennis Schenk's work on Quicksilver (
http://scg.unibe.ch/archive/masters/Sche14a.pdf)
Have a nice evening,
M.
--
Mircea Lungu, PhD.
Researcher
Software Composition Group
University of Bern
Hi!
Just to share a small script. Nothing new in it, but I find it cool.
Each dot is a method. The X-axis is the time, and the Y-axis is the number of lines of code defined in a method.
We can see some picks, illustrating moments in the life of Roassal for which many methods of different sizes have been added.
http://ws.stfx.eu/86C7MEVIPT1S
-=-=-=-=-=-=-=-=-=-=-=-=
methods := RTObject withAllSubclasses flatCollect: #methods.
methods := methods reject: [ :m | m numberOfLinesOfCode > 150 ].
oldestMethod := methods minFor: #date.
b := RTGrapher new.
ds := RTDataSet new.
ds dotShape circle size: 5; color: (Color blue alpha: 0.1).
ds interaction popup.
ds points: methods.
ds y: #numberOfLinesOfCode.
ds x: [ :m | m date julianDayNumber - oldestMethod date julianDayNumber ].
b add: ds.
b axisY title: 'LOC'; noDecimal.
b axisX
title: '';
labelRotation: -30;
numberOfTicks: 10;
numberOfLabels: 10;
labelConvertion: [ :v | (Date julianDayNumber: v + oldestMethod date julianDayNumber) ].
b build
-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
Juraj and I did a small UI using Glamour on Pharo 3. Unfortunately, it behaves differently on Pharo 4.
Here is an excerpt of the script:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
browser := GLMTabulator new.
browser
column: #one;
column: [ :c |
c
row: #rowOne span: 0.2;
row: #rowTwo ].
browser transmit
to: #one;
andShow: [ :a |
a list
shouldValidate: true;
updateOn: GLMItemRemoved from: #yourself;
updateOn: GLMItemAdded from: #yourself;
updateOn: WSRefresh from: self announcer;
display: [ :anObject | Array withAll: self actions ];
format: [ :anAction | anAction name ];
act: [ :b | actions add: WSAction new ]
icon: GLMUIThemeExtraIcons glamorousAdd
on: $+
entitled: 'Add a new action';
act: [ :actionToBeRemoved :b |
actions remove: actionToBeRemoved selection.
self refreshList ]
icon: GLMUIThemeExtraIcons glamorousRemove
on: $-
entitled: 'Remove the selected action';
act: [ :b | self doAllActions ]
icon: GLMUIThemeExtraIcons glamorousGo
on: $g
entitled: 'Executes all actions' ].
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Pharo 3:
On Pharo 4:
The code can be downloaded from the configuration browser. Just look for WorkingSet
Any idea what’s going on?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
I am moving Live Robot Programming to Pharo 4, and I found an issue when loading PetitParser. Some fonts are changed (I guess) and this breaks rendering of text.
To reproduce: in the current build open a playgound and do:
Gofer it
smalltalkhubUser: ‘Moose' project: ‘PetitParser';
configuration;
loadDevelopment
when everything is loaded, the playground text area changes to the red crossed error morph. (DNU: GLMBrickRenderer class>>render:on:) Opening a new playground and new browser goes OK. But when I open the Spotter and start typing all results are the red error morph (DNU: AthensCairoCanvas>>#line:to:width:color:)
Can this be looked at, or can you tell me how I can at least fix the spotter while this is looked at?
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
Excellent!!!
I’ve just fixed the failing tests of Roassal. Actually, these failures were due to the improvement of RTGrapherBuilder, not because of Pharo 4.0. For some reason, when I run the tests before committing, the tests were all green. I think this is due to some weird behavior with class renaming...
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I wanted to have a look at why some tests are failing in the last version of moose.
But I cannot even open a debugger.
Maybe some classes are missing. I see SystemDictionary>>at: in the call stack.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
In the previous version of the website, there was a list of academic partners and its equivalent for the industrial ones. I can’t find on the new version of the website where is the information and the old links lead to 404 pages.
Is the information available somewhere?
Thanks in advance for your help.
Anne
Hi,
Happy New Year!
The GTInspector reaches its full potential when it is being extended to
meet custom needs.
I will try to document more scenarios to show how this works in practice
and how programming changes as a result.
Here is a story that describes a session of debugging a Metacello
configuration problem:
http://www.humane-assessment.com/blog/identifying-a-configuration-problem-w…
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi!
There is an example GLMBasicExamples>>dropDownList where a user can select a value from drop down list. If I change some lines like this:
-=-=-
browser := GLMTabulator new.
browser row: #one size: 30; row: #two.
browser transmit to: #one; andShow: [:a |
a dropDownList
display: [ :myModelObject | myModelObject valuesForDropDownList ] ].
-=-=-
How can I update selected value in myModelObject when a user select something?
Thanks!
Juraj
Hi!
I have improved the Mondrian builder.
Here is the example thumbnails in the version of today :-)
Just open the Roassal example browser :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I am wondering whether a context can be attached to a GTInspector.
For example, I would like to keep some properties about the roassal camera and the position of all the elements to have smooth animation when updating.
Maybe the class GTInspector or GLMCompositePresentation may be a variable attributes with a dictionary in it?
Does this make sense?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I added a new Source anchor, similar to FileAnchor but with the absolute
position instead of the line+column
called it IndexedFileAnchor
Common parts with old FileAnchor (not renamed to minimize the impact)
have been put in a superclass of both:
AbstractFileAnchor
famix tests are green
nicolas
Just wondering now that Moose 5 is out :-)
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
On my quest to inject all the features of the GraphBuilder into Mondrian, I have just improved Mondrian with the (i) the #notUseInLayout option when building edges and (ii) the bezier line that follow a path.
It sounds like very technical, but this effort is to make the Mondrian and the edge/layout builders more expressive.
Here is a small example:
-=-=-=-=-=-=-=-=-=-=-=-=
classes := RTShape withAllSubclasses, TRShape withAllSubclasses.
b := RTMondrian new.
b shape circle.
b nodes: classes.
b edges connectFrom: #superclass.
b shape bezierLineFollowing: #superclass;
color: (Color blue alpha: 0.2).
b edges notUseInLayout; connectToAll: #dependentClasses.
b normalizer
normalizeSize: #numberOfMethods using: #sqrt;
normalizeColor: #numberOfMethods using: (Array with: Color green with: Color red) using: #sqrt.
b layout cluster.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=
Another example:
-=-=-=-=-=-=-=-=-=-=-=-=
classes := RTObject withAllSubclasses, RTTest withAllSubclasses.
b := RTMondrian new.
b shape circle.
b nodes: classes.
b edges connectFrom: #superclass.
b shape bezierLineFollowing: #superclass;
color: (Color blue alpha: 0.2).
b edges
notUseInLayout;
connectToAll: #dependentClasses.
b normalizer
normalizeSize: #numberOfMethods using: #sqrt;
normalizeColor: #numberOfMethods using: (Array with: Color green with: Color red) using: #sqrt.
b layout cluster.
b build.
^ b
-=-=-=-=-=-=-=-=-=-=-=-=
Doru, on some point we discussed whether it was a good idea to have a clause
#if: [ :fromObject :toObject | … return a boolean … ]
You argued that it was not a good idea and I agree with you. However, I cannot see how to avoid it.
For example, how can I have only edges going from the tests to the base code, and not between classes of the base code?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.