Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 995 in moose-technology: Roassal does not export the full PNG

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-5.0 New issue 995 by tu...(a)tudorgirba.com: Roassal does not export the full PNG http://code.google.com/p/moose-technology/issues/detail?id=995 Try this: view node: 1. view node: 2. view horizontalLineLayout horizontalGap: 2000 And the export. If your window is less than 2000 pixels wide, you will not see the second node. -- 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, 7 months

cleaning the issue tracker

by Tudor Girba

Hi, As you probably noticed, I am going through all open issues and cleaning them. My goal would be to keep the tracker to less than 100 items. This means that we have to get rid of old issues that are of no interests or that can be fixed fast so that we can notice and treat the new ones faster. Any help in this direction would be greatly appreciated. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 7 months

Issue 666 in moose-technology: package name in DSM

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-DSM New issue 666 by jannik.l...(a)gmail.com: package name in DSM http://code.google.com/p/moose-technology/issues/detail?id=666 The package name in DSM, specially in encaps DSM are not well placed.

11 years, 7 months

Issue 621 in moose-technology: writing tests for removeMethod

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- CC: cy.delau...(a)gmail.com Labels: Type-Defect Priority-Medium RPackage New issue 621 by stephane...(a)gmail.com: writing tests for removeMethod http://code.google.com/p/moose-technology/issues/detail?id=621 writing tests for "The bug appeared when removing two extensions methods (from the same extending package) for a same class. in RPackage >> removeMethod: , when removing an extension method, we were telling the organizer to remove the extending package for the class concerned. This was wrong, because even if one extension from this package has been removed, some others can still exist. And the organizer should keep the this package as extending package for the class. So removing the first extension method worked correctly, but then removing a second or more methods from the same package was raising some errors "

11 years, 7 months

Issue 527 in moose-technology: Add ModelInfo to hold extra information in MSE

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-MooseCore Milestone-4.3 New issue 527 by tudor.gi...(a)gmail.com: Add ModelInfo to hold extra information in MSE http://code.google.com/p/moose-technology/issues/detail?id=527 We should add a special MooseModelInfo entity that can be serialized in MSE. Like this we would have a backward compatible solution for storing extra information in MSE such as: - source language - importer version - metamodel version - importing date - source version I will give it a try for 4.3

11 years, 7 months

Issue 771 in moose-technology: Problem with tabs in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 771 by santiago...(a)gmail.com: Problem with tabs in Glamour http://code.google.com/p/moose-technology/issues/detail?id=771 Running the following script: | browser | browser := GLMTabulator new. browser row: [ :r | r column: #columnA; column: #columnB ]. browser transmit to: #columnA; andShow: [ :a | a list display: [" :model | "#('Value 1' 'Value 2' 'Value 3' 'Value 1') ] ]. browser transmit from: #columnA; to: #columnB; andShow: [ :a | a list titleIcon: GLMUIThemeExtraIcons glamorousBrowse; display:#('data A' 'data B' 'data C'). a text titleIcon: GLMUIThemeExtraIcons glamorousAccept; display:'something'. a text titleIcon: GLMUIThemeExtraIcons glamorousAdd; display:'add something'. ]. browser openOn: MooseModel root allModels anyOne. after selecting a value in columnA the columnB is opened in the last tab (the one with the glamorousAdd icon). Instead it must be opened in the first tab (the one with the glamorousBrowse icon). Using text instead of icons, it works.

11 years, 7 months

Issue 940 in moose-technology: In Pharo 2.0 the SpyWizard does not take notice of newly added packages. Possible solution: use RPackageOrganizer

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 940 by w...(a)fastmail.fm: In Pharo 2.0 the SpyWizard does not take notice of newly added packages. Possible solution: use RPackageOrganizer http://code.google.com/p/moose-technology/issues/detail?id=940 Describe the problem: what do you get? what do you expect? In Pharo 2.0 the SpyWizard does not take notice of newly added packages. How to reproduce the problem: step by step if necessary - load Spy into Pharo 2.0 - open for example the HapaoWizard and have a look at the packages available. Close the wizard. - add a new package to your image - open the HapaoWizard again: the new package does not appear in the list of available packages. Possible solution: Change SpyWizard>>packagesList ^ (PackageOrganizer default packageNames select: #isString) asSortedCollection: [ :a :b | a < b ] to: SpyWizard>>packagesList ^ (RPackageOrganizer default packageNames select: #isString) asSortedCollection: [ :a :b | a < b ] or perhaps: SpyWizard>>packagesList ^ (SystemNavigation default packageOrganizerClass default packageNames select: #isString) asSortedCollection: [ :a :b | a < b ] -- 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, 7 months

Issue 1010 in moose-technology: FAMIX should provide a FAMIXTypeGroup

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Famix Milestone-5.0 New issue 1010 by tu...(a)tudorgirba.com: FAMIX should provide a FAMIXTypeGroup http://code.google.com/p/moose-technology/issues/detail?id=1010 Right now, we have only FAMIXClassGroup. So, at the moment, we cannot deal with a group that contains both a FAMIXClass and a ParameterizedType. We need a FAMIXTypeGroup that will be the superclass of FAMIXClassGroup. This also implies that we should change the way the group type is inferred to take into account the common superclass. -- 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, 7 months

Build failed in Jenkins: moose-5.0 #150

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/150/> ------------------------------------------ Started by upstream project "glamour" build number 394 originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-5.0/ws/> Deleting project workspace... done [moose-5.0] $ /bin/sh -xe /tmp/hudson8221967386980271775.sh + bash + wget --quiet -O - http://get.pharo.org/30+vmLatest Downloading the latest 30 Image: http://files.pharo.org/image/30/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-5.0 ----SNAPSHOT----2013-11-16T13:49:35.491383+01:00 moose-5.0.image priorSource: 26766002 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-5.0.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0mInstalling ConfigurationOfMoose development [31mError: Could not access http://smalltalkhub.com/mc/Moose/Moose/main/: ConnectionTimedOut: Data receive timed out. [0mMCSmalltalkhubRepository(Object)>>error: MCSmalltalkhubRepository>>loadAllFileNames in Block: [ :exception | self error: 'Could not access ' , s...etc... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ConnectionTimedOut(Exception)>>pass ZnClient>>executeWithRetriesRemaining: in Block: [ :exception | ... 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 o...etc... Socket>>waitForDataFor:ifClosed:ifTimedOut: Socket>>waitForDataFor: ZdcSocketStream(ZdcAbstractSocketStream)>>socketWaitForData ZdcSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer ZdcSocketStream(ZdcAbstractSocketStream)>>next ZnLineReader>>processNext ZnLineReader>>nextLine ZnStatusLine>>readFrom: ZnStatusLine class>>readFrom: ZnResponse>>readHeaderFrom: ZnResponse(ZnMessage)>>readFrom: ZnResponse class(ZnMessage class)>>readFrom: [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 7 months

Re: [Pharo-dev] New builder for Roassal: building geographical maps

by Alexandre Bergel

It is currently ad-hoc since we use a bitmap for the map, and locate cities with distances in pixels. We have found description in SVG and found a couple of formulas to map longitude and latitude into pixels. So we will have something vectorial very soon. If someone has some ideas, data, examples the we will be very happy to take them as challenges! Alexandre > Le 15-11-2013 à 18:39, Sven Van Caekenberghe <sven(a)stfx.eu> a écrit : > > Very nice, Alex, I guess you are using shape files then ? > > Sven > >> On 15 Nov 2013, at 20:56, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> Hi! >> >> During our pair coding session on Friday, we worked on a new builder for Roassal. >> >> Here is short example: >> >> >> | builder | >> builder := ROFranceMapBuilder new. >> builder shape circle size: 15; color: Color red; withLabel. >> builder showCities: #('Paris' 'Lyon' 'Marseille'). >> >> builder shape circle size: 25; color: Color blue; withLabel. >> builder show: 'Nice'. >> >> builder open >> >> It should produce: >> <Screen Shot 2013-11-15 at 4.53.30 PM.png> >> >> >> There is no reference to external files. It runs out of the box. >> >> In case you got a sudden need to press a like button or do some retweet, here a bit of material: >> >> https://www.facebook.com/media/set/?set=a.543459092407359.1073741830.340543… >> https://twitter.com/objectprofile/status/401433558684008448 >> >> On our facebook account we have many more screenshots. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >

11 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev