Moose-dev February 2014

moose-dev@list.inf.unibe.ch

32 participants
93 discussions

[VISSOFT] CFP: 2nd IEEE Working Conference on Software Visualization‏‏
by vis soft 19 Feb '14

19 Feb '14

2nd IEEE Working Conference on Software Visualization Sep 29 - 30, 2014, Victoria, CA http://vissoft.iro.umontreal.ca/ Call for Papers - VISSOFT 2014 The second IEEE Working Conference on Software Visualization (VISSOFT 2014) builds upon the success of the first edition of VISSOFT in Eindhoven, which in turn followed after six editions of the IEEE International Workshop on Visualizing Software for Understanding and Analysis (VISSOFT) and five editions of the ACM Symposium on Software Visualization (SOFTVIS). In 2014, VISSOFT will again be co-located with ICSME in Victoria, BC, Canada. Software Visualization is a broad research area encompassing techniques that assist in a range of software engineering activities, such as, specification, design, programming, testing, maintenance, reverse engineering and reengineering. Covered methods contain the development and evaluation of approaches for visually analyzing software and software systems, including their structure, execution behavior, and evolution. In this conference, we focus on visualization techniques that target aspects of software maintenance and evolution, program comprehension, reverse engineering, and reengineering, i.e., how visualization helps programmers to understand, analyze, and evolve software. We aim to gather tool developers, users and researchers from software engineering, information visualization, and human-computer interaction to discuss theoretical foundations, algorithms, techniques, tools, and applications related to software visualization. We seek theoretical, as well as practical papers on applications, techniques, tools, case studies, and empirical studies. Topics of interest include, but are not limited to: - Program visualization - Visual software analytics - Network visualizations in software engineering - Visualization of software documentations - Visualization of parallel programs - Visualization-based software in computer science and software engineering education - Visualization of workflow and business processes - Integration of software visualization tools and development environments - Visualization of web services - Visualization of software evolution - Visualization of database schemes - Protocol and log visualization (security, trust) - Graph algorithms for software visualization - Layout algorithms for software visualization - Visual debugging - Software visualization on the internet - Empirical evaluation of software visualization - Visualization to support program comprehension - Visualization to support software testing - Visualization of software repositories - Social media visualization Papers are solicited that present original, unpublished research results and will be rigorously reviewed by an international program committee. In addition to full papers, VISSOFT features a New Ideas or Emerging Results (NIER) track and a tool demo track related to the same list of topics suggested above. All accepted submissions will appear in the conference proceedings and the IEEE Digital Library. Hints for writing Software Visualization research papers are available online (http://www.st.uni-trier.de/~diehl/softvis/org/softvis06/hints.html). Submission Information Authors should prepare and electronically submit their papers or abstracts via the EasyChair submission site (https://www.easychair.org/conferences/?conf=vissoft2014). Take care that you provide all required information in EasyChair. At least one author of an accepted paper must attend the conference to present the work. The review process will be single-blind. All papers must conform, at time of submission, to the IEEE Formatting Guidelines. Make sure that you use this MS Word template (http://www.conference-publishing.com/templates/MSW_USltr_format.doc) and this LaTeX class (http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/IEEEtran.cls updated January 3rd, 2013). Submissions must be in PDF format. Make sure that you are using the correct IEEE style file: the title should be typeset in 24pt font and the body of the paper should be typeset in 10pt font. Latex users: please use \documentclass[conference]{IEEEtran} (without option compsoc or compsocconf). Submission Types Technical papers (up to 10 pages): 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 at the end of the abstract input box in EasyChair (not in the submitted paper itself!). NIER papers (up to 5 pages): The NIER contributions 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. Tool papers (up to 4 pages): 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. Challenge paper (up to 4 pages): In the software visualization challenge, authors are to demonstrate the usefulness of their visualization tools on the data provided. The paper should first provide an introduction to the problem, data used, methods and tools used, results and their implications, and conclusions. Important Dates Main track (technical papers) : Abstract Submission: May 9, 2014 Paper Submission: May 16, 2014 Author Notification: June 20, 2014 Camera-ready Copies: July 14, 2014 NIER, Tool Demo, and Tool Challenge tracks: Abstract Submission: June 24, 2014 Paper Submission: July 1, 2014 Author Notification: July 25, 2014 Camera-ready Copies: August 7, 2014 Organizing Committee General Chair: Houari Sahraoui (University of Montreal, CA) Program Co-Chairs: Bonita Sharif (Youngstown State University, US) and Andy Zaidman (Delft University of Technology, NL) NIER & Tool-Demo Track Co-Chairs: Fabian Beck (University of Stuttgart, DE) and Mircea Lungu (University of Bern, CH) Publicity & Web Chair: Daniel Limberger (Hasso Plattner Institute, DE)

1 0

Roassal: double click?
by Martin Dias 18 Feb '14

18 Feb '14

Hi We are working in Roassal and we would like to do something when the user double clicks on a node. We see that both ROMouseLeftClick and ROMouseRightClick are available but we can't see something like ROMouseDoubleClick. Do you plan to add it? Thanks, Roassal is nice! Martín and Gustavo

2 3

Good Moose Dojo
by Anne Etien 17 Feb '14

17 Feb '14

Hi, We (part of the Rmod Inria team from Lille) worked quite well this afternoon during the Moose dojo: - we closed 7 bugs - we corrected more than 120 warnings thanks to APIEvolutioner (from Andre Hora), SmallLint and CriticsBrowser - we migrated the graphics of Ozone to Pharo 3.0 using APIEvolutioner without knowing anything on Glamour, Mondrian and Roassal just looking how the different API evolved. - we started to migrate Torch to Pharo 3.0 but it is not yet finished (at all). And it seems that we didn't brake everything while fixing the rest ;o) So thanks to everyone. Next Moose Dojo in Lille is in March 7th. Anne

7 6

Issue 1048 in moose-technology: Message Not Understood when creating Moose model
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1048 by andreho...(a)gmail.com: Message Not Understood when creating Moose model http://code.google.com/p/moose-technology/issues/detail?id=1048 When loading smalltalk code from the moosepanel. There is a button on the first page of the wizard to create a script But the script generated by this option does not work. Method named createModelNamed:withPackages:importer:candidateClass:mergeClassMetaClass:contextItems: do not exist -- 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

1 1

Issue 942 in moose-technology: Fame-ImportExport - XML Export - transformation of \n and \t not working.
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 942 by v.blonde...(a)gmail.com: Fame-ImportExport - XML Export - transformation of \n and \t not working. http://code.google.com/p/moose-technology/issues/detail?id=942 In the class FMXMLPrinter of the Fame-ImportExport package, the method 'primitive:' doesn't remplace the Character cr by \n and Character tab by \t as expected in the source code. Indeed the affectation of the local block variable by this line of code : char = $n doesn't work. The result expected is : '<?xml version="1.0"?> <Document> <Element name="FAMIX.Comment" id="1"> <Attribute name="content"> <String value="This is a test\"\n\t"/> </Attribute> </Element> </Document>' What we have actually : '<?xml version="1.0"?> <Document> <Element name="FAMIX.Comment" id="1"> <Attribute name="content"> <String value="This is a test\"\ \ "/> </Attribute> </Element> </Document>' Platform : Win7, Pharo 2.0 -- 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

1 7

Issue 1018 in moose-technology: Message not understood Exception when asking for senders of some methods
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Critical Milestone-5.0 New issue 1018 by anne.et...(a)gmail.com: Message not understood Exception when asking for senders of some methods http://code.google.com/p/moose-technology/issues/detail?id=1018 Describe the problem: what do you get? what do you expect? A message not understood exception occurs when asking for senders instead the opening of a window with the list of senders. How to reproduce the problem: step by step if necessary Finding the senders of #+ works. But finding the senders of #ifTrue: or #new or... does not work. Additional information: platform, context which may impact the problem The error comes from GRPackage that does not implement #includesSelector:OfClassName:. Only Magritte and Grease use GRPackage. Please fill in the labels with the following information: * Type-Defect * Component-XXX -- 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

1 6

Issue 1022 in moose-technology: OSProcess should be loaded from the Pharo 3 repo
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-5.0 New issue 1022 by tu...(a)tudorgirba.com: OSProcess should be loaded from the Pharo 3 repo http://code.google.com/p/moose-technology/issues/detail?id=1022 The ConfigurationOfMoose should be modified to make it load from the repository of Pharo 3. -- 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

1 1

1022 - OSProcess now loading from MetaRepoForPharo30
by Usman Bhatti 14 Feb '14

14 Feb '14

The baseline 5.0 in Moose is changed to load OSProcess from MetaRepoForPharo30 thus correcting the bug 1022. Apparently, the loading of OSProcess was causing the moose build to fail. Now the build is unstable because of some previous bugs. We'll close the bug. regards, Usman and Anne

1 0

slice for issue 989
by Anne Etien 14 Feb '14

14 Feb '14

Hello, We create slice to manage exception in the MoosePanel request form (each beginWith: 'C'). We modified Glamour to correctly manage the exception and not launch the debugger when the message sent is not supported. Doru, can you please have a look and integrate our change? Thanks in advance, Rafael, Gustavo, Guillaume and Anne.

2 1

Build failed in Jenkins: moose-5.0 #740
by admin＠moosetechnology.org 14 Feb '14

14 Feb '14

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2014