Moose-dev October 2011

moose-dev@list.inf.unibe.ch

29 participants
175 discussions

Issue 579 in moose-technology: [Kumpel] Incremental loading/Updating of Kumpel Projects

by moose-technology＠googlecode.com

Status: New Owner: junker.m...(a)gmail.com Labels: Type-Enhancement Priority-High Component-Kumpel New issue 579 by junker.m...(a)gmail.com: [Kumpel] Incremental loading/Updating of Kumpel Projects http://code.google.com/p/moose-technology/issues/detail?id=579 The KMPProjectHistory should offer the possibility to update the model to the current head revision.

12 years, 11 months

Issue 543 in moose-technology: inFusion does not export in UTF-8

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 543 by tudor.gi...(a)gmail.com: inFusion does not export in UTF-8 http://code.google.com/p/moose-technology/issues/detail?id=543 MSE should be in UTF-8.

12 years, 11 months

Re: Issue 551 in moose-technology: VerveineJ should export parameterized types

by moose-technology＠googlecode.com

Comment #2 on issue 551 by tudor.gi...(a)gmail.com: VerveineJ should export parameterized types http://code.google.com/p/moose-technology/issues/detail?id=551 Currently, ParameterizableClass is exported, but the instances are duplicated.

12 years, 11 months

Issue 532 in moose-technology: inFusion should also export PrimitiveTypes

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 532 by tudor.gi...(a)gmail.com: inFusion should also export PrimitiveTypes http://code.google.com/p/moose-technology/issues/detail?id=532 void, long, int, boolean, char, char[] ... should be PrimitiveTypes, not Classes

12 years, 11 months

Re: Issue 440 in moose-technology: FamixInvocation>>to should return candidates instead of receiver

by moose-technology＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 440 by simon.de...(a)gmail.com: FamixInvocation>>to should return candidates instead of receiver http://code.google.com/p/moose-technology/issues/detail?id=440 Fixed as first part of MooseChef integration

12 years, 11 months

Re: Issue 420 in moose-technology: Shape should be properly initialized to be useful without further parameter

by moose-technology＠googlecode.com

Comment #3 on issue 420 by tudor.gi...(a)gmail.com: Shape should be properly initialized to be useful without further parameter http://code.google.com/p/moose-technology/issues/detail?id=420 Is this still an issue?

12 years, 11 months

Re: Issue 322 in moose-technology: Add status bar to MOBrowser and MOEasel

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #9 on issue 322 by tudor.gi...(a)gmail.com: Add status bar to MOBrowser and MOEasel http://code.google.com/p/moose-technology/issues/detail?id=322 (No comment was entered for this change.)

13 years

Issue 499 in moose-technology: Port & transmission in Mondrian

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Mondrian New issue 499 by alexandr...(a)gmail.com: Port & transmission in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=499 Hi Alex, -=-=-=-=-= Previous discussion: What we did in Glamour was to attach to each Presentation a kind of default interaction. In your example, I would make #mouseEnter, #mouseClick ... default ports that are populated when the corresponding interactions happen on a graph element. Then of course, these ports will belong to graph elements. Like this transmissions are created between the ports of a graph element. Perhaps there will also be a need to identify graph elements by name so that you can refer to them from outside the context of a script. -=-=-=-=-= Previous discussion: Why not having ports that belong to an interaction instead? Consider the following script: view nodes: (1 to: 1000). Figure selection will imply a transmission between the root and each of these nodes. It could be a single transmission between 'root interaction' and the unique interaction of the nodes? -=-=-=-=-= Doru answer: At least two reasons. First, the ports are not just for transmitting information, but ports also allow you to store arbitrary values that model the graph element, and thus you can model the state of a visualization (including side-effects). Second, using ports you will be able to let the shape populate ports by default without writing any explicit interaction (only write transmission when you want to deal with them). Now, about we can be smart about transmissions and do what we do for shapes: we share the object between multiple graph elements. For this, we will just need a lookup of the origins instead of hardcoding them. Actually in Glamour, we have: GLMTransmission>>originatesAt: aPort and thus, you can have a smart transmission that performs a more complex check by checking if the port is part of any elements from a collection. Like this you will have only one the transmission object. You could write: view nodes: #(1 2 3) labeled: #interestingNodes. view nodes: #(5 6 7) labeled: #otherNodes. view transmitTo: #otherNodes fromAny: #interestingNodes port: #selection. Cheers, Doru

13 years

Issue 645 in moose-technology: we should keep the current selected tab in the moose panel

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 645 by cy.delau...(a)gmail.com: we should keep the current selected tab in the moose panel http://code.google.com/p/moose-technology/issues/detail?id=645 In the moose finder, If I click on an entity, I have a new pane that open on the right. In this new pane, if I select any tab, this one should stay selected when I click on other entities

13 years, 1 month

Issue 726 in moose-technology: FM3PropertyDescription>>getRawFrom: should return false in Boolean properties instead of nil

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Metanool Milestone-4.6 New issue 726 by andreho...(a)gmail.com: FM3PropertyDescription>>getRawFrom: should return false in Boolean properties instead of nil http://code.google.com/p/moose-technology/issues/detail?id=726 It avoids to use the binary message into the Finder with meta-annotated Boolean properties when using Metanool. For example, instead of: each annotations hugeClasses = true We have: each annotations hugeClasses What do you think? Code to fix it is below. FM3PropertyDescription>>getRawFrom: element ^ element privateState attributeAt: self name ifAbsent: [ (self type = FM3 boolean) ifTrue: [false] ifFalse: [nil] ]

13 years, 1 month

← Newer
1
...
4
5
6
7
8
9
10
...
18
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 October 2011