July 2014 - Moose-dev

Issue 1058 in moose-technology: Graphet should provide support for Pie and Kiviat charts

by moose-technology＠googlecode.com

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

8 years, 3 months

1
2
0 / 0

Issue 1084 in moose-technology: Impossible to load an image with opened TRMorph

by moose-technology＠googlecode.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

8 years, 4 months

1
1
0 / 0

Issue 1046 in moose-technology: TextPresentation should update rendering when text port is populated

by moose-technology＠googlecode.com

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

8 years, 4 months

1
4
0 / 0

Issue 981 in moose-technology: Glamour should provide a means to not transmit all Roassal clicks

by moose-technology＠googlecode.com

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-r... 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

8 years, 4 months

1
1
0 / 0

Re: Issue 890 in moose-technology: All meta-entities should have a class comment

by moose-technology＠googlecode.com

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.)

8 years, 4 months

1
4
0 / 0

Issue 816 in moose-technology: MooseMetaBrowser's Map re-display after selection of a node

by moose-technology＠googlecode.com

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)

8 years, 4 months

1
10
0 / 0

Issue 1003 in moose-technology: The treemap builder should offer a default weight of 1

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Roassal Milestone-5.0 New issue 1003 by tu...(a)tudorgirba.com: The treemap builder should offer a default weight of 1 http://code.google.com/p/moose-technology/issues/detail?id=1003 Right now, the weight block has to be specified. Instead, we should have a default weight of 1. Furthermore, right now, if the weight returns 0 (like above), we get a ZeroDivide. Zero should be handled without an error. -- 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, 4 months

1
2
0 / 0

Re: Issue 674 in moose-technology: Bullet graphs in Graph-ET

by moose-technology＠googlecode.com

Updates: Summary: Bullet graphs in Graph-ET Labels: -Component-EyeSee Comment #2 on issue 674 by tu...(a)tudorgirba.com: Bullet graphs in Graph-ET http://code.google.com/p/moose-technology/issues/detail?id=674 I changed the topic to be related to Graph-ET :) -- 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, 4 months

1
1
0 / 0

Issue 514 in moose-technology: Introduce the PharoImageSourceAnchor

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-SmalltalkImporter Component-Famix New issue 514 by tudor.gi...(a)gmail.com: Introduce the PharoImageSourceAnchor http://code.google.com/p/moose-technology/issues/detail?id=514 Currently, FAMIXClass>>sourceText has a hack that checks for mooseModel isSmalltalk explicitly. We should introduce a PharoImageSourceAnchor that properly takes care of this.

8 years, 4 months

1
1
0 / 0

Re: Issue 393 in moose-technology: Interactive sort of table widget by columns

by moose-technology＠googlecode.com

Updates: Cc: simon.de...(a)gmail.com tudor.gi...(a)gmail.com Comment #1 on issue 393 by tu...(a)tudorgirba.com: Interactive sort of table widget by columns http://code.google.com/p/moose-technology/issues/detail?id=393 Issue 156 has been merged into this issue. -- 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, 4 months

1
1
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2014