Moose-dev December 2011

moose-dev@list.inf.unibe.ch

32 participants
167 discussions

Issue 489 in moose-technology: Glamour: action list without the dropdown
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Status: New Owner: ---- CC: tudor.girba Labels: Type-Defect Priority-Medium New issue 489 by jfabry: Glamour: action list without the dropdown http://code.google.com/p/moose-technology/issues/detail?id=489 I have a Glamour pane that is an actionList where I do 5 populate:on:entitled:with: so that the pane has 5 buttons. Now what happens is that the pane also has a dropdown menu, with the same actions as the buttons. This menu should not be there according to Doru ...

1 2

Re: Issue 240 in moose-technology: Smalltalk importer scalability
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Comment #2 on issue 240 by tudor.gi...(a)gmail.com: Smalltalk importer scalability http://code.google.com/p/moose-technology/issues/detail?id=240 Anyone interested in picking this up?

1 1

Re: Issue 191 in moose-technology: Do not execute unnecessary transmissions
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Updates: Labels: -Milestone-4.2 Comment #5 on issue 191 by tudor.gi...(a)gmail.com: Do not execute unnecessary transmissions http://code.google.com/p/moose-technology/issues/detail?id=191 (No comment was entered for this change.)

1 1

Re: Issue 760 in moose-technology: Menssana does not understand set reference value...
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Updates: Summary: Menssana does not understand set reference value... Comment #2 on issue 760 by usman.bh...(a)gmail.com: Menssana does not understand set reference value... http://code.google.com/p/moose-technology/issues/detail?id=760 UndefinedObject(Object)>>doesNotUnderstand: #attributeKeyFrom:

1 7

Issue 600 in moose-technology: Popup does not work properly
by moose-technology＠googlecode.com 03 Mar '12

03 Mar '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hapao Component-Mondrian New issue 600 by alexandr...(a)gmail.com: Popup does not work properly http://code.google.com/p/moose-technology/issues/detail?id=600 It takes times to appear and does not always appears. I am not sure where the problem comes from. Probably Mondrian. The popup has problems probably because the visualization takes time to render. Classes in Hapao are nested within a very large node. This prevent classes to be catched as a bitmap. Tested on Pharo 1.3. Thanks Laurent & Patrick

1 6

Issue 759 in moose-technology: EyeSee window should provide export options
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee New issue 759 by tu...(a)tudorgirba.com: EyeSee window should provide export options http://code.google.com/p/moose-technology/issues/detail?id=759 We should be able to easily export a chart to file.

1 3

Issue 751 in moose-technology: Problem with isPrime
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 751 by stephane...(a)gmail.com: Problem with isPrime http://code.google.com/p/moose-technology/issues/detail?id=751 Describe the problem: what do you get? what do you expect? How to reproduce the problem: step by step if necessary Additional information: platform, context which may impact the problem Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX

1 4

Issue 750 in moose-technology: GLMTextModel(Object)>>doesNotUnderstand: #highlightSmalltalk:
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 750 by usman.bh...(a)gmail.com: GLMTextModel(Object)>>doesNotUnderstand: #highlightSmalltalk: http://code.google.com/p/moose-technology/issues/detail?id=750 In Menssana, when clicking on various reports, we get this error. - Import a model in moose - Launch detailed dashboard in menssana -> top ten lint rules -> browse classes and then we get this error. I may be missing some extensions of glamour in my image?

3 10

Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 743 by usman.bh...(a)gmail.com: This is strange that we have to systematically specify the class of the importer http://code.google.com/p/moose-technology/issues/detail?id=743 a typical sript to import a model is MooseSqueakClassPackageImporterTask new importerClass: SmalltalkImporter; model: model; addFromPackageNamed: #'Moose-TestResources-LAN'; run; yourself But it is rare that we should change the importerClass (it was useful when we had to import FAMIX2 and FAMIX3 side by side). I suggest that we introduce a default and that we initialize the importerClass to SmalltalkImporter.

1 4

Issue 738 in moose-technology: bugs in EyeSee
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Platform-Pharo Component-EyeSee New issue 738 by alexandr...(a)gmail.com: bugs in EyeSee http://code.google.com/p/moose-technology/issues/detail?id=738 I played with the matrix in EyeSee in a Pharo image. I found some problems: - #new:withAll: and #new: seems to raise an emergency debugger, whatever the value we provide - Many references are made that do not belong to EyeSee. For example #zero that refers to MalMatrixCoercion I also found other problems (e.g., hash). I added some tests for those. I produced version 0.9.2 Cheers, Alexandre

1 3

← Newer
1
...
4
5
6
7
8
9
10
...
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2011