- Moose-dev - INF Mailman

wizard-based customizable DistributionMap

by Cyrille Delaunay

Hi, I'm looking to do this customizable DistributionMap and I have several questions: -> When you say 'customizable', I understand that what should be customizable are: -> kind of properties we want to display -> Color associated to each property Am i right? I guess the kind of the parts (Packages , classes ...) and elements (Classes , methods ) to display, will depend on the moose-group we first clicked-on (to launch to visualization). -> What kind of property can be display in a DistributionMap? In the distributionMap paper, I saw that , for example, properties could be 'the owner of a file', or also the result of a clustering algorithm like 'linguistic concepts'. What kind of property should be propose by the wizard? -> Is it better to have a wizard-based customizable map or a full-dynamically-customizable visualization like the one of SystemComplexity ?

15 years, 4 months

2
1
0 0

Glamour depends on OB

by Alexandre Bergel

Is this really wished? I just stumbled on #starBrowser, #morphIcons. Maybe these static references could be removed. Note that I haven't checked other methods. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

2
1
0 0

how can I launch a visualization on a group of packages?

by stephane ducasse

I tried to click on the group label but I could not get group-based visualizations like distribution maps. Stef

15 years, 4 months

5
4
0 0

Added XML as a tag in code.google.com

by Alexandre Bergel

Hi! I received a number of enhancement request and bug fixes for XML Parser and Pastell. It would be great if I could log this on the google code. I therefore added a new tag. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

2
2
0 0

would be nice to have a fly by help showing the syntax for the query field

by Stéphane Ducasse

because this is not obvious to know (entity propertyNamed: #NOM) > 10 Stef

15 years, 4 months

1
0
0 0

problems with dependencies updating moose

by Fabrizio Perin

Hi, I just tried to update moose starting from moose-suite4_0-beta-5 using ConfigurationOfMoose updateDefault and i got this message: This package depends on the following classes: MAMatrix MAVector MASymetricMatrix You must resolve these dependencies before you will be able to load these definitions: DudeBooleanMatrix DudeBooleanSymetricMatrix DudeBooleanVector Select Proceed to continue, or close this window to cancel the operation. can i update Moose like that or i should use a different way? Cheers, Fabrizio

15 years, 4 months

2
1
0 0

dsm problems

by Tudor Girba

Hi, I am trying to test DSM, but it does not work on Namespaces, and thus on Java models this will lead to a crash. Would it be possible to fix it in the next couple of days? If not, we need to make the menu items work only with PackageGroup. Also, I tried them on a Smalltalk system, but they are just too many and with only very little differences between them. It would be great to trim them before the release. Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

15 years, 4 months

2
3
0 0

Fwd: [Pharo-project] Sprint at Bern

by Stéphane Ducasse

Hi scg members do not forget that we will have fun at your place. Please register so that we know how much we should buy. Stef > From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Date: February 20, 2010 10:32:18 AM GMT+01:00 > To: Pharo-project Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [Pharo-project] Sprint at Bern > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Hi guys > > the software composition group of the university of bern is organizing a Pharo sprint > saturday 13 of march. > You are all welcome. > > http://code.google.com/p/pharo/wiki/PharoSprints?ts=1266658289&updated=Phar… > > http://scg.unibe.ch/contact/maps > > Thanks SCG for organizing and hosting this. > > Stef (we should blog about it) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

15 years, 4 months

1
0
0 0

TheMooseBook?

by Simon Denier

I just noticed a new project on squeaksource which is called TheMooseBook Is it a derivation of HelpSystem to document Moose? That would be cool. -- Simon

15 years, 4 months

2
1
0 0

Missing dependencies?

by Alexandre Bergel

Dear List, I took a fresh Pharo, and tried to load Moose. Some dependencies failed. Are Simon and Doru test servers caught this problem? This package depends on the following classes: MOMatrix MOSymetricMatrix MOVectorDecorator MOVector MOArrayVector You must resolve these dependencies before you will be able to load these definitions: DudeBooleanMatrix DudeBooleanMatrix>>at:and: DudeBooleanMatrix>>at:and:put: DudeBooleanMatrix>>columnSize DudeBooleanMatrix>>initializeRows:columns: DudeBooleanMatrix>>putTrueAt:and: DudeBooleanMatrix>>rowSize DudeBooleanMatrix>>transformDiagNo:andDiagIndex:andDo: DudeBooleanMatrix>>transformRow:andColumn:andDo: DudeBooleanMatrix>>withDiagonalsDo: DudeBooleanMatrix>>withDiagonalsStartingAt:do: DudeBooleanSymetricMatrix DudeBooleanSymetricMatrix>>at:and: DudeBooleanSymetricMatrix>>at:and:put: DudeBooleanSymetricMatrix>>diagonalAt: DudeBooleanSymetricMatrix>>matrixColFormDiagNo:andDiagIndex: DudeBooleanSymetricMatrix>>transformRow:andColumn:to: DudeBooleanSymetricMatrix>>vectorSpecies DudeBooleanSymetricMatrix>>withDiagonalsDo: DudeBooleanSymetricMatrix>>withDiagonalsStartingAt:do: DudeBooleanVector DudeBooleanVector classSide>>new: DudeBooleanVector>>at: DudeBooleanVector>>at:put: DudeBooleanVector>>clearAll DudeBooleanVector>>isTrueAt: DudeBooleanVector>>putFalseAt: DudeBooleanVector>>putTrueAt: DudeBooleanVector>>size DudeBooleanVector>>withContinuos:fragmentsOfMinSize:do: MOClusteringData MOClusteringData classSide>>onDistanceSquare: MOClusteringData classSide>>vectorSpecies MOClusteringData>>averageLinkage MOClusteringData>>centroid MOClusteringData>>completeLinkage MOClusteringData>>dendrogram MOClusteringData>>findMinimum MOClusteringData>>initialize: MOClusteringData>>initializeRows:columns: MOClusteringData>>meanLinkage MOClusteringData>>performClustering: MOClusteringData>>privateLinkage: MOClusteringData>>singleLinkage MOClusteringData>>testFindMinimum MOClusteringData>>testPerformClustering: MOClusteringData>>unsetAt:and: MOClusteringData>>wardsMethod MOClusteringVector MOClusteringVector>>at:put: MOClusteringVector>>found MOClusteringVector>>min MOClusteringVector>>unsetAt: MOClusteringVector>>update MOCorrelationSquare MOCorrelationSquare classSide>>defaultDistanceBlock MOCorrelationSquare classSide>>vectorSpecies MOCorrelationSquare>>asImage MOCorrelationSquare>>copyClusteringData MOCorrelationVector MOCorrelationVector classSide>>new: MOCorrelationVector>>at: MOCorrelationVector>>at:put: MOCorrelationVector>>defaultElement MOCorrelationVector>>min MOCorrelationVector>>size MOCorrelationVector>>unsignedShortAt: MOCorrelationVector>>unsignedShortAt:put: MODistanceSquare MODistanceSquare classSide>>defaultDistanceBlock MODistanceSquare classSide>>on: MODistanceSquare classSide>>on:and:using: MODistanceSquare classSide>>on:using: MODistanceSquare classSide>>vectorSpecies MODistanceSquare>>at:and:put: MODistanceSquare>>checkInvariant MODistanceSquare>>copyClusteringData MODistanceSquare>>dendrogram MODistanceSquare>>distanceBlock MODistanceSquare>>distanceBlock: MODistanceSquare>>initialize:and:using: MODistanceSquare>>initialize:using: MODistanceSquare>>items MODistanceSquare>>performSeriation MODistanceSquare>>rearrange: MOSimilarityItem MOSimilarityItem>>dist: MOSimilarityItem>>similarity: MOVectorItem MOVectorItem classSide>>with:and: MOVectorItem classSide>>with:andAll: MOVectorItem>>= MOVectorItem>>dist: MOVectorItem>>item MOVectorItem>>item: MOVectorItem>>printOn: MOVectorItem>>vector MOVectorItem>>vector: Select Proceed to continue, or close this window to cancel the operation. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

5
4
0 0

petit parser

by Tudor Girba

Hi, As you might know, Lukas has created a very nice framework for building parsers called PetitParser. This would come as a very nice addition to Moose as it would cover the weak point of dealing with unknown languages. Thus, I would like to include it in the default configuration and in the 4.0 release. I already used it with success in a client project, it comes with many tests (all green) and it does not conflict with anything in Moose. Please let me know if you have any objections. I already created a minimal Moose page with loading instructions: http://www.moosetechnology.org/tools/petitparser Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

15 years, 4 months

5
10
0 0

2 more bugs in the MooseFinder

by Alexandre Bergel

The following screenshot shows two bugs: - Falws , where I guess it should flaws - selecting a model does not shows up the list of groups associated to it ("all famix classes", ...) I just loaded the very last version of Moose Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

3
3
0 0

[ANN] 4.0 beta 5

by Tudor Girba

Hi, Moose Suite 4.0 beta 5 is now available for download: http://www.moosetechnology.org/download The same version can also be loaded into a Pharo Development image by executing the following code: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. ((Smalltalk at: #ConfigurationOfMoose) project version: '4.0-beta.5') load. Cheers, Doru -- www.tudorgirba.com "Problem solving should be concentrated on describing the problem in a way that is relevant for the solution."

15 years, 4 months

2
12
0 0

convert from VisualWorks to Pharo

by Cyrille Delaunay

Hello, I'm trying to convert some packages from VW to Pharo. For that, I use the technic described in the SCG wiki (using the squeak exporter in visual works and then dragging the .st file in pharo). For some packages it works well. For other, I have syntax errors (that don't really described the problem). In these case, what is the solution ?

15 years, 4 months

4
9
0 0

Issue #319

by Alexandre Bergel

Hi, I normally fixed the issue 319 (mondrian related). http://code.google.com/p/moose-technology/issues/detail?id=319 If everybody is okay with it, then the issue should be closed. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

1
0
0 0

would be nice to have something like that too....

by stephane ducasse

http://zvtm.sourceforge.net/zgrviewer.html Stef

15 years, 4 months

2
1
0 0

DSM and Mondrian?

by Alexandre Bergel

Hi Jannik, Few weeks ago you apparently spotted a problem due to the last change I made on Mondrian. DSM was really slow. Is this problem still present? cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

3
4
0 0

Problems using java code importer with inFusion under windows

by Fabrizio Perin

Hi, i was using moose in windows and i had an error trying to use the function "import from Java source with inFusion". Seems that OSProcess doesn't work properly. To reproduce the error just try to import java code using this function in the Moose panel in windows. In Mac i never had problem using that cool function. Anybody can help me to figure out where the problem is? Thanks in advance for the support, Fabrizio PS: Here the stack trace: --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll: ExternalWindowsOSProcess>>value ExternalWindowsOSProcess class>>command: WindowsProcess>>command: WindowsProcess>>waitForCommand: OSProcess class>>waitForCommand: MooseImportFromJavaSourceFilesWizard>>validateImportation [] in MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction [] in ProgressInitiationException>>defaultAction BlockClosure>>ensure: ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: PSUIManager(MorphicUIManager)>>displayProgress:at:from:to:during: MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction WizardLastPane>>terminateButtonAction PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction PluggableButtonMorphPlus>>performAction [] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: Array(SequenceableCollection)>>do: PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: PluggableButtonMorphPlus>>mouseUp: PluggableButtonMorphPlus(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableButtonMorphPlus(Morph)>>handleEvent: PluggableButtonMorphPlus(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: [] in PasteUpMorph>>becomeActiveDuring: BlockClosure>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: 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

15 years, 4 months

4
8
0 0

Famix2MSE importer Available in PharoMoose

by Laval Jannik

Hi all, With Cyrille we work on a Famix2MseImporter in Pharo Famix3. It is a hack, in two parts: First, we place a script between the parser and the MooseElement creation. So this script switches elements of Famix2 to Famix3. For example, a FAMIX.InheritanceDefinition in the Famix2Mse become a FamixInheritance in Famix3. The other part of the script appears after the mooseModel creation. In Famix3, there are FamixAccess and FamixReference. But in Famix2, there is only FamixAccess. FamixReference is for a target with type FamixClass. But, when the parser works, it is not easily possible to know the type of an attribute. So, to do it easy, when the MooseModel is created, we check all accesses and test if the target is a FamixClass. If true, the script change the link in a FamixReference. Now, we have three elements with no possible switch: - there is no FAMIXGlobalVariable>>declaredType in Famix2. - in Famix3, FAMIXInvocation>>receivingVariable has disappeared. - in Famix3, FAMIXParameter>>position has disappeared. The meta-informations in Famix2Mse are not taken account. Finally, this script is a hack, the aim is to provide a solution for people who want to come to Pharo-Moose. You can load it with: Gofer new squeaksource: 'Famix2Importer'; package: 'Famix2Importer'; load. A menu item is available in MoosePanel menu. You can try it and mail us if you have some bugs. Cheers, Jannik and Cyrille.

15 years, 4 months

6
25
0 0

[Mondrian] Issue #319 solved

by Alexandre Bergel

Name: Mondrian-Alexandre_Bergel.366 Author: Alexandre Bergel Time: 18 February 2010, 1:44:56 am UUID: 7a842f26-b887-4342-bb53-6e254dda0152 Ancestors: Mondrian-Alexandre_Bergel.365 Mondrian-Alexandre_Bergel.366 Before this version, form builder could not be embedded in a subview. The reason is that asking what is the size of a form shape triggered a new recomputation of each bounds shape. Therefore, all the subnodes form shape appeared to be at the same location. MOFormsShape>>widthFor: and heightFor: simply lookup in cacheShapeBounds instead of recomputing the whole thing. Naturally, a test has been added to MOFormsBuilderTest . This f**king beast entertained my long evening. But at least, I got rid of it. In addition to this, I did some cleaning. This version addresses the issue #319 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

2
1
0 0

Problems using java code importer with inFusion under windows

by Fabrizio Perin

Hi, i was using moose in windows and i had an error trying to use the function "import from Java source with inFusion". Seems that OSProcess doesn't work properly. To reproduce the error just try to import java code using this function in the Moose panel in windows. In Mac i never had problem using that cool function. Anybody can help me to figure out where the problem is? Thanks in advance for the support, Fabrizio PS: Here the stack trace: --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll: ExternalWindowsOSProcess>>value ExternalWindowsOSProcess class>>command: WindowsProcess>>command: WindowsProcess>>waitForCommand: OSProcess class>>waitForCommand: MooseImportFromJavaSourceFilesWizard>>validateImportation [] in MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction [] in ProgressInitiationException>>defaultAction BlockClosure>>ensure: ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: PSUIManager(MorphicUIManager)>>displayProgress:at:from:to:during: MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction WizardLastPane>>terminateButtonAction PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction PluggableButtonMorphPlus>>performAction [] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: Array(SequenceableCollection)>>do: PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: PluggableButtonMorphPlus>>mouseUp: PluggableButtonMorphPlus(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableButtonMorphPlus(Morph)>>handleEvent: PluggableButtonMorphPlus(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: [] in PasteUpMorph>>becomeActiveDuring: BlockClosure>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: 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

15 years, 4 months

1
0
0 0

[Mondrian] Issue 275 fixed

by Alexandre Bergel

Name: Mondrian-Alexandre_Bergel.365 Author: Alexandre Bergel Time: 17 February 2010, 9:53:58 pm UUID: b6d63f96-53a1-4148-9606-7a2a5020f94d Ancestors: Mondrian-Alexandre_Bergel.364 Mondrian-Alexandre_Bergel.365 fromPositions and toPositions may now be set to #() This is necessary to make the arrow attach fixed in a forceBasedLayout. This new version solve the issue #275 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

1
0
0 0

New version of XMLParser

by Alexandre Bergel

Dear List, I incorporated some changes of XMLParser proposed by jaayer(a)zoho.com These changes may break some existing applications. For example, I had to adapt CAnalyzer. ConfigurationOfXMLSupport has now #version102: Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

2
2
0 0

Moose becomes modular...

by Laval Jannik

I have simulated a remove cycle process. Manually I move some elements in a mooseModel of Moose. To remove all cycles in Moose, my conclusions are: ===== >extend method>> Smalltalk::FAMIXClass.browseSource() in Moose-Finder. >extend method>> Smalltalk::FAMIXMethod.browseSource() in Moose-Finder. >move class>> Smalltalk::MPImportSTCommand in Moose-Wizard. >move class>> Smalltalk::MPImportJavaSourceFilesWithInFusionCommand in Moose-Wizard. >extend method>> Smalltalk::FAMIXNamedEntity.isAbstract() in Famix-Extensions. >extend method>> Smalltalk::FAMIXNamedEntity.isAbstract:(Object) in Famix-Extensions. >extend method>> Smalltalk::FAMIXClass.isAbstract() in Famix-Extensions. >extend method>> Smalltalk::CompiledMethod.mooseName() in Famix-Implementation. >extend method>> Smalltalk::CompiledMethod.mooseNameWithScope:(Object) in Famix-Implementation. >remove reference>> checkClass: refers to MooseModel. >extend method>> Smalltalk::MooseModel.mseExportationTest() in Moose-SmalltalkImporterTests. >move class>> Smalltalk::MooseScripts in Moose-SmalltalkImporter. >remove method>> Smalltalk::FAMIXClass.ascendingPathTo:(Object). >extend method>> Smalltalk::FAMIXPackage.definedMethods() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.extendedClasses() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.extendedClassesGroup() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.extensionClasses() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.extensionClassesGroup() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.extensionMethods() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.localMethods() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.localClasses() in Famix-Extensions. >extend method>> Smalltalk::FAMIXPackage.localClassesGroup() in Famix-Extensions. ===== Is it ok for you ? Cheers Jannik

15 years, 4 months

3
5
0 0

Some yellow test in CAnalyzer

by Alexandre Bergel

Hi Cyrille, When I run the test of CAnalyzer I have 36 run, 33 passes, 1 expected failures, 2 failures, 0 errors, 0 unexpected passes. (I haven't updated Moose however, my connection is not optimal for this now). Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 4 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev