Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

mondrian help
by Usman Bhatti 11 Nov '11

11 Nov '11

I am working on this script to see dependencies of seaside and citezen... I would to group the nodes according to their names in Mondrian. Is it possible? Here is my script: view shape rectangle width: [:pack | pack numberOfProviderPackages + 3 *3]; height: [:pack | pack numberOfClientPackages + 6 * 3]; if: [:pack | pack name includesSubString: 'Citezen'] fillColor: Color red; if: [:pack | (pack name includesSubString: 'Seaside') and: [(pack name includesSubString: 'Citezen' ) not]] fillColor: Color lightBlue. view nodes: (model allPackages select: [:pack | ((pack name includesSubString: 'Citezen') or: [pack name includesSubString: 'Seaside']) or: [pack name includesSubString: 'Pier']]). view edgesToAll: #staticProviderPackages. view dominanceTreeLayout.. Like in the figure, I would like to group red nodes on the left and light blue nodes on the right and at the same time keeping dominanceTreeLayout. [image: Screen shot 2011-11-09 at 4.08.18 PM.png] thanx. Usman

3 5

Issue 747 in moose-technology: We should have set methods for all properties
by moose-technology＠googlecode.com 10 Nov '11

10 Nov '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.6 New issue 747 by andreho...(a)gmail.com: We should have set methods for all properties http://code.google.com/p/moose-technology/issues/detail?id=747 All methods annotated with <MSEProperty:type:> must have a set methods. Now, when we export a model to MSE we cannot load them because some properties don't have set methods.

1 5

XML mapping DSL (SimpleXO)
by Steffen Märcker 10 Nov '11

10 Nov '11

Hi, I am currently working on an XML to object mapping library. I came up with an early version for a project, since I had to map weird/complex/poor XML files. I'm in contact with Stephané Ducasse about a planned Pharo port. He suggested to ask here for your opinions and ideas on this DSL/library. SimpleXO consists of two parts, a Smalltalk Builder API that constructs a parser object and a non-Smalltalk syntax meant for external binding configuration. This post is on the API. SimpleXO uses two concepts: types and mappings. A type describes how to construct an object. It is configured with a class, a constructor and mappings. A mapping defines which type a set of nodes is mapped to. The nodes are given by a expression similar to XPath. Short Example: <geo id="1"> <rect> <pos x="2" y="3" /> <width>4</width> <height>5</height> </rect> </geo> "Smalltalk'ish way:" builder := SimpleXOParserBuilder new. (builder defineElement: 'Rect') class: 'Rectangle'; "given as string to postpone resolving" mapPath: ('pos' /@ 'x') toType: 'Int'; mapPath: ('pos' /@ 'y') toType: 'Int'; mapPath: ('width') toType: 'Int'; mapPath: ('height') toType: 'Int'; mapPath: (AnyNodeTest /@ 'id') toType: 'Int'. (builder defineCData: 'Int') class: 'Integer'; constructor: #fromString:. parser := builder buildParser: 'rect'. parser mapNode: xmlNode. "this gives the following object:" (Rectangle new) x: 2; y: 2; width: 4; height: 5. Actually we see two kinds of types: element and cdata. The only difference is that elements are constructed using an unary constructor and cdata with a one-argument message that is sent with the string-value of the current node. Of course, SimpleXO supports id resolving, collecting values and tokenizing attribute values. You can find further information on https://wiki.aleturo.com/alpha/simplexo:start I am really interested in your impressions, questions and ideas so far? Regards, Steffen

3 6

Getting the source code of a FAMIXClass
by Alberto Bacchelli 09 Nov '11

09 Nov '11

Hi, I've parsed a Java system by using Verveine-J (pretty fast :) and imported the resulting MSE file in the Moose Suite 4.6 Development I downloaded from the moose website. Everything went fine. I saw that each non-stub FAMIXClass has a FAMIXFileAnchor that correctly points to the java source code file that contains the class declaration. However, I cannot find the right way to directly access this declaration (even though the FAMIXFileAnchor contains also startLine,startColumn,endLine, and endColumn). I tried to call the method FAMIXFileAnchor>>sourceText, but I only get an empty string. Is there a way to access the source code? Thanks. Cheers, Alberto -- View this message in context: http://moose-dev.97923.n3.nabble.com/Getting-the-source-code-of-a-FAMIXClas… Sent from the moose-dev mailing list archive at Nabble.com.

3 5

Issue 742 in moose-technology: smalltalkClass and compiledMethod extensions should be covered by tests
by moose-technology＠googlecode.com 09 Nov '11

09 Nov '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 742 by usman.bh...(a)gmail.com: smalltalkClass and compiledMethod extensions should be covered by tests http://code.google.com/p/moose-technology/issues/detail?id=742 especially when the mporter semantics is to distinguish or not metaclasses. Right now FamixClass>>smalltalkClass "Returns the associated smalltalk class if it exist in the system." ^ FAMIXNameResolver smalltalkClassFromFamixClassName: self name ifAbsent: [nil] FamixMethod>>compiledMethod "Return the compiled method associated to the receiver or nil" | realClass | realClass := self parentType smalltalkClass. self hasClassScope ifTrue: [realClass := realClass class]. ^ realClass isNil ifFalse: [realClass compiledMethodAt: self name asSymbol] ifTrue: [nil] It is strange that we have to do the test hasClassScope in the compiledMethod method since normally smalltalk should correctly handle it.

1 3

An analysis of the MooseTask hierarchy
by Usman Bhatti 08 Nov '11

08 Nov '11

Hi guys here are some notes we wrote when browsing the MooseTask - It would be good to rename MooseTask should be renamed because it has nothing to do in Moose.t - MooseTask and MooseOperator should be in the same package: Moose-Core since MooseOperator has nothing to do with Smalltalk. - the hierarchy of MooseCompositeImporterTask is really dealing only with Smalltalk importing logic. so we should rename it: SmalltalkCompositeExtractorTask or at least SmalltalkCompositeImporterTaskcolle - MooseImportClassesTask should be renamed SmalltalkImportClassesTask or SmalltalkExtractClassesTask since it only create entity extracted from Smalltalk. ( Importer vs extractor I would like to keep the term importer to the action of populating a model and the action to extract model from source code. In java, c3 we have extractor and in Moose importers and extractors) - I would rename SmalltalkImporter as SmalltalkExtractor like that we have a clear line. - Nobody is referencing PackageDescription? - Now our problem is that we would like to run tasks when a a Smalltalk model is extracted and imported and when a mse file is imported. We should probably introduce the logic of the plugin login somewhere in a superclass and (MSEImporter should be a subclass of MooseTask - not verified if make sense) - I have no clue about the contents of the Moose-GenericImporter. It looks like we stopped in the middle of something (which is probably true). - MooseImportingTask is still Smalltalk specific so I would move to the Moose-SmalltalkImporter. - MooseFileStructureImporter looks really broken but it can be a nice example of a subclass of MooseImporterTask (not MooseExtractorTask) Doru it would be fun to do some pair programming to address these changes. Do you have time this evening?

1 0

An analysis of MooseTask hierarchy
by Usman Bhatti 08 Nov '11

08 Nov '11

1 0

Attributes and Properties
by Usman Bhatti 08 Nov '11

08 Nov '11

I would like to know the difference between an attribute and a property of a FamixEntity. thanx, Usman

1 0

MooseId vs MooseName
by Usman Bhatti 08 Nov '11

08 Nov '11

Hi guys We are adding Author to Moose as an experience to learn how to extend moose. In the past, for a moose entity with a unique name we were using the uniqueName as mooseID What is the status now? For example we would to make sure that author can be retrieved by their name mooseModel entityNamed: 'me' and that we do not have conflict with other Moose entity. Stef

3 8

Is there an update button for moose
by Stéphane Ducasse 08 Nov '11

08 Nov '11

Hi I would like to know how I can get the latest version from a given version. Because I do not want to have to merge back. So how do I get all the latest versions of packages? and does it work? Stef

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev