Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 669 by jannik.l...(a)gmail.com: moose menu - on a MooseModel -
import from fl/mse
http://code.google.com/p/moose-technology/issues/detail?id=669
the import seems to work, but I do not see the changes.
There is no new entities in my model.
Maybe the browser is not well updated or the cache ?
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 659 by jannik.l...(a)gmail.com: MooseMenu - bookmark entity
http://code.google.com/p/moose-technology/issues/detail?id=659
In the menu of a package group:
- utilities
- bookmark entity: it does not update the glamour browser and we should
close and reopen the browser to see bookmarked entities. It also changes
the name of my group... which is not the behavior that I want.
Is it an old stuff to remove? I think there is a new bookmark mechanism
(with metanool?). If only I knew where it was...
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 660 by jannik.l...(a)gmail.com: MooseMenu - Create load script
http://code.google.com/p/moose-technology/issues/detail?id=660
- createLoadScriptForGroup: I tried with a new class name, the class is not
created. When I use MooseScripts, I have a DNU because of UIManager
===
The script does not handle class creation -> bug if you want.
===
Ok, so: or we ask for a class name, and we create it, or we do not ask...
or maybe we can provide a list with existing classes.
Hi,
I am trying menus in Moose 4.6. I loaded Moose from MooseScript (method createModelForMoose). And I tried all command in menus.
Here are my comments:
On a PackageGroup, some commands are strange or does not work:
- utilities
- bookmark entity: it does not update the glamour browser and we should close and reopen the browser to see bookmarked entities. It also changes the name of my group... which is not the behavior that I want.
- createLoadScriptForGroup: I tried with a new class name, the class is not created. When I use MooseScripts, I have a DNU because of UIManager
- visualize:
- browse package blueprint: DNU
- customizable eyesee chart: should have a progress bar when the computing is slow.
- Dependencies (cycles): seems not working (loop ?)
- distributionMap for these elements: I just did "next", "finish" without configuring anything, I have a DNU
- distributionMap for these parts: I have a SubscriptOutOfBounds.
- export GML graph: I want to specify the place of the file
- package wise system complexity: Zero Divide
- encaps DSM: the name are not well placed
- enriched cycleTable: should have a progress bar
- enriched dsm too.
Jannik
Status: Accepted
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com, cy.delau...(a)gmail.com
Labels: Type-Other Priority-Medium Component-Glamour Difficulty-Easy
New issue 654 by damien.c...(a)gmail.com: [Glamour] Undocumented differences
between types of actions
http://code.google.com/p/moose-technology/issues/detail?id=654
There are multiple ways to add actions to a presentation:
- using #selectionAct:
- using #act:*
- using #dynamicActionsOnSelection:
These methods do not have comments that help in distinguishing them. The
moose book doesn't present them either.
If you explain them to me, I will write the documentation at the
appropriate places.
Status: New
Owner: alexandr...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-Mondrian
New issue 657 by jannik.l...(a)gmail.com: Mondrian progressBar by default
http://code.google.com/p/moose-technology/issues/detail?id=657
I am seeing that a lot of visualization should have a progress bar....
Is it possible to have it directly in Mondrian, and by default ?
Hi Alex,
I am seeing that a lot of visualization should have a progress bar....
Is it possible to have it directly in Mondrian, and by default ?
---
Jannik Laval
Hi,
I am trying menus in Moose 4.6. I loaded Moose from MooseScript (method createModelForMoose). And I tried all command in menus.
Here are my comments:
On a ClassGroup, some commands are strange or does not work:
- utilities:
- compute duplication: should have a progress bar. When it is finished, nothing happens !
- visualize
- blueprint complexity: progress bar
- distribution map for these elements: loop ?
- uml class diagram: should remove "(type)" in the name of each box.
I will continue on other menu next days.
When I will have your comments about these points, I will open issues in bug tracker.
Cheers,
Jannik
Could we update the project Moose-dev, Mondrian and Spy on Jenkins ?
Cheers,
Alexandre
Begin forwarded message:
> From: Marcus Denker <marcus.denker(a)inria.fr>
> Date: 28 June 2011 11:10:44 CEST
> To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr>
> Subject: [Pharo-project] Please test Pharo 1.3!
> Reply-To: Pharo-project(a)lists.gforge.inria.fr
>
> Please test Pharo 1.3!
>
> There is no magic.. what is now here:
>
> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/
>
> Will be the release. Issues fixed until the released are just those that will be detected and fixed.
>
> There is no magic.
>
> For those who only run released software: Version Number is 1.3. Consider this released. There will be no RC.
>
> Marcus
>
> --
> Marcus Denker -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.