Hi Lukas,
I saw that you worked on the Petit refactorings. This is cool, but you seem to have committed a wrong superclass:
AnObsoleteRefactoring subclass: #PPGrammarRefactoring
Do you have time to fix it?
Cheers,
Doru
Begin forwarded message:
> From: admin(a)moosetechnology.org
> Subject: Build failed in Jenkins: moose-latest-dev #735
> Date: 7 December 2011 22:13:31 CET
> To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)gmail.com
>
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/735/>
>
> ------------------------------------------
> Started by timer
> [workspace] $ /bin/sh -xe /tmp/hudson2362877769901627270.sh
> + rm -rf <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose> <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose-tests> <http://hudson.moosetechnology.org/job/moose-latest-dev/735/artifact/moose_s…>
> + /srv/hudson.moosetechnology.org/builder/build.sh -i Pharo-1.3 -s moose -s glamorous-theme -s glamorous-toolkit -s moose-clean -s cleanupforrelease -o moose
> build.sh: error loading code (/srv/pharo/coglinux2382/squeak)
>
> *** Warning: Warning: This package depends on the following classes:
> AnObsoleteRefactoring
> You must resolve these dependencies before you will be able to load these definitions:
> PPDefineProdcutionRefactoring
> PPDefineProdcutionRefactoring>>checkSource
> PPDefineProdcutionRefactoring>>preconditions
> PPDefineProdcutionRefactoring>>setSource:
> PPDefineProdcutionRefactoring>>sourceRewriter
> PPDefineProdcutionRefactoring>>transform
> PPGrammarRefactoring
> PPGrammarRefactoring>>preconditions
> PPGrammarRefactoring>>rootClass
> PPGrammarRefactoring>>setClass:
> PPRemoveProdcutionRefactoring
> PPRemoveProdcutionRefactoring>>preconditions
> PPRemoveProdcutionRefactoring>>setProduction:
> PPRemoveProdcutionRefactoring>>transform
> PPRenameProdcutionRefactoring
> PPRenameProdcutionRefactoring>>setNewProduction:
> PPRenameProdcutionRefactoring>>setOldProduction:
> PPRenameProdcutionRefactoring>>transform
>
> Recording test results
> Archiving artifacts
>
--
www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
Hi all,
I just download the last Moose build from the server and i notice a weird cursor behavior:
If i copy/paste something either in a workspace or into a code browser i find the cursor at the beginning of the pasted code intend of at the end.
Is it a Moose related problem? Is it a new pharo feature? Or my image is possessed by the devil? Thanks for any help.
Cheers,
Fabrizio
what would be the pragma to describe a date property in the meta-model?
birthDate
<MSEProperty: #birthDate type: #???>
Number? (representing the date as a timestamp?)
nicolas
I am looking for a method which allows wrapping mondrian drawings. That is,
the nodes are draw to a certain width (the width of the mondrian window)
and whatever comes next, is drawn on the following line. The purpose is to
avoid the need to scroll the window.
thanx
Usman
Hi,
Over the past couple of weeks, Fabrizio did a cool job at detaching his work around SQL into PetitSQLite (for parsing) and Famix-SQLite (for importing and modeling).
I already used the parsing in a project and it worked nicely on quite complex SQL statements.
We will add this to the default Moose configuration. It's a really nice addition.
Cheers,
Doru
p.s. For those that want to have fun with optimizing the grammar, it is still a bit slow so it's a cool case study :)
--
www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Status: New
Owner: usman.bh...(a)gmail.com
Labels: Type-Defect Priority-Medium
New issue 760 by usman.bh...(a)gmail.com:
UndefinedObject(Object)>>doesNotUnderstand: #attributeKeyFrom:
http://code.google.com/p/moose-technology/issues/detail?id=760
Menssana dashboard reference values cannot be set because message not
understood error occurs. The message appears before setting the value.
Sometimes, the dialogue for setting the values does appear, but it crashes
when a value is entered.
how to produce:
Right click on an item in Menssana dashboard, click set reference value.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 756 by vuqui...(a)gmail.com: Glamour: errors when updating panels
http://code.google.com/p/moose-technology/issues/detail?id=756
* Type-Defect
* Component-Mondrian
After modifying the data on one panel I update several other panels, that
are not necessarily connected together. The data is correctly updated, but
not the presentations.
Based on the example below:
#when: in the second list does not react.
* If you start with an empty collection, the list does not appear (ok),
then if you add an element the list does not appear either.
* if you start with some elements, the list is there, but after removing
all the elements the list does not disappear, and instead you have a
SubscriptOutOfBounds error because of a tab index
Example to reproduce the problem:
| browser collection |
collection := GLMAnnouncingCollection new.
collection add: 1.
browser := GLMTabulator new.
browser column: #automatic; column: #menu.
browser act: [:b | b entity add: (b entity size + 1) ] entitled: 'Add an
item in the collection'.
browser act: [:b | b entity removeLast ] entitled: 'Remove last item from
the collection'.
browser act: [:b | b update ] entitled: 'Update complete browser'.
browser transmit to: #automatic; andShow: [ :a |
a title: 'Updated automatically'.
a stackedArrangement.
a list title: [:x | 'List: ', x size printString ];
shouldValidate: true;
updateOn: GLMItemAdded from: #yourself;
updateOn: GLMItemRemoved from: #yourself ].
browser transmit to: #menu; andShow: [ :a |
a title: 'Updated via menu'.
a list title: 'List';
when:[ :e| e size > 0 ];
act: [:p | p update ] entitled: 'Update'.
a text title: 'Text'; act: [:p | p update] entitled: 'Update'. ].
browser openOn: collection
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 645 by cy.delau...(a)gmail.com: we should keep the current selected
tab in the moose panel
http://code.google.com/p/moose-technology/issues/detail?id=645
In the moose finder, If I click on an entity, I have a new pane that open
on the right.
In this new pane, if I select any tab, this one should stay selected when I
click on other entities
Hi
During Smalltalks conference, we started with Mariano and Doru to do an
experiment: to use Mondrian to visualize the graph that is being serialized
with Fuel.
I want to make two questions about that:
1) Is it fine how I installed Mondrian?
Gofer it
squeaksource: 'Mondrian';
package: 'ConfigurationOfMondrian';
load.
(ConfigurationOfMondrian project latestVersion) load.
2) For large graphs, I would like to show them lazily, maybe drawing some
expandable nodes (+). Do you understand what I mean? Is that possible?
thanks!
Martin