- Moose-dev - INF Mailman

are there more than Fuel and MSE exporting/importing moose models?

by Mariano Martinez Peck

Hi guys. The question is simple, I know that you are using Fuel to import/export moose models. I know there is also a way to do it with MSE. My question is, is there another way already implemented and working or that's all? Thanks! -- Mariano http://marianopeck.wordpress.com

13 years, 8 months

2
1
0 0

text pane in Glamour

by Nicolas Anquetil

I have a text pane in a Glamour browser : browser transmit from: #A; to: #B; andShow: [ :a | a text title: [ :c | c name, ' source']; display: [ :c | c sourceText ] . ]. is it possible to programatically highlight a given line in this text? May be by selecting it? How can it be done? nicolas

13 years, 8 months

3
2
0 0

petit git log paser

by Fabrizio Perin

Hi, I will start to work on a parser to parse git logs. For now i will parer the info generated by "git log --stat". A full diff parser will came later. If you have any suggestion or comment please ping me. Cheers, Fabrizio

13 years, 8 months

4
7
0 0

happy man...

by Alexandre Bergel

Hi ! Yesterday I spent about 30 minutes with a guy from microsoft to generate .mse from C#. We were able to extract the data and generate the mse. I was happy to have a blueprint complexity after such a short amount of time. Usman, we use http://ccimetadata.codeplex.com for extracting the data. I can share the code if you wish. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 8 months

4
21
0 0

Fwd: petit question

by Fabrizio Perin

Hi, I'm not sure how to answer the forwarded email. At list i have an idea but without using PPExpressionParser. Someone has an answer that rely on PPExpressionParser? Cheers, Fabrizio Begin forwarded message: > Hi Fabrizio, > How are you? Its Friday, its me again :D. > I realized some stuff but still don't really get the Expressions. Let me give you an example: > > exp := PPExpressionParser new. > exp term: (($$ asParser trim , #letter asParser star) flatten / ($" asParser trim, $" asParser negate star, $" asParser trim) flatten); > group: [ :g | > g right: '=' asParser trim do: [:a :op :b | {a. op. b.}]. > ]. > > exp parse: '$var = "dings"'. "this is valid code" > exp parse: '"dings" = $var'. "this is invalid code" > > How do i tell the expression parser to make a constrain on one side? Or a better question could be: How do i combine expression parsers to achieve a similar behavior? Do i even have to? Or am I to assume that the programmer just knows the order...? I could do something like: > > group: [ :g | > g right: '=' asParser trim do: [:a :op :b | > { (LeftAssignmentSideExpressionParser new parse: a.) op. (RightAssignmentSideExpressionParser new parse: b.) } > ]. > ]. > > Do you see my Problem? > > Cheers Michael

13 years, 8 months

1
0
0 0

Fwd: looking for a FCA library in Smalltalk

by Stéphane Ducasse

doru do you know if the library of adrian for FCA has been ported to Pharo? Stef Begin forwarded message: > From: Usman Bhatti <usman.bhatti(a)gmail.com> > Date: October 13, 2011 5:28:18 PM GMT+02:00 > To: gabriela.b.arevalo(a)gmail.com > Cc: Stéphane Ducasse <stephane.ducasse(a)inria.fr>, Nicolas Anquetil <nicolas.anquetil(a)inria.fr> > Subject: looking for a FCA library in Smalltalk > > Hello Gabriella, > > I am working with Stephane and Marianne on a paper related to FCA patterns. The idea is to identify a few patterns in FCA lattices that would reduce lattice exploring task to searching and looking at a few of these patterns. We describe the combination of nodes and subgraphs in the lattices as patterns. When identifying patterns, we took care of the following things: > > 1. the patterns should be generic (i.e. not related to a particular context) > 2. the patterns should produce little false-positives (that is the nodes that are not important in lattices should not appear in candidates for evaluation).. > > we presented our paper in wcre 2011 but it got rejected. Now, we are reviewing the paper to present it in CSMR 2012. > > The purpose of the mail is that we are looking for a tool (specifically in Smalltalk) that would automate the process of patterns identification in FCA. So, I am looking for a library in FCA that: > > - extracts program info from smalltalk (if possible) > - calculates lattices based on program info > - permits to do queries on lattices (top, bottom, a concept with objects, attributes, etc.) > - find horizontal decomposition and modules in lattices. > > Would you have a knowledge of such a library? > > If you wish I can send you the paper to have a look at it. There is a tool in Java called Colibri that allows to do some of these queries on lattices: > http://code.google.com/p/colibri-java/ > but its written in Java and I am looking for something in Smalltalk. > > > thanx in advance, > > Usman > > >

13 years, 8 months

3
3
0 0

Moose should load AST-Core-lr.89

by Fabrizio Perin

Hi guys, so by loading the latest AST-Core package 4 errors and 6 failures of PetitSmalltalk-Tests get green. So can we load AST-Core-lr.89 in Moose? or we have to wait that the Pharo-dev image includes that version? If we can include that version in Moose, where should i add it? in ConfigurationOfMoose>>>version44beta1: ? Cheers, Fabrizio

13 years, 8 months

3
2
0 0

Issue 725 in moose-technology: EyeSee Pie Charts

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-EyeSee Milestone-4.6 New issue 725 by andreho...(a)gmail.com: EyeSee Pie Charts http://code.google.com/p/moose-technology/issues/detail?id=725 We should have pie charts in EyeSee.

13 years, 8 months

1
1
0 0

Pie Charts in EyeSee

by Andre Hora

Hello, I worked a bit to implement pie charts in EyeSee. I am developing (slowly..), but for now we can have some charts like the ones attached. regards, -- Andre Hora

13 years, 9 months

5
7
0 0

question about SystemAnnouncement

by Stéphane Ducasse

Hi guys we are cleaning the design of systemAnnouncement (removing the internalAnnouncement). So that after I can work on RPackage again... (agrh). Now a question, do you have an idea of the impact of change on Moose. Because once we change systemAnnouncement (normally the public anonucement stays the same) I will have to update RPackage and this may impact moose. Stef

13 years, 9 months

3
2
0 0

what is the process to get changes into moose?

by Stéphane Ducasse

Hi guys I ask because I published some changes related to the comments of FAMIX Classes and they are not in the latest image. So what is the process because I would like to avoid to lose time and energy there. Stef

13 years, 9 months

2
3
0 0

do we have some scripts for newbie

by Stéphane Ducasse

Hi I was wondering if we have a list of scripts to Load a model Import a model Access entities in a model Navigate Save a model Stef

13 years, 9 months

3
6
0 0

cool tool for visualization

by Stéphane Ducasse

I saw a presentation of an inria team Graphite and their tool is cool (of course we cannot compete) but may be looking at ome of their work or use it could be cool. http://tulip.labri.fr/TulipDrupal/ Stef

13 years, 9 months

3
2
0 0

Issue 724 in moose-technology: <MSEClass:superclass:> should not contain the package name in MSEClass, just the Fame name

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.6 New issue 724 by andreho...(a)gmail.com: <MSEClass:superclass:> should not contain the package name in MSEClass, just the Fame name http://code.google.com/p/moose-technology/issues/detail?id=724 I created concern OnMooseUsagesOfPackagePrefixInMSEClassInMetaAnnotations in OnMoose-Report to test that. 25 problems were found basically in Hismo. Example: HismoClassHistory class>>annotation <MSEClass: #HismoClassHistory super: #HismoAbstractHistory> <package: #Hismo> And the correct pattern should be: HismoClassHistory class>>annotation <MSEClass: #ClassHistory super: #HismoAbstractHistory> <package: #Hismo> So should I change that?

13 years, 9 months

1
2
0 0

Moose Chef

by Júlio Martins

I would like know a little more about Moose Chef. I need to compute a RFC and LCOM metrics and I would know if the Moose Chef can help me on this task. RFC is Rsponse for methods and it give a number of methods that is called in reponse to a I don't know exactly from where to start to compute these metrics. Could you help me? -- View this message in context: http://forum.world.st/Moose-Chef-tp3895442p3895442.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 9 months

2
1
0 0

Mondrian on VW

by Alexandre Bergel

Hi! Today we tried to load the VisualWorks version of Mondrian in VW and we bumped into some problem. For example, there was references to Color, whereas VW uses ColorValue. Maybe we did not load it properly. Anyone remembers what is the status of VW Mondrian? Was it working properly? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 9 months

2
2
0 0

Fwd: Jenkins build is unstable: moose-latest-dev #637

by Tudor Girba

Hi, It looks like there are some 67 test failures in Moose :). They are most likely due to the changes in the annotations, like Fabrizio mentioned. Could someone fix them? :) Cheers, Doru Begin forwarded message: > From: admin(a)moosetechnology.org > Subject: Jenkins build is unstable: moose-latest-dev #637 > Date: 11 October 2011 15:25:21 CEST > To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)gmail.com > > See <http://hudson.moosetechnology.org/job/moose-latest-dev/637/> > > -- www.tudorgirba.com "Speaking louder won't make the point worthier."

13 years, 9 months

2
8
0 0

Issue 723 in moose-technology: <MSEClass:superclass: > should use a symbol to point to the superclass.

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Fame Component-Famix Milestone-4.6 New issue 723 by andreho...(a)gmail.com: <MSEClass:superclass: > should use a symbol to point to the superclass. http://code.google.com/p/moose-technology/issues/detail?id=723 Use of string instead of symbol to denote superclass.

13 years, 9 months

1
7
0 0

Fwd: [gdr.gpl ] Frama-C Nitrogen-20111001

by Stéphane Ducasse

This would be interesting to evaluate how we can use Frama-C to connect c to moose. Stef Begin forwarded message: > From: Julien Signoles <Julien.Signoles(a)cea.fr> > Date: October 10, 2011 4:14:07 PM GMT+02:00 > To: gdr.gpl(a)imag.fr > Subject: [gdr.gpl ] Frama-C Nitrogen-20111001 > > Dear all, > > We are glad to announce a new major release of the static analysis platform Frama-C, namely Nitrogen-20111001. > > ======== > DOWNLOAD > ======== > > You can download the release at http://frama-c.com/download.html . > > For now, there is a source tar-ball distribution without the Jessie > plug-in, but including the WP plug-in. Binary versions will be released as soon as possible. A new version of Why which includes the Jessie plug-in will shortly be released separately by Inria and will be compatible with Frama-C Nitrogen. > > ============ > MAIN CHANGES > ============ > > This new major version includes too many bug fixes and improvements to list here: the detailed list is available at http://frama-c.com/Changelog.html . > > Major improvements benefit: > - Value Analysis plug-in > - PDG plug-in and its derivatives (Slicing, Impact, Scope, Sparecode) > - Aoraï plug-in > - the GUI > - kernel property statuses > > For plug-in developers: this major release changes several Frama-C APIs in an incompatible way. A subset of the plug-in side changes can automatically be applied by using the script bin/carbon2nitrogen.sh of the source distribution. Complex plug-ins should be reviewed for compatibility. > > ====== > ENJOY! > ====== > > Enjoy this release and do not hesitate to report any issue and/or > successes with this version through the usual channels, listed at > http://frama-c.com/support.html . > > Have fun with Frama-C, > Julien Signoles > ------ > Plus d'infos sur le GDR GPL : http://gdr-gpl.cnrs.fr

13 years, 9 months

2
1
0 0

Annotation pattern

by Andre Hora

Hello, What should be the conversion in the pragma #MSEClass:super: in #annotation methods? For now there is no conversion, example: - super with dot and MSEClass without prefix of the meta-model (Famix) FAMIXClass>>annotation <MSEClass: #Class super: 'FAMIX.Type'> - super without dot and MSEClass without prefix of the meta-model (Famix) FAMIXComment>>annotation <MSEClass: #Comment super: #FAMIXSourcedEntity> <package: #FAMIX> - MSEClass with prefix of the meta-model (Hismo) and super without dot HismoAbstractHistory>>annotation <MSEClass: #HismoAbstractHistory super: #FAMIXEntity> I can fix it if you tell me correct pattern. -- Andre Hora

13 years, 9 months

2
2
0 0

Importing from a metacello configuration

by Alexandre Bergel

Hi! With Santiago we are trying to import different versions of a configuration in Moose. The following script does a relatively good job. Some of you may be interested in it. Note that it is specialized for Mondrian, but can be easily adapted for other projects. -=-=-=-=-=-=-=-=-=-= | mooseModel packages task | #('2.10' '2.13' '2.100') do: [:version | | project | project := (ConfigurationOfMondrian project version: version). [ project load. "This is necessary by Moose to properly import" Gofer new url: 'http://www.squeaksource.com/CollectionExtensions'; version: 'CollectionExtensions-TudorGirba.29'; load. packages := (project packages collect: #name) select: [:p | p beginsWith: 'Mondrian']. mooseModel := MooseModel new. task := MooseSqueakClassCategoryImporterTask new. task importerClass: SmalltalkImporter. task importingContext mergeClassAndMetaclass. task model: mooseModel. task runCandidateOperator. task addFromPackagesNamed: packages. task runWithProgress. mooseModel name: 'Mondrian ', version. mooseModel install. ] on: Error do: [ :ex | Transcript show: 'cannot load version ', version, ' ', ex printString. ]. ] -=-=-=-=-=-=-=-=-=-= This way of importing is however not perfect. It installs the software, which is not necessary in principle and can be a showstopper. But at least, it gives some result. Shall I put this script in MooseScripts? If would be cool to have more users of Versionner/MonticelloBrowser, small tools I made to automatically save your packages and give a new version number. Versionner has a commit button, a bit like in SVN. This give some food for evolution analysis. Currently, we cannot really go that far since we do not have explicit versions of what we are building! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 9 months

2
6
0 0

eyesee editor

by Tudor Girba

Hi, The latest Glamour ships with an editor for EyeSee (the same user interface as for Mondrian and Glamour). It is also integrated in Moose. See an example screenshot. Cheers, Doru -- www.tudorgirba.com "Live like you mean it."

13 years, 9 months

4
3
0 0

Issue 715 in moose-technology: VerveineJ does not export source anchors to Enums

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 715 by tu...(a)tudorgirba.com: VerveineJ does not export source anchors to Enums http://code.google.com/p/moose-technology/issues/detail?id=715 FAMIX.Enums should have SourceAnchors attached.

13 years, 9 months

1
1
0 0

Re: Issue 341 in moose-technology: Make the number of entities in table widget customizable

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.6 Comment #10 on issue 341 by tudor.gi...(a)gmail.com: Make the number of entities in table widget customizable http://code.google.com/p/moose-technology/issues/detail?id=341 This is fixed now.

13 years, 9 months

1
1
0 0

Issue 722 in moose-technology: CompositePresentation should be usable as a starting point

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.6 New issue 722 by tudor.gi...(a)gmail.com: CompositePresentation should be usable as a starting point http://code.google.com/p/moose-technology/issues/detail?id=722 We should be able to write something like this: composer := GLMCompositePresentation new. composer tabulator with: [:t | t column: #one. t transmit to: #one; andShow: [:a | a text ]]. composer openOn: 42. In this way, the composer can be instantiated somewhere else.

13 years, 9 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