Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Tudor Girba

Hi Nicolas, I would like to parse ArgoUML 0.32 and I would like to also be able to parse the annotations. For this, I understand that I should pass the jars to the parser. How do I make VerveineJ be aware of the jars? Do I have to edit the verveineJ.sh and add each of the jars to the classpath? Is there no other way? Cheers, Doru -- www.tudorgirba.com "Don't give to get. Just give."

13 years, 10 months

[ANN] Moose Suite 4.5

by Tudor Girba

We are happy to announce the Moose Suite version 4.5: http://moosetechnology.org/download This is a minor release. What is new: • Important fixes in FAMIX to deal better with Java systems • Better EyeSee engine for scripting visual charts • Improved VerveineJ compatibility for Java parsing Have fun, The Moose Team http://moosetechnology.org

13 years, 10 months

Git + Moose ? (Kumpel ?)

by Simon Denier

As another side project which could be of interest here, in order to demo the Moose platform, I would like to load a Git repo into Moose. I was thinking of using Kumpel for example and one of the current Git projects on Squeaksource. It looks like http://www.squeaksource.com/FSGit.html is the most recent project (May 2011). Is it up to date with the latest version of Pharo/FileSystem? I could load it in a 1.3 Core (a few tests red) but not in a Moose 4.4 (problem with RPackage). I am not knowledgeable in either FSGit or Kumpel. Is anyone working on something similar? Would it be difficult or cumbersome? -- Simon Denier

13 years, 10 months

wait before releasing 4.5

by Alexandre Bergel

Hi! I would like to fix the exporter of Mondrian. I will do it today. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

MondrianNew

by Tudor Girba

Hi, I took a look at MondrianNew. This is an API to construct explicitly every node and edge. There is no factory for you, at least not yet. This can be good or bad, depending on your model. Let's take an example: renderer := MORenderer new. node1 := renderer node on: 'hello'. node2 := renderer node on: 'world'. edge := renderer edge from: node1 to: node2. Here you are explicitly remembering the node references and you are passing them to the edge creation. When you have a handful of these nodes, this can fit nicely what you want. As soon as you have a multitude of nodes, it is no longer easy to make the mapping, because you will have to manage the references manually. In MOViewRenderer we have API that helps you lookup and match nodes only in terms of your model (basically you never get to manipulate nodes or edges, unless you really really want to). The idea behind this is that you should only think in terms of your model and never get to manipulate the internals of Mondrian. This works in many cases, but you do not have such a convenient way to work with explicit nodes and edges like above. So, maybe a good thing would be to add finally some edgeFromNode:toNode: that provides a creation of a node without any node lookup. So, you could have: view := MOViewRenderer new. node1 := view node: 'hello'. node2 := view node: 'world'. edge := view edgeFromNode: node1 toNode: node2. What do you think? Cheers, Doru On 20 Jun 2011, at 15:03, Alexandre Bergel wrote: > The package MondrianNew in the squeaksource repository of Mondrian contains a bunch of classes we quickly defined: > MORenderer>> > addEdge: > addEdges: > addNode: > addNodes: > > MOEdgeFactory>> > from:to: > > MONodeFactory>> > on: > > Cheers, > Alexandre -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

13 years, 10 months

[ANN] humane-assessment.com

by Tudor Girba

Hi, I am happy to announce the new home for humane assessment: http://humane-assessment.com Humane assessment is a new software engineering method for making the assessment of software systems practical and manageable. This is made possible by the Moose analysis platform. The core idea is quite simple: build custom analysis tools to analyze the contextual complexity of your software systems so that you can make better decisions. By decisions I mean anything that has to do with the system: it can be technical (such as, is this concept well encapsulated?, or is my component used the right way?), or it can be broad and strategic (such as, should I refactor my system?). To make it practical we need to be able to craft tools (sometimes complex tools) fast. This is made feasible by Moose, and in turn, Moose achieves this because of Smalltalk. The method also covers process and organization-related problems. If you wish, humane assessment is the coat that can place Moose and Smalltalk within any development team. If you want to promote Smalltalk, perhaps you might want to use this path. I would be happy to provide more information, support and even materials. Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

13 years, 10 months

display matching rule in petit parser

by Norbert Hartl

In the petit ui I can easily see the output of a successful parse as result node tree. Is there a way to show the rules that matched a particular node along with the result? thanks, Norbert

13 years, 10 months

verveinej build failed

by Tudor Girba

Hi Nicolas, The latest VerveineJ build failed: http://ci.moosetechnology.org/job/verveinej/70/ :) Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

13 years, 10 months

Customizable EyeSee chart

by Andre Hora

Hello, I created a simple application using EyeSee, Customizable EyeSee chart, where you can set the metrics you want to see (similar to Customizable System Complexity) in a chart. The x axis shows individual entities (a FAMIXClass, a FAMIXPakage, ...) or a group (MooseGroup) according to the granularity you set. The y axis shows the values of the metrics. I you want to try, run the script below and then right-click in a MooseGroup -> Visualize -> Customizable EyeSee chart. Gofer new squeaksource: 'Moose'; package: 'Moose-EyeSeeCharts'; load. todo: - Allow multiple charts - Interaction. regards, -- Andre Hora

13 years, 10 months

Issue 652 in moose-technology: compositeDiagram bugs

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 652 by andreho...(a)gmail.com: compositeDiagram bugs http://code.google.com/p/moose-technology/issues/detail?id=652 Trying to use compositeDiagram two problems were found: - ESAbstractDiagram>>elements is working in a wrong way. It should return the elements of the composed diagrams; - interaction over ESAbstractDiagram contains some bugs. The selection is not working (maybe) due the problem above.

13 years, 10 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