- 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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Roassal
New issue 1058 by usman.bh...(a)gmail.com: Graphet should provide support for
Pie and Kiviat charts
http://code.google.com/p/moose-technology/issues/detail?id=1058
Now that Roassal provides support for nice visualizations and we are in the
process of reviving GraphEt, two important missing charts in the repository
of GraphEt are pie and kiviat charts. Is it possible to provide builders
for these two types of charts in GraphEt?
--
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
Hello
RTZoomableView should enable zooming with mouse wheel. It works fine on
Linux, not tested on Mac, but doesn't work for me on Windows (mouse wheel
does nothing). For example, this one:
RTRoassalExample new exampleScrollZoom
Jan
--
View this message in context: http://forum.world.st/Roassal2-RTZoomableView-not-working-on-Windows-tp4786…
Sent from the Moose mailing list archive at Nabble.com.
Status: New
Owner: ----
CC: alexandr...(a)gmail.com
Labels: Type-Defect Priority-High Component-Roassal
New issue 1084 by guillaum...(a)gmail.com: Impossible to load an image with
opened TRMorph
http://code.google.com/p/moose-technology/issues/detail?id=1084
When you save an image with a TRMorph opened; it is not possible to load
this image anymore.
You have to do on the command line: TRMorph allInstances do: #delete to be
able to open your image.
--
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
Status: New
Owner: tu...(a)tudorgirba.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-5.0
New issue 1046 by tu...(a)tudorgirba.com: TextPresentation should update
rendering when text port is populated
http://code.google.com/p/moose-technology/issues/detail?id=1046
This should update the rendering to '42':
composite := GLMCompositePresentation new with: [:a | a text ].
composite openOn: 'fourtytwo'.
composite first text: '42'.
--
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
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
Updates:
Summary: All meta-entities should have a class comment
Comment #1 on issue 890 by tu...(a)tudorgirba.com: All meta-entities should
have a class comment
http://code.google.com/p/moose-technology/issues/detail?id=890
(No comment was entered for this change.)
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-MooseCore
New issue 816 by anquetil...(a)gmail.com: MooseMetaBrowser's Map re-display
after selection of a node
http://code.google.com/p/moose-technology/issues/detail?id=816
In the Moose MetaBrowser, when selecting a node in the Map, this map is
redisplayed at a new location which can even hide the selected node.
How to reproduce the problem:
- open MetaBrowser
- the map (drawing) must be larger than the Map panel
- scroll to the right of the map
- select a node (at the right)
- the map is redisplayed scrolled back to its initial position (full left)
Same thing happens vertically (scroll down, select a node down, map is
redisplayed from top)