Hi Jannik,
I would like to add the DSM to the Moose configuration. Could you
please point me to what I should do to load it?
Cheers,
Doru
--
www.tudorgirba.com
"Some battles are better lost than fought."
Hi Moose list:
I'm trying to load Fame for VisualWorks.
I added the bundle MooseLoaderFromSCGStore, and executed the line:
MooseLoaderFromSCGStore new loadLatestDevelopment
But it stops in the following method with ByteArray>>doesNotUnderstand
Store.Package>>developmentPrerequisites
^self properties at: #developmentPrerequisites ifAbsent: [ nil ].
Thanks again!
Hi all,
I found some methods which use CFBlockOperator or other unknown classes
The list is:
- MooseEntity>>uniqueNameMatchesExpression with no sender which use
CFBlockOperator
- HismoClassHistoryGroup>>historiesThatChangedLOCTogether with no
sender which use FormalContext
- HismoHistoryGroup>>coChangeConceptsUsing: with no sender which use
FormalContext.
I think there are other concerned methods.
I have create the issue 140.
Is it possible to remove these methods ?
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi,
A new version of Moose is now available as a one-click bundle.
It would be great if you could check it on Windows and Linux.
Cheers,
Doru
--
www.tudorgirba.com
"Presenting is storytelling."
Dear List,
Did anyone tried whether the version iFusion available on the web
works with the last version of Moose?
I haven't tried, but I am wondering.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
When I load DSM, it takes a lot of time.
Simon and Alex had the same problem.
Is there anything to do to speed up the loading ?
Thanks
Cheers
Jannik
I get this:
This package depends on the following classes:
ClassHistoryGroup
AbstractHistory
ClassHistory
You must resolve these dependencies before you will be able to load
these definitions:
AbstractHistory>>viewSimpleEvolutionMatrix
AbstractHistory>>viewSimpleEvolutionMatrixIn:
ClassHistory>>viewEvolution
ClassHistory>>viewEvolutionOn:
ClassHistoryGroup>>viewEvolutionMatrix
ClassHistoryGroup>>viewEvolutionMatrixOn:
Select Proceed to continue, or close this window to cancel the
operation.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
Is Moose always maintain in VisualWorks ?
DSM is not up to date and I do not know if I do somethink more on the
VisualWorks version.
Cheers
Jannik
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
A new version of Mondrian is available
254:
- the lower pane may now be freely resized.
255:
- following lint hints, MOSugiyamaLayout has now some code in cleanUp
commented
- added MOLayoutTest>>testFlowInLayout
- added MOLayoutTest>>testEllipseShape
- dead code commented in MOFormsShape>>translateBoundsForFigure:
aFigure by: aPoint context: aDictionary
- MOViewRenderer>>decreaseZoom and increaseZoom removed since not used
- Removed MOReadme>>jajaDSM
- minor fix in MOReadme>>exportingAsFile
256:
- Removed MOMatrixShape : This class is empty and is used nowhere
- Updated methods in MOLineshape: apply:bounds:, computeExtentFor:
- Canceled MOLineShape>>heightFor:
257:
- added convenient methods in MOGraphElement (hasInteraction,
isNotSelected)
- clean in MOCanvas>>keyStroke:
- Cleaning in MOEasel (added numberOfPreviousScripts and
removeAPreviousScript)
- clean in the test MOEventHandlerTest
- clean in MOAnnouncer (popupText: popupView:delay:)
- Added delegating methods in MOFormsAdaptor (heightFor: and widthFor:)
- Added convenient methods in MOEvent
- Refactor of MOFormsBuilder>>boundsOf:
- Push up of MONIdentityNormalizer>>command: This is better since
MONAbstractNormalizer defines the variabe command
258:
- better arguments names
- a number of 'self flag: ' have been removed
- 'size = 0' replaced by isEmpty
- a lot of code cleaning
- removed MOCanvas>>mouseLeave: and addCustomMenuItems: aMenu hand:
aHand
- removed MOLabelShape>>apply: anElement bounds: aBounds
- Removed unused variables in MOViewRenderer
259:
-renamed a lot of "aFigure" into "anElement"
- a lot of rewrite
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I am currently cleaning Mondrian by following Lint.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I'm trying to describe how the new Moose Finder based on Glamour works
here. All for those people which are not Glamour-savvy (like me) :)
Especially interesting if you want to use the search field on
MooseGroups or the Evaluator pane
http://code.google.com/p/moose-technology/wiki/MooseFinderUsage
--
Simon
Hi,
I went through the issues again and labeled them with the component in
which they belong:
http://code.google.com/p/moose-technology/issues/list
Cheers,
Doru
--
www.tudorgirba.com
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
I see some cycles between packages in Moose.
So, I propose some fixes:
- in ImportingTask>>initialize, we should not specify importerClass as
SmalltalkImporter. This should be specified in
MooseSqueakClassPackageImporter.
- method MooseAbstractGroup>>allModelHistories should be extended in
Moose-Hismo.
- MooseModel>>lanSampleModel and MooseModel>>historySampleModel in
Moose-ModelTest.
What are your opinion about these potential fixes ?
Cheers
Jannik
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
DEADLINE EXTENSION
Due to multiple requests, the deadline for submissions to the FAMOOSr
workshop at WCRE 2009 has been extended to September 4. Notification
will be sent September 21 and workshop is scheduled on October 14.
After notification, authors will have the opportunity to send a
polished version of their paper for publications in the proceedings.
So do not hesitate to write and send your idea even if it is still a
bit rough!
Simon & Doru
----
CALL FOR CONTRIBUTIONS
FAMOOSr 2009 - 3rd Workshop on FAMIX and Moose in Reengineering
http://moose.unibe.ch/events/famoosr2009
Co-located with WCRE 2009, Lille, France
http://web.soccerlab.polymtl.ca/wcre2009/
We solicit experience reports and position papers (2-4 pages, IEEE
format). Experience reports will be expected to discuss meta-modeling
and software analysis using, but not limited to, FAMIX or Moose.
Position papers will be expected to describe new directions and
challenges for software analysis infrastructures, like FAMIX or Moose.
Papers may address issues along general themes, including but not
limited to:
• Analysis specific meta-models for evolution data, dynamic traces,
bug entries, etc...
• Meta-modeling in reengineering tools
• Visualization techniques.
• Analysis techniques: clustering, data mining, machine learning,
pattern matching, probabilistic approaches, etc...
• Mechanisms for tool composition and rapid tool prototyping.
• Reusability of research: making research results and tools
available to and reusable by the community.
• Persistency and manipulation of models and meta-models.
Submissions are not limited to FAMIX and Moose or to their active
users. We welcome any related ideas.
During the workshop, authors are expected to present their ideas using
a short format, lasting 3 to 7 minutes, in order to spawn vivid
discussions between participants. More information about this format
can be found at:http://moose.unibe.ch/events/famoosr2008/presenterskit
Submissions should be made via Easychair at
http://www.easychair.org/conferences/?conf=famoosr2009
Important dates
• submission: September 4
• notification: September 21
• workshop: October 14
Organizers:
• Simon Denier, INRIA Lille, France
• Tudor Girba, University of Bern, Switzerland
I separated classes that rely on the moose browser into a different
package (CAnalyzerOBCommands). CAnalyzer should now be loaded without
having MooseOBBrowser installed. I am trying it now.
Alexandre
On 27 Aug 2009, at 02:23, Stéphane Ducasse wrote:
> Then?
>
> should we load it?
> how?
>
> Stef
>
> On Aug 27, 2009, at 12:34 AM, Alexandre Bergel wrote:
>
>> Yes, MB* classes are part of Moose-OBBrowser, which is not loaded
>> per default I think. However, I need it until the Glamour version
>> of the browser is usable.
>>
>> Alexandre
>>
>>
>>
>> On 26 Aug 2009, at 08:44, Stéphane Ducasse wrote:
>>
>>> This package depends on the following classes:
>>> MooseBrowser
>>> MBFAMIXNode
>>> MBListModelUpdateCommand
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear All,
When I try to load Moose in a Pharo image, I have a rollback. The
message baseTraitName:classTraitComposition:category: is not defined.
ClassTrait>>asMCDefinition
^MCClassTraitDefinition
baseTraitName: self baseTrait name
classTraitComposition: self traitCompositionString
category: self category
Only MCClassTraitDefinition>>baseTraitName:classTraitComposition: is
For some reason, MCClassTraitDefinition does not know about the
category in which the trait should be defined.
Isn't that odd?
http://code.google.com/p/pharo/issues/detail?id=1095
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Begin forwarded message:
> From: stephane ducasse <stephane.ducasse(a)free.fr>
> Date: August 26, 2009 5:35:17 PM CEDT
> To: Related to the development of Moose and other related tools <moose-dev(a)iam.unibe.ch
> >
> Subject: why mondrian easel redefined app-M to be browse senders?
>
Hi all,
I have just loaded Moose with "MooseLoader load" in a new Pharo-core
image (419).
I see three bugs in Mondrian:
- Mouse interaction does not work (it works in the version 241) (issue
129)
- zoom buttons (+ and -) are static on keyboard --> with a french
keyboard, working buttons are - for "zoom+" and ) for "zoom-" (issue
130)
- when Mondrian is loaded, Morphic package is not updated. Is it
useful ? (issue 131)
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Begin forwarded message:
> From: Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> Date: August 26, 2009 5:24:02 PM CEDT
> To: Related to the development of Moose and other related tools <moose-dev(a)iam.unibe.ch
> >
> Subject: can we inspect an object in the mondrian easel on the
> binding list on the right?
>
Begin forwarded message:
> From: stephane ducasse <stephane.ducasse(a)free.fr>
> Date: August 26, 2009 5:15:03 PM CEDT
> To: Related to the development of Moose and other related tools <moose-dev(a)iam.unibe.ch
> >
> Subject: how can I inspect an entity when selecting a mondrian node?
>
Hi!
Is there any plan for the Dojo of this Sunday? I guess that killing
bugs and polishing the Glamour version of the browser are hot topics.
I added this request for enhancement:
http://code.google.com/p/moose-technology/issues/detail?id=132
I am personally interested in:
- killing bugs in Mondrian
- making the remaining yellow and red tests green
- working on the C importer
- working on the ADA importer
Of course, not everything will be tackled during the same day, but if
some people want to work with me on these task, I will be delighted to.
Lamentably, I will physically remain in Chile, however, facebook's
chat and MSN will help a lot. My facebook ID and MSN ID is godfroy_bern(a)hotmail.com
(do not send email to this email, I won't read).
People interested to work on these topics, please get in touch with me.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi
When I see mondrian flow of bugs I feel like we are really not having
a good process.
Process to test release version
Process to use existing version
So could we get a stable version and a process to use stable code?
May be we could have a released moose package where stable release are
pushed.
Stef