Hi,
I'll remove GLMRubricSmalltalkCodePresentation.
It has no users in the image and now there are GLMPharoMethodPresentation
and GLMPharoPlaygroundPresentation.
Cheers,
Andrei
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"
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"
Hi,
sorry if this is a known thing, but I’ve just notices this and it made my day.
So in GTInspector you can browse filesystem, but when you select a fuel file, you can press a "plus” button in top right corner, and it materialises the object. Amazing.
Uko
Since you are working on a new code browser. Please please please, it would be fantastic to see the definition of the setUp method when I create a new test method.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
Recently, there have been changes in PetitParser related to support for
island grammar and parsing context which requires some modifications in the
tools using PetitParser. Not all tools can be adapted immediately to use
the new version. Hence, I have created a new version of PetitParser that
loads the packages prior to these changes for backward compatibility.
Name: ConfigurationOfPetitParser-usmanbhatti.49
Author: usmanbhatti
Time: 28 September 2014, 8:58:00.540857 pm
UUID: 54877ca2-77b0-4c5e-937d-5124dd76b075
Ancestors: ConfigurationOfPetitParser-JanKurs.48
adding a baseline and a version that loads packages before changes made to
petitparser related to parsing context and island grammar.
regards,
usman
Hi,
It seems that Alex's demo at VISSOFT has done very well :). Take a look at
the tweets (feel free to retweet). Good job, Alex!
Live analysis is hot, and right now, we are on top of it. Let's keep it up.
[image: Inline image 1]
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi all,
we did some work on Dude.
One thing that was bothering us was that it cleaned the source code
(remove comments, '{', ...), but left empty lines behind that interfered
with the detection.
To correct that:
- DudeSourceCodeLine now keeps the lineno of its line in the original
source code
- empty lines do not generate any DudeSourceCodeLine
- DudeSourceCodeFragment keeps beginLine and endline in terms of real
line numbers in the source code
- DudeSourceCodeFragment also has to keep the length of the clone
fragment as the number of non empty lines (previously it would be
computed from beginLine and endline)
- and we had to refactor the code in various places to deal with these
changes
Overall, a rather big commit, but the tests (new and old) are green
nicolas
Name: SmallDude-Core-NicolasAnquetil.46
Author: NicolasAnquetil
Time: 30 September 2014, 1:42:10.634399 pm
UUID: f5004983-82f1-4649-8e8e-efe22776cb35
Ancestors: SmallDude-Core-TudorGirba.45
changed Dude so that empty lines are discarded when computing clones
