Hi!
How can I set the bar color with eyesee?
The script:
-=-=--=-=--=-=--=-=--=-=-
| diag factory |
factory := ESDummyFactory new.
factory yValues: numberOfExecutionsTable values.
diag := ESDiagramRenderer new.
(diag verticalBarDiagram)
y: #yValue;
regularAxis;
width: 300;
height: 200;
setInvertedLinearFill;
setColoredFill;
defaultColor: Color lightBlue;
models: factory buildDummies. "or setInvertedLinearFill"
-=-=--=-=--=-=--=-=--=-=-
Gives me
How can I turn it into light blue?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
It now contains Version 1.3 with the last improvement.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I know this is Moose-dev, but it was the best I could find.
I am at a customer with an extremely large and messy Perl system - so I
was curious - what languages does Moose handle? Any chance of handling Perl?
Trying to check the Moose book about import formats but... are those
formats all invented by the Moose project?
regards, Göran
Hi!
I fixed the configuration.
It now contains a version 0.9.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
Today I experimented some strange behaviours with announcements that I
didn't have in some previous moose images.
I think that there was some changes related to announcements in pharo
recently, but I could not be sure it is related.
At one point in my code I have:
browser on: AnnouncementClass send: #actionSelector
browser announce: anAnnouncementClass.
....
....
I have the feeling that sometimes #actionSelector is executed asynchronously
from the rest the code below 'browser announce: ...' .
Not sure but there is maybe something with exception signals. If any signal
is emited in #actionSelector it will not execute the rest of the method.
I was at leat able to write a test that do not pass in latest dev
Gofer new
squeaksource: 'DelaunayTmpStuffs';
package: 'ExampleAnnouncementProblems';
load.
will not pass with:
http://ci.moosetechnology.org/job/moose-latest-dev/402/artifact/moose_suite…
will pass with:
http://ci.moosetechnology.org/job/moose-latest-dev/393/artifact/moose_suite…
Hi!
Is it okay to commit the following method?
-=-=-=-=-=-=-=-=-=
ESDiagramrenderer>>getRenderedForm
"Simulate the graphical morph rendering"
| form Name is already defined aCanvas c |
diagram gcWrapper: ESDiagramGraphicsContextWrapper new.
diagram setup.
aCanvas := ESCanvas onDiagram: diagram.
aCanvas updateBounds.
form := Form extent: aCanvas bounds extent depth: Display depth.
c := FormCanvas on: form.
aCanvas drawOn: c..
^ form
-=-=-=-=-=-=-=-=-=
Such a form can freely appear in Mondrian, as a popupView.
I am not sure whether this has been done already.
You can try:
-=-=-=-=-=-=-=-=-=
| diag factory |
factory := ESDummyFactory new.
factory yValues: #(25 50 19 24 35 23 28 26 24 23).
diag := ESDiagramRenderer new.
(diag verticalBarDiagram)
y: #yValue;
regularAxis;
width: 300;
height: 200;
setInvertedLinearFill;
setColoredFill;
models: factory buildDummies. "or setInvertedLinearFill"
diag getRenderedForm asMorph openInHand
-=-=-=-=-=-=-=-=-=
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi
I tried loading Glamour using the instructions at
<http://www.moosetechnology.org/tools/glamour>
Gofer new
squeaksource: 'Glamour';
package: 'ConfigurationOfGlamour';
load.
(Smalltalk at: #ConfigurationOfGlamour)
perform: #loadDefault
However, in the process of loading, I get this warning:
This package depends on the following classes:
SubscriptionRegistry
You must resolve these dependencies before you will be able to load these
definitions:
SubscriptionRegistry>>glmSubscriptions
Select Proceed to continue, or close this window to cancel the operation.
If I hit proceed, I then get another warning:
This package depends on the following classes:
SubscriptionRegistry
You must resolve these dependencies before you will be able to load these
definitions:
SubscriptionRegistry>>hasHandlerFor:
SubscriptionRegistry>>lookFor:
SubscriptionRegistry>>lookFor:ifNone:
SubscriptionRegistry>>unsubscribeForEvent:
Select Proceed to continue, or close this window to cancel the operation.
I selected Proceed and when I do:
GLMBasicExamples open
I get a MNU in
GLMAnnouncer>>resetAnnouncer
registry reset "since registry is not defined"
I compared the methods in GLMAnnouncer to the Moose-4.4 image
<http://www.moosetechnology.org/download/4.4> and found out that the
methods are
different from what ConfigurationOfGlamour loads – which might explain the
problem.
Is it still possible to load Glamour on its own? I only need it for creating
some simple browsers and I don't need everything else in Moose. I've already
built the browser in the Moose-4.4 image and just want to run in inside a
Pharo-1.2 image.
Thanks!
--
Nick
--
View this message in context: http://forum.world.st/Problem-loading-ConfigurationOfGlamour-in-Pharo-1-2-S…
Sent from the Moose mailing list archive at Nabble.com.
view shape rectangle size: 20.
view interaction action: #inspect.
view interaction
whenEnteringUpdateNode: [:node | view interaction forwarder.
view nodes: (Set allSubclasses).
view interaction forwarder.
view edgesFrom: #superclass.
view treeLayout ]
whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true.
view nodes: (1 to: 3)
when I try this example I do not see the tree representing subclasses.
Stef
Hi Tudor. I have no idea about Moose, but I was wondering if you need to
copy models (in addition to export them to disk).
So, do you need? and if true, how do you do it? #veryDeepCopy ?
Thanks
--
Mariano
http://marianopeck.wordpress.com
Status: Accepted
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 631 by damien.c...(a)gmail.com:
GLMListMorphicTest>>testOnlyOneMorphPerRowInList failing
http://code.google.com/p/moose-technology/issues/detail?id=631
The test GLMListMorphicTest>>testOnlyOneMorphPerRowInList is failing. It
looks like the node 43 is always the one which makes the last assertion
fail.
We should try to reproduce outside the Glamour environment.
Hi Cyrille,
Thanks for fixing the VerveineJ wizard.
It would indeed be cool to get the variables set in the settings.
One idea would be to have as default folder for VerveineJ as relative to the current moose.image. Like this we could just copy VerveineJ in the current folder (and package it in the Moose Suite one click) and everything would just work.
Cheers,
Doru
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Tu dois #candidates
Essaye:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
view shape rectangle.
view interaction menuMorphBlock: [ :element | element mooseMenuMorph ].
view nodes: model allClasses
forEach: [:class |
view shape rectangle
fillColor: Color orange;
height: 7;
width: 7.
view interaction menuMorphBlock: [ :element | element mooseMenuMorph ].
view interaction
whenEnteringUpdateNode: [:node |
view
edges: node outgoingInvocations
from: #sender
toAll: #candidates
using: (MOStraightLineShape color: Color blue)].
view nodes: class methods.
view gridLayout gapSize: 2.
].
view edges: model allInheritanceDefinitions
from: #superclass
to: #subclass
"using: MOLineShape new".
view treeLayout.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On 25 May 2011, at 10:19, Cyrille Delaunay wrote:
> Quelque chose comme ca a l'air de marcher, mais bizarement il n'y a pas beaucoup d'invocations
>
> view shape rectangle.
> view interaction menuMorphBlock: [ :element | element mooseMenuMorph ].
>
> view nodes: model allClasses
> forEach: [:class |
> view shape rectangle
> fillColor: Color orange;
> height: 10;
> width: 10.
> view interaction menuMorphBlock: [ :element | element mooseMenuMorph ].
> view interaction
> whenEnteringUpdateNode: [:node |
> view
> edges: node outgoingInvocations
> from: #sender
> to: #receiver
> using: (MOStraightLineShape color: Color blue)].
> view nodes: class methods.
> view gridLayout.
> ].
> view edges: model allInheritanceDefinitions
> from: #superclass
> to: #subclass
> "using: MOLineShape new".
>
> view treeLayout.
>
>
> Le 25 mai 2011 15:54, Alexandre Bergel <abergel(a)dcc.uchile.cl> a écrit :
> D'ici quelques heures je peux essayer de faire cette visu.
>
> Alexandre
>
>
>
> Le 25 mai 2011 à 09:39, Cyrille Delaunay <cy.delaunay(a)gmail.com> a écrit :
>
>> Je pense que je commence a voir ce que tu aimerais :)
>> Tu aimerais avoir la visu de base avec seulement l'heritage. Ensuite , a chaque que tu passe la souris sur une methode, tu aimerais que des edges aparaissent dynamiquement du noeud (la methode) vers les methodes invoques ?
>>
>> 2011/5/25 Stéphane Ducasse <stephane.ducasse(a)inria.fr>
>> cyrille
>>
>> comment je peux avoir l'heritage entre classes
>>
>> deuxieme question:
>> comment je peux faire que je vois les invocations seulement du noeud que je veux.
>>
>> Stef
>>
>> view shape rectangle.
>> view interaction menuMorphBlock: [ :element | element mooseMenuMorph ].
>> view nodes: classGroup allClasses
>> forEach: [:class |
>> view shape rectangle
>> fillColor: Color orange.
>> view interaction menuMorphBlock: [ :element | element mooseMenuMorph ].
>> view nodes: class methods.
>> view gridLayout.
>> ].
>> view edges: classGroup allInheritanceDefinitions
>> from: #superclass
>> to: #subclass
>> "using: MOLineShape new".
>> view edges: classGroup allInvocations
>> from: #sender
>> to: #receiver
>> using: (MOStraightLineShape color: Color blue).
>> view treeLayout.
>> view open.
>>
>>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Scenario one:
bookmark a model
(I did not know what is should do)
this creates a tab with a x cross
I clicked on it
argh I lost my model
but the model is still in the list
argh I click and I get a DNU.
Stef (next bug soon :).
Because we did it for
http://www.themoosebook.org/book/externals/import-export/root-folder
kind of ....
I suggested to cyrille to spend 1 hours and add some settings.
Which ones do you want to have.
Me
- Project main folder location
- VerveineJ code location
- Import statements to be used
I do not see why I have to type
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
Each time I import a model I do not want to have to dive into this fucking file system to find my way (with a soon) resizeable interface.
Stef
Hi guys
I did import FAMIX model from file sources with verveineJ and I would like to see the code
of the java method when I use a browser. Now I do not see the code.
Should I do something special.
Stef
Hi,
For your information.
If you want to use a fast Java case study, you can use the running example from the Moose Book (most examples in the book are based on it):
http://www.themoosebook.org/book/externals/running-example
The page includes both the MSE model and the related sources.
Cheers,
Doru
--
www.tudorgirba.com
"Value is always contextual."
Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel
development through the ESUG SummerTalk. I am Martin Dias, a student at
Buenos Aires, Argentina. The idea behind this SummerTalk is to implement
Fuel, a binary, fast and general-purpose object graph serializer in
Pharo<http://www.pharo-project.org/>.
It is based on VisualWorks' Parcels ideas.
Actually, the project has already started since several months. Tristan
Bourgois and I started with the project while doing an internship with RMoD,
INRIA <http://rmod.lille.inria.fr/web/pier>. Since a couple of months, Mariano
Martinez Peck <http://marianopeck.wordpress.com/> joined the team, and now
he is the official mentor in the SummerTalk.
ESUG website for SummertTalk:
http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011
The website with all the necessary information is here:
http://rmod.lille.inria.fr/web/pier/software/Fuel
It even includes slides explaining the algorithm. In addition, a paper is in
progress.
For the moment, Fuel already provides the following features:
- Fast pickle format. It is much faster to materialize than to serialize.
- Correctly support class reshape (when the class of serialized objects has
changed).
- Serialize ANY kind of object. For the moment there is no object to our
knowledge that we cannot serialize and materialize.
- Be able to completely serialize classes and traits (not just a global
name).
- Support cycles and avoid duplicates in the graph.
- Integration to Moose <http://www.moosetechnology.org/> with an extension
to export and import their models.
- Detection of globals: for example if you serialize Transcript, it is not
duplicated and instead managed as a global reference.
- Solve common problems like Set rehash.
- Buffered writing: we use a buffered write stream for the serialization
part (thanks Sven!).
- No need of special support from the VM.
- Try to have a good object oriented design.
- Well tested (about 120 tests, for the moment).
- Large set of benchmarks (even benchmarks for Moose extension).
And of course, there are a lot features for the future. You can see some of
them in the website and some in the issue tracker:
http://code.google.com/p/fuel/issues/list
We really appreciate all kind of feedback and comments. If you want to try
it, check in the website how to do it. It is extremely easy.
Once again, I want to thank a lot to ESUG for sponsoring the project. I plan
to create a "news" section in the website with some RSS. I will keep you
informed.
Best regards,
Martin
Hello,
i tried parsing a simple project with VerveineJ with only one class as
follows:
import java.util.ArrayList;
import java.util.List;
public class Bla {
public static void main(String[] arg){
List list = new ArrayList();
Arrays.asList("abc");
}
}
When i load the mse in Moose, i only have the following model classes:
Object, Bla, String, CharSequence, Serializable, Arrays
However the List related classes (List, ArrayList, Collection,...) seem to
be missing. It's weird, because the class Arrays is in the same jar/package
as List (java.util) but doesn't get parsed. Could this be a problem with
Generics?
Cheers,
Matt
At the end of a wizard, would you replace the 'terminate' button by
something like 'Ok', or any idea you have ?
Stephane got problem with 'terminate' :)