Moose-dev January 2014

moose-dev@list.inf.unibe.ch

41 participants
119 discussions

[Glamour] default selection in ListPresentation
by Cyrille Delaunay 24 Mar '18

24 Mar '18

Hello, Is there a way to set a default selection to a list presentation? so that when I open the browser, the morphic list has already a value selected. I tried that: |tmpBrowser| tmpBrowser := GLMTabulator new. tmpBrowser row: #list. tmpBrowser transmit to: #list; andShow: [:a | a list display: [:input | input]; selection: #a; yourself ]. tmpBrowser openOn: #( b c d v a d f r). but the list still open with nothing selected

3 4

Issue 896 in moose-technology: Roassal should offer a proper scrolling mechanism
by moose-technology＠googlecode.com 04 Mar '15

04 Mar '15

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Roassal New issue 896 by tu...(a)tudorgirba.com: Roassal should offer a proper scrolling mechanism http://code.google.com/p/moose-technology/issues/detail?id=896 For any visualisation that is larger than the screen, you immediately get lost in Roassal. Furthermore, the current dragging style does not scale for visualizations that are much larger on one dimension than the screen. We need a mechanism that helps us: - get an idea of where we are (and how much is left outside the current view) - have an easy way to actually scroll through a larger space

3 12

Issue 956 in moose-technology: Problem of focus with GLM-Roassal
by moose-technology＠googlecode.com 27 Feb '15

27 Feb '15

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Roassal New issue 956 by usman.bh...(a)gmail.com: Problem of focus with GLM-Roassal http://code.google.com/p/moose-technology/issues/detail?id=956 The focus is not correct in visualizations created with GLM-Roassal: The focus is centered on the lower right part of the diagram. So zooming-in hides the upper-left part of the diagram. To reproduce: Moose Finder -> a-Moose-Model -> all packages -> visualize -> Dependencies (cycles) -> zoom-in. -- 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 2

Issue 1004 in moose-technology: Roassal should offer circular treemaps
by moose-technology＠googlecode.com 27 Feb '15

27 Feb '15

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Roassal Milestone-5.0 New issue 1004 by tu...(a)tudorgirba.com: Roassal should offer circular treemaps http://code.google.com/p/moose-technology/issues/detail?id=1004 Rectangle treemaps are nice, but the still make it difficult to understand deep nesting. Circular treemaps do a better job there. It should not be hard to extend the TreeMapBuilder to support this. See here: http://lip.sourceforge.net/ctreemap.html -- 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 915 in moose-technology: Roassal Mondrian - Circle with Text obscures text
by moose-technology＠googlecode.com 27 Feb '15

27 Feb '15

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 915 by cunningh...(a)gmail.com: Roassal Mondrian - Circle with Text obscures text http://code.google.com/p/moose-technology/issues/detail?id=915 I want to draw a node in the diagram with a circle (actually, an ellipse) around it, which works. However, the circle obscures part of the text. If the text is multi-line, it obscures quite a bit, in fact. File in the attached extension to ROMondrianExmaple, then run: ROMondrianExample new labeledCircle You should see the issue. Latest Moose Suite 4.7, windows platform. Labels: Type-Enhancement Labels: Component-Roassal Attachments: LabeledCircle.1.cs 582 bytes -- 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 3

Re: FAMIXClass does not understand parameterizedTypes
by Stephan Eggermont 02 Feb '15

02 Feb '15

Could you try with .76? Problem could also be in 74. Working on our presentation for monday, no time to look into it deeply now. Stephan & Diego

4 8

Moose 5.0. DNU point:from:
by Stéphane Ducasse 23 Dec '14

23 Dec '14

Apparently when I move the moose from the finder elements (classes) to the model item I get a DNU point:from: MoprhTreeListManager>>clicked: event inTheCheckboxOf: aTargetMorph | position | position := aTargetMorph point: event position from: client. ^ self isCheckList and: [ (aTargetMorph checkClickableZone translateBy: 2 @ 0) containsPoint: position ] Stef

3 6

What Moose is for me...
by Alexandre Bergel 22 Dec '14

22 Dec '14

- a powerful modeling platform - a nice tower of expressive piles of cool stuff. E.g., If my visualizations works with small numbers, then it will work large Java or tweet models. And this is impressive. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

A suggestion for Roassal
by Hernán Morales Durand 14 Dec '14

14 Dec '14

It would be cool to have a visual catalog for Roassal visualizations. Like a thumbnail viewer. I want to start working in a genome visualization: http://www.blog.telecomfuturecentre.it/wp-content/uploads/files/2012/09/Mbb… Any hints where to start? Any example to start on? Hernán

3 4

Issue 981 in moose-technology: Glamour should provide a means to not transmit all Roassal clicks
by moose-technology＠googlecode.com 25 Nov '14

25 Nov '14

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-5.0 New issue 981 by tu...(a)tudorgirba.com: Glamour should provide a means to not transmit all Roassal clicks http://code.google.com/p/moose-technology/issues/detail?id=981 Originally reported on stackoverflow: http://stackoverflow.com/questions/18829093/make-edges-not-clickable-in-roa… In the below example, you need to uncomment the two lines to work around this issue. We need a better solution. browser := GLMTabulator new. browser column: #myRoassal ; column: #mySelection. browser transmit to: #myRoassal ; andShow: [ : aGLMPresentation | aGLMPresentation roassal painting: [ : view : numbers | |edges| view shape rectangle ; withText ; size: 30. view nodes: numbers. view interaction noPopup. view edges: numbers from: [ :x | x / 2] to: [ :x | x ]. " view edges do: [ :edge | edge model:#doNotSelectMe ]." view treeLayout. ]. ]. browser transmit to: #mySelection ; from: #myRoassal ; " when: [ :selection | selection ~= #doNotSelectMe ] ;" andShow: [ : aGLMPresentation | aGLMPresentation text display: [ : selectedItem | selectedItem asString ] ]. browser openOn: (1 to: 10). -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev January 2014