Moose-dev October 2013

moose-dev@list.inf.unibe.ch

29 participants
128 discussions

by Stephan Eggermont

Hi, Today I looked at getting Glamour and Torch working in Pharo 3.0 - ConfigurationOfMondrian refers to a stable version of ProfStef, which isn't defined for 3.0 - GLMUITheme has UThemeWatery2 as ancestor, which is removed. UIThemeWatery works fine - RectangleMorph behavior was moved to BorderedMorph, so GLMPaneScroller needs a different ancestor - old version of Grease-Pharo-Core is loaded, using BlockContext (refering to squeaksource instead of smalltalkhub) With those changes, most browsers work. GLMBasicExamples open works, most examples work. Action List -> Inspect has a problem. (ConfigurationOfTorch project version: '1.4') load misses AST-Semantic should refer to smalltalkhub refers to an older version of ConfigurationOfGlamour AST changes seem to be substantial. Changes needed in TCParser? Stephan

11 years, 1 month

Loading Hapax

by Hernán Morales Durand

Hello, I know that Hapax possibly isn't fully ported to Pharo, but running the Hapax tests causes my Moose 4.5 image to hang (I've loaded everything in the SqS Hapax repository). What image and package loading order should one use to load Hapax? I'm interested in the information retrieval part for natural language analysis, could that part be repackaged in its own package? Cheers, Hernán

11 years, 1 month

[Moose-dev] „Zoom to fit pane“ for Roassal?

by MartinW

Hi, i use Roassal graphs in Glamour panes, and i wonder if there is a way to zoom and center the Roassal graph so that it fits entirely into its Glamour pane. Can this be done? Best regards, Martin. -- View this message in context: http://forum.world.st/Zoom-to-fit-pane-for-Roassal-tp4716227.html Sent from the Moose mailing list archive at Nabble.com.

11 years, 1 month

moose 4.9

by Tudor Girba

We are happy to announce version 4.9 of the Moose Suite: http://moosetechnology.org/download/4.9 This is a minor release still based on Pharo 2.0. The differences from Moose 4.8 are: The Mondrian engine was removed. The transition to Roassal is now complete. - Small fixes in Roassal layouts and rendering. - Small fix in FAMIX regarding manipulation of accesses. - Small visual fix in Glamour for rendering splitters in tables. A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… The Moose Suite 4.9 comes for each platform as a separate bundle: - Moose Suite 4.9 for Mac https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-mac.zip - Moose Suite 4.9 for Windows https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-win.zip - Moose Suite 4.9 for Linux https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_9-linux.zip The Moose Suite 4.9 can also be loaded in a Pharo 2.0 image either from the Configuration Browser, or by executing the following script: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. ((Smalltalk at: #ConfigurationOfMoose) project version: '4.9-snapshot') load

11 years, 1 month

Re: edges in 3D

by Alexandre Bergel

Hi Usman, Can you try the following example: R3Example new edgeExample2 There are many many edges displayed and it moves smoothly. On Windows the example goes well. On my machine (MacBookAir), I have an error that appears times to time. If this is the case for you, simply modify the method with: -=-=-=-=-=-=-=-=-=-=-=-= R3Morph>>visibleObjectInScreenX: screenX y: screenY | id | stateTracker ifNil: [ ^nil ]. ^ view -=-=-=-=-=-=-=-=-=-=-=-= Here is a screenshot: https://www.facebook.com/photo.php?fbid=533958193357449&set=a.3411893793009… Cheers, Alexandre On Oct 29, 2013, at 5:59 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Usman, > > Can you try the following example: > R3Example new edgeExample2 > > There are many many edges displayed and it moves smoothly. On Windows the example goes well. On my machine (MacBookAir), I have an error that appears times to time. If this is the case for you, simply modify the method with: > > -=-=-=-=-=-=-=-=-=-=-=-= > R3Morph>>visibleObjectInScreenX: screenX y: screenY > | id | > stateTracker ifNil: [ ^nil ]. > ^ view > -=-=-=-=-=-=-=-=-=-=-=-= > > Cheers, > Alexandre > > <Screen Shot 2013-10-29 at 5.41.40 PM.png> > > On Oct 21, 2013, at 10:08 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > >> Hi Alex, >> >> Thanx for adding the support for edges in Roassal 3D. I tried and it works. >> Now, when I try to add several edges (5-10), there is a huge lag and the CPU (~97% mark) and memory utilization of Pharo (~ +300MB) become tremendously high. Which means that I can try things examples but for getting something useful to work would require some memory and load profiling. >> >> Can you have a look? >> >> Usman >> >> >> On Fri, Oct 18, 2013 at 10:53 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi Usman, >> >> Sorry for the delay in our answer. >> We have produced a new version of Roassal3d with a support for edges. Consider this example: >> -=-=-=-= -=-=-=-= -=-=-=-= -=-=-=-= >> | view e1 e2 e3 | >> view := R3View new. >> e1 := R3CubeShape element. >> e1 translateToX: 1 y: 1 z: 1. >> >> e2 := R3UVSphereShape element. >> e2 translateToX: -1 y: 1 z: 1. >> >> e3 := R3ConeShape element. >> e3 translateToX: -1 y: -1 z: 1. >> >> view add: e1; add: e2; add: e3. >> view add: (R3LineShape blue elementFrom: e1 to: e2). >> view add: (R3LineShape blue elementFrom: e2 to: e3). >> >> view addInteraction: R3MouseControl new. >> view open . >> -=-=-=-= -=-=-=-= -=-=-=-= -=-=-=-= >> >> It will produces the following: >> >> >> <Screen Shot 2013-10-18 at 5.53.36 PM.png> >> >> Cheers, >> Alexandre >> >> >> On Oct 14, 2013, at 7:57 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: >> >>> Hello, >>> >>> I am trying to create a new shape, an edge, in Roassal 3D between two entities. My idea is to draw an edge from the position vector of a source shape to the position vector of a target. The edge is created but not at the correct position, it might be due to the fact that I need to set the position of the edge shape or mismatch between position in Roassal and OpenGL. Can you please have a look? >>> >>> Attached with this mail my proposition for the shape that works with the following script. >>> >>> |el1 el2 els el3| >>> view := R3View new. >>> view camera translateLeft: -2; translateBackward:3. >>> el1 := (R3CubeShape new color: Color green) element. >>> el2 := (R3CubeShape new color: Color red) element. >>> el3 := (R3CubeShape new color: Color cyan) element. >>> els := { el1. el2. el3 }. >>> view add: (R3EdgeShape new from: el2; to: el3; size: 1; color: Color blue) element. >>> view addAll: els. >>> R3XLineLayout on: els. >>> view addInteraction: R3MouseControl new. >>> view open. >>> <Roassal3d.st>_______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 1 month

Call for Participation in the Smalltalk Devroom at FOSDEM2014

by Stephan Eggermont

Call for Participation in the Smalltalk Devroom at FOSDEM 2014. http://www.fosdem.org, please forward " A devroom for the Pharo, Squeak, Amber, GST, Etoilé, Seaside, Moose Smalltalk projects & Newspeak as derived language. Smalltalk environments offer a very high development productivity, unmatched by their successors. Come do some pair programming with us and experience yourself the advantages of a real OO environment" The meetup will take place Saturday, February 1, 2014, from 9AM until 5PM, building AW. This room has 72 seats, a VGA video projector and wireless internet. More information will be available later. If there are volunteers to record video content, the FOSDEM organization kindly offered to provide needed equipment & instructions. Please let me know if you would be willing to spend some time pointing a camera at a speaker. Proposals on content and format are welcome. People interested in running a session should send me an email at stephan ( @ ) stack ( dot ) nl with 'FOSDEM2014’ in the subject and the following information: - Their name - The project they are associated with - A short bio, to be put on the website along with their speaker name - (optionally) a picture of themselves - The title of their session (which will go on the website and in the booklet) - A abstract describing the session in further detail. - The desired length of the session. - The desired time slot in which they want to hold the session. I will send out updates on a regular basis to the lists and anyone stating his interest. Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha). The desired time slot is meant to help you prevent conflicts with other dev rooms in which you might have a talk or your travel arrangements. There are alternative, non smalltalk-specific tracks available: lightning talk and the main track The deadline for submissions is December 31, 23:00 GMT+1. Devroom related URLs: http://www.pharo-project.org http://www.squeak.org/ http://etoileos.com/ http://www.seaside.st/ http://smalltalk.gnu.org/ http://www.moosetechnology.org http://amber-lang.net http://newspeaklanguage.org/ http://www.esug.org First proposal already arrived: Stefan Marr proposed: I could give a presentation on SOM (Simple Object Machine) Smalltalk. I would especially go into detail of the Truffle-based and the RPython (PyPy) based implementations to show modern ways of language implementations with the goal of achieving high performance.

11 years, 1 month

Re: moose 4.9

by Stephan Eggermont

I’ve looked with DeprecationFinder at my (older) cache of SmalltalkHub. In the following packages I’ve found references to ‚mondrian' that might need changing to ‚roassal’ to work in Moose 4.9 AnneEtien/RingJET Ring-History-Browsers-VeronicaUquillas.28 FabrizioPerin/MooseEE Moose-JEE-Core-Model-FabrizioPerin.29 FabrizioPerin/MooseEE Moose-JEE-Experiments-AdempiereCaseStudy-FabrizioPerin.2 FabrizioPerin/MooseEE Moose-JEE-FabrizioPerin.76 FabrizioPerin/MooseEE Moose-JEE-Browsers-FabrizioPerin.5 FabrizioPerin/MooseEE Moose-JEE-Reports-FabrizioPerin.15 FabrizioPerin/MooseEE Moose-JEE-Model-FabrizioPerin.24 FabrizioPerin/MooseEE Moose-JEE-Model-FabrizioPerin.77 FabrizioPerin/MooseEE Moose-JEE-Model-FabrizioPerin.142 abergel/Legacy DomainProfiler-AlexandreBergel.13 abergel/Legacy MrHolmes-Ivan_Rojas.36 abergel/Legacy MrHolmes-IvanRojas.3 abergel/Legacy MetaSpy-lr.22 abergel/Legacy MrHolmes-Ivan_Rojas.5 abergel/Legacy MrHolmes-Ivan_Rojas.32 abergel/Legacy MrHolmes-Ivan_Rojas.30 HerveVerjus/Nimrod Nimrod-HerveVerjus.26 HerveVerjus/Nimrod Nimrod-HerveVerjus.15 HerveVerjus/Nimrod Nimrod-HerveVerjus.24 HerveVerjus/Nimrod Nimrod-HerveVerjus.31 PabloEstefo/TestSurgeon TestSurgeon-PabloEstefo.11 PabloEstefo/TestSurgeon TestSurgeon-PabloEstefo.16 andrehora/BugMaps BugMaps-Browser-PedroPires.15 andrehora/BugMaps BugMaps-Browser-CesarCouto.17 andrehora/FindBugs AnnotationGraph-AndreHora.102 andrehora/FindBugs AnnotationGraph-AndreHora.81 andrehora/FindBugs AnnotationGraph-AndreHora.17 andrehora/FindBugs AnnotationGraph-AndreHora.96 andrehora/Menssana Menssana-Browsers-cyrilledelaunay.8 andrehora/HoraExp Moose-Finder-AndreHora.355 andrehora/HoraExpTemp Moose-Finder-AndreHora.359 andrehora/HoraExpTemp2 Moose-Finder-AndreHora.357 andrehora/HoraExpTemp3 Moose-Finder-AndreHora.359 andrehora/FamixBugEntity Famix-Extensions-Bugs-CesarCouto.16 andrehora/FamixBugEntity Famix-Extensions-Bugs-CesarCouto.12 andrehora/FamixBugEntity Famix-Extensions-Bugs-CesarCouto.20 AlainPlantec/Platypus2 Platypus2Pharo-AlainPlantec.9 CipT/OverviewPyramidStats Moose-MondrianPaintings-cipt.166 JLaval/Orion OrionBrowser-janniklaval.31 JLaval/Ozone Ozone-janniklaval.24 jfabry/AspectMaps AspectMaps-johanfabry.159 jfabry/AspectMaps AspectMaps-johanfabry.133

11 years, 1 month

Re: moose 4.9

by Stephan Eggermont

In Moose 4.9, Mondrian is replaced by roassal. By looking at my old package-cache with DeprecationFinder, I’ve found the following packages referring to a selector 'mondrian’. They might need updating to refer to 'roassal’ instead. Stephan AnneEtien/RingJET Ring-History-Browsers-VeronicaUquillas.28 FabrizioPerin/MooseEE Moose-JEE-Core-Model-FabrizioPerin.29 FabrizioPerin/MooseEE Moose-JEE-Experiments-AdempiereCaseStudy-FabrizioPerin.2 FabrizioPerin/MooseEE Moose-JEE-FabrizioPerin.76 FabrizioPerin/MooseEE Moose-JEE-Browsers-FabrizioPerin.5 FabrizioPerin/MooseEE Moose-JEE-Reports-FabrizioPerin.15 FabrizioPerin/MooseEE Moose-JEE-Model-FabrizioPerin.24 FabrizioPerin/MooseEE Moose-JEE-Model-FabrizioPerin.77 FabrizioPerin/MooseEE Moose-JEE-Model-FabrizioPerin.142 abergel/Legacy DomainProfiler-AlexandreBergel.13 abergel/Legacy MrHolmes-Ivan_Rojas.36 abergel/Legacy MrHolmes-IvanRojas.3 abergel/Legacy MetaSpy-lr.22 abergel/Legacy MrHolmes-Ivan_Rojas.5 abergel/Legacy MrHolmes-Ivan_Rojas.32 abergel/Legacy MrHolmes-Ivan_Rojas.30 HerveVerjus/Nimrod Nimrod-HerveVerjus.26 HerveVerjus/Nimrod Nimrod-HerveVerjus.15 HerveVerjus/Nimrod Nimrod-HerveVerjus.24 HerveVerjus/Nimrod Nimrod-HerveVerjus.31 PabloEstefo/TestSurgeon TestSurgeon-PabloEstefo.11 PabloEstefo/TestSurgeon TestSurgeon-PabloEstefo.16 andrehora/BugMaps BugMaps-Browser-PedroPires.15 andrehora/BugMaps BugMaps-Browser-CesarCouto.17 andrehora/FindBugs AnnotationGraph-AndreHora.102 andrehora/FindBugs AnnotationGraph-AndreHora.81 andrehora/FindBugs AnnotationGraph-AndreHora.17 andrehora/FindBugs AnnotationGraph-AndreHora.96 andrehora/Menssana Menssana-Browsers-cyrilledelaunay.8 andrehora/HoraExp Moose-Finder-AndreHora.355 andrehora/HoraExpTemp Moose-Finder-AndreHora.359 andrehora/HoraExpTemp2 Moose-Finder-AndreHora.357 andrehora/HoraExpTemp3 Moose-Finder-AndreHora.359 andrehora/FamixBugEntity Famix-Extensions-Bugs-CesarCouto.16 andrehora/FamixBugEntity Famix-Extensions-Bugs-CesarCouto.12 andrehora/FamixBugEntity Famix-Extensions-Bugs-CesarCouto.20 AlainPlantec/Platypus2 Platypus2Pharo-AlainPlantec.9 CipT/OverviewPyramidStats Moose-MondrianPaintings-cipt.166 JLaval/Orion OrionBrowser-janniklaval.31 JLaval/Ozone Ozone-janniklaval.24 jfabry/AspectMaps AspectMaps-johanfabry.159 jfabry/AspectMaps AspectMaps-johanfabry.133

11 years, 1 month

Issue 914 in moose-technology: withCenteredText not centering text correctly

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 914 by cunningh...(a)gmail.com: withCenteredText not centering text correctly http://code.google.com/p/moose-technology/issues/detail?id=914 When I ask for centeredText, I would expect it to be centered horizontally in the area that it is displaying in. Instead, it appears to be bumped up vertically above the location where it should be. If you add the following (missing?) method: ROMondrianExample>>centeredText " self new centeredText " | view | view := ROMondrianViewBuilder new. self centeredTextOn: view. view open and then run ROMondrianExample new centeredText, you will see the issue. How to reproduce the problem: step by step if necessary This is from the latest (2013-02-14) Moose Suite 4.7 from the MooseTechnology.org download page, on Windows 7 os. Labels: Type-Defect Component-Roassal -- 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

11 years, 1 month

Build failed in Jenkins: moose-latest-dev-4.9 #1342

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/1342/> ------------------------------------------ Started by timer Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.9/ws/> Deleting project workspace... done [moose-latest-dev-4.9] $ /bin/sh -xe /tmp/hudson2076311877495556671.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.9 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.9.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: ConnectionTimedOut: Data receive timed out. [0mSocket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc... Socket>>waitForDataFor:ifClosed:ifTimedOut: Socket>>waitForDataFor: Socket>>receiveDataSignallingTimeout:into:startingAt: SocketStream>>receiveData SocketStream>>next ZnLineReader>>processNext ZnLineReader>>nextLine ZnStatusLine>>readFrom: ZnStatusLine class>>readFrom: ZnResponse>>readHeaderFrom: ZnResponse(ZnMessage)>>readFrom: ZnResponse class(ZnMessage class)>>readFrom: ZnClient>>executeRequestResponse ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse] BlockClosure>>ensure: ZnClient>>getConnectionAndExecute ZnClient>>executeWithRedirectsRemaining: ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc... BlockClosure>>on:do: ZnClient>>executeWithRetriesRemaining: ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: ConnectionTimedOut(Exception)>>signal ConnectionTimedOut(Exception)>>signal: ConnectionTimedOut class(Exception class)>>signal: Socket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc... [0m[31mGot startup errors: [0m[31m ConnectionTimedOut: Data receive timed out. [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 1 month

← Newer
1
2
3
4
5
6
7
8
9
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2013