Moose-dev December 2011

moose-dev@list.inf.unibe.ch

32 participants
167 discussions

Issue 503 in moose-technology: Abstract classes and Hapao

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: vhane...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Spy New issue 503 by alexandr...(a)gmail.com: Abstract classes and Hapao http://code.google.com/p/moose-technology/issues/detail?id=503 Gaëtan le Brun suggested to remove abstract classes before running the test in Hapao. This makes sense

12 years, 6 months

Issue 601 in moose-technology: Covered methods and tests

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hapao New issue 601 by alexandr...(a)gmail.com: Covered methods and tests http://code.google.com/p/moose-technology/issues/detail?id=601 It would be good to see what are the tests that _indirectly_ tests a methods. Thanks Laurent & Patrick

12 years, 6 months

Reviewing Fuel export/import utility

by Martin Dias

Hello, I'm looking to improve current implementation, and maybe you can help me. The current procedure is based in a custom serialization of each MooseElement. It's inspired on MSE, I describe this with the following pseudo-code: serialize: aMooseElement (MooseModel meta descriptionOf: aMooseElement class) allAttributes do: [ :anAttribute | | values | values := anAttribute getFrom: aMooseElement. (self shouldIgnore: anAttribute withAll: values) ifFalse: [ self serialize: anAttribute withAll: values ] ]. where: shouldIgnore: anAttribute withAll: values ^ values isEmpty or: [ anAttribute isDerived or: [ anAttribute type == FM3MetaDescription boolean and: [ values size == 1 and: [ values first == false ]]]] The advantage of serializing the MooseElements in this way (and not just as a normal object) is to avoid storing unnecessary stuff that aMooseElement references. It's a disadvantage using FM3PropertyDescription>>getFrom: (and then to import, FM3PropertyDescription>>setOn:values:) which ends sending #perform: of the corresponding accessor selector. It'd be better to use #instVarAt: (and #instVarAt:put:) as Fuel normally does. I hope I've been clear enough to explain up to this point. Now my question: Do you think Fuel can do something on each MooseElement like - clean up some unnecessary references - declare some instance variables as transient - if it's not good idea to modify the elements, create a method like MooseElement>>copyWithoutDerivedValues, and so actually serialize such copy instead of the original element - any other ??? and thus, serialize the MooseElements as normal Fuel objects, removing the custom procedure. I'll be happy to receive some help from Moose and Fame experts! Thanks in advance. Martín

12 years, 7 months

Issue 509 in moose-technology: Modularization Quality Metric

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Famix New issue 509 by andreho...(a)gmail.com: Modularization Quality Metric http://code.google.com/p/moose-technology/issues/detail?id=509 We implemented the Bunch metrics of coupling and cohesion as quality metrics for existing packages (FAMIXPackage) and namespaces (FAMIXNamespace). Now the idea is to implement the Modularization Quality Metric as a quality metric for existing group of packages (FAMIXPackageGroup) and namespaces (FAMIXNamespaceGroup). Pointer to the papers that propose the metrics: Using Automatic Clustering to Produce High-Level System Organizations of Source Code (http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=693283) Bunch: A Clustering Tool for the Recovery and Maintenance of Software System Structures (http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=792498)

12 years, 7 months

Issue 767 in moose-technology: Book: presentation names are confusing

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 767 by sean.p.d...(a)gmail.com: Book: presentation names are confusing http://code.google.com/p/moose-technology/issues/detail?id=767 For example, on http://www.themoosebook.org/book/internals/glamour/presentations/action-list ActionListPresentation is referenced, but the class name is GLMActionListPresentation. So, when I pasted it into a workspace, it was highlighted red as an unrecognized class. I think it'd be clearer to either use full presentation class names or spaces between camel case (e.g. "Action List Presentation"). The same is true for some of the other presentations e.g. DiffPresentation

12 years, 7 months

Issue 644 in moose-technology: A fly by help to show each time the source code of an entity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 644 by cy.delau...(a)gmail.com: A fly by help to show each time the source code of an entity http://code.google.com/p/moose-technology/issues/detail?id=644 Maybe it would be interesting when navigating in moose, to always have a fly by help that show the source code of an element

12 years, 7 months

Issue 582 in moose-technology: Watcher support in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 582 by tudor.gi...(a)gmail.com: Watcher support in Glamour http://code.google.com/p/moose-technology/issues/detail?id=582 Like we now have a statusbar, we should also have a detailed preview shown in a floating Watcher window. The behavior would be similar to Quick Look on Mac.

12 years, 7 months

Issue 763 in moose-technology: VerveineJ generates wrong paths in source anchors when there is a . in the root folder

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.6 New issue 763 by tudor.gi...(a)gmail.com: VerveineJ generates wrong paths in source anchors when there is a . in the root folder http://code.google.com/p/moose-technology/issues/detail?id=763 Do this: - download: http://sourceforge.net/projects/jfreechart/files/latest/download - go to: jfreechart-1.0.14 - execute: /PATH_TO_verveine.extractor.java/verveinej.sh -Xmx2000m -- -autocp . . The fileNames all start with "0.14/./" instead of "./"

12 years, 8 months

Issue 721 in moose-technology: VerveineJ should mark constructors

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 721 by tu...(a)tudorgirba.com: VerveineJ should mark constructors http://code.google.com/p/moose-technology/issues/detail?id=721 Constructors should be marked with isConstructor.

12 years, 8 months

Re: Issue 602 in moose-technology: Hapao should provide a legend in every window

by moose-technology＠googlecode.com

Updates: Summary: Hapao should provide a legend in every window Comment #3 on issue 602 by tudor.gi...(a)gmail.com: Hapao should provide a legend in every window http://code.google.com/p/moose-technology/issues/detail?id=602 Then let's name the issue for what it should do.

12 years, 9 months

← Newer
1
2
3
4
5
6
7
8
9
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2011