Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 607 in moose-technology: inFusion should make AnnotationInstanceAttribute>>annotationTypeAttribute point to AnnotationTypeAttribute

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 607 by tudor.gi...(a)gmail.com: inFusion should make AnnotationInstanceAttribute>>annotationTypeAttribute point to AnnotationTypeAttribute http://code.google.com/p/moose-technology/issues/detail?id=607 Currently it points to the declaredType.

14 years

Project moose-on-moose

by Andre Hora

Hello Doru, I saw you are generating a Moose On Moose Report.xml<http://hudson.moosetechnology.org/job/moose-on-moose/lastSuccessfulBuild/ar…>report. Is it SmallLint rules? Is the code (to generate this report) provided by Moose? thanks and regards, -- Andre Hora

14 years

Issue 604 in moose-technology: VerveineJ should export in UTF-8

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 604 by tudor.gi...(a)gmail.com: VerveineJ should export in UTF-8 http://code.google.com/p/moose-technology/issues/detail?id=604 The MSE file format should be always in UTF-8.

14 years

preparing for Moose 4.4

by Tudor Girba

Hi, The list of issues for 4.4 got smaller, but we won't make it with a release today: http://code.google.com/p/moose-technology/issues/list?q=milestone=4.4 I will work on them in the following week, but it would be great to have some help. Especially, it would be cool to have VerveineJ ready for prime time. The good news is that it does not crash and it is super fast. However, there are still some small issues that make it less usable in practice (like setting correct source anchors, exporting all annotations and setting the file format in utf-8). I would also need some help on the SmalltalkImporter issues. Cyrille and Jannik, would you have some time to look into these issues? I will try to finalize Metanool and look into fixing FAMIX queries. The new deadline is in 1 week or so :). Cheers, Doru -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

14 years

Issue 581 in moose-technology: Computing text size

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-High New issue 581 by alexandr...(a)gmail.com: Computing text size http://code.google.com/p/moose-technology/issues/detail?id=581 Execute in a workspace: (UMLClassDiagram render: Collection withAllSubclasses) open There is too much white space

14 years

verveinej out of memory

by Tudor Girba

Hi, I am testing VerveineJ and I am getting "Exception in thread "main" java.lang.OutOfMemoryError: Java heap space". To reproduce: 1. download https://github.com/Silverpeas/Silverpeas-Core/zipball/master 2. run ./verveinej.sh -Xmx2000m PATH_TO_SILVERPEAS Nicolas, is there anything to do to get this working? Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

14 years

Issue 554 in moose-technology: DSM has flags for refactoring

by moose-technology＠googlecode.com

Status: New Owner: jannik.l...(a)gmail.com Labels: Type-Defect Priority-Medium Milestone-4.4 New issue 554 by jannik.l...(a)gmail.com: DSM has flags for refactoring http://code.google.com/p/moose-technology/issues/detail?id=554 some flags in DSM I should verify for 4.4

14 years

Issue 553 in moose-technology: DSM should be split

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: jannik.l...(a)gmail.com Labels: Type-Engineering Priority-Medium Component-DSM Milestone-4.4 New issue 553 by tudor.gi...(a)gmail.com: DSM should be split http://code.google.com/p/moose-technology/issues/detail?id=553 It should be split into generic algorithms (moved to Moose-Algos) and FAMIX specific applications.

14 years

Issue 595 in moose-technology: [Glamour] Transmission>>from: is said to take a port

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 595 by damien.c...(a)gmail.com: [Glamour] Transmission>>from: is said to take a port http://code.google.com/p/moose-technology/issues/detail?id=595 The method GLMTransmission>>from: takes a parameter 'aPort'. However, this method is most of the time used with a pane symbol instead of a port. This is confusing as the Moose book says " For specifying a transmission origin that points to a #selection port of a pane, you simply use from:. " In this case it is clear that the port is #selection and it is the default. The reader is then waiting for an implementation similar to: GLMTransmission>>from: aPaneSymbol ^ self from: aPaneSymbol port: #selection

14 years

FAMIXPackage>>methods and MooseChef

by Tudor Girba

Hi, I am continuing to review MooseChef and I stumbled across the definition of query**Invocations defined in TScopingEntityQueries: TScopingEntityQueries>>queryAllOutgoingInvocations ^ self createOutgoingInvocationQueryResultWith: (self methods flatCollect: [ :m | m outgoingInvocations ]) This depends on #methods. However, in FAMIXPackage, methods only returns the extended methods defined in the package: FAMIXPackage>>methods ^ self privateState cacheAt: #methods ifAbsentPut: [ childNamedEntities select: [ :child | child isKindOf: FAMIXBehaviouralEntity ]] This has a different semantics from the one defined in Namespace: FAMIXNamespace>>methods ^ self privateState cacheAt: #methods ifAbsentPut: [ self classes flatCollect: #methods ] So. I propose that FAMIXPackage>>methods is changed to classExtensionMethods and methods is computed like in Namespace + classExtensionMethods. Anyone else depending on methods with the semantics of classExtensionMethods? Cheers, Doru -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

14 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev