Hi Julien,
You should have a look at the Moose platform: http://moosetechnology.org <http://moosetechnology.org/>
Moose is made exactly to analyze software, and has more then 15 years of engineering. Roassal is a component of Moose.
To analyze some Java, you need a tool to translate your .java files into a big .mse file. MSE is a meta-model that is accepted by Moose. As far as I know, two tools are available for this: VerveineJ and inFamoos(? I cannot remember the exact name).
VerveineJ is unfortunately not free. Ask directly in the Moose mailing list for this.
However, I have a copy of it. I can generate the .MSE file if you give me access to the Java code.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Mar 26, 2015, at 9:39 AM, Julien Delplanque <julien(a)tamere.eu> wrote:
>
> Hi,
>
> I saw this repository on smalltalkhub:
> http://smalltalkhub.com/#!/~blabux/JavaLoader/ and I wonder if someone
> could give me some examples of use.
>
> For example, is it possible to use JavaLoader with Roassal to display
> class hierarchy of a java project or something like that?
>
> I browsed google and the mailing list's archives but didn't found any
> doc/examples... Maybe I'm not searching in the right place? :)
>
> Thanks in advance,
>
> Julien
>
Hi!
Seeing your other (Grapher charting engine) post I wanted to look at it and
it looks interesting. :)
However I've encountered weird behavior - maybe because I'm not using in
correctly.
When you look at the bar chars they do not line up with the tick numbers at
bottom.
I have explicitly specified number of ticks (20). Interestingly if I change
it (to 30) then it lines up but is moved to left by one (starts at zero
instead of one - just by changing numberOfTicks).
Here is the script I used to create it (the data is generated from another
script)
================================
data := {1->0.3024011554432208. 2->24.359090088463624.
3->17.660001805380034. 4->12.111843293013179. 5->7.624345549738219.
6->5.985963170247337. 7->4.740250947824517. 8->3.837560931576097.
9->3.0691460552446292. 10->2.819777938256003. 11->2.3334536920021667.
12->1.9915598483480772. 13->1.6970572305470302. 14->1.3089005235602094.
15->1.1847806463260515. 16->1.0640458566528253. 17->0.8891496660046939.
18->0.7244087380393573. 19->0.670247337064452. 20->0.5878768730817837}.
y := [ :pair | (data select: [ :each | each key <= pair key ]) inject: 0
into: [:sum :item | sum + item value ]].
b := RTGrapher new.
b extent: 500 @ 400.
ds := RTStackedDataSet new.
ds points: data.
ds x: #key.
ds y: y.
ds barShape.
b add: ds.
ds2 := RTStackedDataSet new.
ds2 points: data.
ds2 x: #key.
ds2 y: y.
ds2 connectColor: Color green.
ds2 highlightIf: [ :pair | true ] using: [ :pair | (y value: pair) roundTo:
1 ].
b add: ds2.
b axisX
noDecimal;
numberOfTicks: 20; "<- change to 30 to break it"
title: 'method size (LOC)'.
b axisY
noDecimal;
title: '% share'.
b build.
lb := RTLegendBuilder new.
lb view: b view.
lb addColor: Color green text: 'Method size distribution'.
lb build.
b view open.
================================
It's also amazing that 1/4 of all Pharo code is in two-line methods; that's
including the method name. :)
Peter
Hi!
The GT crew recently introduces in Pharo a way to keep track of what people are searching in the system.
This is a highly valuable piece of information that could benefit everybody.
For example, I would love to know which Roassal classes are looking the most often. Or which Roassal examples people are repeatedly searching.
However, this is hard to know currently. The reason is because of anonymity. No strings are stored in what is being sent over. To me, this is _highly counter-productive_: if you are working with sensitive information (I don’t personally), then do not send things over. But enforcing anonymity generate frustration.
So, here is my call:
If you care about letting us improving the tools everybody use, feel free to reveal your identity. Simply send the result of the following expression:
GTSpotterEventRecorderSettings uniqueInstance secretUUID hash
For me
=> 195966943
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
Is there any documentation about algorithms available in Moose-Algos-Graph?
It looks interesting but there is no class comment ...
Thanks,
Christophe.
Hi everyone,
I’m playing with glamour, and I’m trying to construct a list that can be edited e.g. you can add items, edit them and remove and for adding and editing you have a custom popup written again in glamour. So first question is how can I dead with basic actions? Is the GLMActionListPresentation way to go, or I should look on the other things. Another question is how do you open a modal window with glamour and how do you get the result from it.
I’ll be very thankful for any reply.
Cheers.
Uko
The inspector is so cool because one can get feedback for each step. I was
working with a text list, and going in very small steps because I wasn't
quite sure what I wanted to do, so I:
1. Pasted into playground:
'lineOne
...
lastLine'
cmd-g
2. self lines sort
cmd-g
3. self asSet asOrderedCollection sort
Then I thought (although the above is a bad example for this), since GT
encourages to take these small steps, it would be cool to have a command to
assemble the code from all the workspaces into one statement, so 1, 2, and 3
above would become: "aString lines sort asSet asOrderedCollection sort".
Again, not a great example, but I know this would've been useful other
times...
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/GT-Inspector-Assemble-Statement-tp4814849.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
On March 31, we will have a one day of Pharo in Bern:
10:15 - 11:00 Talk by Alain Plantec on Bloc: Reinventing Morphic
Registration:
https://www.eventbrite.com/e/bloc-reinventing-morphic-choose-talk-tickets-5…
11:00 - 17:00 Working session on the Pharo IDE
Registration:
https://www.eventbrite.com/e/pharo-ide-choose-working-session-tickets-16283…
The event will be held at the Software Composition Group:
Schützenmattstrasse 14, Room 107, Bern
The event is sponsored by CHOOSE a subgroup of the Swiss Informatics
Society and hosted by the Software Composition Group at the University of
Bern. They are primarily organized for CHOOSE and SI members, but the
events are open for other students and professionals as well.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi!
> If you're heading to make "Roassal the best visualizing engine of the Universe" then what are your intentions with connecting it to the outer world ?
This is a rather broad question :-)
While our visualizations are meant to run in a standard Smalltalk environment, they are exportable to HTML. Interaction are also preserved. Here are two simple examples:
https://dl.dropboxusercontent.com/u/31543901/TMP/memoryBlueprintExample.html <https://dl.dropboxusercontent.com/u/31543901/TMP/memoryBlueprintExample.html>
https://dl.dropboxusercontent.com/u/31543901/online/WebReport/seisms.html <https://dl.dropboxusercontent.com/u/31543901/online/WebReport/seisms.html>
And a larger and more complex example is in the file
https://dl.dropboxusercontent.com/u/31543901/TMP/ExampleReport.zip <https://dl.dropboxusercontent.com/u/31543901/TMP/ExampleReport.zip>
check the file Example.pillar.html
> Will it remain a multiplatform toolbox ? Or are you heading towards a BI desktop or Web app ?
Roassal will remain closely linked to Smalltalk (VisualWorks & Pharo).
Cheers,
Alexandre
>
> Regards,
>
> Maarten MOSTERT
>
>
>
> 28 Av Alphonse Denis
> 83400 Hyères, France
> +33 676411296
> http://stakepoint.com/ <http://stakepoint.com/>
>
>
>
> > "Alexandre Bergel" <alexandre.bergel(a)me.com> |
>
> Dear all,
>
> As many of you know, Grapher is a über-cool charting engine, part of Roassal.
> For people who do not know what Grapher is, here is a (compelling we hope) example:
> <855A292C-DE42-4FF5-83ED-49477CDAA250.png>
> Which is obtained by the following script:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> | b colors points ds pts dec lb |
> b := RTGrapher new.
> colors := Array with: Color red with: Color blue.
> points := OrderedCollection new.
>
> colors do: [ :c |
> ds := RTStackedDataSet new.
> pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum.
> points add: pts.
> ds points: pts.
> dec := RTDevVarDecorator new.
> dec moveBehind;
> desviation: 0.5;
> color: (c alpha: 0.3);
> points: pts.
> ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ).
> b add: ds.
> b addDecorator: dec.
> ].
>
> b axisX; axisY.
> b build.
>
> lb := RTLegendBuilder new.
> lb view: b view.
> colors doWithIndex: [ :c :i |
> lb addColor: c text: 'Series ', i printString ].
> lb build.
> b view @ RTZoomableView.
> b view
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
> In our grand vision of making Roassal the best visualizing engine of the Universe (we also know to be modest time to time, but not today :-), Grapher will play a very important role. We would like to stabilize Grapher and make it sure it happily fits everybody needs. You can help on it:
>
> - When you are tempted to look at the dark side of the planet (this is where R, JFreeChart, gnuplot, D3 and all their friends live), let us know. We will make sure to make you are happy again.
>
> - Share your wishlist with us. We already have a long todo list, but your opinion does matter and will take it seriously
>
> - we are open to contributions, which could be financial, bug fixe, enhancement, or simply encouragement.
>
> I am very happy to be surrounded by very smart engineers. Your encouragement are making them happy :-)
>
> Cheers,
> Alexandre, in the name of the Object Profile Team
> NB: sorry for the cross-list posting, but this email is very important for us, and for you we hope.
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
> <855A292C-DE42-4FF5-83ED-49477CDAA250.png>
Hi all,
I had not updated to the last version of PetitParser for some weeks, now I did and the following rule breaks because PPInputEnds disappeared. Can anybody tell me how to update my rule? If I replace it by PPEndOfInputParser I get a DNU, so I guess I need to do something else.
endOfComment
^ PPInputEnds new / lineTerminator
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile