- Moose-dev - INF Mailman

Re: how to load Canalyzer using metacello

by Dale Henrichs

15 years, 7 months

2
1
0 0

how to load Canalyzer using metacello

by Stéphane Ducasse

Hi I do not understand when I do ConfigurationOfCAnalyzer loadVersion: '1.3' nothing happens ;( still we have version0013: spec <version: '1.3' imports: #('1.2-baseline' )> spec for: #common do: [ spec author: 'simondenier'. spec timestamp: '11/27/2009 16:55'. spec package: 'CAnalyzer' with: 'CAnalyzer-simondenier.159'; package: 'XML-Parser' with: 'XML-Parser-Alexandre_Bergel.17'; package: 'Pastell' with: 'Pastell-Alexandre_Bergel.17'; package: 'Filesystem' with: 'Filesystem-cwp.51'.]. any idea. It seems that metacello is confused Bored stef

15 years, 7 months

2
4
0 0

if I want to load the latest version of moose

by Stéphane Ducasse

how should I do it? without default of course. because you know I want to be able to load any version from now. Does ((Smalltalk at: #ConfigurationOfMoose) project version: '4.0-beta.2') load. load the latest version of mondrian? In a word how can I avoid to lose hours with loading Moose? Stef

15 years, 7 months

4
6
0 0

I could not find the OSProcess requirement in MooseConfiguration

by Stéphane Ducasse

Name: ConfigurationOfMoose-cyrille_delaunay.34 Author: cyrille.delaunay Time: 2 December 2009, 2:21:04 pm UUID: de4e4698-ae05-406d-8b9e-544b5037c542 Ancestors: ConfigurationOfMoose-tg.33 adding OSProcess to the external requirements. This package is used by Moose-Wizard to import java source files with inFusion

15 years, 7 months

2
3
0 0

Fwd: [Pharo-project] Very tiny fonts

by Stéphane Ducasse

any taker because we could have hypercool fonts in pharo. Stef Begin forwarded message: > From: Juan Vuletich <juan(a)jvuletich.org> > Date: December 3, 2009 1:12:33 PM GMT+01:00 > To: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Cc: Marcus Denker <denker(a)acm.org> > Subject: Re: [Pharo-project] Very tiny fonts > > Hi Stef, > > Stéphane Ducasse wrote: >> juan >> do you have some code that we could study to turn this micro police into font in our smalltalk :) >> > > The code is already in Pharo! Look at #createDejaVu:, the senders and the methods called. > > Besides, (and I already answered this to Marcus), in Cuis evaluate Preferences tinyFonts. Then open a class browser. This font is 5 pixels high, and letters are about 3.5 pixels wide. (Not 7 pixels high and 4.3 wide as I told Marcus, my mistake.) It is the smallest size I found easy to read, especially lowercase characters. I find it useful on PDAs (together with the 6 and 7 sizes also in Cuis). It uses about the same screen space as the "Flea's Knees" and I really find it much easier to read. > > So, don't you prefer DejaVu 5 instead? > > BTW, do play with FreeType. It can produce results equivalent to my DejaVu 5, 6 and 7. > > Cheers, > Juan Vuletich > > Ps: Feel free to forward to the Pharo list > >> Stef >> On Dec 2, 2009, at 6:06 PM, Marcus Denker wrote: >> >> >>> Hi, >>> >>> While discussing Visualisations, we realized we want *really* tiny fonts... >>> Here is a hand-drawn sub-pixel font that is just 5 pixels high... >>> >>> http://typophile.com/node/61920 >>> >>> >>> Now we need to make a font for Pharo... >>> Marcus >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> ------------------------------------------------------------------------ >>> >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.91/2542 - Release Date: 12/03/09 04:32:00 >>> >>> >

15 years, 7 months

1
0
0 0

VW.Famix2 to Pharo.Famix3 ?

by Laval Jannik

Hi all, What is the state of Famix30 in VisualWorks ? I had a problem today: a guy ask to me how to use the DSM in VW. DSM is not updated in VW. I would like to propose to him to export as mse file. But I think that the mse file is in Famix2. In pharo, we have Famix3. So, we should do a tool to make Famix3 with Famix2. Is it difficult to do this ? I think no, but my vision may be bad ? Cheers --- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---

15 years, 7 months

3
2
0 0

java import wizard

by Tudor Girba

Hi Cyrille, Thanks for building the bridge to inFusion. It was long on my todo list and I am happy that you did a nice work there :). Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

15 years, 7 months

1
0
0 0

Changes in Fame

by Cyrille Delaunay

Hi, I just save some changes on the Fame squeaksource repository: - Implement a 'ParseClientFilter' that enable to parse and import mse filtering some elements. This is use in Moose to specify the FAMIX elements (FAMIX.Class, FAMIX.Method, ...) you want to import in a MooseModel from a MSE File (This is already available by selecting 'import from MSE' in the MoosePanel). - Two Lint rules in Fame-Util about the Moose issue 143 -> checking if a FM3 class respect the fame name convention between FM3 and Smalltalk -> checking if the superclass defined in a FM3MetaDescription t exist and is well defined.

15 years, 7 months

2
1
0 0

Can you publish an update to date version of CAnalyzer

by Stéphane Ducasse

hi guys our process just SUCKS!!! I have to go into XML pastell ... to make sure that I get the right version numbers. I would like to WORK today. Stef

15 years, 7 months

1
0
0 0

New version of Mondrian

by Alexandre Bergel

Dear List, I produced a new version of Mondrian (Mondrian-Alexandre_Bergel.296) which include a highly wished features. Edges may now received events. It gives a relatively good approximation for Spline edges also. All tests are green. I tried it on large visualizations (UML, System complexity, Class blueprint). It runs well. If you encounter some issues, please let me know. I am now investigating whether there is a slow down or not. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 7 months

5
10
0 0

Glamour Panes communication

by Laval Jannik

Hi Doru, I'm working on a browser and I have a problem for communication between pane. Here is a part of my sourcecode: ===== | browser| browser := GLMTabulator new. browser row: #browser; row: #feedback. browser showOn:#browser; using:[ browser custom: self orionBrowser. ]. browser showOn: #feedback; from: #browser -> #selectedVersion; from: #browser -> #selectedCat; from: #browser -> #selectedElement; using:[ |feed| feed := self feedback. feed allowNil. browser custom: feed. ]. ^ browser ==== In the "self feedback", I only have selectedVersion. The other values are nil. Have you an idea of my problem ? the repository is:'http://www.squeaksource.com/Orion' and the concerned method is OrionBrowser>>oBrowser. Thank you for your help. Cheers --- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---

15 years, 7 months

5
13
0 0

popupView: is now working

by Alexandre Bergel

Today is a good day! Open a Mondrian easel on a FAMIXClassGroup and execute: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= view interaction popupView: [:entity :aView | entity viewBlueprintOn: aView]. view shape rectangle width: #numberOfMethods; height: #numberOfAttributes. view nodes: classGroup. view edgesFrom: #superclass. view treeLayout -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Following the idea of Doru, the nice things is that you can have popup on a popup. Execute the following in a MOEasel, and move the mouse in the popup. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= view interaction popupView: [:entity :aView | aView interaction popupView: [: anentity :aView2 | aView2 nodes: (1 to: 20)]. aView nodes: (1 to: 20)]. view nodes: (1 to: 20). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= popupView: accept a Two arguments block. If you forget one, then the image freeze. This is a know issue, we're working on it.... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 7 months

4
13
0 0

Re: [Pharo-project] Feature request: Waiting cursor on load

by Tudor Girba

Hi Johan, Thanks for the report. A better forum for Moose related problems would be the moose-dev(a)iam.unibe.ch mailing list. You can subscribe here: https://www.iam.unibe.ch/mailman/listinfo/moose-dev Also, to create an issue related to Moose, please use: http://code.google.com/p/moose-technology/issues/list Coming to your issue, this is due to Metacello having no progress bar. However, if you open a Transcript, you will get a progress report. So, now I changed a bit the ConfigurationOfMoose and it opens it for you when you loadDefault. You can get the change in: ConfigurationOfMoose-tg.33 Cheers, Doru On 30 Nov 2009, at 16:19, Alexandre Bergel wrote: >> finally able to get going on Pharo, I wanted to load Moose. I got the >> ConfigurationOfMoose package, and run the loadDefault method. > > Very good start! > >> I have no problem with a 'load' taking for ever, I know I am on the >> other side of the ocean. But please change the cursor to a 'wait' >> cursor while doing the load. It takes a loooooooong time before the >> first progress bar shows, I almost panicked. And now a progress bar >> just dissapeared, but there is still nothing I can do. The 'wait' >> cursor would go a long way in easing my mind. And it's probably just >> one line of code ... > > > Yeah, this is a well known problem. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "One cannot do more than one can do."

15 years, 7 months

4
3
0 0

Assessing bottlenecks in the Moose importer

by Simon Denier

Hi there I'm trying to assess bottlenecks in the Moose importer. I think there are some hidden scalability issues especially in the InstallElementsOperator and the CandidateListOperator. Now I cant run a profiler on that because the image crashes before the end, so I just randomly pick some interruption from time to time (especially when I dont have feedback by a progress bar). Some suspect code: InstallElementsOperator >>basicRun model entityStorage forSetup. self container do: [:each | model add: each. self increment]. model entityStorage forRuntime <------- here: converting to a runtime storage takes a long time CandidateListOperator >>setUp "dont call 'model allMethods' here because it sorts the group and we dont care at this level" groups := ((model allWithType: FAMIXMethod) reject: #isAbstract) groupedBy: #signature <----- groupedBy: create a dictionary with all method signatures, I suspect it becomes inefficient on large models Any taker/suggestion on this? ----------------------------- Also I think it would be good to launch the importer in a separate/ background thread, with the possibility to cancel it. What we can do basically (for example): [MooseScripts createModelForPharo] forkAt: 20 (give it a low priority to not starve other process, esp. UI) and we can still interrupt the process in Now if someone knowledgeable in Morphic can come with an enhanced progress bar with a cancel button, which would terminate the import process when clicked. -- Simon

15 years, 7 months

5
9
0 0

Mondrian Health report

by Alexandre Bergel

From the version Mondrian-Alexandre_Bergel.277 in October, the current version of Mondrian is slightly slower on rendering nodes (it took 2907 ms to render 1600 nodes). And we are slightly faster on edges (amazing :-). Report produced on 2009-12-01T12:53:48+00:00 Benchmark ManyNode (simple rendering of nodes) : 100 nodes => 17 ms 200 nodes => 51 ms 300 nodes => 113 ms 400 nodes => 193 ms 500 nodes => 316 ms 600 nodes => 440 ms 700 nodes => 590 ms 800 nodes => 770 ms 900 nodes => 951 ms 1000 nodes => 1218 ms 1600 nodes => 3054 ms Benchmark ManyEdges (simple rendering of edges) : 10 edges => 2 ms 20 edges => 5 ms 30 edges => 14 ms 40 edges => 29 ms 50 edges => 50 ms 60 edges => 82 ms 70 edges => 124 ms 80 edges => 188 ms 90 edges => 268 ms 100 edges => 350 ms 200 edges => 4651 ms 300 edges => 36049 ms 56.04 % of methods are covered Progress from last time: +0.92 % Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 7 months

1
0
0 0

FAMIXSourceAnchor superclass

by Cyrille Delaunay

Hi, The smalltalk superclass of 'FAMIXSourceAnchor' is 'MooseEntity'. But in its method #annotation, the superclass described in the pragma #MSEClass:super: is 'FAMIXEntity'. I guess it's a problem but my lack of knowledge in Fame doesn't allow me to be sure.(?)

15 years, 7 months

2
1
0 0

progress bars

by Tudor Girba

Hi, I created a convenience subclass of MooseTask called MooseCustomTask that allows you to easily display a progress bar. Here is an example: MooseCustomTask runWithProgress: [:task | (1 to: 500000) do: [:each | task increment ] ] description: 'Demo' length: 500000 Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow."

15 years, 7 months

1
0
0 0

Fwd: [Pharo-project] new version of CAnalyzer?

by Stéphane Ducasse

Begin forwarded message: > From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Date: November 27, 2009 8:25:02 PM GMT+01:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [Pharo-project] new version of CAnalyzer? > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > hi alex > > did you publish a new version of the configurationOfCanalyzer? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

15 years, 7 months

4
13
0 0

Issue with RuntimeStorage

by Alexandre Bergel

Dear List, While programming with Simon, we bumped into a sensible issue. Consider the two following methods: SetupStorage>>selectAllWithType: aSmalltalkClass ^ self select: [ :each | "-- select returns an ArrayList" each isKindOf: aSmalltalkClass ] RuntimeStorage>>selectAllWithType: aSmalltalkClass ^ byGroup at: aSmalltalkClass ifAbsent: [ OrderedCollection new ] These two methods do not have the same behavior. We could have something starting with "(byGroup keys select: [:cls | cls isKindOf: aSmalltalkClass]) ..." But that would defeat the whole idea of having different storages... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 7 months

3
6
0 0

Re: unable to load moose

by Tudor Girba

The problem is due to the repository of Lukas which is not responsive. Cheers, Doru On 29 Nov 2009, at 20:11, Fabrizio Perin wrote: > Hi Doru, > I'm not able to load Moose. I think that there are some problem with > the repository. The whole day I had back a message like: HTTP error > timout, or something like that. The last time that I tried out I get > this message: can't find EOCD position. At the end there is the full > stack. It's a problem of the repository or a problem of my script to > load moose? > I'm using the configuration for MooseJEE that you create. has > something changed in the loading system? > > Thanks in advance, > > Fabrizio > > > --- The full stack --- > ZipArchive(Object)>>error: > ZipArchive>>readFrom: > MCMczReader>>zip > MCMczReader>>parseMember: > MCMczReader>>loadPackage > MCMczReader(MCVersionReader)>>package > MCMczReader(MCVersionReader)>>basicVersion > MCMczReader(MCVersionReader)>>version > [] in > MCHttpRepository(MCFileBasedRepository)>>loadVersionFromFileNamed: > BlockClosure>>valueWithPossibleArgs: > MCMczReader(ProtoObject)>>ifNotNil: > MCHttpRepository>>versionReaderForFileNamed:do: > MCHttpRepository(MCFileBasedRepository)>>loadVersionFromFileNamed: > GoferVersionReference>>version > GoferLoad>>addReference: > [] in GoferLoad>>initializeOn: > OrderedCollection>>do: > GoferLoad>>initializeOn: > GoferLoad class(GoferOperation class)>>on: > [] in Gofer>>execute:do: > BlockClosure>>on:do: > GoferVersionCache class>>during: > Gofer>>execute:do: > Gofer>>execute: > Gofer>>load > [] in [] in ConfigurationOfMooseJEE class>>ensureMetacello > SystemDictionary(Dictionary)>>at:ifPresent: > [] in ConfigurationOfMooseJEE class>>ensureMetacello > SystemDictionary(Dictionary)>>at:ifAbsent: > ConfigurationOfMooseJEE class>>ensureMetacello > ConfigurationOfMooseJEE>>project > ConfigurationOfMooseJEE class>>project > ConfigurationOfMooseJEE class>>loadDefault > ImageSetup>>perinWorkspace > ImageSetup>>perinSetup > UndefinedObject>>DoIt > Compiler>>evaluate:in:to:notifying:ifFail:logged: > [] in TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection > BlockClosure>>on:do: > - - - - - - - - - - - - - - - > - - - - - - - - - - - - - - - - - - > TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection > TextMorphForShoutEditor(ParagraphEditor)>>doIt > [] in TextMorphForShoutEditor(ParagraphEditor)>>doIt: > TextMorphForShoutEditor > (ParagraphEditor)>>terminateAndInitializeAround: > TextMorphForShoutEditor(ParagraphEditor)>>doIt: > TextMorphForShoutEditor(ParagraphEditor)>>dispatchOnKeyEvent:with: > TextMorphForShoutEditor(TextMorphEditor)>>dispatchOnKeyEvent:with: > TextMorphForShoutEditor(ParagraphEditor)>>keystroke: > TextMorphForShoutEditor(TextMorphEditor)>>keystroke: > [] in [] in TextMorphForShout(TextMorph)>>keyStroke: > TextMorphForShout(TextMorph)>>handleInteraction: > TextMorphForShout(TextMorphForEditView)>>handleInteraction: > [] in TextMorphForShout(TextMorph)>>keyStroke: > ECToolSet class>>codeCompletionAround:textMorph:keyStroke: > DEVToolSet class>>codeCompletionAround:textMorph:keyStroke: > ToolSet class>>codeCompletionAround:textMorph:keyStroke: > TextMorphForShout(TextMorph)>>keyStroke: > TextMorphForShout(TextMorphForEditView)>>keyStroke: > TextMorphForShout(TextMorph)>>handleKeystroke: > KeyboardEvent>>sentTo: > TextMorphForShout(Morph)>>handleEvent: > TextMorphForShout(Morph)>>handleFocusEvent: > [] in HandMorph>>sendFocusEvent:to:clear: > [] in PasteUpMorph>>becomeActiveDuring: > BlockClosure>>on:do: > PasteUpMorph>>becomeActiveDuring: > HandMorph>>sendFocusEvent:to:clear: > HandMorph>>sendEvent:focus:clear: > HandMorph>>sendKeyboardEvent: > HandMorph>>handleEvent: > HandMorph>>processEvents > [] in WorldState>>doOneCycleNowFor: > Array(SequenceableCollection)>>do: > WorldState>>handsDo: > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > PasteUpMorph>>doOneCycle > [] in Project class>>spawnNewProcess > [] in BlockClosure>>newProcess > ------------------------------------------------------------ > > > > -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

15 years, 7 months

2
1
0 0

Mondrian question

by stephane ducasse

hi all I would like to display files and folders. I did something like that but it only display folder and I do not like the first nesting (the first folder got the other nested in). I also found FolderGroup rather boring because it is not polymorphic to folder. May be we should really start to consider trait for Famix40. view shape rectangle width: #numberOfFiles; height: #numberOfFunctions. view nodes: folderGroup forEach: [:each | view node: each. view shape rectangle width: #numberOfFiles; height: #numberOfFunctions. view nodes: each allRecursiveFolders. view nodes: each allRecursiveFiles. view edgesFrom: #belongsTo. view treeLayout. view interaction popupText: [:aFile | aFile entities first numberOfVariables printString, ' variables x ', aFile entities first numberOfFunctions printString, ' functions ' ]. ] any suggestion how to code that in a better way? Mondrian looks too magic for me. Stef

15 years, 7 months

3
8
0 0

filestructureimporter and filesystem

by Tudor Girba

Hi, I worked a bit on the FileStructureImporter to work with Filesystem. The metric calculations are still wrong (see the red test in FileStructureImporterTest). In the process, I also refactored a bit FAMIXFile to make it work with Filesystem. Perhaps this will impact CAnalyzer, but given that it was not really working before, I guess not in a bad sense. Please let me know if it broke anything. There is one conflict in FAMIXFile>>readStream. Currently, there is an override in CAnalyzer with a wrong implementation. I wanted to commit the removal of the method, but I do not have commit rights. Cheers, Doru -- www.tudorgirba.com "Value is always contextual."

15 years, 7 months

1
1
0 0

DSM visualization of java code

by Laval Jannik

Hi all, I made a DSM visualization of iText (a java open-source project). In the screenshot there are only inheritances and invocations, I load the code with inFusion. But the created mse is not complete, I think. I posted an issue (223) on moose bug tracker. Cheers --- Jannik Laval ---

15 years, 7 months

4
6
0 0

New version of CAnalyzer

by Alexandre Bergel

hi! Today I worked with Simon on type resolution and struct constructs of C Version 155 in SqueakSource Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 7 months

3
3
0 0

Mondrian easel

by Stéphane Ducasse

would it be possible that Apple-M shows implementors when use in the mondrian easel Stef

15 years, 7 months

3
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev