Moose-dev November 2014

moose-dev@list.inf.unibe.ch

42 participants
98 discussions

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

10 years, 6 months

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

10 years, 6 months

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.

10 years, 6 months

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

10 years, 6 months

Issue 973 in moose-technology: Roassal font organizer singleton inconsistencies

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 973 by benjamin...(a)gmail.com: Roassal font organizer singleton inconsistencies http://code.google.com/p/moose-technology/issues/detail?id=973 Following on from Issue 971, use of singletons related to the Roassal font organizer seems not used consistently. Using Finder, I've searched all 'Source' of Roassal packages, for the following both 'ROFontOrganizer' and 'fontOrganizerClass' and found... ----Part1-------------- ROAbstractLabel >> fontFor: anElement with: aCamera fo := ROPlatform current fontOrganizerClass. ROAbstractLabel >> offsetWhenDrawing ^ ROPlatform current fontOrganizerClass ROAbstractLabel >> widthOfLine: string withFont: aFont ^ ROFontOrganizer current widthOfString: string font: font. I propose the last is changed to... ROAbstractLabel >> widthOfLine: string withFont: aFont ^ ROPlatform current fontOrganizerClass widthOfString: string font: font. and also delete... ROFontOrganizer >> current ^ self subclasses first which seems plain wrong. ----Part2-------------- Also I'm a perplexed by the way both of these methods ROMorphicPlatform>>fontOrganizerClass ^ ROFontOrganizerMorphic ROPharoAthensPlatform>>fontOrganizerClass ^ ROFontOrganizerAthens override this one ROPlatform>>fontOrganizerClass ^ fontOrganizerClass such that the instance-variable 'fontOrganizerClass' is ignored, as well as the following seeming irrelevant... ROPlatform>>fontOrganizerClass: ^ fontOrganizerClass := aClass. Is ROPlatform ever instantiated, or abstract? A search for all references to 'ROPlatform' in the 'Source' of all Roassal finds... * ROPlatform current (x40) * ROPlatform platforms (x2) * ROPlatform removeNamed: (x1) * ROPlatform add: (x2) * ROPlatform setCurrent: (x1) * ROPlatform new (x1) The last is only in a test ROPlatformTest>>testAddingAPlatform. I propose to modify... ROPlatform>>fontOrganizerClass self subclassResponsibility delete.... fontOrganizerClass instance-variable delete... ROPlatform>>fontOrganizerClass: from... ROPlatformTest>>testAddingAPlatform remove line... platform fontOrganizerClass: ROFontOrganizer subclasses anyOne. hope this helps, cheers -ben -- 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

10 years, 6 months

Issue 1077 in moose-technology: System complexity is not interactive

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1077 by damien.c...(a)gmail.com: System complexity is not interactive http://code.google.com/p/moose-technology/issues/detail?id=1077 The system complexity visualisation is not interactive: I don't get any fly-by-help nor can I click on rectangles to have details about the class. -- 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

10 years, 6 months

Issue 1070 in moose-technology: Group 'UI' depends on PPBrowser without loading it

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1070 by damien.c...(a)gmail.com: Group 'UI' depends on PPBrowser without loading it http://code.google.com/p/moose-technology/issues/detail?id=1070 Execute this in Pharo 3: (ConfigurationOfMoose project version: #development) load: 'UI' Then you can't open the World menu anymore. PPBrowser is missing. -- 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

10 years, 6 months

Issue 1089 in moose-technology: Roassal should export PNG

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-5.0 New issue 1089 by tu...(a)tudorgirba.com: Roassal should export PNG https://code.google.com/p/moose-technology/issues/detail?id=1089 We have a first draft of RTPNGExporter, but the problem is that it provides only the visible part of the morph. The problem is here: exportToFile PNGReadWriter putForm: view view canvas morph imageForm onFileNamed: self fileName -- 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

10 years, 6 months

Issue 1096 in moose-technology: Glamour Table presentation does not have horizontal scrollbars

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-5.0 New issue 1096 by tu...(a)tudorgirba.com: Glamour Table presentation does not have horizontal scrollbars https://code.google.com/p/moose-technology/issues/detail?id=1096 Until we find a better way to provide access to the contents in wide tables and lists, we have to re-enable the horizontal scrollbars -- 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

10 years, 6 months

roassal1 -> roassal2 todos left

by Tudor Girba

Hi, We have gone through most of the Roassal problems, but we still have a couple of issues left. First, we need to be able to export to PNG. Right now, the implementation exports only the visible part of the morph, but it should export the whole canvas. Ideally, we should use the Athens ability of exporting PNGs: https://code.google.com/p/moose-technology/issues/detail?id=1089 Then, we still have a couple of visualizations left to port: PPParser>>visualizeStructureInGraphOn: PPParser>>viewAllNamedParsersWithSelection:previewing:on: Any takers? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2014