Moose-dev February 2011

moose-dev@list.inf.unibe.ch

23 participants
136 discussions

by Stéphane Ducasse

Hi guys I have a question about XMLWriter. I have cards and group of cards. Each class know how to serialize itself. For card I have xmlOn: (one of my methods) that describes the card attributes Card>>xmlOn: aWriter "write a description of the receiver properties as xml uing aWriter, an instance of XMLWriter" aWriter tag name: #card; with: [self xmlInstVarOn: aWriter] Group>>xmlOn: aWriter "write a description of the receiver properties as xml uing aWriter, an instance of XMLWriter" | cardWriter | cardWriter := XMLWriter new. cards do: [:each | each xmlOn: cardWriter]. aWriter tag name: #group; with: [ aWriter tag: #groupName with: self groupName. aWriter tag: #cards with: [ aWriter raw: cardWriter contents]] And I'm not really happy. Because I would like to avoid to use raw: and instantiate a new writer. I would like to know how I could use the write to pass the results of the iteration over cards I wanted to write something like aWriter tag name: #group; with: [ aWriter tag: #groupName with: self groupName. aWriter tag: #cards with: [self cards do: [:each | each xmlOn: aWriter]]

13 years, 2 months

preparing 4.3

by Tudor Girba

Hi, It seems that I am the only one working on 4.3 :). So the plan is to release it in 10 days, on February 20. Please let me know if you are interested in giving a hand. It can be as small as testing or writing some piece of documentation or a blog post. Cheers, Doru -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

13 years, 2 months

[ANN] Moose 4.3

by Tudor Girba

We are happy to announce the Moose Suite version 4.3: *http://moosetechnology.org/download* What is new: - New look and feel - New and flexible API to browse FAMIX models - Extensible Moose Finder - Enhanced Glamour engine to deal with complex actions - Enhanced FAMIX support for Java systems - Enhanced Glamour rendering for Morphic - Enhanced meta browser - Enhanced documentation of Mondrian - Enhanced XMLSupport - Enhanced Smalltalk importer A list of issues addressed in this release can be found at: *http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%20milestone=4.3* Have fun, The Moose Team

13 years, 2 months

Issue 539 in moose-technology: Introduce SourceLanguage as an explicit entity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.3 New issue 539 by tudor.gi...(a)gmail.com: Introduce SourceLanguage as an explicit entity http://code.google.com/p/moose-technology/issues/detail?id=539 Currently, sourceLanguage is modeled with a symbol stored in the Model. This is suboptimal due to at least two things: - the only way to decide strategies of what highlighting to use when displaying text is with an if - there is no possibility of having multiple languages in the same model I would like to introduce FAMIXSourceLanguage as an explicit entity that can be linked to any FAMIXEntity. If an entity does not have a FAMIXEntity, it will fallback to the mooseModel sourceLanguage. The overall MooseModel sourceLanguage will be decided based on the FAMIXSourceLanguage object that has no attached entities.

13 years, 2 months

XML support

by Andre Hora

Hello, I would like to know if it is possible to import XML code to Moose. I saw in the Moose Book ( http://www.themoosebook.org/book/introduction/nutshell) that it is possible. thanks! -- Andre Hora

13 years, 2 months

Issue 524 in moose-technology: Importing from Monticello is not working

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MonticelloImporter New issue 524 by andreho...(a)gmail.com: Importing from Monticello is not working http://code.google.com/p/moose-technology/issues/detail?id=524 The Importing from Monticello is not working in the last version of moose-latest-dev: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… I got this messsage when I try to open a Monticello package with the importer using the Moose Panel: MessageNotUnderstood: MooseMonticelloMethodPopulator>>ensureImplicitVariable:inFamixMethod:

13 years, 2 months

Project version (Moose, DSM, RPackage, Glamour, SmallDude)

by Alexandre Bergel

Hi! I think I reached a first milestone in my quest to have consistent and traceable version in Moose. Version 4.3.3 is now defined. I produced the versions: - DSM 2.1 - RPackage 1.0 - Glamour 2.1 - SmallDude 2.1 I created version 4.3.2. and 4.3.3 of Moose. - 4.3.2 uses the 'default' version of SmallDude. It is not necessary, but it helped me to track down some problem. - 4.3.3 does not depend on any baseline. This is an important step since it means that we should be able to load 4.3.3 of Moose in 10 years from now, and so, whatsoever you will commit in the dependent packages. So, at the next commit of any packages, I will produce version 4.3.4 and so on. The configurations were full of problems (e.g., PetitJava that does not require PetitParser for example). This means that the validator of Metacello seriously needs to be improved. It took me some time to identify and fix all this. I worked with Pharo1.2OneClick image. I haven't tried with Core. Now, the question is, should we create a hudson project to try the stable version? To make my life simpler, I always assign the last version as the stable version. I hope this is ok with you. Comments are welcome Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 2 months

> 2500 tests

by Tudor Girba

Hi, I just wanted to let you know that the amount of tests in Moose Suite just passed the threshold of 2500. The next step is to improve the coverage :). Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

13 years, 2 months

configuration of moose is broken

by Tudor Girba

Hi, ConfigurationOfMoose is broken. I tried to introduce ConfigurationOfFame and somehow all the missing requirements are now exploding and I cannot load it anymore. It looks like it will take some hours of work. Please do not touch these configurations for now. I will get back with another status report later today. Cheers, Doru -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

13 years, 2 months

Issue 508 in moose-technology: Fix the random Fame tests

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Fame Milestone-4.3 New issue 508 by tudor.gi...(a)gmail.com: Fix the random Fame tests http://code.google.com/p/moose-technology/issues/detail?id=508 These tests randomly crash: Fame.Tests.FMSingleEdgeStrategyTest.testMarkBlue Fame.Tests.FMSingleEdgeStrategyTest.testMarkRed Fame.Tests.FMSingleEdgeStrategyTest.testPropagationGraph Fame.Tests.FMSingleEdgeStrategyTest.testSetupGraph I have no idea why, but on the other hand it seems that they do not test something that we really use.

13 years, 2 months

← Newer
1
...
4
5
6
7
8
9
10
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2011