- Moose-dev - INF Mailman

Issue 980 in moose-technology: Integrate GraphET in Glamour

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 980 by tu...(a)tudorgirba.com: Integrate GraphET in Glamour http://code.google.com/p/moose-technology/issues/detail?id=980 Just what it says -- 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, 10 months

1
1
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1064

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1064/>

11 years, 10 months

1
1
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1059

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1059/>

11 years, 10 months

1
1
0 0

ROGridLayout versus ROCellLayout semantics

by Ben Coman

11 years, 10 months

2
1
0 0

The "Moldable Debugger" Framework

by Andrei Vasile Chis

Hi, I'd like to announce the first version of the Moldable Debugger. It is a framework for creating and working with domain specific debuggers. It's integrated into Moose and it currently comes with three debuggers: one for announcements, one for PetitParser and one for Glamour. More information can be found here: * http://scg.unibe.ch/research/moldabledebugger* A video introducing the framework is here: *https://vimeo.com/73980431* (more are on the way) Cheers, Andrei

11 years, 10 months

3
2
0 0

Issue 979 in moose-technology: Default window sizes for large screens

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 979 by benjamin...(a)gmail.com: Default window sizes for large screens http://code.google.com/p/moose-technology/issues/detail?id=979 The following should probably be pushed upstream for Pharo 3.0, but I thought it best to report here in case it is feasible to include in Moose 4.8. Let me know what you think and if needed I can submit a changeset or slice (what is the preferred method for submissions for Moose) I've got a 24 inch screen that I have been using with Moose-4.8-dev for a couple of weeks. I am finding it annoying that the Glamorous Inspector and Glamorous Debugger open to maximum full screen size. 1. For the Standard Debugger, I don't agree with making the default size bigger for bigger screens. I think the extra screen space is useful for inspectors and observing the application. Indeed, the debugger width should match the width of the System Browser, since that is the basis for the formatting of code. Matching these helps give a consistent UI feel for users. For Moose4.8/Pharo2.0 we have... NautilusWindow>>initialExtent ^ 850@600 Actually, perhaps that shouldn't be hard coded and instead be... NautilusWindow>>initialExtent ^ RealEstateAgent standardWindowExtent then for Debugger we could have something similar to this... Debugger>>initialExtent dependents size < 9 ifTrue: [^ super initialExtent]. "Pre debug window" RealEstateAgent standardWindowExtent y < 400 "a tiny screen" ifTrue: [^ super initialExtent]. ^ [ RealEstateAgent standardWindowExtent. ] on: Error do: [800@600] 2. For Glamourous Inspector I understand defaulting to maximum width is useful, but its overkill to default to the full height of the screen. So you could have... GLMMorphicRender>>open: aRenderable window := GLMMorphicWindowRenderer render: aRenderable from: self. ^ window openInWorld "removed 'maximize' from here" GTInspector>>initialExtent ^ RealEstateAgent fullscreenWindowExtent x @ RealEstateAgent standardWindowExtent y which requires also... RealEstateAgent class >> fullscreenWindowExtent ^ self maximumUsableArea insetBy: self fullscreenMargin. and... RealEstateAgent class >> fullscreenMargin ^ FullscreenMargin ifNil: [FullscreenMargin := 25] The last was copied from SystemWindow class >> fullScreenMargin which as an option can then be... SystemWindow class >> fullScreenMagin ^ RealEstateAgent fullscreenMargin 3. Glamorous Debbugger needs a bit more vertical height, so perhaps... GTDebugger >> initialExtent ^ RealEstateAgent fullscreenWindowExtent x @ RealEstateAgent fullscreenWindowExtent y * 2 // 3 -- 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, 10 months

1
2
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1049

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1049/>

11 years, 10 months

1
2
0 0

Re: FAMIXClass does not understand parameterizedTypes

by Stephan Eggermont

Hi Fabrizio, We made quite some FAMIX changes recently. All test were green, but It can be a test coverage problem. In the latest moose I only have FAMIXParameterizableClass>>parameterizedTypes <MSEProperty: #parameterizedTypes type: #FAMIXParameterizedType opposite: #parameterizableClass> <multivalued> <derived> ^ parameterizedTypes Do you have a sample MSE file for me exhibiting the problem? Stephan

11 years, 10 months

3
4
0 0

graph-et is integrated in glamour

by Tudor Girba

Hi, Glamour now offers an integration of Graph-ET. In the latest Moose image you can do: GLMCompositePresentation new with: [ :c | c graphET chart: [:chart :interval | (chart lineDiagram) models: interval; y: [ :x | x*x ] ] ]; openOn: (1 to: 10) It requires some more polishing, but it works. Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 10 months

2
1
0 0

Graph-ET Screencast

by Daniel Aviv Notario

I made a screencast of Graph-ET :-) It is my GSoC project and will be presented on ESUG this year. http://www.youtube.com/watch?v=PkKNALQHa88 Any comments or suggestions to this mail.Enjoy! - Daniel

11 years, 10 months

6
7
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1037

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1037/>

11 years, 10 months

1
1
0 0

about FAMIX-AST

by Stéphane Ducasse

Hi just a short question does FAMIX-AST forces to have the AST node subclass of a Moose entity what is the independence of the tree? can we reuse him outside of famix and moose? Stef

11 years, 10 months

2
1
0 0

FAMIXClass does not understand parameterizedTypes

by Fabrizio Perin

Hi, I just generated an mse with inFamix and I got a MNU while importing the file into the latest Moose. Is there a newer release of inFamix I should download? Is it a know problem? Thanks, Fabrizio

11 years, 10 months

1
0
0 0

[ANN:] FamixDiff and OrionMerge

by Anne Etien

Hi, If you have to compare two MooseModels, we got tools for you. We created the ConfigurationOf FamixDiff and OrionMerge. - FamixDiff enables to do a diff between two MooseModels (or one OrionModel and a MooseModel). The result is a set of changes between the two models. - OrionMerge takes this set of changes and creates a versioned OrionModel by applying the Orion action associated to each change. The result is thus an OrionModel corresponding to the target model of the diff, but taking less space of memory since its benefits from the way of Orion to manage model (between two versions, only the modified entities are stored. A clever system enables to access each entity whatever, it has been modified or not). More information about Orion can be found there http://www.moosetechnology.org/tools/orion I hope it is understandable. So if you need to use them, please don't hesitate. Anne

11 years, 10 months

2
1
0 0

Re: Change in FAME

by Stephan Eggermont

Nicolas wrote: >did you run the tests before? >I believe I saw some of them fail in the past ... ? Uhm, we broke the build from 981 to 984, but I'm not aware of earlier problems. Stephan

11 years, 10 months

3
2
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1028

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1028/>

11 years, 10 months

1
1
0 0

How to get vertical labels with Roassal?

by MartinW

Hi, i could not find a way to get vertical labels in a Roassal visualization. Is there a way? Or a general way to rotate elements? See attached image. I also asked this on Stackoverflow (http://stackoverflow.com/questions/18416989/how-to-get-vertical-labels-with…), but as there was no answer i repost it here . <http://forum.world.st/file/n4705387/vertical_labels.png> M. -- View this message in context: http://forum.world.st/How-to-get-vertical-labels-with-Roassal-tp4705387.html Sent from the Moose mailing list archive at Nabble.com.

11 years, 10 months

5
16
0 0

did the ada parser ever worked?

by Stéphane Ducasse

Hi doru i'm trying to get the parsers written by moser to work. I cannot get the red executed (VW mess Sunittoo vs Sunit argggggghhhhhh) I cannot get the parsers regenerated in VW. So I'm trying to find a fix point. stef

11 years, 10 months

2
2
0 0

FAMIX

by Diego Lont

Hi all, We (Stephan and myself) decided to add a Delphi unit to the FAMIX hierarchy in the Famix-Delphi package, since this is both a package and a namespace. But here we ran into trouble: we can inherit from package, from namespace, or from a scoping entity, but in all cases the method allPackages and allNamespaces do not return the desired value. Also some derived functionality, like the code browser, does not function properly, since it uses namespaces to browse the code. So we propose the following changes: 1) allPackages and allNamespaces should return "allWithSubTypesOf: " instead of withAll: 2) The message "allWithSubTypesOf: aSmalltalkClass ofGroupClass: aGroupSmalltalkClass" should iterate over a new method call "withMooseSubclasses" instead of "withAllSubclasses" 3) Default return value of withMooseSubclasses is withAllSubclasses, except when a class registers itself as a Moose subclass, indicating it is of the "Moose type" of the class it registers to. This allows us to create a "merged" type of package and namespace for Delphi and still allowing for the codeBrowser to function properly. What do you think about this change. I implemented it in my image, and it seems to work fine. Cheers, Diego

11 years, 10 months

1
0
0 0

Roassal - Mouse Enter and leave

by Usman Bhatti

Hello, Mouse Enter and Leave in Roassal is not working so well. Dynamic edges are removed sometimes but sometimes they are not. Can you please have a look? tx, Usman

11 years, 10 months

2
2
0 0

[ANN]Moose On Web Release II

by Vincent Blondeau

Dear Moose Community, My internship ends today in the Rmod team. So I share with you the latest improvements I've made on Moose On Web. This application is in two parts: - the server part on a Moose Image is querying the moose model through a REST API based on Zinc-REST. You can access the model but also import our own models through it. Download at : http://smalltalkhub.com/#!/~VincentBlondeau/MooseOnWeb - the client part is using the server part and display the moose data. It's based on Amber, a smalltalk to JavaScript compiler. Download at : https://github.com/VincentBlondeau/amber-MooseOnWeb. The live demo is here : http://37.139.2.203/client The new features: - Upload MSE files - Model deletion - No 'noname' anymore - Useless buttons deleted - sourceLanguage bug resoved - latest amber version - New querying grammar : Some examples : - http://37.139.2.203/API/entities/1?action=allClasses!(name,fanIn) : get on each classes of the model of id 1 the name and the fanIn - http://37.139.2.203/API/entities/1?action=allClasses;size :get the number of classes of the model of id 1 - http://37.139.2.203/API/entities/1?action=allClasses*allPackages : get all the classes and the packages of the model of id 1 Thanks for your feedback ! Vincent

11 years, 10 months

4
3
0 0

Issue 976 in moose-technology: MSE import should be faster

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Fame Component-MooseCore Milestone-4.8 New issue 976 by tu...(a)tudorgirba.com: MSE import should be faster http://code.google.com/p/moose-technology/issues/detail?id=976 FROM Stephan Eggermont: Do I understand correctly that 36% of the time here is spend updating the progress bar? Reading a JHotDraw7 mse. | model stream | stream := UITheme builder fileOpen: 'Import model from MSE file' extensions: #('mse'). stream isNil ifFalse: [ "name without extension" MessageTally spyOn: [ model := MooseModel new. model importFromMSEStream: stream. stream close ]. model size > 0 ifTrue: [ model install. ]] **Tree** -------------------------------- Process: (40s) Morphic UI process: nil -------------------------------- 83.1% {26938ms} MooseModel class>>importFrom: 83.1% {26938ms} MooseModel class>>importFrom:withMetamodel: 83.1% {26932ms} MSEImporter(FMImporter)>>run 83.0% {26901ms} FMMSEParser>>run 83.0% {26897ms} FMMSEParser>>basicRun 83.0% {26897ms} FMMSEParser>>Document 82.1% {26615ms} FMMSEParser>>Element 38.4% {12451ms} FMMSEParser>>Attribute |19.9% {6449ms} MSEImporter(FMImporter)>>endAttribute: | |19.8% {6428ms} FMFutureElement>>endAttribute: | | 19.8% {6409ms} FMFutureAttribute>>endAttribute: | | 17.8% {5780ms} FMFutureAttribute>>maybeEnd | | |11.1% {3590ms} FM3MetaDescription>>attributeNamed:ifAbsent: | | | |7.0% {2271ms} FM3MetaDescription>>attributeNamed:ifAbsent: | | | | |3.3% {1072ms} FM3MetaDescription>>attributeNamed:ifAbsent: | | | | | |2.5% {799ms} FM3MetaDescription>>attributeNamed:ifAbsent: | | | | |1.7% {537ms} ByteString(String)>>= | | | | | |1.6% {509ms} primitives | | | | |1.6% {508ms} FMMultivalueLink(Collection)>>detect:ifNone: | | | | | 1.5% {480ms} FMMultivalueLink>>do: | | | | | 1.4% {467ms} OrderedCollection>>do: | | | |1.9% {610ms} FMMultivalueLink(Collection)>>detect:ifNone: | | | | |1.6% {508ms} FMMultivalueLink>>do: | | | | | 1.4% {459ms} OrderedCollection>>do: | | | |1.5% {478ms} ByteString(String)>>= | | | | 1.4% {469ms} primitives | | |5.9% {1912ms} FM3PropertyDescription>>setOn:values: | | | 5.2% {1692ms} FAMIXParameterType(Object)>>mmSetProperty:to: | | | 5.1% {1653ms} FM3PropertyDescription>>setOn:rawValue: | | | 1.6% {526ms} ByteSymbol(Symbol)>>asMutator | | | 1.5% {491ms} ByteString(String)>>asSymbol | | | 1.2% {379ms} Symbol class>>intern: | | | 1.2% {379ms} Symbol class>>lookup: | | | 1.2% {377ms} WeakSet>>like: | | | 1.2% {373ms} WeakSet>>scanFor: | | 1.8% {575ms} PhexMatcher>>= |8.8% {2844ms} FMMSEParser>>Value | |4.2% {1365ms} FMMSEParser>>Primitive | | |3.1% {1017ms} FMMSEParser>>Number | |3.5% {1138ms} FMMSEParser>>Reference | | 1.8% {583ms} FMMSEParser>>Identifier |4.5% {1463ms} FMMSEParser>>tNAME | |1.9% {610ms} Character>>isAlphaNumeric | | |1.5% {479ms} Character>>isLetter | |1.0% {340ms} FMMSEParser>>next |2.9% {948ms} MSEImporter(FMImporter)>>beginAttribute: | 2.8% {898ms} FMFutureElement>>beginAttribute: | 2.1% {674ms} PhexMatcher>>beTrue | 2.0% {663ms} PhexMatcher>>true | 1.7% {541ms} PhexMatcher>>expectedUnknownMessageToReturn: 36.5% {11837ms} FMMSEParser>>increment |36.5% {11837ms} Job>>value: | 36.5% {11819ms} Job>>currentValue: | 36.5% {11819ms} Job>>announceChange | 36.5% {11814ms} Job>>announce: | 36.4% {11789ms} SystemAnnouncer>>announce: | 36.4% {11789ms} SystemAnnouncer(Announcer)>>announce: | 36.3% {11775ms} SubscriptionRegistry>>deliver: | 22.1% {7148ms} SubscriptionRegistry>>subscriptionsHandling: | |10.3% {3326ms} WeakAnnouncementSubscription>>handles: | | |8.7% {2823ms} MethodRemoved class(Announcement class)>>handles: | | | |8.4% {2707ms} JobChange class(Behavior)>>inheritsFrom: | | |1.6% {503ms} primitives | |5.3% {1714ms} primitives | |4.8% {1558ms} IdentitySet(Set)>>do: | |1.3% {420ms} AnnouncementSubscription>>handles: | | 1.1% {349ms} AnnouncementSet>>handles: | 13.7% {4450ms} SubscriptionRegistry>>deliver:to: | 13.6% {4403ms} SubscriptionRegistry>>deliver:to:startingAt: | 13.5% {4364ms} AnnouncementSubscription>>deliver: | 13.4% {4335ms} MessageSend>>cull:cull: | 12.8% {4132ms} MessageSend>>cull: | 12.4% {4032ms} MessageSend>>value: | 12.4% {4030ms} MessageSend>>valueWithArguments: | 12.0% {3902ms} SystemProgressMorph class>>updateJob: | 8.5% {2754ms} JobProgressMorph>>progress: | |7.2% {2333ms} JobProgressBarMorph>>progress: | | 7.0% {2253ms} ProgressBarMorph>>value: | | 7.0% {2253ms} ProgressBarMorph(Morph)>>changed | | 6.9% {2251ms} ProgressBarMorph(Morph)>>invalidRect: | | 6.9% {2251ms} ProgressBarMorph(Morph)>>invalidRect:from: | | 6.9% {2246ms} JobProgressBarMorph(Morph)>>invalidRect:from: | | 6.9% {2222ms} JobProgressMorph(Morph)>>invalidRect:from: | | 6.8% {2214ms} SystemProgressMorph(Morph)>>invalidRect:from: | | 6.8% {2210ms} PasteUpMorph>>invalidRect:from: | | 6.3% {2025ms} Rectangle>>intersect:ifNone: | | 3.3% {1081ms} Rectangle>>intersects: | | | 1.9% {620ms} SmallInteger>><= | | | | 1.7% {552ms} SmallInteger(Integer)>><= | | | | 1.7% {552ms} Float>>adaptToInteger:andCompare: | | | | 1.7% {538ms} Float>>asTrueFraction | | | 1.4% {450ms} SmallInteger>>>= | | | 1.1% {359ms} SmallInteger(Integer)>>>= | | | 1.1% {359ms} Float>>adaptToInteger:andCompare: | | | 1.1% {348ms} Float>>asTrueFraction | | 1.5% {471ms} SmallInteger>>> | | | 1.2% {390ms} SmallInteger(Integer)>>> | | | 1.2% {390ms} Float>>adaptToInteger:andCompare: | | | 1.2% {388ms} Float>>asTrueFraction | | 1.2% {393ms} SmallInteger>>< | | 1.0% {327ms} SmallInteger(Integer)>>< | | 1.0% {325ms} Float>>adaptToInteger:andCompare: | 3.0% {961ms} JobProgressMorph>>label: | 2.8% {914ms} JobProgressMorph(Object)>>changed: | 2.5% {811ms} SystemProgressMorph>>update: | 2.1% {677ms} SystemProgressMorph>>updateWidth | 2.1% {677ms} SystemProgressMorph>>resize | 1.7% {562ms} SystemProgressMorph>>maxBarWidth | 1.4% {458ms} JobProgressMorph(Morph)>>minExtent 2.7% {891ms} MSEImporter(FMImporter)>>beginElement: |2.6% {836ms} FMFutureElement class>>with:name: | 2.6% {829ms} FMFutureElement>>with:name: | 2.1% {668ms} FM3MetaDescription>>createInstance | 2.0% {638ms} FAMIXNamespace class(Behavior)>>new 2.4% {775ms} FMMSEParser>>tFULLNAME |1.3% {408ms} Character>>isAlphaNumeric | 1.0% {335ms} Character>>isLetter 1.1% {349ms} FMMSEParser>>Serial **Leaves** 8.9% {2897ms} JobChange class(Behavior)>>inheritsFrom: 5.3% {1714ms} SubscriptionRegistry>>subscriptionsHandling: 5.1% {1649ms} IdentitySet(Set)>>do: 4.6% {1476ms} ByteString(String)>>= 4.4% {1423ms} OrderedCollection>>do: 2.2% {700ms} Array(SequenceableCollection)>>at:ifAbsent: 2.0% {637ms} FMMSEParser>>tOPEN 1.8% {598ms} SmallInteger(Number)>>negative 1.8% {582ms} UndefinedObject(ProtoObject)>>~~ 1.8% {582ms} FAMIXParameterizedType(Object)>>= 1.6% {522ms} SmallInteger>>bitShift: 1.6% {503ms} WeakAnnouncementSubscription>>handles: 1.2% {395ms} MultiByteFileStream(StandardFileStream)>>basicNext 1.2% {388ms} WriteStream>>nextPut: 1.1% {372ms} FMMSEParser>>tWHITESPACE 1.0% {339ms} WriteStream>>reset 1.0% {336ms} Unicode class>>isLetter: **Memory** old +39,936,212 bytes young -1,252,716 bytes used +38,683,496 bytes free +1,684,040 bytes **GCs** full 2 totalling 1,398ms (4.0% uptime), avg 699.0ms incr 1844 totalling 3,883ms (12.0% uptime), avg 2.0ms tenures 737 (avg 2 GCs/tenure) root table 0 overflows -- 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, 10 months

1
2
0 0

loading mse should not block the ui

by Tudor Girba

Hi, I committed a little enhancement to the load MSE menu action: it no longer blocks the ui. Thus, even if you load a larger MSE file, you can still use the user interface. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 10 months

1
0
0 0

Issue 978 in moose-technology: Loading MSE should not block the UI

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.8 New issue 978 by tu...(a)tudorgirba.com: Loading MSE should not block the UI http://code.google.com/p/moose-technology/issues/detail?id=978 Right now, choosing to load from MSE blocks the UI. A better solution would be to load the MSE in parallel. The implementation should be in MPImportMSECommand. -- 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, 10 months

1
1
0 0

Smacc question

by Stéphane Ducasse

Hi thierry I imported the generated parsers (a student did a while ago on VW using Smacc). The generated parser parse apparently the tests. Now when I regenerate the parser with Pharo I cannot get the Smacc compuling the parser. I get a SmaCCParserError: Token not expected do you have any idea what would not be supported in the Pharo/Squeak version # # Expression Parser #============================================= goal: expression* ; expression: relation ( ( and | and then | or | or else | xor ) relation )*; relation: simple_expression sndPart?; sndPart: relational_operator simple_expression | ( not )? ( in range | in type_mark); simple_expression: (unary_adding_operator)? term (binary_adding_operator term)*; term: factor (multiplying_operator factor)*; factor: primary ( ** primary)? | abs primary | not primary; #<identifier> instead of name primary: <numeric_lit> | null | <string_lit> | <number> | <identifier> | <identifier> '' <identifier> | function_call | ( expression ) ; #simplified binary_adding_operator: + | - | & ; unary_adding_operator: + | - ; multiplying_operator: * | / | mod | rem ; relational_operator: = | /= | < | <= | > | >= ; #============================================================================= function_call: <identifier> ''identifier'' function_arguments ''args'' { ADFunctionCall withElements: args withName: identifier } ; function_arguments: ( expression ( , expression)* ) ; #==== Declarations =========================================================== discrete_range: range | subtype_indication; #discrete_? subtype_indication: type_mark (constraint)? ; type_mark: type; constraint: range_constraint; range_constraint: range range; range: range_attribute | (simple_expression .. simple_expression); range_attribute: <identifier> '' range ; #cf. 4.1.4 #==== Names ================================================================== name: simple_name | <char_lit> | indexed_component | slice | selected_component | attribute; #operator_symbol prefix: name | function_call; simple_name: <identifier>; indexed_component: prefix ( expression ( , expression )* ) ; slice: prefix ( discrete_range ) ; selected_component: prefix . selector; selector: simple_name | <char_lit> | all ; #operator_symbol attribute: prefix '' attribute_designator; attribute_designator: simple_name ( ( <universal_static_expression> ) )? ; #==== Types: appendix c: package STANDARD plus more ========================================================= type: BOOLEAN | REAL | INTEGER | FLOAT | CHARACTER | DURATION | STRING | RAINBOW ; '

11 years, 10 months

1
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev