Currently GSBerlin is the only build that fails from Jenkins.
The problem is in ConfigurationOfVidi>>baseline031: which tries to load the
Roassal2 group from ConfigurationOfGlamour.
Removing the line 'loads: #('Roassal2');' should fix the build.
I have pushed a new version for indentation sensitivity into the
PetitParser. If I am not mistaken, with the new changes, you can parse
languages such as Python, F#, Haskell, YAML or Markdown. There are proof of
concept implementations in the PetitParser repository. YAML and Markdwon
are almost complete, for Python only the indentation-sensitive rules.
There is a small introduction to the indentation parsing with PetitParser (
http://scg.unibe.ch/research/indentParsing), let me know, if you are
missing something or if you want to know something more. There are also
many examples of the indentation sensitive grammars in the repository.
If you wonder about performance, the indentation sensitive grammar is
approximately five times slower, because the position and an extra
indentation stack is remembered instead of the simple position. If you
don't use indentation, there is no slowdown. I am working on improvements,
any ideas are welcome :)
If you don't like new changes, you can still stable version
(ConfigurationOfPetitParser loadStable) or version 1.11.
Following the advice of Peter Uhnák on tag clouds and avatars I made
some progress on my intended visualization. If you run the code at 
you will get something similar to  (the difference is that screenshot
is for code inside a grafoscopio document instead of a simple playground).
I will prioritize working on scrapping and cleaning the data, leaving
the position of the avatar to the end (hopefully Alexandre will read
this and in his attempt to make Roassal the best visualization engine in
the universe and its users happier, he will implement my suggestion at
So in my attempt to clean the data I'm trying to process originalText
(look at ) to split it to single words. For that I start copying that
text and replacing any occurrence of punctuation characters and
parenthesis by spaces and then applying #splitOn: ' ' to the new string.
I made this by the chunk of code at , but seems inelegant and trying
to use cascades and ending in #yourself didn't make the trick.
cookedText1 := originalText.
cookedText1 := cookedText1 copyReplaceAll: ',' with: ' '.
cookedText1 := cookedText1 copyReplaceAll: ';' with: ' '.
cookedText1 := cookedText1 copyReplaceAll: '.' with: ' '.
cookedText1 := cookedText1 copyReplaceAll: ':' with: ' '.
cookedText1 := cookedText1 copyReplaceAll: ')' with: ' '.
cookedText1 := cookedText1 copyReplaceAll: '(' with: ' '.
So here come my questions:
a) There is any form to replace code at  by a more elegant
Smalltalk-ish way so I can have only words no matter if they are
separated by spaces, punctuation marks of starting/ending with parenthesis?
b) Why some uninteresting words like the Spanish 'La' or 'Se' are still
getting their way in the final visualization even if I try to evade them
with the code at 
(cookedText1 splitOn: ' ') do: [:word |
((word size > 1) & (uninterestingWords includes: word asLowercase) not)
ifTrue: [cookedText2 := cookedText2, word, ' ']].
And my suggestion:
Please consider making tag clouds with variable layouts and forms.
Python has something similar with 
I will be waiting for your suggestions and thanks for keeping
Many of you have an interest in software visualization. Which is why this call for papers may be relevant for you.
==== Call for Papers ====
3rd IEEE Working Conference on Software Visualization
September 27 - September 28, 2015, Bremen, Germany
Software visualization is a broad research area encompassing concepts, methods, tools, and techniques that assist in a range of software engineering and software development activities. Covered aspects include the development and evaluation of approaches for visually analyzing software and software systems, including their structure, execution behavior, and evolution.
The VISSOFT IEEE Working Conference on Software Visualization continues the history of the ACM SOFTVIS Symposium on Software Visualization and the IEEE VISSOFT International Workshop on Visualizing Software for Understanding and Analysis. The conference focuses on visualization techniques that target aspects of software maintenance and evolution, program comprehension, reverse engineering, and reengineering, i.e., how visualization helps professionals to understand, analyze, test and evolve software. We aim to gather tool developers, experts, users, and researchers from software engineering, information visualization, computer graphics, and human-computer interaction to discuss theoretical foundations, algorithms, techniques, tools, and applications related to software visualization. We seek technical papers, empirical studies, applications, or case studies and provide a platform for presenting novel research ideas and tools.
Topics of interest include, but are not limited to:
* Innovative visualization and visual analytics techniques for software engineering data, such as,
- source code
- static and dynamic dependencies
- software evolution and repositories
- software documentation
- web services
- protocol, log, and performance data
- parallel techniques
- database schemes
- software security and privacy issues
- workflow and business processes
* Visualization to support program comprehension, software testing, and debugging
* Interaction techniques and algorithms for software visualization
* Visualization-based techniques in computer science and software engineering education
* Integration of software visualization tools and development environments
* Empirical evaluation of software visualization
* Industrial experience on using software visualization
Papers are solicited that present original, unpublished research results and will be rigorously reviewed by an international program committee. In addition to technical papers, VISSOFT features a New Ideas or Emerging Results (NIER) track and a Tool track related to the same list of topics suggested above. All accepted submissions will appear in the conference proceedings and the IEEE Digital Library.
-== Technical papers ==-
These contributions describe in-depth mature research results in the above-mentioned areas of interest. The submission of a video (up to 5 minutes in length) to accompany the paper is highly encouraged to show interaction possibilities. Authors who wish to submit such video should provide a URL to the video. Technical papers have to be maximum 10 pages long (including bibliography and annexes).
Abstract submission date: April 27, 2015
Full paper submission date: May 4, 2015
Author response period: June 8 - 12, 2015
Notification: June 18, 2015
Traditionally, technical research papers are published without including any artifacts (such as tools, data, models, videos, etc.), even though the artifacts may serve as crucial and detailed evidence for the quality of the results that the associated paper offers. Following the effort initiated at ESEC/FSE’11, authors of accepted technical papers at VISSOFT 2015 can have their artifacts evaluated by the program committee. Positively evaluated artifacts will be reflected in the paper publication and presentation. More information about the artifacts may be found on http://www.artifact-eval.org .
Artifact submission for accepted papers: June 24, 2015
Artifact notification: July 31, 2015
VISSOFT 2015 will award distinguished technical papers. Monetary awards will be sponsored by ObjectProfile.com
A selection of the best technical papers will be invited to submit an extended version for a special section of Information and Software Technology (IST) published by Elsevier.
-== NIER papers ==-
The NIER contributions (New Ideas and Emerging Results) describe work-in-progress and preliminary exciting results. Authors should include open questions and even provocative hypotheses to get early feedback on their research ideas or even support through new research collaborations. NIER papers have to be maximum 5 pages long (including bibliography and annexes).
Paper submission date: June 15, 2015
Notification: July 31, 2015
-== Tool papers ==-
Tool contributions describe the design or actual utilization of software visualization tools, with a focus on relevant tool construction aspects or the use of the tool for gaining new insights. Authors should be prepared to demonstrate their tool at the conference. The submission may also contain a link to a screencast (video). Tools papers have to be maximum 5 pages long (including bibliography and annexes).
Paper submission date: June 15, 2015
Notification: July 31, 2015
-== How to Submit ==-
Submissions must be submitted online via the VISSOFT 2015 EasyChair conference management system at https://easychair.org/conferences/?conf=vissoft2015
Please adhere to the formatting instruction published on the ICSME website: http://www.icsme.uni-bremen.de/formatting.php
-== Organizing Committee ==-
Jürgen Doellner, Hasso-Plattner-Institut, Germany -- http://www.hpi.uni-potsdam.de/doellner/
Fabian Beck, University of Stuttgart, Germany -- http://research.fbeck.com
Alexandre Bergel, University of Chile, Chile -- http://bergel.eu
Craig Anslow, University of Calgary, Canada -- http://anslow.cpsc.ucalgary.ca/
Johan Fabry, University of Chile, Chile -- http://pleiad.cl/people/jfabry
Juraj Kubelka, University of Chile, Chile -- http://www.juraj-kubelka.cz/
Craig Anslow, University of Calgary
Stephan Diehl, University Trier
Johan Fabry, PLEIAD lab - Department of Computer Science (DCC) - University of Chile
Tudor Girba, University of Bern
Carsten Goerg, University of Colorado School of Medicine
Michele Lanza, Faculty of Informatics, University of Lugano, Switzerland
Claus Lewerentz, Brandenburgische Technische Universität Cottbus
Jonathan Maletic, Kent State University
Chris Muelder, U. C. Davis
Emerson Murphy-Hill, North Carolina State University
James Noble, Victoria University of Wellington
Wim De Pauw, Google Inc.
Steven Reiss, Brown University
Sébastien Rufiange, EISTI
Houari Sahraoui, DIRO, Université De Montréal
Bonita Sharif, Youngstown State University
Margaret-Anne Storey, University of Victoria
Alexandru Telea, University of Groningen
Andy Zaidman, TU Delft
Please visit http://vissoft.info for updates.
Fabian Beck and Alexandre Bergel
Alexandre Bergel http://www.bergel.eu
I realized that currently, it is not possible to inspect elements in the
GLMRosassal2 presentation when they are created, as it works only on
elements created at the initialization in:
I think the new elements added to the RTView should be inspectable in the
A possible solution would be to GLMRoassal2Presentation to observe the
RTView and when notified of creation of a new element, add the interaction
to the new element ?
v := RTView new.
v add: ((RTBox new size: 40) elementOn: x).
v elements when: TRMouseRightClick do: [ | b |
b := ((RTBox new size: 40) elementOn: x).
v add: b.
b translateBy: (x := x + 50)@0.
v signalUpdate ].