Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

by Andrei Chis

Hi, 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. Cheers, Andrei

9 years, 9 months

Indentation Sensitive Languages in PetitParser

by Jan Kurš

Hi All, 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. Regards, Jan

9 years, 9 months

Tagcloud around avatar part 2: Advances, questions and suggestions

by Offray Vladimir Luna Cárdenas

Hi, 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 [1] you will get something similar to [2] (the difference is that screenshot is for code inside a grafoscopio document instead of a simple playground). [1] http://ws.stfx.eu/9G5PEGYFL1MW [2] http://mutabit.com/deltas/repos.fossil/datapolis/doc/tip/Figures/personal-t… 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 the end). So in my attempt to clean the data I'm trying to process originalText (look at [1]) 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 [3], but seems inelegant and trying to use cascades and ending in #yourself didn't make the trick. =[3]========================== 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 [3] 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 [4] =[4]========================== (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 [5] [5] http://sebastianraschka.com/Articles/2014_twitter_wordcloud.html I will be waiting for your suggestions and thanks for keeping Pharo/Moose awesome! Cheers, Offray

9 years, 9 months

3rd IEEE Working Conference on Software Visualization

by Alexandre Bergel

Dear all, Many of you have an interest in software visualization. Which is why this call for papers may be relevant for you. Kind regards, Alexandre ==== 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: 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 ==- General Chair: Jürgen Doellner, 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 NIER/Tool Co-Chairs: Craig Anslow, University of Calgary, Canada -- http://anslow.cpsc.ucalgary.ca/ Johan Fabry, University of Chile, Chile -- http://pleiad.cl/people/jfabry Web Chair: Juraj Kubelka, University of Chile, Chile -- http://www.juraj-kubelka.cz/ Program Committee: 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. Best regards, Fabian Beck and Alexandre Bergel Program Co-Chairs -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 9 months

Adding elements to GLMRoassal2Presentation

by Pierre CHANSON

Hi all, 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: GLMRoassal2Presentation>>renderOn: I think the new elements added to the RTView should be inspectable in the presentation. 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. x:=0. 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 ]. v. ---------------------------------------------------------------------- Pierre

9 years, 9 months

Issue 1118 in moose-technology: GT Inspector: Double Click Doesn't Always Select Text Properly

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1118 by sean.p.d...(a)gmail.com: GT Inspector: Double Click Doesn't Always Select Text Properly https://code.google.com/p/moose-technology/issues/detail?id=1118 In Pharo #40589 It took me a while to figure out that GT has a feature I've wanted for a long time: when you activate a workspace by clicking, the selection is preserved. Very cool! One thing though, where it also took me a while to figure out what was going on... 1. Type in the playground: 'aString'. 'anotherString'. 2. "Go" to bring up a second pane - doesn't matter which 3. Click in the second pane to put the keyboard focus there 4. Double click on one of the lines in pane #1 It is selected - great! 5. Repeat #3 6. Double click on the unselected line The selection will be cleared, but the other line will not be selected. NB: an interesting thing is that if you do the above exercise with a text editor outside the same GT window, like another GT Inspector, steps 5 and 6 work correctly just like the previous. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 9 months

Spotter feedback

by Stephan Eggermont

Keep up the good work! It is getting better all the time. - I wanted to search for source, not source: or something starting with source. I thought perhaps typing a space after source would reduce the result set. - I tried selecting the list of implementors with the mouse, but was only able to do so after moving the selection to the first of the implementors. Stephan

9 years, 9 months

Roassal Example Browser in Pharo

by Sean P. DeNigris

How do I get the example browser working (i.e. drawing the visualizations instead of inspecting them) in Pharo 4.0? I loaded Roassal2 stable per https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/QuickStart/… . Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Roassal-Example-Browser-in-Pharo-tp4813039.html Sent from the Moose mailing list archive at Nabble.com.

9 years, 9 months

GTInspector and string search

by phil＠highoctane.be

I've loaded GTPlayground and GTInspector in my 3.0 image. Works nice. Now, I needed to search a string in a string show in the String tab. There seemed to be no way to do that. Is there a shortcut key? I have a large piece of text and I missed that feature. Got away by copy/pasting to an old workspace and searching from there. TIA for the pointer. Phil

9 years, 9 months

Moose-Algos. Why Moose?

by Christophe Demarey

Hi, Packages in MooseAlgos are quite independent of Moose. I wonder if it would be good to have them as an independent project. In fact, they are not far from being independent (some dependencies to break) but the name of the project does not reflect that. Maybe it is something that prevents other developers to use these algorithms. I personally think MooseAlgos will benefit from a name without Moose. 'Algos' is not a good name and it is difficult to find a good one because there are algorithms for graphs (mostly), clustering, and matrix. There is also a package with code under the BSD license. Need to split? Name ideas? Here are the dependencies (only static analysis, I do not know if there are some runtime dependencies not detected) : Moose-Algos-Graph has a dependency on Moose-Core because Moose-Algos-Graph defines an extension method cyclesToAll: for MooseGroup. It is very strange. #cyclesToAll: is only called by FAMIXNamespaceGroup>>#cyclesToAllProviderNamespaces in the Famix-Extensions package. This methods has no senders. Either MooseGroup>>#cyclesToAll and FAMIXNamespaceGroup>>#cyclesToAllProviderNamespaces should be removed or moved MooseGroup>>#cyclesToAll should be moved to #FAMIXNamespaceGroup. WDYT? Moose-Algos-Clusturing depends on Moose-Core because MalClusterEngine>>performClusteringShowProgress: references MooseCustomTask. I don't know how to break this dependency. Best regards, Christophe.

9 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev