Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Tudor Girba

Hi, I played a bit with the ROTreeMapBuilder, and there are two things that came to mind and that would be nice to extend. I opened some issues: - Support for multiple types of nodes. https://code.google.com/p/moose-technology/issues/detail?id=1002 - Default weight should be 1. https://code.google.com/p/moose-technology/issues/detail?id=1003 - Circular treemap https://code.google.com/p/moose-technology/issues/detail?id=1004 @Roberto: Would you be interested in working on something like this? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

Issue 1012 in moose-technology: GLMExpander does not allow changing pane size

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 1012 by usman.bh...(a)gmail.com: GLMExpander does not allow changing pane size http://code.google.com/p/moose-technology/issues/detail?id=1012 In GLMExpander panes cannot be resized to show completely the contents of the contained presentation. A script with an expander showing an Eyesee chart to demonstrate the problem: browser := GLMDashboard new. browser title: 'Expander Example'. expander := GLMExpander new. expander title: 'Chart'. expander show: [ :a | a title: [ 'A simple eyesee chart' ]. a eyesee title: 'Sample bar chart'; diagram: [:renderer :x :y | renderer verticalBarDiagram y: #yourself; models: #(5 2 10 6 12 8); width: 200; height: 450; baseAxisLine. renderer interaction popupText: #yourself ]]. browser addPaneNamed: #metrics extent: 200@450. browser transmit to: #metrics; andShow: [:a | a custom: expander ]. browser openOn: #('first exmple') -- 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

11 years, 5 months

Strange behavior of Athens font rendering?

by Alexandre Bergel

Hi! Time to time, the following gets rendered: Characters have different sizes, which is not pleasant to read. Any idea how this comes from? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 5 months

another pic from our map builder

by Alexandre Bergel

hi! Some have asked about adding routes and defining cities: https://twitter.com/objectprofile/status/402397548067176448 We have extended our builder with such possibilities. Soon the builder will work on Roassal@Amber. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 5 months

Issue 732 in moose-technology: Moose should improve the visuals for larger fonts

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Usability New issue 732 by tudor.gi...(a)gmail.com: Moose should improve the visuals for larger fonts http://code.google.com/p/moose-technology/issues/detail?id=732 The icons from GLMUIThemeExtraIcons and from MooseIcons should be saved in larger resolutions (currently, they are in 16x16). Mondrian should offer a default class variable for the size of nodes and the width of nodes and edges. These should be settable via global settings.

11 years, 5 months

Re: Issue 362 in moose-technology: Add commands to create/delete Hismo models

by moose-technology＠googlecode.com

Comment #5 on issue 362 by alexandr...(a)gmail.com: Add commands to create/delete Hismo models http://code.google.com/p/moose-technology/issues/detail?id=362 In Moose-Hismo-AlexandreBergel.57 , you can now delete an hismomodel. We need a way to create an hismo model

11 years, 5 months

setting roassal platform

by Tudor Girba

Hi, The current way of setting the Roassal platform is rather clunky. For some reason we have to pass a string: ROPlatform setCurrent: 'athens'. ROPlatform setCurrent: 'morphic'. This string is then matched against a string returned by each subclass. The platforms are stored in a dictionary that is updated in the initialize of each subclasses. I think this is highly complicated for what it should do. We should simply replace this with a mechanism that goes in this direction: ROPlatform setCurrent: ROAthensPlatform new. ROPlatform setCurrent: ROMorphicPlatform new. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

how to programmatically export a png with roassal?

by Tudor Girba

Hi, I am trying to find a way to obtain a bitmap programmatically with a Roassal visualization. I try this: | view | view := ROMondrianViewBuilder new. view nodes: (1 to: 10). view raw bitmap The problem is that the nodes are not yet laid out. As far as I remember, this used to work. How do I trigger the layouts easily? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 5 months

Issue 923 in moose-technology: EyeSee red-square-of-death from ESValueLabelDecorator>>chooseNonOverlappingValues

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 923 by benjamin...(a)gmail.com: EyeSee red-square-of-death from ESValueLabelDecorator>>chooseNonOverlappingValues http://code.google.com/p/moose-technology/issues/detail?id=923 ESValueLabelDecorator>>chooseNonOverlappingValues has the line... chosenValues add: (self values minValue: [:each | each value]). but minValue: injects (Float infinity) so that if 'self values' is empty then (Float infinity) is added to choseValues, which later are #rounded causing an error in the Morph drawing and subsequent RSOD for the EyeSee morph. I am not sure if I've done something wrong that causes 'self values' to be empty, but in any case, this should not kill the Morph. Just for further information, here is the triggering code... browser transmit from: #navigationtree; to: #attributes; andShow: [ :a | a eyesee title: 'Optimize' ; diagram: [ :renderer :input | renderer scatterplot diagramTitle: '@', input absorbedLoad asString , 'kW' ; x: #ratedOutput ; y: [ :m | m powerLossForAbsorbedLoad: input absorbedLoad ] ; valueAxis ; addXDecorator: ESValueLabelDecorator new ; models: (LEKCatalogMotor catalog values sort: [ :m1 :m2 | m1 ratedOutput < m2 ratedOutput ]). ]. where if in a Workspace I do... models:= (LEKCatalogMotor catalog values sort: [ :m1 :m2 | m1 ratedOutput < m2 ratedOutput ])'. models collect: [ :m | m ratedOutput -> m powerLossForAbsorbedLoad: 24 ] explore ...then all the data looks okay. -- 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

11 years, 5 months

Issue 1009 in moose-technology: GTInspector does not accept code on CMD+s

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-GlamorousToolkit Milestone-5.0 New issue 1009 by tu...(a)tudorgirba.com: GTInspector does not accept code on CMD+s http://code.google.com/p/moose-technology/issues/detail?id=1009 When editing code, pressing CMD+s does not trigger the accept. You have to press on the check icon to do it. -- 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

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