- Moose-dev - INF Mailman

Jenkins build is back to stable : moose-latest-dev-4.9 #1281

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1281/>

11 years, 8 months

1
0
0 0

Reverse Radial tree layout

by Alexandre Bergel

Hi! I finally got the time to include of the last layout of Mathieu that was not included: the reverse radial tree layout. Here what it looks like (the edges are just for aesthetic purpose). The script was made in Moose, using the following: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= view shape ellipse size: [ :cls | cls numberOfMethods log * 7 ]. view nodes: classGroup. edges := view edgesFrom: #superclass. view layout: (ROReversedRadialTreeLayout new userDefinedEdges: edges). bs := (ROBSplineLine new). bs alpha: 0.85. bs setDiscovery: [ :cls | cls superclass ]. bs color: (Color red alpha: 0.5). view shape: bs. lastlevel := classGroup select:[ :cls | (cls subclassHierarchy size) == 0 ]. view edges: lastlevel from: #yourself toAll: [ :cls | (cls queryAllOutgoingInvocations atTypeScope) select: [:clsa | (clsa subclassHierarchy size) == 0 ]]. view raw bitmap. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 8 months

3
2
0 0

Jenkins build became unstable: moose-latest-dev-4.9 #1278

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1278/>

11 years, 8 months

1
0
0 0

Jenkins build is back to stable : moose-latest-dev-4.9 #1273

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1273/>

11 years, 8 months

1
0
0 0

serializing and materializing MSE files with the Fame meta-engine

by Tudor Girba

Hi, I put together a short description/tutorial on using Fame for serialization and materialization of models and meta-models. Perhaps it can be useful for others, too: http://www.humane-assessment.com/blog/serializing-and-materializing-mse-fil… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 8 months

2
1
0 0

Jenkins build became unstable: moose-latest-dev-4.9 #1266

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1266/>

11 years, 8 months

1
0
0 0

Moose 4.9 and tests

by Usman Bhatti

Hello, There are several tests failing in Moose 4.9. Majority of them are related to OSProcess and some others are related to Moose and Roassal. We have Pharo sprint next week so, here in Lille, we can work on making unstable builds on the moose jenkins green (Moose 4.9, Moose-algos, and Moose-on-the-web). Because, it will be difficult for us to move the downstream projects to Moose 4.9 unless the build is stable. It would be good to know the roadmap to move to Pharo 3.0 because the major change between Moose 4.8 and Moose 4.9 is removing Mondrian. So when do we move to Pharo 3.0? regards, Usman

11 years, 8 months

4
8
0 0

Fwd: [Pharo-users] Please contributors fill up this form...

by Stéphane Ducasse

Hi guys This is important. If you ever contributed to Pharo please send your information and this is also good for your visibility this is a win-win situation. Stef Begin forwarded message: > From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Subject: [Pharo-users] Please contributors fill up this form... > Date: October 9, 2013 1:34:07 PM GMT+02:00 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>, Pharo Development List <pharo-dev(a)lists.pharo.org> > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Hi guys > > I would like to get > contributors.pharo.org a bit more representative of Pharo. > > We should have Previous contributors and enhance the current list. > Can you please reply to this mail > > PharoContributor new > name: 'Esteban Lorenzano'; > id: 'estebanlm'; > email: 'estebanlm(a)gmail.com'; > website: 'http://smallworks.eu'; > description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; > image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > yourself > > > Stef

11 years, 8 months

2
1
0 0

Problem loading ConfigurationOfGlamour

by MartinW

(Sorry if this is a repost. I have a problem with Nabble.com.) Whenever i try to load ConfigurationOfGlamour in a 20621 Pharo image i get the following error: Error: Could not resolve: CollectionExtensions [CollectionExtensions-TudorGirba.34.mcz] in /Users/wm/Pharo Images/package-cache So i can no longer load ConfigurationOfGlamour. I tried 2.4 and 2.5-snapshot and i did also empty my package-cache. No difference. Any idea where the problem lies? -- View this message in context: http://forum.world.st/Problem-loading-ConfigurationOfGlamour-tp4711634.html Sent from the Moose mailing list archive at Nabble.com.

11 years, 8 months

2
5
0 0

missing parenthesis - R3CubeLayout>>on:

by Usman Bhatti

n := elements size nthRoot: 3 ceiling should be n := (elements size nthRoot: 3) ceiling in on: elements | n rowSizes rowPositions columnSizes columnPositions levelSizes levelPositions | n := elements size nthRoot: 3 ceiling. "Initialize the cell sizes" rowSizes := Array new: n. columnSizes := Array new: n. levelSizes := Array new: n. Otherwise, Array is initialized on a float and that gives an error. usman

11 years, 8 months

2
1
0 0

Jenkins build became unstable: moose-latest-dev-4.9 #1261

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1261/>

11 years, 8 months

1
1
0 0

Jenkins build is back to stable : moose-latest-dev-4.9 #1260

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1260/>

11 years, 8 months

1
0
0 0

[Roassal] New tree map builder for Roassal

by roberto.minelli＠usi.ch

Hi, I finished the first version of the new tree map builder for Roassal. You can find the source code in my SmalltalkHub package 'DevFlow-View'! Gofer new smalltalkhubUser: 'RobertoMinelli' project: 'DevFlow'; package: 'DevFlow-View'; load. Here's an example usage: builder := DFTreeMapBuilder new. builder weightBlock: [ :el | el ]. builder nodes: (1 to: 50). builder associations: (builder nodes allButFirst collect: [:each | (each // 2) -> each ]). "Some optional configurations parameters" colors := Color white mix: Color blue shades: (builder nodes size). builder colorBlock: [ :el | colors at: el ]. builder rootColor: ((Color red) alpha: 0.5). builder inset: 5. builder extent: 500@300. builder origin: 10@30. builder draw. And the resulting tree map! [cid:EC2669CC-CA97-4B81-8B1B-B792FBE1C04F@mobile.usilu.net] Please tell me what do you think! The next steps are: - Add customizable interactions - Remove z-ordering and use proper nesting - Eventually unroll the recursion in the layout algorithm Cheers, Roberto

11 years, 8 months

4
19
0 0

Possibility of adding text in Roassal 3D

by Usman Bhatti

Hello, Is there a way to add text (similar to ROPopup in Roassal 2D or openGL text) in roassal 3d visualizations? I've had a look at the examples and the API but couldn't spot its implementation? tx, usman

11 years, 9 months

2
2
0 0

Modeling tweets with Moose

by Alexandre Bergel

Hi! I have been working with a professor interested in visualizing tweets. Here a first shoot. It simply shows the retweet over the time. I will share some more soon Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 9 months

2
1
0 0

[Fwd: [GSoC Mentors] QEMU/CPC project: an experience report]

by Ben Coman

This was an interesting write up on code refactoring from GSoC. Since continuations are a big part of Smalltalk, it was particularly interesting to read about Continuation Passing C. cheers -ben -------- Original Message -------- Dear all, We were so excited about our QEMU/CPC GSoC project that we have decided to write a 12-page article to share our experience: QEMU/CPC: static analysis and CPS conversion for safe, portable, and efficient coroutines http://gabriel.kerneis.info/research/files/qemu-cpc.pdf If you want to learn more about QEMU internals, how we fixed hundreds of lines of code with a small checking tool, or discover a nice compilation technique for coroutines, you will probably be interested in this article. We also hope that other mentors will find it useful as a resource for prospective students looking for an example of past GSoC projects. Thanks to Google, and everybody involved, for making this great project possible. -- Gabriel Kerneis http://gabriel.kerneis.info/ -- You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-summer-of-code-mentors-list+unsubscribe(a)googlegroups.com. To post to this group, send email to google-summer-of-code-mentors-list(a)googlegroups.com. Visit this group at http://groups.google.com/group/google-summer-of-code-mentors-list. For more options, visit https://groups.google.com/groups/opt_out.

11 years, 9 months

1
0
0 0

loading configurationOfGlamour in 2.0 displays warning

by Usman Bhatti

Take fresh pharo 2.0 and then ConfigurationOfGlamour loadDevelopment displays this warning. Did someone encounter this problem before? [image: Inline image 1]

11 years, 9 months

2
1
0 0

significant Moose-Core internal changes

by Tudor Girba

Hi, I would like to signal that Diego and Stephan worked on some internal changes to Moose-Core that can have impact on other code. So, here is a little review to start the discussion: - mooseName is now cached. This can have an impact if you rely on your model to be more dynamic. If you have a custom entity that can receive sub-entities at runtime, you might want to resetMooseName. For example, if you modify the scope of a FAMIXType, the mooseName has to be reset: FAMIXType>>container: aContainerEntity container := FMMultivalueLink on: self update: #types from: self container to: aContainerEntity. *self resetMooseName* This is supposed to be an optimization, but it makes the code more complicated. To see if it is actually worth it, we should benchmark the impact. @Diego, @Stephan: Did you do some benchmarking on this? - An entity now answers if it hasUniqueMooseNameInModel. This is at the moment used when caching the entity by name in groups. For example, Associations do not have a unique name and thus, they are not cached. - There are some parts of the code I do not understand. For example, the need of this code: MooseGroupStorage>>becomeKind: elementStorageClass ... *self do: [ :each | each hasUniqueMooseNameInModel ifTrue: [ each privateClearMooseName ] ].* ... Did I miss anything? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 9 months

4
6
0 0

Where is moose 4.8 and 4.9?

by Juraj Kubelka

Hi! On that page https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ is development version, now called 4.9? And stable image is available here http://www.moosetechnology.org/download? I am a bit confused because main page http://www.moosetechnology.org says "4.8 beta". Thanks, Jura

11 years, 9 months

2
2
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #1243

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1243/> ------------------------------------------ Started by upstream project "petitjava" build number 261 originally caused by: Started by upstream project "petitparser" build number 237 originally caused by: Started by timer Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson1244262677231347669.sh + wget --quiet -O - http://get.pharo.org/20+vmLatest + bash Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: Error: Could not resolve: ConfigurationOfCommandShell [ConfigurationOfCommandShell] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.squeaksource.com/MetacelloRepository ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/MetacelloRepository: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mMetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] Array(SequenceableCollection)>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>explicitLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushExplicitLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>explicitLoadPackageSpecs:repositories: MetacelloPackageSpec>>explicitLoadUsing: MetacelloPackageSpec>>loadUsing: in Block: [self explicitLoadUsing: mcLoader] MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>doingLoads: MetacelloPackageSpec>>loadUsing: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: ConfigurationOfCommandShell [ConfigurationOfCommandShell] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.squeaksource.com/MetacelloRepository ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/MetacelloRepository: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 9 months

1
0
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #1241

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1241/> ------------------------------------------ Started by timer Started by upstream project "fame" build number 215 originally caused by: Started by timer Started by upstream project "graph-et" build number 51 originally caused by: Started by timer Started by upstream project "glamour" build number 337 originally caused by: Started by timer Started by upstream project "gtoolkit" build number 395 originally caused by: Started by timer Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson3529985657416679134.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: Error: Could not resolve: ConfigurationOfCommandShell [ConfigurationOfCommandShell] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.squeaksource.com/MetacelloRepository ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/MetacelloRepository: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mMetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] Array(SequenceableCollection)>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>explicitLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushExplicitLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>explicitLoadPackageSpecs:repositories: MetacelloPackageSpec>>explicitLoadUsing: MetacelloPackageSpec>>loadUsing: in Block: [self explicitLoadUsing: mcLoader] MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>doingLoads: MetacelloPackageSpec>>loadUsing: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: ConfigurationOfCommandShell [ConfigurationOfCommandShell] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.squeaksource.com/MetacelloRepository ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/MetacelloRepository: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 9 months

1
0
0 0

z-ordering PopupView in GLMRoassalPresentation

by Usman Bhatti

Hello, When creating a visualization with Roassal in a Glamour browser, the popup view is shown behind the entity on which popup is invoked. Here is the code to reproduce: | browser | browser := GLMTabulator withStatusbar. browser column: #visu. browser transmit to: #visu; andShow: [ :a | a roassal painting: [:view :number | | popupView inner aView outerElement| popupView := ROView new. aView := view raw. outerElement := (ROElement on: 'Outer'). popupView add: (ROElement new extent: 50@50; model: 'popup')+ (ROBox new color: Color blue). inner := (ROElement sprite) + (ROBox new borderWidth: 1; color: (Color gray: 0.9)); extent: 150@100. outerElement add: inner. inner @ (ROPopupView new view: popupView). aView add: outerElement. ]]. browser openOn: 42. Although the problem does not occur without Glamour: | popupView inner aView outerElement| popupView := ROView new. aView := ROView new. outerElement := (ROElement on: 'Outer'). popupView add: (ROElement new extent: 50@50; model: 'popup')+ (ROBox new color: Color blue). inner := (ROElement sprite) + (ROBox new borderWidth: 1; color: (Color gray: 0.9)); extent: 150@100. outerElement add: inner. inner @ (ROPopupView new view: popupView). aView add: outerElement. aView open Is this a bug or do I need to set some property for my nodes? tx, Usman [image: Inline image 8][image: Inline image 7][image: Inline image 6][image: Inline image 5]

11 years, 9 months

3
3
0 0

Issue 982 in moose-technology: [Metaceller] Doesn't refresh configurations when clicking on refresh

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 982 by damien.c...(a)gmail.com: [Metaceller] Doesn't refresh configurations when clicking on refresh http://code.google.com/p/moose-technology/issues/detail?id=982 In the left pane of Metaceller is a refresh button. If I open Metaceller, load a configuration from monticello, and click this button, I don't see any change in this pane. I have to close Metaceller and open it again. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 9 months

2
2
0 0

Issue 983 in moose-technology: [Metaceller] Doesn't load the dependent configurations

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-GlamorousToolkit New issue 983 by damien.c...(a)gmail.com: [Metaceller] Doesn't load the dependent configurations http://code.google.com/p/moose-technology/issues/detail?id=983 I'm having a look at the ConfigurationOfPierVoyage in Metaceller. When I look at this configuration, I do not see all the transitive dependencies. For example, I see that PierVoyage depends on Pier3, but not that Pier3 depends on Magritte3. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 9 months

1
1
0 0

[Roassal] Z-Ordering for ROPopup

by roberto.minelli＠usi.ch

Hi, I am building a visualization in which nodes are layout'd one on top of the other (e.g., a tree map). Thus while I place the nodes I incrementally increment a variable (i.e., the level) and set their #zIndex accordingly so that are placed in the correct way. I want my nodes to have a popup, thus I am adding @ ROPopup when I construct the ROElement. Unfortunately the ROPopup, even though I assigned a higher zIndex to it, seems not to obey to the z-ordering. Any help? Thanks in advance, R

11 years, 9 months

4
7
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev