Moose-dev November 2011

moose-dev@list.inf.unibe.ch

25 participants
191 discussions

Issue 644 in moose-technology: A fly by help to show each time the source code of an entity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 644 by cy.delau...(a)gmail.com: A fly by help to show each time the source code of an entity http://code.google.com/p/moose-technology/issues/detail?id=644 Maybe it would be interesting when navigating in moose, to always have a fly by help that show the source code of an element

11 years, 11 months

Issue 582 in moose-technology: Watcher support in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 582 by tudor.gi...(a)gmail.com: Watcher support in Glamour http://code.google.com/p/moose-technology/issues/detail?id=582 Like we now have a statusbar, we should also have a detailed preview shown in a floating Watcher window. The behavior would be similar to Quick Look on Mac.

11 years, 11 months

Issue 721 in moose-technology: VerveineJ should mark constructors

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 721 by tu...(a)tudorgirba.com: VerveineJ should mark constructors http://code.google.com/p/moose-technology/issues/detail?id=721 Constructors should be marked with isConstructor.

12 years

Re: Issue 602 in moose-technology: Hapao should provide a legend in every window

by moose-technology＠googlecode.com

Updates: Summary: Hapao should provide a legend in every window Comment #3 on issue 602 by tudor.gi...(a)gmail.com: Hapao should provide a legend in every window http://code.google.com/p/moose-technology/issues/detail?id=602 Then let's name the issue for what it should do.

12 years, 1 month

Issue 489 in moose-technology: Glamour: action list without the dropdown

by moose-technology＠googlecode.com

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

12 years, 1 month

Re: Issue 240 in moose-technology: Smalltalk importer scalability

by moose-technology＠googlecode.com

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?

12 years, 1 month

Re: Issue 191 in moose-technology: Do not execute unnecessary transmissions

by moose-technology＠googlecode.com

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

12 years, 1 month

Issue 600 in moose-technology: Popup does not work properly

by moose-technology＠googlecode.com

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

12 years, 1 month

Issue 751 in moose-technology: Problem with isPrime

by moose-technology＠googlecode.com

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

12 years, 2 months

Issue 750 in moose-technology: GLMTextModel(Object)>>doesNotUnderstand: #highlightSmalltalk:

by moose-technology＠googlecode.com

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?

12 years, 2 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2011