Hello,
I would like to manage the size of a chart when drawing it into a glamour
presentation. For now the default size is quite big and i am not able to see
it fully.
Does such a mechanism already exist ? Or do you have any starting points
where I should look at ? Is this possible for example with mondrian
visualizations ?
Hello,
I Improved the distributionMap wizard on several points:
=> no long computations anyMore. Should be usable with large models
=> adding some 'conditions' before leaving the first pane. Avoid to end with
exceptions:
- if properties are not well entered
- if properties specified are not 'computable' for this model
=> refactored/cleaned code/ Divided into shorter methods/recategorized
Looks at least cleaner than before
It should fixe the problems recently experimented when trying all moose
menus
I am a PhD student at UFMG, Brazil, and I'm working with source code
metrics. I have a FAMIX model generated by the inFusion tool and I
would like to know if the Moose can export source code metrics (LOC,
WMC, LCOM, etc) of Java classes to .CSV ou XML files?
Is there any plugin of the Moose that have this functionality?
Cesar Couto
--
http://www.decom.cefetmg.br/cesar
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 MooseModel, some commands are strange or does not work:
- browse:
- code with dependencies:
> why are there 2 times Smalltalk in the first pane ?
> the visu seems strange and slow !
> is it used by someone ?
- code with design flow
> unusable as it is slow
> is it used by someone ?
- code with namespace
> is it used by someone ?
- code with package
> is it used by someone ?
- export:
- export to fl
> does not work, there is a DNU. It seems that the notification does not work
- export to mse
> same problem than export to fl
- import file structure
> no progress bar.
> why is it loaded in the same mooseModel and change the model name ?
- import from fl / mse
> it imports, but I do not see what it does. There is no new model in the root. And no new entities in my model.
> after the import mse, the MooseBrowser twinkled !!! (strange behavior) and the VM used 100% of my processor....
- utilities
- bookmark entity: do nothing after asking for a name
- ensure classes and namespaces: do nothing. What is it ?
- infer namespace parents based on names: do nothing
- set root folder does not work: I select a folder, and it does not keep my selection.
Jannik
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 668 by jannik.l...(a)gmail.com: moose menu - on a MooseModel -
import file structure
http://code.google.com/p/moose-technology/issues/detail?id=668
importing a file structure should not change the model name.
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Tudor,
It looks like replacing:
GLMMorphicListingRenderer>>#actOnUpdatedPresentation: anAnnouncement
treeMorph model updateRoots
with:
GLMMorphicListingRenderer>>#actOnUpdatedPresentation: anAnnouncement
anAnnouncement presentation
suspendAllWhile: [ treeMorph model updateRoots ]
makes sense (I was having a lot of updates when updating on a list who was being "transmited" by a tree presentation)
what do you think? can I commit this?
cheers,
Esteban
Hi,
The Moose build is finally green again!
I spent some time to add guard conditions to the menu entries that use the tool registration mechanism like this:
Object>>mooseInspect
<menuItem: 'In Inspector' category: 'Browse'>
Smalltalk isInteractive ifTrue: [
self inspect ]
This solves the problem of triggering all the menu entries when in headless mode.
Cheers,
Doru
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Doru, it seems it was integrated.
---------- Forwarded message ----------
From: <squeak-dev-noreply(a)lists.squeakfoundation.org>
Date: Tue, Jun 28, 2011 at 3:30 AM
Subject: [Vm-dev] VM Maker: VMMaker.oscog-eem.86.mcz
To: vm-dev(a)lists.squeakfoundation.org, lewis(a)mail.msen.com
Eliot Miranda uploaded a new version of VMMaker to project VM Maker:
http://www.squeaksource.com/VMMaker/VMMaker.oscog-eem.86.mcz
==================== Summary ====================
Name: VMMaker.oscog-eem.86
Author: eem
Time: 27 June 2011, 4:09:22 am
UUID: 9fa2ae33-553f-4e81-b8d8-45c5ba299256
Ancestors: VMMaker.oscog-eem.85
Integrate Igor's fix from http://code.google.com/p/cog/issues/detail?id=46.
Modify to use #= instead of #== (important in the simulator)
--
Mariano
http://marianopeck.wordpress.com
Hi,
I would like each finder's pane to be a simple browser instead of just
a presentation. The following does not work and I can't make it work.
When the #selection port is triggered, a new pane is correctly added
to the finder, but all of the finder's panes are updated with the same
content as the new one.
|navigator finder|
navigator := GLMTabulator new.
navigator row: #content.
navigator transmit to: #content; andShow: [:a | a list display:
#allSuperclasses].
navigator transmit from: #content; toOutsidePort: #selection.
finder := GLMFinder new.
finder show: [:a | a custom: navigator].
finder openOn: String
Could you please tell me what I did wrong or if it's a bug?
Thank you
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry
Status: Accepted
Owner: damien.c...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 653 by damien.c...(a)gmail.com: [Glamour]
GLMBasicExamples>>staticAndDynamicMenu presents not working actions
http://code.google.com/p/moose-technology/issues/detail?id=653
0) open a transcript
1) execute: 'GLMBasicExamples open'
2) select 'Menus' (this is populated by the #staticAndDynamicMenu method)
3) go to the 'Text' tab
4) select some text (e.g., 'Character')
5) right click on the text and choose 'Print selection'
you would expect 'Character' to be printed but 'nil' is printed instead. If
you then go to the 'List' tab, select a letter and repeat the process from
step 3, you will get this letter printed in the transcript. I would have
expected the selected text to be printed.
Hi,
Synoptic is a nice tool that offers mining of event state machines from custom logs. You basically get some log file, you define a regular expression that identifies the events (usually, an event on each line) and then pass both the file and the expression to Synoptic.
The result is an inferred state machine. This sounds pretty cool, and I think it can be used as an importer for Moose.
Here is the development webpage:
http://code.google.com/p/synoptic/
Cheers,
Doru
--
www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."
---------- Forwarded message ----------
From: Franco Sabadini <fsabadi(a)gmail.com>
Date: 2011/6/21
Subject: problems linking code
To: info(a)moosetechnology.org
Cc: juan.yue(a)hotmail.com, Santiago Vidal <santiago.a.vidal(a)gmail.com>
Hello,
We're trying to use Moose to analyze code replication on a Java application,
but we haven't been able to link the model with the code, we already tried
the 2 possibilities that are shown on the moose book and nothing worked,
also we tried to do it with ArgoUML app and we couldn't do it either.
The Moose versions we tried are from 4.0 to 4.5, and we tried it in linux,
windows and in mac OS.
Do you have any idea what could be happening?
Thanks.
- Franco
Hello,
I created a extension of the FAMIX meta-model to support XML. It was also
implemented an importer, some metrics and some simple visualization to the
XML tree.
The importer is in "Import FAMIX XML model from file sources" on the import
menu of Moose. It possible to import: setting a file, a directory with XML
files or from an URL.
Visualization is now under a group of FAMIXXMLElement ->
FAMIXXMLElementGroup.
To try, first install the last version of Merlin and then the FamixXML:
Gofer new
squeaksource: 'FamixXML';
package: 'ConfigurationOfMerlin';
load.
(ConfigurationOfMerlin project version: #development) load.
Gofer new
squeaksource: 'FamixXML';
package: 'ConfigurationOfFamixXML';
load.
(Smalltalk at: #ConfigurationOfFamixXML) perform: #loadDefault
regards,
--
Andre Hora
Hi,
I am happy you like Moose.
We know that "MooseScripts createModelForConfigurationOfMoose" creates a model that is stored in a global model cache. However, the idea was to reproduce an image that is large enough to not be openable with the Windows VM. The image with three large models opens just fine on Mac.
In the meantime, Igor produced a new version of the Windows VM that enables one to load this image. However, now the question is when these fixes will make it in the main branch.
Igor, do you happen to have an update on this issue?
Cheers,
Doru
On 26 Jun 2011, at 18:43, Alain Rastoul wrote:
> Hi,
> There was a previous message in the list about an out of memory problem with
> Moose when running
> 3 times MooseScripts createModelForConfigurationOfMoose
> I downloaded moose suite 4.5 (Pharo 1.3) and played a bit with it reading
> the moose book (nice).
>
> IMHO although something is perhaps not completly clear in the vm in memory
> allocation and/or ui process and/or low space watcher (I tryed to debug the
> vm but did not succeed), here the problem seems to be in the Moose model.
> I suspect that the problem is just that the cache keeps a reference to the
> Moose model each time the script is run, see at the end of
> MooseScripts>>createModelForConfigurationOfMoose the model is added to a
> cache ((MooseModel root => MooseGroupRuntimeStorage>> byType) and takes abut
> 130M of memory each time.
> clearing the Moose cache resolve the problem.
> MooseModel allInstancesDo:[ :m | m remove ] seems to be working here, except
> that there is an exception for the root model (I don't know Moose, it may
> not be the best command).
> Perhaps the moose model should not be added by type but overriden each time
> (beeing identified by a "name" ?).
>
> PS: Moose is cool :)
>
> Cheers
> Alain
>
>
>
>
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Hi,
For Java, there is a grammar in PetitJava.
This ships with Moose and is available in the PetitJava squeaksource repo.
Cheers,
Doru
On 26 Jun 2011, at 18:59, Alain Rastoul wrote:
> Hi all,
>
> Do someone know about a PetitParser grammar for c# or java ?
> Verveine seems to be a Java development (and is not accessible).
> TIA
>
> Cheers
> Alain
>
>
>
>
--
www.tudorgirba.com
"Every successful trip needs a suitable vehicle."