Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

ROForceBasedLayout>>on:
by Ben Coman 05 Jan '13

05 Jan '13

All my previous use of layouts with the Roassal API has been of the form.. ROSomeLayout on: rawview elements. where elements returns both ROElement and ROEdge. This has never been a problem until I do... ROForceBasedLayout on : rawview elements which fails in doExecute since ROEdge does not understand #center. This might not have been noticed earlier since the tests send only elements, and the only other use is by ROMondrianExample where ROMondrianFrame>>applyLayout uses 'self nodes' which returns only elements, eg.... ROMondrianFrame>>nodes ^ (elements select: [ :el | el class ~~ ROEdge ]) asArray So should the caller of a layout _required_ to send only ROElements to a layout (which may clutter user code) or perhaps now that there is ROAbstractComponent, ROView>>elements might return only ROElements, with ROView>>components returning both ROElement and ROEdge ? (except I think you wanted to minimise the dependency of separate ROElement/ROEdge. Or perhaps ROLayout>>on: might filter out ROEdge(s) ? cheers -ben

1 0

Issue 899 in moose-technology: PetitParse World Menu item missing
by moose-technology＠googlecode.com 29 Dec '12

29 Dec '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 899 by benjamin...(a)gmail.com: PetitParse World Menu item missing http://code.google.com/p/moose-technology/issues/detail?id=899 Ben Coman wrote: > I don't have time right now to stop and isolate this, but a quick > note... I just loaded PetitParser-lr.228 & PetitCSV-tg.7 > and World > Tools > PetitParser menu item has disappeared, which I had > used half an hour ago - on Moose 4.7. Not sure if you'll see the same > thing being just a single observation point. Actually, it comes with loading... PetitGui-TudorGirba.114 Time: 8 December 2012, 9:22:37.027 pm PPAllParsersBrowser is now PPBrowser

1 1

where was moose used for teaching/training?
by Tudor Girba 28 Dec '12

28 Dec '12

Hi, I would be interested in putting together some figure about the impact of Moose in academia and industry. If any of you have used Moose (or some of its subcomponents) for teaching/training purposes, please send a quick note with the context in which it happened. Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

3 2

Petitparser support request (LEImportSKMPowerTools)
by Ben Coman 28 Dec '12

28 Dec '12

'From Pharo1.4 of 18 April 2012 [Latest update: #14457] on 26 December 2012 at 10:58:18 am'! PPCompositeParser subclass: #LEImportSKMPowerTools instanceVariableNames: 'endOfLine nonComma start tableName columnNames columnName columnNamesRow table dataCell dataRow dataRows' classVariableNames: '' poolDictionaries: '' category: 'Lektrek-ImportExport'! !LEImportSKMPowerTools methodsFor: 'as yet unclassified' stamp: 'BenComan 12/24/2012 15:23'! dataCell ^ nonComma star flatten ==> [ :nodes | nodes value ]! ! !LEImportSKMPowerTools methodsFor: 'as yet unclassified' stamp: 'BenComan 12/24/2012 19:37'! dataRows ^ (dataRow delimitedBy: endOfLine) ==> [ :nodes | nodes reject: [ :each | each class = PPToken ] ]! ! !LEImportSKMPowerTools methodsFor: 'as yet unclassified' stamp: 'BenComan 12/24/2012 12:18'! endOfLine ^ #newline asParser token! ! !LEImportSKMPowerTools methodsFor: 'as yet unclassified' stamp: 'BenComan 12/24/2012 12:23'! nonComma ^ PPPredicateObjectParser anyExceptAnyOf: {Character tab . Character cr . Character lf . $, }! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/24/2012 15:38'! columnName ^ $< asParser , (#letter asParser / #digit asParser / #space asParser / $_ asParser / $/ asParser ) star flatten , $> asParser ==> [ :nodes | nodes second value ]! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/24/2012 14:54'! columnNames ^ ((columnName delimitedBy: $, asParser token) ) ==> [ :nodes | nodes reject: [ :each | each class = PPToken ] ]! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/24/2012 14:56'! columnNamesRow ^ '//' asParser, columnNames ==> [ :nodes | nodes second value ]! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/24/2012 15:23'! dataRow ^ (dataCell delimitedBy: $, asParser token) ==> [ :nodes | nodes reject: [ :each | each class = PPToken ] ]! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/26/2012 10:30'! start ^ table star end! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/26/2012 10:38'! table ^ ( (tableName , endOfLine, columnNamesRow , endOfLine , dataRows) ==> [ :nodes | { nodes first . nodes third . nodes fifth } ] )! ! !LEImportSKMPowerTools methodsFor: 'grammar' stamp: 'BenComan 12/24/2012 14:24'! tableName ^ '// --- ' asParser, #word asParser star flatten, ' ---' asParser ==> [ :nodes | nodes second value ]! ! PPCompositeParser subclass: #LEImportSKMPowerTools instanceVariableNames: 'endOfLine nonComma start table tableName columnNamesRow columnNames columnName dataRows dataRow dataCell' LEImportSKMPowerTools>>start ^ table star end LEImportSKMPowerTools>>table ^ ( (tableName , endOfLine, columnNamesRow , endOfLine , dataRows) ==> [ :nodes | { nodes first . nodes third . nodes fifth } ] ) LEImportSKMPowerTools>>tableName ^ '// --- ' asParser, #word asParser star flatten, ' ---' asParser ==> [ :nodes | nodes second value ] LEImportSKMPowerTools>>columnNamesRow ^ '//' asParser, columnNames ==> [ :nodes | nodes second value ] LEImportSKMPowerTools>>columnNames ^ ((columnName delimitedBy: $, asParser token) ) ==> [ :nodes | nodes reject: [ :each | each class = PPToken ] ] LEImportSKMPowerTools>>columnName ^ $< asParser , (#letter asParser / #digit asParser / #space asParser / $_ asParser / $/ asParser ) star flatten , $> asParser ==> [ :nodes | nodes second value ] LEImportSKMPowerTools>>dataRows ^ (dataRow delimitedBy: endOfLine) ==> [ :nodes | nodes reject: [ :each | each class = PPToken ] ] LEImportSKMPowerTools>>dataRow ^ (dataCell delimitedBy: $, asParser token) ==> [ :nodes | nodes reject: [ :each | each class = PPToken ] ] LEImportSKMPowerTools>>dataCell ^ nonComma star flatten ==> [ :nodes | nodes value ] LEImportSKMPowerTools>>endOfLine ^ #newline asParser token LEImportSKMPowerTools>>nonComma ^ PPPredicateObjectParser anyExceptAnyOf: {Character tab . Character cr . Character lf . $, } // Export start : 12/18/12 18:18:07 // Datablock format : All Input Data // Query name : *ALL COMPONENTS // --- Bus --- //<ComponentName>,<ComponentType>,<SystemNominalVoltage>,<AF_ArcType>,<AF_WorkingDistance> 00BFA10,10,415,In Box,609.6 00BFA20,10,415,In Box,609.6 // The following field(s) are enumerated data types // Either the quoted text or integer may be used in importing // <InService>: "Out"=0 "In"=1 // <Phase>: "None"=0 "A"=1 "B"=2 "C"=4 "AB"=3 "AC"=5 "BC"=6 "ABC"=7 "AB MidTap"=48 "BC MidTap"=96 "CA MidTap"=80 "ABC MidTap"=112 // <Size/Do Not Size>: "Size"=0 "Do Not Size"=1 // --- Cable --- //<ComponentName>,<SystemNominalVoltage>,<Phase>,<CableSize>,<NeutralSize>,<Length>,<Size/Do Not Size> 11P08023,11500,ABC,240,,680.0,Do Not Size 11P08024,11500,ABC,240,,610.0,Do Not Size

3 5

PetitParser World Menu item missing
by Ben Coman 24 Dec '12

24 Dec '12

I don't have time right now to stop and isolate this, but a quick note... I just loaded PetitParser-lr.228 & PetitCSV-tg.7 and World > Tools > PetitParser menu item has disappeared, which I had used half an hour ago - on Moose 4.7. Not sure if you'll see the same thing being just a single observation point. cheers -ben

1 0

[ann] moose and humane assessment courses
by Tudor Girba 17 Dec '12

17 Dec '12

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."

1 0

thankyou for GLMBasicExamples>>updateableIndividualPresentations
by Ben Coman 17 Dec '12

17 Dec '12

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

3 3

Build failed in Jenkins: moose-latest-dev #1234
by admin＠moosetechnology.org 16 Dec '12

16 Dec '12

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

1 1

Issue 898 in moose-technology: Roassal performance with Unicode
by moose-technology＠googlecode.com 16 Dec '12

16 Dec '12

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.

1 1

moose jenkins is down
by Fabrizio Perin 13 Dec '12

13 Dec '12

Service Temporarily Unavailable

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