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 | ... ]
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.
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.
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
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
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
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