Moose-dev February 2013

moose-dev@list.inf.unibe.ch

21 participants
145 discussions

Issue 871 in moose-technology: One click distribution has old vms

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium OpSys-All Milestone-4.7 New issue 871 by tu...(a)tudorgirba.com: One click distribution has old vms http://code.google.com/p/moose-technology/issues/detail?id=871 We need to update the VMs for the one click distribution.

12 years

Issue 905 in moose-technology: The rendering of ListPresentation should not raise error when setting the selection to a value outside of the visible elements

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: usman.bh...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour New issue 905 by tu...(a)tudorgirba.com: The rendering of ListPresentation should not raise error when setting the selection to a value outside of the visible elements http://code.google.com/p/moose-technology/issues/detail?id=905 testSettingSelectionOutsideOfVisibleElementsShouldNotRaiseError | browser items | browser := GLMTabulator withStatusbar. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a | a tree showOnly: 30 ]. window := browser openOn: (1 to: 100). self shouldnt: [((browser paneNamed: #one) port:#selection) value: 40] raise: Error.

12 years

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

by admin＠moosetechnology.org

See <http://ci.moosetechnology.org:8020/job/moose-latest-dev/1293/> ------------------------------------------ Started by timer Building in workspace <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/> [workspace] $ /bin/sh -xe /tmp/hudson4533343565087546929.sh + rm -rf <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose> <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose-tests> + /srv/ci.moosetechnology.org/builder/build.sh -i Pharo-1.4 -s monticello-fix-for-14 -s moose -s glamorous-theme -s moose-clean -s glamorous-toolkit -s cleanupforrelease -o moose [31m[33m =============================================================================== Notice: Errors in script loaded from <http://ci.moosetechnology.org:8020/job/moose-latest-dev/1293/artifact/moose…> =============================================================================== [0m[0m[31m==== Startup Error: Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0mMetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: in Block: [^ self error: 'Name not found: ' , aString] MetacelloMCVersionSpec>>packageNamed:forMap:ifAbsent: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: in Block: [:req | (self... Set>>do: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpec>>resolveToLoadableSpecs: MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... [0m[31mGot startup errors: [0m[31m Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.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://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose-tests/moos…> =============================================================================== [0m[0m[31m==== Startup Error: MessageNotUnderstood: receiver of "new" is nil [0mUndefinedObject(Object)>>doesNotUnderstand: #new UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: Compiler class>>evaluate:for:notifying:logged: Compiler class>>evaluate:for:logged: Compiler class>>evaluate:logged: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [| chunk | val := (self peekFor: $!)... BlockClosure>>on:do: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [:bar | ... NonInteractiveUIManager(CommandLineUIManager)>>progressInitiationExceptionDefaultAction: [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: receiver of "new" is nil [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.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 /srv/ci.moosetechnology.org/builder/build-oneclick.sh: line 170: zip: command not found Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE Archiving artifacts

12 years

call for speakers - pharoconf (april 2, 3) / mooseday (april 4) - bern, switzerland

by Tudor Girba

Hi, During April 2-4 we will organize a PharoConf and a MooseDay in Bern, Switzerland. Mark the day and join us. The participation will be free of charge. The conference will focus on interactivity and exchange, and will feature experience report talks, tutorials, show-us-your-project sessions and open discussions. We are looking for speakers: TUTORIAL These sessions will walk the audience through a piece of technology. Target duration: 30min - 60min. Example topics: - ZeroConf continuous integration builds - Building vectorial interfaces with Athens - Building UIs with Spec - New development tools (Fuel/Tanker, Glamorous Debugger, Nautilus ...) - Manipulating databases in Pharo (Riak, MongoDB ...) - Visualizing data (Roassal, EyeSee ...) TALK These sessions expose a topic that is not necessarily technical. Target duration: 30min - 60min. Example topics: - Experience of using Pharo to solve business problems - Experience of using Pharo and Moose to solve various technical problems (not necessarily related to Smalltalk) - Successes in marketing Pharo-based solutions - Future directions for Pharo or Moose SHOW-US-YOUR-PROJECT These sessions will feature short presentations of the projects (7-10 minutes) followed by open-space demos. Example topics: - The Glamorous Debugger - Nautilus - Analysis tools like Softwarenaut or Carrack - Fuel/Tanker - ... Please send us your submissions by email at tudor(a)tudorgirba.com. Cheers, Doru on behalf of the organizers -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

12 years

Migrating CAnalyzer from SS to SHub/Moose/CAnalyzer

by Stéphane Ducasse

Hi guys I'm currently migrating CAnalyzer from SS to SHub/Moose/CAnalyzer Stef

12 years

Parse VisualAge Smalltalk st files (or app as they are called)

by Fabrizio Perin

Hi, I would like to create a Moose model of a VisualAge smalltalk application. I tried to fileout a bunch of applications (which are groups of packages as far as I understood) and the result file .app has naturally a different syntax from pharo st files. Now, the questions are: - Should I customize the PPSmalltalkParser or should I start a parser from scratch? - Did anybody tried to import in moose a smalltalk dilect different from pharo? If yes how did he do that? I just want to understand if I can save time or I should build a whole parser and importer from scratch. Thanks for any suggestion or information. Cheers, Fabriyio (bloodz german kezboard)

12 years

BlockContext

by Usman Bhatti

Some methods in Moose introduce extension methods on BlockContext. BlockContext has been replaced by BlockClosure. We already have the required moose extension methods in BlockClosure, so I'll remove extension methods on BlockContext so that we do not have warnings while loading Moose on pharo 2.0. For info, the ist of extension categories added by Moose packages on BlockContext: - eyesee-support - moose-core - petitparser-core-converting

12 years

Issue 916 in moose-technology: allChioldScopes include self

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix New issue 916 by anquetil...(a)gmail.com: allChioldScopes include self http://code.google.com/p/moose-technology/issues/detail?id=916 From a FAMIXScopingEntity, asking allChildScope will include the receiver ... this is due to withAllChildScopesDo: which therforew suffers from the same problem Expected behaviour: only the direct children of the receiver -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

12 years

Issue 881 in moose-technology: Missing browser instance variable

by moose-technology＠googlecode.com

Status: Accepted Owner: kurs....(a)gmail.com CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-PetitParser New issue 881 by kurs....(a)gmail.com: Missing browser instance variable http://code.google.com/p/moose-technology/issues/detail?id=881 PPParserBrowser and PPAllParserBrowser are missing browser instance variable, since the supperclass was changed from BrowserTemplate to CompsoitePresentation (PetitGui.107). I presume, this is minor issue, but I have no idea why it was changed from Template to CompositePresentation.

12 years

Issue 872 in moose-technology: Roassal refactor RubberBand>>onDrop:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 872 by benjamin...(a)gmail.com: Roassal refactor RubberBand>>onDrop: http://code.google.com/p/moose-technology/issues/detail?id=872 ROExample>>rubberBandOn: currently has the line... rawView add: (newEdgeRaw + ROLine). While this is fine in the ROExample script, in my application rawView was not available at that point, so instead I needed... newEdgeRaw from view add: (newEdgeRaw + ROLine). For a while I confused myself by trying to use... newEdgeRaw view add: (newEdgeRaw + ROLine). but that was not the same view, since the ROEdge created in the sender had a random default. So I now think it is more clear to not create the ROEdge in the sender, but instead pass the fromElement and toElement and let the user create the ROEdge themselves. I think this is conceptually clearer. See the two methods in the attached changeset. Attachments: RubberBand-20121125.1.cs 2.4 KB

12 years

← Newer
1
...
5
6
7
8
9
10
11
...
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2013