- Moose-dev - INF Mailman

[ann] moose and humane assessment courses

by Tudor Girba

Hi, In the new year, I will be organizing a couple of public courses around the topic of humane assessment and Moose. These two will be held in Bern: - Humane Assessment Primer on January 25. This course is relevant for both managers and engineers. It covers assessment economics and the means to integrate humane assessment in the development process and in the organization: http://www.humane-assessment.com/courses/humane-assessment-primer - Moose Apprentice on February 7-8. This course is relevant for engineers. This is an introductory hands-on course on using the Moose analysis platform for putting humane assessment into practice: http://www.humane-assessment.com/courses/moose-apprentice Cheers, Tudor -- www.tudorgirba.com "Don't give to get. Just give."

12 years, 6 months

1
0
0 0

thankyou for GLMBasicExamples>>updateableIndividualPresentations

by Ben Coman

I wanted to feedback my appreciation for the extensive examples included with Glamour & Roassal. In particular it was enlightening to observe the use of Announcements and #updateOn:from: in GLMBasicExamples>>updateableIndividualPresentations This helped me achieve something I had been unable to get working for several months through other means. Suddenly it was easy and took only a half-hour to get working. The penny dropped to enable my first use of Announcements. cheers -ben

12 years, 6 months

3
3
0 0

Build failed in Jenkins: moose-latest-dev #1234

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1234/> ------------------------------------------ Started by user girba [workspace] $ /bin/sh -xe /tmp/hudson1912595674060777165.sh + rm -rf <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose> <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose-tests> <http://hudson.moosetechnology.org/job/moose-latest-dev/1234/artifact/moose_…> + /srv/hudson.moosetechnology.org/builder/build.sh -i Pharo-1.4 -s moose -s glamorous-theme -s moose-clean -s glamorous-toolkit -s cleanupforrelease -o moose /tmp/hudson1912595674060777165.sh: line 3: /srv/hudson.moosetechnology.org/builder/build.sh: No such file or directory Recording test results Archiving artifacts

12 years, 6 months

1
1
0 0

Issue 898 in moose-technology: Roassal performance with Unicode

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 898 by benjamin...(a)gmail.com: Roassal performance with Unicode http://code.google.com/p/moose-technology/issues/detail?id=898 In my application I need to display polar notation complex numbers in Roassal. This notation uses the angle ∠ symbol (http://www.fileformat.info/info/unicode/char/2220/index.htm) Using this there is a noticeable performance drop/lag when using this unicode character, as demonstrated by the sample below. Specifically, dragging with a non-Unicode element is instantaneous. The element immediately follows the hardware cursor and even when moving the mouse suddenly-and-at-speed it is hard force any space between the element and the hardware cursor. When dragging a Unicode element, the hardware cursor easily makes it to the other side of the window before the element moves. -------------------- rawView := ROView new. 10 timesRepeat: [ rawView add: (ROLabel elementOn: '22#22') @ RODraggable. ]. rawView open. rawView := ROView new. 10 timesRepeat: [ rawView add: (ROLabel elementOn: '33', Character angle asString, '33') @ RODraggable. ]. rawView open ------------- Character>>angle "The ANGLE symbol '∠' U+2220, from Unicode version 1.1 ISO/IEC-10646-1:1993" "One font family that contains this character is DejaVu" ^ Unicode value: 16r2220 ----- Further, changing this to 100 times locks the image for about 30 seconds before either "Roassal Visualization" window is displayed. If you then drop the System Browser over the top of the Roassal-Unicode window, it introduces a noticeable lag when moving the System Browser away. Is there anything obvious/quick that can be done to improve this performance - otherwise for now I'll just have to drop this nice-to-have symbol. However in the broader context of Roassal internationalization, this might be an important issue.

12 years, 6 months

1
1
0 0

moose jenkins is down

by Fabrizio Perin

Service Temporarily Unavailable

12 years, 6 months

2
1
0 0

Roassal how to display bottom corner of graph

by Ben Coman

With Roassal after applying a layout, I would like to be able to translate the graph such that the bottom left corner of the graph is displayed. Is there someway to do that already? I looked into ROFocusView, ROCanvas & ROCamera, but could not work it out what was needed. With the script below, the attached image is what I would like to see. "-------------" #(1 2 3 4 5 6 7 8 9) do: [ :x | rawView add: (ROElement spriteOn: x) + ROLabel. ]. rawView add: (ROEdge lineFrom: rawView elements seventh to: rawView elements eighth). rawView add: (ROEdge lineFrom: rawView elements seventh to: rawView elements ninth). (ROHorizontalTreeLayout new verticalGap: 40; horizontalGap:60) on: rawView elements. "HERE TRANSLATE CANVAS/CAMERA TO SHOW NODES 7, 8 & 9 IN THE BOTTOM LEFT CORNER OF WINDOW PANE" "-------------" cheers -ben

12 years, 7 months

3
21
0 0

Development of FAMIX AST meta-model extension

by Yuriy Tymchuk

Hi everyone! I'm extending FAMIX meta-model to add support for AST models.The project can be found at: http://smalltalkhub.com/#!/~YuriyTymchuk/Famix-AST <http://smalltalkhub.com/#!/~YuriyTymchuk/Famix-AST> I'll be thankful for any suggestions an support :) At the moment I've developed a hierarchy of the AST meta-model itself and you can load it from MSE files, as an example you can use this one: https://raw.github.com/Uko/metamodels-support-files/master/mse/ast.mse <https://raw.github.com/Uko/metamodels-support-files/master/mse/ast.mse> Please note that only /middleOf:And:/ method has it's AST defined. To explore AST model you should select a method node and see *statements* as it's subnode. My next step is automatic creation of the AST model from existing source of the method. Here is a diagram of a current Famix-AST class hierarchy: <http://moose-dev.97923.n3.nabble.com/file/n4025674/ClassDiagram.png> -- View this message in context: http://moose-dev.97923.n3.nabble.com/Development-of-FAMIX-AST-meta-model-ex… Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 7 months

6
12
0 0

[Roassal] Nested nodes and RODraggable

by roberto.minelli＠usi.ch

Hi, It's me again! ;) I'm building a calendar visualization inspired by http://www.xconomy.com/wordpress/wp-content/images/2012/11/skeuo-calendar.p…. Each node of visualization will be a month that contains: - An header (with (a) the name of the month and (b) the headers for the columns containing 'Mon' 'Tue' 'Wed' etc.) - Inner nodes for the days I created such visualization without the headers and now I'm wondering which is the clearer solution to add them. As I wrote in the previous mail, I'm using nodes:forEach: to generate the visualization with inner nodes. The first solution that came to my mind is to nest another nodes:forEach to draw the headers. Let me explain: view nodes: months forEach: [ :month | … headers := OrderedCollection with: month name . headers addAll: #('Sun' 'Mon' 'Tue' 'Wed' 'Thu' 'Fri' 'Sat' ). view nodes: headers forFirst: [ :header | 'The first header is an instance of the Month class, which is used as a key in the Dictionary that represents my data.' 'Thus I use that to recover the days for the current month from the dictionary' days := myData at: header. view nodes: days. ] ] Notice that nodes:forFirst: is a message I implemented that works like nodes:forEach: but only considers the first node of nodes and attaches the inner nodes only to that element. I feel this solution is a bit of a hack. How would you do it in a cleaner way? ____ Another question concerns drag & drop. I set my inner nodes (i.e, days) to be not draggable since I do not want the user to drag them, but I want the user to be able to drag the entire shape representing a month (i.e., outer node). As an effect to drag the month you should explicitly start the dragging from the outer node but this is counter intuitive. I'd like to be able to drag the month also from its inner nodes (days). Is there a way to propagate the interaction and from the inner nodes I can drag the container shape? ____ Thanks in advance, Roberto

12 years, 7 months

5
19
0 0

Build failed in Jenkins: moose-latest-dev #1231

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1231/> ------------------------------------------ Started by timer [workspace] $ /bin/sh -xe /tmp/hudson7094437068829965338.sh + rm -rf <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose> <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose-tests> <http://hudson.moosetechnology.org/job/moose-latest-dev/1231/artifact/moose_…> + /srv/hudson.moosetechnology.org/builder/build.sh -i Pharo-1.4 -s moose -s glamorous-theme -s moose-clean -s glamorous-toolkit -s cleanupforrelease -o moose [31m[33m =============================================================================== Notice: Errors in script loaded from <http://hudson.moosetechnology.org/job/moose-latest-dev/1231/artifact/moose/…> =============================================================================== [0m[0m[31m==== Startup Error: PrimitiveFailed: primitive #primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: in Socket failed [0mSocket(Object)>>primitiveFailed: Socket(Object)>>primitiveFailed Socket>>primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: Socket>>initialize: Socket class>>newTCP in Block: [super new initialize: TCPSocketType] BlockClosure>>repeatWithGCIf: Socket class>>newTCP Socket class>>new SocketStream class>>openConnectionToHost:port:timeout: SocketStream class>>openConnectionToHost:port: [0m[31mGot startup errors: [0m[31m PrimitiveFailed: primitive #primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: in Socket failed [0m blockNoContextSwitchOffset != null 9102 + /srv/hudson.moosetechnology.org/builder/build.sh -i moose -s patch-inputsensor -s testrunner -s moose-tests -o moose-tests [31m[33m =============================================================================== Notice: Errors in script loaded from <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose-tests/moose…> =============================================================================== [0m[0m[31m==== Startup Error: GoferRepositoryError: primitive #primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: in Socket failed [0mMCHttpRepository(MCFileBasedRepository)>>goferReferences in Block: [:error | ^ GoferRepositoryError signal: error mes...etc... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [(self tempAt: 2)... BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: PrimitiveFailed(Exception)>>pass [0m[31mGot startup errors: [0m[31m GoferRepositoryError: primitive #primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: in Socket failed [0m blockNoContextSwitchOffset != null 9102 + /srv/hudson.moosetechnology.org/builder/build-oneclick.sh -i moose -o moose_suite-4_7_dev -n Moose -t 'Moose Suite 4.7 Development ' -v 4.7 -c Moose cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.png': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.ico': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.icns': No such file or directory Recording test results No test report files were found. Configuration error? Archiving artifacts

12 years, 7 months

1
1
0 0

Roassal + nested nodes + withText

by roberto.minelli＠usi.ch

Hi guys, I'm using Roassal to build a visualization that looks like the following: http://www.xconomy.com/wordpress/wp-content/images/2012/11/skeuo-calendar.p… I create two ad-hoc layouts (i.e., extending the ROGridLayout) to individually layout days inside months and months inside years. I have a piece of code that looks something like: > view shape rectangle withText. > > view nodes: nodes forEach: [ :aGroupOfObjects | | innerNodes | > > innerNodes := do something with aGroupOfObjects. > ... > view shape rectangle size: 25; withCenteredText. > ... > view nodes: innerNodes. > view layout: ROMonthLayout new. > ] > > view layout: ROYearLayout new. > > view edges: ... Notice that I want the both the outer node (i.e., the month container) and the inner nodes (i.e., days) with labels. The problem is that when I set both nodes with labels the view takes time to be generated and interactions become impossible (i.e., the whole image actually becomes slow and you can no longer drag around shapes in the view). I explored the issue a little bit and discovered that it might be something related to ROShape>>chainedDrawOn:for: and the way Roassal handles shapes with "nested" shapes (i.e., when 'next' is not a RONullShape . I inspected one of my outer nodes and discovered that I have a chain such that 'outerNode next' is a ROLabel and the ROLabel has a ROChildrenShape as next and the next of the ROChildrenShape is a RONullShape . Have you ever experienced such a problem? Do you know how can I handle that? Do you see any potential problem in the snippet I posted above? Cheers and thanks in advance, Roberto

12 years, 7 months

4
10
0 0

seaside-glamour: some exp

by Usman Bhatti

Hello all, Andrei, a PhD student from U. Bern, is visiting Lille and he showed me seaside-glamour, rendering glamour in a web browser. So, without much effort we could move a glamour browser and start using it on the web. So, it was a great to see this thing working. Now, there are some widgets missing. But, we were able to create DropDown list and to transmit selection from it to other panes in the browser with some effort and its working now. Now, next step is Table widget, so we will see if we have some time to do it in the coming days. Now, for me, the missing part of the story is to see if can play with Roassal on the web :-). best, Usman

12 years, 7 months

3
4
0 0

OnMooseHardcodedViewRenderer Report

by Fabrizio Perin

Hi Doru, don't you think you can remove the class MOBenchmarks from this report?

12 years, 7 months

2
1
0 0

Jenkins build became unstable: moose-latest-dev #1228

by admin＠moosetechnology.org

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

12 years, 7 months

1
1
0 0

Issue 893 in moose-technology: The Moose menu entries labels do not match the window titles

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Milestone-4.7 Component-Finder New issue 893 by tu...(a)tudorgirba.com: The Moose menu entries labels do not match the window titles http://code.google.com/p/moose-technology/issues/detail?id=893 For example, the label shows 'Glamorous Glamour Editor' and the title is 'Glamorous Browser Editor'

12 years, 7 months

1
1
0 0

Issue 781 in moose-technology: VerveineJ should mark getters setters and constants

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 781 by santiago...(a)gmail.com: VerveineJ should mark getters setters and constants http://code.google.com/p/moose-technology/issues/detail?id=781 The property "kind" of the MSE models should be used to mark if a method is a getter, a setters or constant. Currently is only used to mark if a method is constructor

12 years, 7 months

1
2
0 0

[ann] moose talk at the java user group in bern

by Tudor Girba

Hi, On December 12, 18:15 I will give a talk at the Java User Group in Bern. I will be talking about how Moose redefines the meaning of analysis :): http://www.humane-assessment.com/blog/moose-talk-at-jug-bern-2012/ Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

12 years, 7 months

1
0
0 0

Issue 889 in moose-technology: All meta-properties should have an MSEComment

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.7 Component-Famix New issue 889 by tu...(a)tudorgirba.com: All meta-properties should have an MSEComment http://code.google.com/p/moose-technology/issues/detail?id=889 Here is the list of missing comments: http://ci.moosetechnology.org/job/moose-on-moose/lastCompletedBuild/testRep…

12 years, 7 months

1
6
0 0

Issue 892 in moose-technology: Roassal does not render properly on update

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 892 by tu...(a)tudorgirba.com: Roassal does not render properly on update http://code.google.com/p/moose-technology/issues/detail?id=892 browser := GLMWrapper new. browser show: [:a| a roassal title: 'Patterns'; act: [:roassal | roassal update ] icon: GLMUIThemeExtraIcons glamorousRefresh entitled: 'Update'; painting: [:view :collection | view nodes: collection. view edgesFrom: [:x | x // 2]. view treeLayout ] ]. browser openOn: (1 to: 100)

12 years, 7 months

1
1
0 0

Using Roassal as part of a Glamour-based UI

by Stephan Eggermont

Hi, I tried using a Roassal painting as a card-based layout for a glamour UI, but don't have too much luck updating it. The self refresh sends the CPRefresh, and the painting is updated, but all nodes are on top of each other. Related to issue 808? (Roassal 383, Glamour-Roassal-Presentations 7) browser := GLMTabulator new. browser row: #content; title: 'Change Patterns'. browser transmit to: #content; andShow: [:a| a roassal title: 'Patterns'; updateOn: CPRefresh from: self announcer; painting: [:view :patternHolder | |paintingBlock| paintingBlock := [ view shape width: [:el | 180]; height: [:el| 80]; fillColor: [:aPattern | aPattern applicable ifTrue: [Color r: 1.0 g: 1.0 b: 0.8] ifFalse: [Color red]]. view nodes: patternHolder patterns forEach: [:aPattern | view interaction item: 'inspect' action: [:el | aPattern switchApplicable. view raw elementsDo: #remove. self refresh]. view shape label. view nodes: (Array with: aPattern title with: aPattern applicable asString). view verticalLineLayout ]. view gridLayout]. view interaction item: 'inspect' action: [:el | el model inspect]; item: 'switch applicable' action: [:el | el model switchApplicable. view raw elementsDo: #remove. paintingBlock value. self refresh]. paintingBlock value. ]]. ^browser Stephan

12 years, 7 months

2
1
0 0

Issue 875 in moose-technology: Moose should test if it runs on a vm with the freetype plugin

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 875 by step...(a)stack.nl: Moose should test if it runs on a vm with the freetype plugin http://code.google.com/p/moose-technology/issues/detail?id=875 There are several vms that don't have a working freetype plugin. This severely reduces the number of fonts available (1 or 2 families with a very limited set of font sizes). This is an issue for 4.6 as well as 4.7 A testcase is added in Moose-Tests-FreeType-StephanEggermont.1 Attachments: Moose-Tests-FreeType-StephanEggermont.1.mcz 1.4 KB

12 years, 7 months

1
1
0 0

Issue 883 in moose-technology: viewTree does not work for Glamour browsers

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-High Component-Glamour Milestone-4.7 New issue 883 by tu...(a)tudorgirba.com: viewTree does not work for Glamour browsers http://code.google.com/p/moose-technology/issues/detail?id=883 This should work: GLMTabulator new viewTree

12 years, 7 months

1
2
0 0

getting closer to 4.7

by Tudor Girba

Hi, The way it looks now, we will be able to release Moose somewhere at the end of the week. Are there any particular issues that you might still have open? Are there any particular Moose-based projects that you would want to include in the main distribution? @Alex: is there anything in Roassal that is pending and that we should wait for? Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

12 years, 7 months

5
9
0 0

Presentations at FOSDEM?

by Stephan Eggermont

Hi, I would be interested to see some of the (new or very impressive) developments presented at the devroom FOSDEM. Would someone be able to show Softwarenaut on Pharo? Stephan

12 years, 7 months

1
0
0 0

adding comments to FAMIX

by Tudor Girba

Hi, Does anyone want to help commenting properties and entities in FAMIX meta-models? Here are the two issues: http://code.google.com/p/moose-technology/issues/detail?id=889 (add an MSEComment) http://code.google.com/p/moose-technology/issues/detail?id=890 (add a class comment) Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

12 years, 7 months

2
1
0 0

Issue 890 in moose-technology: All meta-entities should have an MSEComment

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.7 New issue 890 by tu...(a)tudorgirba.com: All meta-entities should have an MSEComment http://code.google.com/p/moose-technology/issues/detail?id=890 Here is the list of missing comments: http://ci.moosetechnology.org/job/moose-on-moose/lastCompletedBuild/testRep…

12 years, 7 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev