Moose-dev October 2011

moose-dev@list.inf.unibe.ch

29 participants
175 discussions

Issue 717 in moose-technology: Hismo and isStub
by moose-technology＠googlecode.com 03 Oct '11

03 Oct '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hismo Milestone-4.6 New issue 717 by alexandr...(a)gmail.com: Hismo and isStub http://code.google.com/p/moose-technology/issues/detail?id=717 The following test fails. No idea why. ClassB is a stub -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= testStubAndHismo | allModelClasses allHistoryModelClasses mooseSampleData sampleMooseModel hismoHistoryModel | mooseSampleData := MooseSampleData new. sampleMooseModel := (mooseSampleData readMSEString: self sampleMSE) name: #'example'. allModelClasses := sampleMooseModel allModelClasses. self assert: (sampleMooseModel allModelClasses size = 1). self assert: (sampleMooseModel allClasses size = 2). hismoHistoryModel := HismoModelHistory new. hismoHistoryModel addLastVersionForMooseModel: sampleMooseModel. allHistoryModelClasses := hismoHistoryModel allClassHistories select: [:each | each last isStub not]. self assert: allModelClasses size = allHistoryModelClasses size sampleMSE ^ '( (FAMIX.Namespace (id: 1) (name ''aNamespace'')) (FAMIX.Class (id: 2) (name ''ClassA'') (container (ref: 1)) (parentPackage (ref: 201))) (FAMIX.Method (name ''methodA1'') (signature ''methodA1()'') (parentType (ref: 2)) (LOC 2)) (FAMIX.Attribute (name ''attributeA1'') (parentType (ref: 2))) (FAMIX.Class (id: 3) (name ''ClassB'') (container (ref: 1)) (isStub true) (parentPackage (ref: 201))) (FAMIX.Inheritance (subclass (ref: 3)) (superclass (ref: 2))) (FAMIX.Package (id: 201) (name ''aPackage'')) (FAMIX.Package (id: 202) (name ''aPackage'') (parentPackage (ref: 201))) )' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Indeed, it looks like MooseEntity>>isStub is the trouble maker. We need to create an issue. In the meantime you can use: allHistoryModelClasses := hismoHistoryModel allClassHistories select: [:each | each last versionEntity isStub not].

1 1

Issue 718 in moose-technology: Glamour editor should provide a wrapping browser in preview
by moose-technology＠googlecode.com 03 Oct '11

03 Oct '11

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.6 New issue 718 by tudor.gi...(a)gmail.com: Glamour editor should provide a wrapping browser in preview http://code.google.com/p/moose-technology/issues/detail?id=718 Currently, we cannot refer properly to the outside pane from a glamour script in the editor. The reason is because the outer pane is also the pane that receives the script, and thus is not like the default pane that will surround the browser when opened normally. The solution is to wrap the preview in another browser that only forward the entity without the script.

1 1

#mooseName and fully qualified name?
by Alexandre Bergel 03 Oct '11

03 Oct '11

Hi! [context: I am reviving CAnalyzer. My goal is to have it part of Moose for good. ] At the time I worked on it, we had mooseName that return the fully qualified name (e.g., 'file2.hunit.recGlobal'). This was quite handy to lookup value. For example, I could write: mooseModel entityNamed: 'file2.hunit.recGlobal' this will return the definition of recGlobal defined in the file2.h. Apparently, mooseName now returns the name (a String) as a symbol. The method printOn: return the fully qualified name. We had some discussion some times ago, but I kind of forgot what the motivation was for that change. Should't we have a way to fully quality entities? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

ok, more glamour questions
by Esteban Lorenzano 02 Oct '11

02 Oct '11

Hi, I have a browser with this form: buildBrowser | browser | browser := GLMTabulator new title: 'Game Viewer'; row: #galaxy; row: #status size: 25; yourself. browser transmit to: #galaxy; andShow: [ :presenter | presenter morph title: [ :aGame | aGame name ]; display: [ :aGame | (HGUIGalaxyMorph on: aGame galaxy) ]. browser transmit to: #status; from: #galaxy; andShow: [ :presenter | presenter text display: [ :aStar | aStar asString ] ]. ^browser problem is that HGUIGalaxyMorph is a very complex morph (well... it will be ;) )... and it updates some status around the "stars"... and I need to transmit that information to other panes... and I don't know how... so... that's the question: how I trigger an event? is that possible? if not... how it is supposed to do something like that? cheers, Esteban

2 1

Issue 664 in moose-technology: MooseMenu - export GML graph
by moose-technology＠googlecode.com 01 Oct '11

01 Oct '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 664 by jannik.l...(a)gmail.com: MooseMenu - export GML graph http://code.google.com/p/moose-technology/issues/detail?id=664 It should be cool to specify the place of the new file. For now, it is saved just near the image.

2 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2011