Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 792 in moose-technology: Mondrian - broken popupText:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 792 by google....(a)ben.coman.com.au: Mondrian - broken popupText: http://code.google.com/p/moose-technology/issues/detail?id=792 I have isolated what I assume is an issue introduced in ConfigurationOfMondrian-AlexandreBergel.332 with #popupText: Test Case to execute in Mondrian Easel... view interaction popupText: [ :es | 'popupText works']. view shape label. view node: 'node value'. With a freshly unzipped Moose_Suite_4_6, hovering over the node displays a blue box that says 'popupText works' Using Monticello Browser to load ConfigurationOfMondrian-AlexandreBergel.331 then doing '(Smalltalk at: #ConfigurationOfMondrian) project lastVersion load' has the same behaviour. With Monticello Browser, loading ConfigurationOfMondrian-AlexandreBergel.332 then doing '(Smalltalk at: #ConfigurationOfMondrian) project lastVersion load' hovering over the node displays a white box that says 'node value' This behaviour persists through to current ConfigurationOfMondrian-AlexandreBergel.348 The comment on 332 is: 2.147 : Pharo ground is seriously shaking those days... popupText: does not use the Pharo popup, it instead uses popupView: Platform: Windows 7

12 years, 7 months

Issue 833 in moose-technology: Roassal presentation should populate by default the selection port on selection

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 833 by tu...(a)tudorgirba.com: Roassal presentation should populate by default the selection port on selection http://code.google.com/p/moose-technology/issues/detail?id=833 Selecting a figure (or perhaps just clicking on it) in a Roassal painting should populate the selection port of the pane containing the RoassalPresentation.

12 years, 7 months

Issue 830 in moose-technology: ROLabel dynamic text not updating bounds/ROBorder properly

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 830 by google....(a)ben.coman.com.au: ROLabel dynamic text not updating bounds/ROBorder properly http://code.google.com/p/moose-technology/issues/detail?id=830 The code below results in the image attached, where you can see the ROBorder does not encompass the text. The border should probably expand to encompass dynamically changing shapes. but not necessarily since you may want to have a border only around the label with the children having no border. The symptom is more that the width is inconsistent between each of the text nodes. ----------------- | view rawView node1 node2 node3 node4 | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. node1 := ROElement new . node1 model: 'node1'. node1 addShape: ROBorder. node1 addShape: (ROLabel text: [ 'node1 ' , node1 bounds extent asString, ' ', node1 bounds asString ] ). node1 addInteraction: RODraggable. rawView add: node1. node2 := ROElement new . node2 model: 'node2'. node2 addShape: ROBorder. node2 addShape: (ROLabel text: [ 'node2 ', String crlf, node2 bounds extent asString, ' ', node2 bounds asString ] ). node2 addInteraction: RODraggable. rawView add: node2. node3 := ROElement new . node3 model: 'node3'. node3 addShape: ROBorder. node3 addShape: (ROLabel text: [ 'node3 ', String crlf, node3 bounds extent asString, String crlf, node3 bounds asString ] ). node3 addInteraction: RODraggable. rawView add: node3. node4 := ROElement spriteOn: 'node4' . node4 addShape: (ROLabel text: [ 'node4 ', String crlf, node4 bounds extent asString, String crlf, String crlf, node4 bounds asString ] ). node4 addInteraction: RODraggable. rawView add: node4. ROVerticalLineLayout on: rawView elements. ROEaselMorphic new populateMenuOn: view. view noLayout. view open This is Moose4.7 with Roassal.283 on Windows 7. Attachments: ROBorder does not encompass ROLabel text.png 17.6 KB

12 years, 7 months

Delphi parser development started

by Stephan Eggermont

Hi, We started building a Delphi parser using PetitParser. It is modeled like PetitJava and uses the grammar from http://www.dragonkiller.nl/Delphi/delphi2009.html Any feedback (and code) welcome. Source: http://ss3.gemstone.com/ss/PetitDelphi.html License: MIT Have fun, Diego & Stephan

12 years, 7 months

Very detailed Moose model ? (at the level of statement)

by Nicolas Anquetil

It might be interesting in some cases to have very detailed moose models, at the level of single instruction (there is a loop, its test compares variable x to 5, ...) That would generates incredibly huge models, of course, but for localized tasks it could be useful. Was there some work along these lines at any point in time? Or are we the only one to think it could be useful? nicolas

12 years, 7 months

Issue 832 in moose-technology: Meta Browser should provide information about derived properties

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.7 New issue 832 by tu...(a)tudorgirba.com: Meta Browser should provide information about derived properties http://code.google.com/p/moose-technology/issues/detail?id=832 It should somehow show the derived properties different from the non derived ones. Perhaps simply using /, like in UML

12 years, 7 months

MSE models repository

by Andrea Caracciolo

Hi folks, At the following address you will find a repository of MSE files derived from the Qualitas Corpus: => http://scg.unibe.ch/pangea/ The purpose of this repository is providing a common and easy to setup dataset for (moose-based) analyses. The files can be freely downloaded and used. The repository has the following structure: - QualitasCorpus - yyyymmdd(e | r): qualitas corpus with MSE files - yyyymmdd(e | r)-compressed: original qualitas corpus (as downloaded from http://qualitascorpus.com/) - extractor: tool used to generate MSE files (verveineJ SVN rev. 192) - mse: generated MSE files - scripts: shell script for setting up the analysis data folder How to setup the analysis data folder ? 1. download all files available at http://scg.unibe.ch/pangea/scripts/ 2. chmod +x 3a. ./fetchQCr.sh for downloading and uncompressing Qualitas Corpus "recent release" + MSE files 3b. ./fetchQCe.sh for downloading and uncompressing Qualitas Corpus "evolution release" + MSE files at the end you should have an exact clone of http://scg.unibe.ch/pangea/QualitasCorpus/20120401r/ and/or http://scg.unibe.ch/pangea/QualitasCorpus/20120401e/ How to run an analysis ? Use a script like this> ----------------------------------------------- cog="path/to/CogVM" moose="path/to/moose.image" smalltalk="path/to/SmallTalkCode.st" for m in $(find . -name 'model.mse'); do src=${m/model.mse/src} ln -s $m model.mse # link to model file ln -s $src src # link to src file $cog -nodisplay $moose $smalltalk rm model.mse rm src done ----------------------------------------------- where SmallTalkCode.st is something like> ----------------------------------------------- | stream model | model := MooseModel new. stream:= MultiByteFileStream newFrom:(FileStream readOnlyFileNamed: 'model.mse'). model name:(FileDirectory baseNameFor: stream localName). model importFromMSEStream: stream. model size > 0 ifTrue: [ model install ]. model rootFolder:'src'. "… analysis ..." WorldState addDeferredUIMessage: [ SmalltalkImage current snapshot: false andQuit: true ]. ----------------------------------------------- Andrea

12 years, 7 months

Issue 827 in moose-technology: Strange popupView in Roassal

by moose-technology＠googlecode.com

Status: New Owner: alexandr...(a)gmail.com Labels: Type-Defect Priority-Critical Component-Roassal New issue 827 by alexandr...(a)gmail.com: Strange popupView in Roassal http://code.google.com/p/moose-technology/issues/detail?id=827 The popupView: behaves oddly. Consider the following script: | view | view := ROMondrianViewBuilder new. view interaction popupView: [ :el :myView | myView shape rectangle fillColor: Color yellow. myView node: 20 forIt: [ myView shape rectangle fillColor: Color blue. myView node: 30 ]. myView horizontalLineLayout. myView applyLayout ]. view shape rectangle size: 40. view node: 10. view open

12 years, 8 months

Issue 826 in moose-technology: Roassal hover popup on edges

by moose-technology＠googlecode.com

Status: New Owner: alexandr...(a)gmail.com Labels: Type-Defect Priority-High Component-Roassal New issue 826 by alexandr...(a)gmail.com: Roassal hover popup on edges http://code.google.com/p/moose-technology/issues/detail?id=826 With the following script, in Mondrian when you hover over edges a popup appears showing the name of the edge. Is the same possible with Roassal? view shape rectangle size: 20. nodes := view nodes: (1 to: 20). view edges: (2 to: 20) from: 1 to: #yourself. view circleLayout. Thanks Ben for noticing this!

12 years, 8 months

verveineJ - Java heap space

by Andrea Caracciolo

Hi, I' trying to run verveineJ on the Eclipse source code .. and i always get this: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space at java.util.LinkedList.addBefore(LinkedList.java:778) at java.util.LinkedList.add(LinkedList.java:198) at fr.inria.verveine.core.Dictionary.getEntityByName(Unknown Source) at fr.inria.verveine.extractor.java.JavaDictionary.ensureFamixMethod(Unknown Source) at fr.inria.verveine.extractor.java.VerveineVisitor.visitVariablesDeclarations(Unknown Source) at fr.inria.verveine.extractor.java.VerveineVisitor.visit(Unknown Source) at org.eclipse.jdt.core.dom.FieldDeclaration.accept0(FieldDeclaration.java:279) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) at fr.inria.verveine.extractor.java.FamixRequestor.acceptAST(Unknown Source) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:1016) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:628) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:988) at fr.inria.verveine.extractor.java.VerveineJParser.parse(Unknown Source) at fr.inria.verveine.extractor.java.VerveineJParser.main(Unknown Source) I tried adding -Xmx4000m .. but i still get the same exception. Is there another trick ? Thanks. Andrea

12 years, 8 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