Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Tool to export Moose packages list to freeze a version
by Guillaume Larcheveque 14 Aug '12

14 Aug '12

Today we created a tool with stephane: I'm a kind of loader that know how to save and load list of packages. First when you have a configuration of packages that you want to version use: (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) publishNewVersion it will create a new method scriptXXX on the MooseConfigurationRepository You can then version this class in the package containing the Reloader class. In another image once you load this new version you can reload the configuration you save using the method reload: aNumber and it will load all the packages you previously specified. Under the cover, we need a way to know which packages to save and where to load them. Here is how this information is specified right now, it can be modified using accessors. defaultSavedPackagesPatternNames ^ #(#('Moose-Tests-Algos-InformationRetrieval*' ' http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' ' http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' ' http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' ' http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' ' http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' ' http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' ' http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' ' http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' ' http://www.squeaksource ......) Currently, it kills squeaksource but we will retry with a wait between each package and it should works. This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main -- *Guillaume Larcheveque*

4 8

MSE 3.0 to 2.1 Converter?
by Torben Knerr 14 Aug '12

14 Aug '12

Hi everybody, last question for today :-) Is there a converter which converts from MSE 3.0 to 2.1 format? I'm obviously trying to visualize some Java code with Code City. The MSE was created using verveinej. I know that the inFamix paid version can produce MSE 2.1 output, but if somehow possible I would prefer an open source / non-paid solution. Maybe, is there an older version of verveinej available which would produce MSE 2.1? Or was verveinej producing MSE 3.0 from the beginning? Thanks a lot and best regards, Torben

2 3

Build failed in Jenkins: moose-latest-dev #1090
by admin＠moosetechnology.org 11 Aug '12

11 Aug '12

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1090/> ------------------------------------------ [...truncated 762 lines...] - - - - - - - - - - - - - - - - - - MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: ByteString(String)>>displayProgressAt:from:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: [:pkg | pkg loadUsing: self gofer: gofer] in MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: [super linearLoadPackageSpecs: packageSpecs repositories: repositories] in MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushAtomicLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: [:dict | ^ self executeLoadFromArray: anArray] in [self versionSpec loader: newLoader. MetacelloPlatform current useStackCacheDuring: [:dict | ^ self executeLoadFromArray: anArray] defaultDictionary: Dictionary new] in [[self versionSpec loader: newLoader. MetacelloPlatform current useStackCacheDuring: [:dict | ^ self executeLoadFromArray: anArray] defaultDictionary: Dictionary new] ensure: [self versionSpec loader: originalLoader]] in MetacelloMCVersion>>fetchRequiredFromArray: [^ aBlock value: dict] in MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: [self versionSpec loader: newLoader. MetacelloPlatform current useStackCacheDuring: [:dict | ^ self executeLoadFromArray: anArray] defaultDictionary: Dictionary new] in [[self versionSpec loader: newLoader. MetacelloPlatform current useStackCacheDuring: [:dict | ^ self executeLoadFromArray: anArray] defaultDictionary: Dictionary new] ensure: [self versionSpec loader: originalLoader]] in MetacelloMCVersion>>fetchRequiredFromArray: BlockClosure>>ensure: [[self versionSpec loader: newLoader. MetacelloPlatform current useStackCacheDuring: [:dict | ^ self executeLoadFromArray: anArray] defaultDictionary: Dictionary new] ensure: [self versionSpec loader: originalLoader]] in MetacelloMCVersion>>fetchRequiredFromArray: [:bar | bar value: 1. aBlock value. bar value: 2] in MetacelloPharoPlatform>>do:displaying: NonInteractiveUIManager(CommandLineUIManager)>>progressInitiationExceptionDefaultAction: ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: ByteString(String)>>displayProgressAt:from:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloMCVersion>>fetchRequiredFromArray: [| fetchLoader | fetchLoader := self fetchRequiredFromArray: (self defaultPackageNamesToLoad: anArray). MetacelloPlatform current do: [fetchLoader doLoad] displaying: 'Loading ' , displayString. Transcript cr; show: '...finished ' , self versionNumber printString. ^ fetchLoader] in MetacelloMCVersion>>doLoadRequiredFromArray: BlockClosure>>ensure: MetacelloMCVersion>>doLoadRequiredFromArray: MetacelloMCVersion>>load ConfigurationOfGlamoroust class>>loadDevelopment ConfigurationOfGlamoroust class>>loadDefault UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: Compiler class>>evaluate:for:notifying:logged: Compiler class>>evaluate:for:logged: Compiler class>>evaluate:logged: [| chunk | val := (self peekFor: $!) ifTrue: [(self class evaluatorClass evaluate: self nextChunk logged: false) scanFrom: self] ifFalse: [chunk := self nextChunk. self checkForPreamble: chunk. self class evaluatorClass evaluate: chunk logged: true]] in [:bar | [self atEnd] whileFalse: [bar value: self position. self skipSeparators. [| chunk | val := (self peekFor: $!) ifTrue: [(self class evaluatorClass evaluate: self nextChunk logged: false) scanFrom: self] ifFalse: [chunk := self nextChunk. self checkForPreamble: chunk. self class evaluatorClass evaluate: chunk logged: true]] on: InMidstOfFileinNotification do: [:ex | ex resume: true]. self skipStyleChunk]. self close] in FileSystemFileStream(PositionableStream)>>fileInAnnouncing: BlockClosure>>on:do: [:bar | [self atEnd] whileFalse: [bar value: self position. self skipSeparators. [| chunk | val := (self peekFor: $!) ifTrue: [(self class evaluatorClass evaluate: self nextChunk logged: false) scanFrom: self] ifFalse: [chunk := self nextChunk. self checkForPreamble: chunk. self class evaluatorClass evaluate: chunk logged: true]] on: InMidstOfFileinNotification do: [:ex | ex resume: true]. self skipStyleChunk]. self close] in FileSystemFileStream(PositionableStream)>>fileInAnnouncing: NonInteractiveUIManager(CommandLineUIManager)>>progressInitiationExceptionDefaultAction: ProgressInitiationException>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ProgressInitiationException(Exception)>>signal ProgressInitiationException>>display:at:from:to:during: ProgressInitiationException class>>display:at:from:to:during: ByteString(String)>>displayProgressFrom:to:during: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: FileSystemFileStream(PositionableStream)>>fileIn [^ (FileSystemFileStream with: stream contents asString) reset fileIn] in [:stream | [^ (FileSystemFileStream with: stream contents asString) reset fileIn] on: Error , ParserNotification do: [:e | self handleError: e reference: aReference]] in BasicCodeLoader>>installSourceFile: BlockClosure>>on:do: [:stream | [^ (FileSystemFileStream with: stream contents asString) reset fileIn] on: Error , ParserNotification do: [:e | self handleError: e reference: aReference]] in BasicCodeLoader>>installSourceFile: [aBlock value: stream] in FileReference>>readStreamDo: BlockClosure>>ensure: FileReference>>readStreamDo: BasicCodeLoader>>installSourceFile: [:reference | self installSourceFile: reference] in [sourceFiles do: [:reference | self installSourceFile: reference]] in BasicCodeLoader>>installSourceFiles Array(SequenceableCollection)>>do: [sourceFiles do: [:reference | self installSourceFile: reference]] in BasicCodeLoader>>installSourceFiles BlockClosure>>ensure: BasicCodeLoader>>installSourceFiles BasicCodeLoader class>>commandLineHandlerAction: [:commandLine | BasicCodeLoader commandLineHandlerAction: commandLine] in BasicCodeLoader class>>initialize [:each | | actionBlock conditionBlock | conditionBlock := each key. actionBlock := each value. (conditionBlock value: anUserInput) ifTrue: [actionBlock value: anUserInput]] in CommandLine class(AbstractUserInput class)>>dispatch: [:association | aBlock value: association value] in Dictionary>>valuesDo: [:each | each ifNotNil: [aBlock value: each]] in Dictionary>>associationsDo: Array(SequenceableCollection)>>do: Dictionary>>associationsDo: Dictionary>>valuesDo: Dictionary>>do: CommandLine class(AbstractUserInput class)>>dispatch: [self dispatch: singleton] in CommandLine class>>dispatch BlockClosure>>cull: [each cull: resuming] in [:each | self logStartUpErrorDuring: [each cull: resuming] into: errors tryDebugger: self isInteractive] in SmalltalkImage>>executeDeferredStartupActions: -- and more not shown --------------------------------------------------------------------------------- THERE_BE_DRAGONS_HERE Got startup errors: ------------------------------------------------------------------------------- THERE_BE_DRAGONS_HERE Error: Could not resolve: GT-Tests-Inspector [GT-Tests-Inspector] in <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose/package-cac…> http://www.squeaksource.com/glamoroust ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/glamoroust: ConnectionTimedOut: Data receive timed out.' ------------------------------------------------------------------------------- Recording test results Archiving artifacts

1 1

Issue 798 in moose-technology: Mondrian should store edges in the most specific parent of the from/to nodes
by moose-technology＠googlecode.com 10 Aug '12

10 Aug '12

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.7 New issue 798 by tudor.gi...(a)gmail.com: Mondrian should store edges in the most specific parent of the from/to nodes http://code.google.com/p/moose-technology/issues/detail?id=798 The edges should be stored in the most specific parent of the from and to nodes, and not in the parent of the node in which they are defined. This is because the layout takes this information into account. For example, the below layout does not show a tree inside node 1. view := MOViewRenderer new. view node: 1 forIt: [ view shape label. view nodes: (10 to: 11). view treeLayout. ]. view edgesFromAssociations: {10 -> 11}. view open.

1 4

Jenkins build is unstable: moose-latest-dev #1004
by admin＠moosetechnology.org 09 Aug '12

09 Aug '12

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1004/>

4 89

Roassal & Spec [Fwd: [Pharo-project] Spec default row layout]
by Ben Coman 06 Aug '12

06 Aug '12

2 1

Roassal - view shape rectangle - view shape line - returned class
by Ben Coman 06 Aug '12

06 Aug '12

In experimenting to understand ROMondrianExample>>attachPointOn: I broke into the execution as follows: "forEach: [:cls | self haltOnce." now if I highlight and inspect 'view shape line' I get a ROLine. but if I highlight and inspect 'view shape rectangle' I get a ROMondrianViewBuilder rather than the expected something like ROBox. This seems wrong that these are not consistent. cheers, -ben

2 3

Roassal - idea for compound shapes
by Ben Coman 06 Aug '12

06 Aug '12

I think the following would be the start of a good example of how Roassal works... | view rawView el1 el2 edge line | rawView := ROView new. el1 := ROElement new. el1 extent: 50@50. el1 + ROBox red + ROCircle yellow + ROLabel @ RODraggable. rawView add: el1. rawView open ...except that it would be nice if the ROLabel could be centred. In addition, being able to place the ROLabel in various "offset" locations, I think that would satisfy a lot of my composition requirements - for example building a transformer compound symbol with two overlapping circles and two labels for "equipment tag" and "power size". To that effect it would be great if ROLabel or similar could have a callback mechanism to get different attributes from the model. Alternatively I guess I could make a new subclass of ROShape that draws such that directly. cheers -ben

2 2

migrating to Roassal - custom shapes
by Ben Coman 05 Aug '12

05 Aug '12

Referring to the attached graph, what is the best way to approach the following in Roassal. Currently with Mondrian I produce a produce a custom shape using the forms builder in #mondrianShape, which is a method of my ModelRoot class. Referring to the attached graph, as an example this shows the class name "Substation" above the instance "SS1" and has a space for contained items to be displayed within it. >>mondrianShape | builder | builder := MOFormsBuilder new. builder column; center; fill; pref; grow. builder row; center; pref; fill; grow; row; center; pref; fill; grow; row; center; pref; fill; grow. builder x: 1 y: 1 add: ( MORectangleShape new text: #strippedClassName; textAlignment: #left; borderColor: Color white ) . builder x: 1 y: 2 add: ( MORectangleShape new text: #localName; textAlignment: #left ) . builder x: 1 y: 3 add: ( MORectangleShape new ) . builder x: 1 y: 3 add: ( MOChildrenShape new ) . ^builder shape In conjunction with the use of MOChildrenShape above, class ModelRoot also has method #addSubViewTo: which descends through contained classes - for example instance "primary" inside "T1" inside "SS2" inside "Figure 8..." >>addSubViewTo: aMOViewRenderer aMOViewRenderer node: self using: self mondrianShape forIt: [ self children do: [ :child | child addSubViewTo: aMOViewRenderer. ] ] My initial issues in migrating this to Roassal are: 1. Roassal appears to not provide any methods that have "using:" in them. 2. Roassal appears to not support MOFormsBuilder It may be that I am accessing to much internal methods. The code above was the result of evolutionary hacking as I was learning Mondrian. I would be happy to re-architect if someone can advise best practice for Roassal. cheers -ben

3 5

some Roassal use cases
by Ben Coman 05 Aug '12

05 Aug '12

Just to give you an idea of where I would like to end up... referring to the attached [1] & [2]. I am looking to be able to generate a first layout from data by applying a layout, but then mostly move nodes around and draw links manually - then save and load these layouts. I imagine that similar might be useful for software analysis wanting to intuitively arrange a few nodes to annotate together for printing purposes - saving different zoomed in "views" of the system under analysis. One thing I am contemplating is whether one of my "busbar" shapes could be defined to have several regularly spaced attachpoints, with the attachpoints themselves optionally visible - either full time or when hovering over a shape. Also I'd like to be able to group shapes that a layout can act on as a whole. A little different from the MOFormsBuilder, it would just be offsets relative to each other, to the point where interactively you could multi-select nodes and "Group" them to be acted on by a layout as a whole. I've also marked a couple of other ideas on these attached files. [1] Roassal Use Case - Motor Control Centre Single Line Diagram (small).pdf [2] Roassal Use Case - Industrial Plant Power Distribution Single Line Diagram (small).pdf cheers, -ben

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev