Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Santiago Vidal

Hi, I'm trying to open a Roassal visualization in glamour. I have the following script: | browser action| browser := GLMTabulator new. browser row: [ :r | r column: #columnA; column: #columnB ]; row: #seconRow. browser transmit to: #columnA; andShow: [ :a | a list display: [#('Value 1' 'Value 2' 'Value 3') ]; dynamicActionsOnSelection: [:list | self actionsFor: list ] ]. browser transmit from: #columnA; to: #columnB; andShow: [ :a | a list titleIcon: GLMUIThemeExtraIcons glamorousBrowse ;title:'Data'; display:#('data A' 'data B' 'data C'). ]. browser openOn: MooseModel root allModels anyOne. actionsFor: aPresentation |actions| actions:=OrderedCollection new. actions add: ((GLMGenericAction new) action: [:each |AMerlinWizard openWizard(each selection)]; title: 'Open visualization'; yourself). ^actions. Specifically, when I click in the option "Open visualization" of the popup menu (see dynamicActionsOnSelection) a Merlin Wizard is opened (there are some options that the user has to select) to create a Roassal (or Mondrian) visualization. Currently, I'm creating the visualization in a new view. However, I would like to open it in the #seconRow pane. Someone please could tell me how I can accomplish this? Thanks Cheers Santiago -- Santiago Vidal

12 years, 11 months

Issue 803 in moose-technology: Improve pie and kiviat charts

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-EyeSee New issue 803 by andreho...(a)gmail.com: Improve pie and kiviat charts http://code.google.com/p/moose-technology/issues/detail?id=803 Pie and kiviat charts should work with legends. Kiviat chart to plot metric labels on axis.

12 years, 11 months

moose apprentice course - summary

by Tudor Girba

Hi, Here is a little summary of the first Moose Apprentice public course: http://www.humane-assessment.com/blog/moose-apprentice-day-1-2012-06-02 http://www.humane-assessment.com/blog/moose-apprentice-day-2-2012-06-03 It was fun :) Cheers, Doru -- www.tudorgirba.com "Quality cannot be an afterthought."

12 years, 11 months

Issue 802 in moose-technology: The MetaBrowser spawns an error when wanting to browse the implementation of a property

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.7 New issue 802 by tudor.gi...(a)gmail.com: The MetaBrowser spawns an error when wanting to browse the implementation of a property http://code.google.com/p/moose-technology/issues/detail?id=802 browser := MooseMetaExplorer new browser. browser openOn: MooseModel meta. (browser pane port: #entityToSelect) value: FAMIXClass mooseDescription. (browser pane port: #propertyToSelect) value: FAMIXClass mooseDescription allComplexAttributes anyOne. Then switch to the second pane and press Command+b.

12 years, 11 months

Issue 804 in moose-technology: GLMRoassalEasel should support the Mondrian API of Roassal

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 804 by tudor.gi...(a)gmail.com: GLMRoassalEasel should support the Mondrian API of Roassal http://code.google.com/p/moose-technology/issues/detail?id=804 Right now, it provides ROView as an input. Instead, it should provide ROMondrianViewBuilder

12 years, 11 months

working with athens balloon

by Tudor Girba

Hi, I would like to get Athens for Balloon loaded by default in a Moose image. The idea would be to make it easy for people to migrate to this interface, to make the code ready for Cairo. In the process of testing it, I noticed that the text examples do not work with StrikeFont. Please note that we are using Pharo 1.4. I tried it by doing the followings: Gofer new squeaksource: 'Athens'; package: 'ConfigurationOfAthens'; load. ((Smalltalk at: #ConfigurationOfAthens) project version: #development) load: 'Athens-Morphic'. And then: AthensTextRenderTest test1. The problem seems to be caused by a missing method: StrikeFont>>getPreciseAscent @Igor: Is this a missing method, or is it something else? Would it be difficult to fix this? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years, 11 months

A preprocessor for PetitParser

by Guillaume Larcheveque

Hi everybody, i am currently implementing a preProcessor which is a kind of PPParser, so you can combine it like any parser. At this moment, it is able to manage a simple transformation (a matched regular expression is replaced by a substitution string) and it release the stream in a correct state after his action (the remaining data are not preprocessed and the position is correct). Do you think i should release it directly in PetitParser or in another module? -- *Guillaume Larcheveque*

12 years, 11 months

Moose meta-model extension

by Andrea Caracciolo

Hi, I'm writing to this mailing list for the first time, so let me shortly introduce myself: I'm a PhD student at SCG (prof. O. Nierstrasz / University of Bern) and i'm currently working on architecture validation. I recently started a little project (a more flexible and generic version of moose chef), and since i wanted to display my output in moose i tried to build an extension to the moose meta-model. What i did was creating a new class named FAMIXLiftedAssociation which extends FAMIXAssociation and has a 'from' and to 'to' attribute. I defined the following methods: to <MSEProperty: #to type: #MooseEntity> <MSEComment: 'to-side of the association'> ^ to. from <MSEProperty: #from type: #MooseEntity> <MSEComment: 'from-side of the association'> ^ from where both 'from' and 'to' attributes are MooseEntity objects. On the class side i redefined: annotation <MSEClass: #FAMIXLiftedAssociation super: #FAMIXAssociation> <package: #FAMIX> ^self When i try to browse a group populated with instances of the above described class, i'm able to see them all correctly. But as soon as i click on one of them i get the following error: MessageNotUnderstood: receiver of "allPrimitiveAttributes" is nil I guess the new class has not been recognized as being part of the moose meta-model. Am i wrong ? Did i forget any pragma ? Andrea Caracciolo

12 years, 11 months

[ANN] Roassal 1.28

by Alexandre Bergel

Dear Fellow, A couple of weeks ago we have released the Roassal visualization engine. Many of you gave us feedback and we are deeply grateful for this. Since we released the first version, we have closed 25 issues [*]. Many things are left to do, especially to satisfy all the requirements from the Moose community. We are currently working on an HTML exporter for Roassal. We know this is a highly wanted feature. In a couple of weeks we should be able to deliver it. Since the first release of Roassal, we have worked very hard on it and we will continue to do so. Thanks to all of you! Alexandre, Vanessa, Juan Pablo [*] http://code.google.com/p/objectprofile/issues/list?can=1&q=status=Fixed%20c… -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 11 months

the owner of mondrian edges

by Tudor Girba

Hi Fabrizio. Thanks for helping me reproduce the problem. It should be fixed now. However, there are still some red tests because they assume the old wrong behavior of assigning edges to an owner node. Cheers, Doru On 26 May 2012, at 15:28, Fabrizio Perin wrote: > Hi Doru, > Here is the code you were working on: > > view := MOViewRenderer new. > view nodes: #(2) forEach: [:each | > view shape label. > view node: each* 10. > view shape label. > view node: (each * 10 + 1). > view treeLayout. > ]. > view edgesFromAssociations: {"10->20. 10 -> 11 ." 20->21}. > view open. > > Cheers, > Fabrizio -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

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