Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 769 in moose-technology: Glamour should support drag and drop
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Milestone-4.6 Component-Glamour New issue 769 by tudor.gi...(a)gmail.com: Glamour should support drag and drop http://code.google.com/p/moose-technology/issues/detail?id=769 Something like this: a list allowItemDrag: [:item :list | ... ]; itemDrag: [:item :list | ... ] a list allowDropOnItem: [:draggedObject :targetItem :list | ... ]; dropOnItem: [:draggedObject :targetItem :list | ... ]

5 12

Re: Issue 870 in moose-technology: ROFocusView focuses on the wrong spot
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Issue 870: ROFocusView focuses on the wrong spot http://code.google.com/p/moose-technology/issues/detail?id=870 This issue is now blocking issue moose-technology:816. See http://code.google.com/p/moose-technology/issues/detail?id=816 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Re: Issue 865 in moose-technology: Reloader should get the list of packages to be loaded from the ConfigurationOfMoose
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Issue 865: Reloader should get the list of packages to be loaded from the ConfigurationOfMoose http://code.google.com/p/moose-technology/issues/detail?id=865 This issue is now blocking issue moose-technology:851. See http://code.google.com/p/moose-technology/issues/detail?id=851 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 809 in moose-technology: Glamour selection should happen through an action
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-4.7 New issue 809 by tudor.gi...(a)gmail.com: Glamour selection should happen through an action http://code.google.com/p/moose-technology/issues/detail?id=809 Right now, selecting an item in the user interface will directly populate the #selection port. However, this is less than ideal because it does not allow the developer to intervene in this process. One possibility would be to introduce a selectionAction that is triggered by the ui, and to provide the default behavior is simply setting the #selection port.

1 1

Issue 708 in moose-technology: Fame should accept comments both for properties and for meta descriptions
by moose-technology＠googlecode.com 25 Nov '12

25 Nov '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MooseCore Milestone-4.6 New issue 708 by tudor.gi...(a)gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708 Currently, the MSEComment: is used to define comments of a property. SomeEntity>>someProperty <MSEProperty: ...> <MSEComment: 'comment'> This is used by the MetaBrowser but not by Fame. At the very least, we should add a means to add MSEComment: to the class side for the overall class.

1 5

Reset meta from the moose panel?
by Alexandre Bergel 24 Nov '12

24 Nov '12

Hi! Shouldn't the MooseModel>>resetMeta be accessible from the Utility menu? I think it was on some point, but not anymore apparently. Shall I can introduce it ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

linearFillColor
by roberto.minelli＠usi.ch 23 Nov '12

23 Nov '12

Hi, I'm trying out Roassal to draw the entire revision graph of a Git repository. Looking at the examples, the #tutorial>>step5LinearFillColor is broken (i.e., I got big red rectangle with a yellow diagonals). Do anyone of you know a solution? Cheers, Roberto Minelli

5 11

Famix = static typing
by Nicolas Anquetil 23 Nov '12

23 Nov '12

We have been discussing here for long time that the meta-model approach of Moose is not that much adapted to the problems of reverse engineering. Because we need to model detailed informations on the programs being modeled, Famix has many entities that are language specific. Up to now we manage because Moose "core" deals with only two languages: Java and Smalltalk But if we wanted to deal with other languages C#, PHP, Python, Java-script, Cobol, Pascal, Lisp, ... we would have to add entities and/or constructs specific to each language and the tools would become less and less generic. More recently, it occurred to me that this is very similar to the kind of issues one has to deal with in a statically typed language (Java is evil :-) ). So basically Famix introduced static typing in Moose. If this analysis is correct, the questions would be: - was it necessary to go that way? why? - is there another way to do it? more in tune with the smalltalk way of life? nicolas

3 3

Efficient Roassal Layout
by roberto.minelli＠usi.ch 22 Nov '12

22 Nov '12

Hi, I have a collection of objects (revisions of a Git repository) and I'm trying to build a tree of all the revisions (about 14k). I already computed the neighboring relationships, thus for each revision I know parents and children revisions. I wrote a small Roassal script to build a tree and I tried with subsets of revisions (i.e., 50, 100, 200, 300). Everything works fine until I reach 375 revisions or so.. After more than 10 minutes the graph was not yet displayed. So, I profiled the execution and discovered that the bottleneck is the ROHorizontalDominanceTreeLayout I'm using. I know that the Dominance Tree Layout is expensive to compute, and I was wondering if you could suggest a layout to display a tree with more that 300 nodes. Thanks in advance, Roberto

3 2

No easy way to know which Moose version I am using?
by Mariano Martinez Peck 21 Nov '12

21 Nov '12

Hi guys. I have an image with Moose and I don't know how to get which version is it (like 4.7 or so). If there is nothing existing, I think a good place would be in the Moose Panel, when you click the '?' and you get the Help windows... on the left (index) you can add one item more "Current Version" or something like that with the information (version, date of release, details, etc) ? cheers, -- Mariano http://marianopeck.wordpress.com

4 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev