November 2014 - Moose-dev

[Glamour] default selection in ListPresentation

by Cyrille Delaunay

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

5 years, 8 months

3
4
0 / 0

Issue 896 in moose-technology: Roassal should offer a proper scrolling mechanism

by moose-technology＠googlecode.com

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

8 years, 9 months

3
12
0 / 0

Issue 956 in moose-technology: Problem of focus with GLM-Roassal

by moose-technology＠googlecode.com

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

8 years, 9 months

1
2
0 / 0

Issue 1004 in moose-technology: Roassal should offer circular treemaps

by moose-technology＠googlecode.com

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

8 years, 9 months

1
6
0 / 0

Issue 915 in moose-technology: Roassal Mondrian - Circle with Text obscures text

by moose-technology＠googlecode.com

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

8 years, 9 months

1
3
0 / 0

Roassal2: Heads/arrows on both ends of a line

by Jan Blizničenko

Hello We use Roassal 2 for visual side of a project we are working on - a diagram modelling tool (like enterprise architect) and we came to a specific need. There are notations like UML which need heads/arrows on both ends of a single line. As far as I understand the roassal code, line decorations are encoded to be at the "to" end and can't be on the other one. We would use help with this problem. Thanks Jan Blizničenko

8 years, 9 months

3
2
0 / 0

VerveineJ download

by Andrea Caracciolo

Hi, Is it still possible to download verveineJ for free ? I tried: svn checkout svn://scm.gforge.inria.fr/svn/verveinej But it now seems to require special permissions. Creating an account at InriaForge does not seem to solve the problem. Can you help me? P.S: the moose book ( http://www.themoosebook.org/book/externals/import-export/external/verveineJ) points to a broken link (http://www.moosetechnology.org/tools/verveinej) Cheers, Andrea Caracciolo _____________________________ Software Composition Group University of Bern

8 years, 10 months

6
6
0 / 0

Re: FAMIXClass does not understand parameterizedTypes

by Stephan Eggermont

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

8 years, 10 months

4
8
0 / 0

Another Moose Thesis

by Mircea Filip Lungu

Hi guys, I don't know if anybody still counts, but I would like to announce another Masters thesis that was written while contributing to Moose: Dennis Schenk's work on Quicksilver ( http://scg.unibe.ch/archive/masters/Sche14a.pdf) Have a nice evening, M. -- Mircea Lungu, PhD. Researcher Software Composition Group University of Bern

8 years, 11 months

3
3
0 / 0

Moose 5.0. DNU point:from:

by Stéphane Ducasse

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

8 years, 11 months

3
6
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2014