Roassal2: new RTMenuBuilder
by Pierre CHANSON
Hi everyone,
I changed the RTMenuBuilder in Roassal2, especially it's behavior, default
colors and added more features as the definition of the highlight color.
I also changed a bit the architecture but could still be a lot improved.
We can also add a lot of different features to really specify the look of
the menu using the builder so let me know if you have any ideas, comments.
You can have a look with the example 06:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| v b |
v := RTView new.
b := RTMenuBuilder new view: v.
b menu: 'add' submenu: '10' callback: [
| es |
es := (RTLabel new color: [ :tt| Color random ]) elementsOn: (1 to:
10).
es do: [ :e | e translateTo: ((500 atRandom @ 500 atRandom) - (250
@ 250)) ].
v addAll: es.
v canvas signalUpdate ].
b menu: 'add' submenu: '20' callback: [
| es |
es := (RTLabel new color: [ :tt| Color random ]) elementsOn: (1 to:
20).
es do: [ :e | e translateTo: ((500 atRandom @ 500 atRandom) - (250
@ 250)) ].
v addAll: es.
v canvas signalUpdate ].
b menu: 'remove' submenu: 'odd' background: (Color blue alpha:0.3)
callback: [ (v elements select: [ :e | e model odd ]) do: #remove. v canvas
signalUpdate ].
b menu: 'remove' submenu: 'even' background: Color red callback: [ (v
elements select: [ :e | e model even ]) do: #remove. v canvas signalUpdate
].
b menu: 'shuffle' highlight: Color lightBlue callback: [
| tra |
tra := RTSmoothLayoutTranslator new.
tra nbCycles: 0.5.
(v elements do: [ :e | tra translate: e to: ((500 atRandom @ 500
atRandom) - (250 @ 250)) ]) ].
v open
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
sincerely yours,
Pierre Chanson
8 years, 3 months
Re: petitjava tests failing
by Jan Kurš
Mea Culpa, I fixed one error, introduced another one :(
I hot-fixed the other one as well. But the implementation of PPJavaParser
is broken. It cannot hanlde foo().bar() properly, causing the DNU while
calling #object: on PJ<xy>Node.
Cheers,
Jan
>
> ---------- Forwarded message ----------
> From: Tudor Girba <tudor(a)tudorgirba.com>
> Date: Wed, Dec 17, 2014 at 4:54 PM
> Subject: petitjava tests failing
> To: moose-dev <moose-dev(a)iam.unibe.ch>
>
> Hi,
>
> The PetitJava tests are failing:
> https://ci.inria.fr/moose/job/moose-5.0/3594/testReport/
>
> @Jan: I saw you committed the last. Could you check?
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
8 years, 3 months
[ANN] CubeHelix and slider
by Alexandre Bergel
Hi!
Yesterday with Damien P., we had a great discussion about modeling color palettes. Damien showed me an implementation he did about cubehelix. This is a fantastic way to model colors, while preserving the intensity. More info about it on: https://www.mrao.cam.ac.uk/~dag/CUBEHELIX/
Here is a code example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| v helix shape elements slider |
v := RTView new.
helix := RTCubeHelix new.
helix rotations: 2.
helix gamma: 2.
shape := (RTBox new height: 300; width: 1; color: [ :model | helix level: model ]).
elements := shape elementsOn: (0.0 to: 1.0 by: 0.002).
v addAll: elements.
RTHorizontalLineLayout new gapSize: 0; on: elements.
"Set the gamma value"
slider := RTSlider new.
slider view: v.
slider labelled.
slider callback: [ :aValue | helix gamma: 5 * aValue. elements updateShape ].
slider moveBelow.
slider build.
"Set the rotation value"
slider := RTSlider new.
slider view: v.
slider labelled.
slider callback: [ :aValue | helix rotations: 5 * aValue. elements updateShape ].
slider moveBelow.
slider build.
v
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
And the accompanying screenshot
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
8 years, 3 months
focus and key stroke in GTInspector?
by Alexandre Bergel
Hi!
Consider the following script:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
v := RTView new.
label := RTLabel elementOn: 'TypeSomething'.
v add: label.
v when: TRKeyDown do: [ :evt |
label trachelShape text: label trachelShape text, evt keyValue asCharacter asString.
v signalUpdate.
].
v
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
If I open the view, then typing write text in the roassal view. In GTInpector, this does not work, because the left pane keeps the key focus. I have the impression the left pane should release the keyboard focus when the mouse on the right pane. No?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
8 years, 3 months
CFP VISSOFT 2015: 3rd IEEE Working Conference on Software Visualization
by Alexandre Bergel
==== Preliminary Call for Papers ====
VISSOFT 2015:
3rd IEEE Working Conference on Software Visualization
September 27 - September 28, 2015, Bremen, Germany
http://vissoft.info
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
Artifacts:
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
Awards:
VISSOFT 2015 will award distinguished technical papers. Monetary awards will be sponsored by ObjectProfile.com
Special issue:
We plan to invite a selection of the technical papers accepted at VISSOFT 2015 to submit an extended version to a journal.
-== 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
General Chair:
Jürgen Döllner, Hasso-Plattner-Institut, Germany -- http://www.hpi.uni-potsdam.de/doellner/
Program Co-Chairs:
Fabian Beck, University of Stuttgart, Germany -- http://research.fbeck.com
Alexandre Bergel, University of Chile, Chile -- http://bergel.eu
Please visit http://vissoft.info for updates.
Best regards,
Fabian Beck and Alexandre Bergel
Program Co-Chairs
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
8 years, 3 months
Re: petitjava tests failing
by Stephan Eggermont
And there might be a similar (but earlier) problem with Coral (Since August 18).
I assume that has to do with
Name: PetitParser-JanKurs.234
Author: JanKurs
Time: 19 August 2014, 1:42:13.758355 pm
UUID: 2ce06ac7-8b97-40c0-aae0-4b06778e6cfc
Ancestors: PetitParser-DiegoLont.233
Merging the cool context extensions. Still work in progress. Some external parsers might get impacted in the meantime (together with Doru)
https://ci.inria.fr/pharo-contribution/job/Coral/
Stephan
8 years, 3 months
[ANN] RTStackBarPlot
by Alexandre Bergel
Hi!
Today Andrei and I pair-programmed on a stack bar plot builder.
Here is an example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
b := RTStackBarPlot new.
b interaction popupText.
b colorPalette colors: { Color blue . Color lightBlue }.
b add: #(37 33 0 0 0) title: 'DN1'.
b add: #(24 26 17 3 0) title: 'DN2'.
b add: #(25 29 15 1 0) title: 'DN3'.
b add: #(30 33 6 1 0) title: 'DN4'.
b addLegend: #('strongly agree' 'agree' 'neutral' 'disagree' 'strongly disagree').
b barWidth: 260 height: 20.
b addLabelToBars: [ :assoc | (assoc key / b totalSum * 100) asInteger asString, '%' ] if: [:assoc | assoc key > 5 ] color: Color white.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Result is the following:
Cheers,
Andrei & Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
8 years, 3 months
Re: help needed with creating moose 5.0 configuration
by Stephan Eggermont
Name: ConfigurationOfFame-StephanEggermont.29
Author: StephanEggermont
Time: 12 December 2014, 1:44:19.682481 pm
UUID: a59ec3f1-2e02-4e1e-a35b-2b195f3f8f1c
Ancestors: ConfigurationOfFame-StephanEggermont.28
wrong version fix in place
Name: ConfigurationOfSmallDude-StephanEggermont.30
Author: StephanEggermont
Time: 12 December 2014, 1:52:50.120165 pm
UUID: a71f5053-b9c9-4024-8457-631db8e8cdf4
Ancestors: ConfigurationOfSmallDude-TudorGirba.29
Version for Moose 5.0
Name: ConfigurationOfPetitSQLParser-StephanEggermont.24
Author: StephanEggermont
Time: 12 December 2014, 1:59:02.954291 pm
UUID: 5150f87c-ee94-43cc-886d-d1933b341ab3
Ancestors: ConfigurationOfPetitSQLParser-StephanEggermont.23
Use the new version in #stable
Name: ConfigurationOfPetitSQLParser-StephanEggermont.25
Author: StephanEggermont
Time: 12 December 2014, 2:07:43.151571 pm
UUID: d631128c-fd0e-4ea6-a4b4-3f6d1ff7c784
Ancestors: ConfigurationOfPetitSQLParser-StephanEggermont.24
typo
I've added a first version of the release5.0 version, only containing
stable versions of the depending configurations. Loading that gives
an emergency debugger.
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
load.
((Smalltalk at: #ConfigurationOfMoose) project version: #'release5.0') load
8 years, 3 months
