- Moose-dev - INF Mailman

by Juraj Kubelka

Hi, I have just found, there are two failing tests in MooseModelTest which have not been discovered by Jenkins. I can reproduce it in the newest Jeninks' build moose-latest-dev-4.8 and also in older too. Do you have the same issue? Methods are #testAsMSEString and #testExport. Problem is in initialization in method: === FMRepositoryVisitor>>run nb := 0. UIManager default displayProgress: 'Writing ', printer stream localName at: Sensor cursorPoint from: 1 to: self roots size during: [ :bar | progBar := bar. self basicRun] === There is "from: 1" and "to: self roots size". "self roots size" returns 1. And then in method Job>>progress ^ (currentValue - min) / (max - min) counts "(max - min)" as "(1 - 1)" = 0 and raises ZeroDivide. Easy fix is to set "from: 0". I would do it, but I hesitate because Jenkins does not introduce this error. Any idea? Cheers, Jura

12 years, 3 months

2
2
0 0

hasClassScope derived?

by Anne Etien

Hi, Shouldn't the hasClassScope property of FAMIXMethod be declared as <derived>? It is computed from privateState just as isConstructor or declaredExceptions which are derived. Same question for timeStamp. Thanks in advance. Anne

12 years, 3 months

4
8
0 0

roassal repository url

by Tudor Girba

Hi Alex, In the Moose image, the url of Roassal appears as: http://smalltalkhub.com/mc/ObjectProfile/Roassal/main Ideally, it should appear as: http://www.smalltalkhub.com/mc/ObjectProfile/Roassal/main Could you modify it? Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

12 years, 3 months

2
2
0 0

Should I port method MOViewRenderer>>getRenderedForm?

by Juraj Kubelka

Hi, Should I port method MOViewRenderer>>getRenderedForm (and corresponding class MOMorphPainterVisitor)? Out of Mondrian it is used just once in DistributionMapExampleTest>>testSample where it can be easily changed by calling "viewRenderer open delete". Thanks, Jura

12 years, 3 months

5
9
0 0

cycle detection with moose

by Tudor Girba

Hi, I wrote up a little blog post describing how we can use the cycle detection that resides silently in the Moose image. Perhaps it can be useful for people: http://www.humane-assessment.com/blog/demystifying--cycle-detection-with-mo… Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

12 years, 3 months

3
2
0 0

Call for papers for Dyla'13: 7th Workshop on Dynamic Languages and Applications @ECOOP

by Damien Cassou

Call for Papers =========================================================== Dyla'13, 7th Workshop on Dynamic Languages and Applications Colocated with ECOOP, ECMFA and ECSA In-cooperation with SIGPLAN and SIGSOFT 1–5 July, Montpellier, France http://rmod.lille.inria.fr/web/pier/Events/Dyla13 !! Important dates - Submission deadline: *April 19th* - Notification: mid-May - Workshop: July 1st - Ecoop early registration: mid-May !! Abstract The advent of Java and C# has been a major breakthrough in the adoption of some important object-oriented language characteristics. This breakthrough turned academic features like interfaces, garbage collection, and meta-programming into technologies generally accepted by industry. Nevertheless, the massive adoption of these languages now also gives rise to a growing awareness of their limitations. A number of reactions from industry testify this: invokedynamic bytecode instruction has been included in latest Java virtual machine release; the dynamic language runtime (DLR) is gaining popularity; C# adopted dynamic as a valid static type. Gartner prognoses further growth (http://blogs.gartner.com/mark_driver/2008/12/10) of dynamic languages. Researchers and practitioners struggle with static type systems, overly complex abstract grammars, simplistic concurrency mechanisms, limited reflection capabilities, and the absence of higher-order language constructs such as delegation, closures and continuations. Dynamic languages such as Ruby, Python, JavaScript and Lua are a step forward in addressing these problems while getting more and more popular. Making these languages mainstream requires practitioners to look back and pick mechanisms up in existing dynamic languages such as Lisp, Scheme, Smalltalk and Self. Practitioners also need to further explore discover new dynamic approaches in the context of new challenging fields such as pervasive computing. The goal of this workshop is to act as a forum where practitioners can discuss new advances in the design, implementation and application of dynamically typed languages that, sometimes radically, diverge from the statically typed class-based mainstream. Another objective is to discuss new as well as older "forgotten" languages and features in this context. Topics of interest include, but are not limited to: - programming language extensions - programming environment extensions - executing environments - static and dynamic analyses - optional type-checking - meta-object protocols - reserve engineering - domain-specific languages/tooling - testing environments - live programming !! Targeted audience The expected audience of this workshop is practitioners and researchers sharing the same interest in dynamically typed languages. Lua, Python, Ruby, Scheme and Smalltalk are gaining a significant popularity both in industry and academia. Nevertheless, each community has the tendency to only look at what it produces. Broadening the scope of each community is the goal of the workshop. To achieve this goal we will form a PC with leading persons from all languages mentioned above, fostering participation from all targeted communities. !! Workshop Format and Submission Information The workshop will have a demo-oriented style. The idea is to allow participants to demonstrate new and interesting features and discuss what they feel is relevant for the dynamic-language community. To participate to the workshop, you can either - submit (before __April 19th 2013__) an article (ACM Tighter Alternate style http://www.acm.org/sigs/publications/proceedings-templates) describing your presentation and/or tool. Articles whose length ranges from 2 to 15 pages will be carefully reviewed by a program committee including but not limited to the organizers. Each accepted paper will be presented for 20 to 30 minutes and be published to the ACM Digital Library (at the option of each author) and the workshop's web site. The submission website is http://www.easychair.org/conferences/?conf=dyla2013. - or give a 10-minute lightning demo of your work. A dedicated session will be allocated for this, provided there is ample time available. A session on pair programming is also planned. People will then get a chance to share their technologies by interacting with other participants. !! Program committee - Carl Friedrich Bolz, Heinrich-Heine-Universität Düsseldorf, Germany (http://cfbolz.de) - Camillo Bruni, Inria Lille-Nord Europe, France (http://rmod.lille.inria.fr/web/pier/team/bruni) - Adrian Kuhn, University of British Columbia, Canada (https://www.cs.ubc.ca/people/adrian-kuhn) - Lukas Renggli, Google, Switzerland (http://www.lukas-renggli.ch/) - Juan Pablo Sandoval Alcocer, University of Chile (http://users.dcc.uchile.cl/~jsandova/) - Bastian Steinert, Hasso-Plattner-Institute, Germany (http://www.bastiansteinert.org) - Veronica Uquillas Gomez, Vrije Universiteit Brussel, Belgium (http://soft.vub.ac.be/~vuquilla/) - Simon Urli, University of Nice-Sophia Antipolis, France (http://www.simonurli.fr/) - Didier Verna, EPITA Research and Development Laboratory, France (http://www.lrde.epita.fr/~didier) - the 4 workshop organizers !! Workshop Organizers - Alexandre Bergel (http://bergel.eu) - Damien Cassou (http://damiencassou.seasidehosting.st) - Jorge Ressia (http://www.jorgeressia.com) - Serge Stinckwich (http://www.doesnotunderstand.org) !! News feed Follow us on twitter: http://twitter.com/dyla2013 For further information: http://rmod.lille.inria.fr/web/pier/Events/Dyla13

12 years, 3 months

1
0
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #190

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/190/>

12 years, 3 months

3
8
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #188

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/188/> ------------------------------------------ Started by upstream project "gtoolkit" build number 27 originally caused by: [URLTrigger] A change within the response URL invocation (log) [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson7168353918600658867.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip image.9hKzH/Pharo-20596.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui Please install the 32bit libraries sudo aptitude install ia32-libs + ./vm.sh Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup [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

12 years, 3 months

2
2
0 0

roassal build

by Tudor Girba

Hi Alex, I added you in the mail notification for the Roassal build: https://ci.inria.fr/moose/job/roassal/ Btw, if anyone wants special notifications for individual builds, please let me know. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

12 years, 3 months

2
1
0 0

statically typed language

by Nicolas Anquetil

Famix can be seen as a statically typed language. For example Invocation is an association between two behaviouralEntities (if I recall correctly). The question that bugs me is why (or how) die-hard smalltalkers [ :-) ] ended-up making that choice? nicolas

12 years, 3 months

3
3
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #184

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/184/> ------------------------------------------ Started by upstream project "gtoolkit" build number 24 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-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson7959591288962466457.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip image.0DT4g/Pharo-20596.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui Please install the 32bit libraries sudo aptitude install ia32-libs + ./vm.sh Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup [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

12 years, 3 months

1
3
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #179

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/179/> ------------------------------------------ Started by upstream project "fame" build number 14 originally caused by: Started by user tudor(a)tudorgirba.com Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson8490378866447075765.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 2.0 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Pharo.changes + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharoVMLatest.sh Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts vm.sh and vm-ui.sh Please install the 32bit libraries sudo aptitude install ia32-libs + ./vm.sh Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup [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

12 years, 3 months

3
4
0 0

Issue 924 in moose-technology: VerveineJ does not export isWrite flags for accesses

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.8 New issue 924 by tu...(a)tudorgirba.com: VerveineJ does not export isWrite flags for accesses http://code.google.com/p/moose-technology/issues/detail?id=924 isWrite should be populated for every access to a variable residing on the left hand side of an assignment. -- 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, 3 months

1
1
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #177

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/177/> ------------------------------------------ Started by upstream project "gtoolkit" build number 22 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-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson6200527060324890121.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 2.0 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Pharo.changes + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharoVMLatest.sh Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts vm.sh and vm-ui.sh Please install the 32bit libraries sudo aptitude install ia32-libs + ./vm.sh Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./vm.sh moose-latest-dev-4.8.image mooseimagesetup [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

12 years, 3 months

1
0
0 0

Broken method GlamourousHealth>>produceReport

by Juraj Kubelka

Hi, there is class GlamourousHealth which apparently is not used. Command GlamourousHealth new produceReport. produces some errors (at least missing message GLMFinder>>list). Is it used? Should we remove it? Or fix it? Thank you a lot, Jura

12 years, 3 months

2
1
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #160

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/160/>

12 years, 3 months

3
8
0 0

#pharoconf #mooseday on twitter

by Tudor Girba

Hi, If you want to tweet/follow what is going on at PharoConf and MooseDay, please use #pharoconf and #mooseday. Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

12 years, 3 months

1
0
0 0

Jenkins build is back to stable : moose-latest-dev-4.8 #168

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/168/>

12 years, 3 months

2
1
0 0

new version of the (old) versionner

by Alexandre Bergel

Hi! In the meantime we have a reliable solution to manage configuration, I have updated http://squeaksource.com/Versionner.html The two most significant changes are: - SmalltalkHub is now supported - Committing a project now produces a stable version (instead of a development) and the most recent baseline is marked as #development. In the meantime to have Versionner2 around, I worked a bit on Versionner to solve some pressing issues with Moose. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 3 months

2
1
0 0

Re: SmalltalkHub and Versionner

by Alexandre Bergel

> If you want to use Versionner on Pharo1.4 with SmalltalkHub, there is no problem. You just need to declare an http repository: > MCHttpRepository > location: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal/main' > user: '' > password: '' Thanks, it works fine >> @Christophe: what is needed to have Versionner working on Pharo 2.0. > > > I still have work to be able to edit existing configurations (add packages, projects, ...) but "old" Versionner commands are still there. > The biggest issue I have with Pharo2 is MetacelloToolBox. > Metacello have been ported to Pharo2 but not MetacelloTests (despite this, it seems to work quite fine). > Metacello Toolbox shipped with Pharo2 is not working because it comes from another branch than Metacello core (different behavior, methods missing). > I planned to work on this point next week with Esteban. > Once done, I just need to check that we do not have issues with announcements (biggest change for Versionner between pharo 1.4 and 2.0). > > To resume, to have the "old" Versionner working, the point is to fix MetacelloToolbox in Pharo2 and check announcements. > I will see with Esteban if we can start this work earlier (have Metacello tests green in Pharo2, update the toolbox). > I hope to have good news on this front very soon because I also decided to give up Pharo 1.4 for dev. We have Pharo2 and now Pharo3 on the road, I cannot use anymore on old version. > > Is it fine for you? Yes, it looks like to be okay. Thanks for this update Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 3 months

1
0
0 0

Re: [Pharo-users] GLMMorphPresentation

by Tudor Girba

Hi, I updated the book with the code that works with the latest Glamour. Also, if you want to see examples, they already exist in the image. For the GLMMorphPresentation, you have an example here: GLMBasicExamples>>morphIcons For further clarifications, you better join the Moose mailing list: moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev Cheers, Doru On Mar 28, 2013, at 3:25 PM, Jesus Nuñez <poissonbreaker(a)gmail.com> wrote: > Hello everyone, > > Does anybody have the full definition of GLMMorphPresentation such > that is usable with Glamour, especifically with the > GLMCompositePresentation?. Actually the only method it defines is > #renderGlamorouslyOn:. > > On the other hand in my installed version of Glamour, GLMTabulator > does not have the #using: method and in the monticello repositories > does not seems to be a version that has it. In Moose Book=>Building > browsers with Glamour=>custom presentations section > (http://www.themoosebook.org/book/internals/glamour/presentations/custom), > it is used for embeed a widget from Morphic. which is exacly what I > need. If somebody knows the version used in the examples please let me > know it. > > Thanks in advance, > Jesus Nuñez > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

12 years, 3 months

1
0
0 0

committing roassal to sthub

by Tudor Girba

Hi Alex, Moose is now loading Roassal from STHub, but in the meantime I see you are committing to squeaksource. I truly see no reason for it. You can use the following regular Monticello repository to commit to STHub: MCHttpRepository location: 'http://www.smalltalkhub.com/mc/ObjectProfile/Roassal/main' user: '' password: '' Please, let's do a little effort to accommodate this transition. Cheers, Doru -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

12 years, 3 months

2
1
0 0

Fwd: [Pharo-project] Postdoc position in Santiago

by Tudor Girba

FYI Begin forwarded message: > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: [Pharo-project] Postdoc position in Santiago > Date: March 30, 2013 2:15:57 PM GMT+01:00 > To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr>, ESUG Mailing list <esug-list(a)lists.esug.org> > Cc: smalltalk-research(a)googlegroups.com > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Dear Friends and Colleagues, > > The Chilean research agency will soon open its postdoc program. Doctors in Computer Science who want to get a rich experience are encouraged to apply. > > Working at the DCC: > ************************ > The position will have to be carried out at the DCC, University of Chile. No teaching duty is expected from you. > Research topics are broad: Testing, Code execution profiling, Visualization, programming languages, Domain Specific Languages, Programming environments, Modeling, Smalltalk, .... Yes, we are open minded people :-) > The postdoc will be inserted in the Pleiad laboratory, meaning she/he will have to interact with our PhD students, help us to guide smart students and engineers, eat chocolate with us. > > > Mini FAQ: > ************************ > - Do I need to know Spanish to apply? No, knowing Spanish is not mandatory at all. Thanks to the Chilean friendliness, even with a deeply broken Spanish coupled with a heavy accent you will have no problem to integrate. > - How long this position is for? You can stay with us up to 3 years with this position. The DCC is growing, meaning there is perspective to get a permanent position (Assistant Professor). > - How often can I expect to return home? This essentially depends on your productivity. Santiago is only 1 night away from Paris: board-in, eat, sleep, board-out, welcome home. > - What does it mean to live in Santiago? If you like sun, fresh fruits, (very) friendly people, high mountains, glaciers, nature, good wine, sushis, exotic places, ... then you will feel happy. > > > Contact: > ************************ > If you have questions, then you can directly contact the author of this email (http://bergel.eu) or meet us at esug, stic, ecoop, esec/fse > > > Links: > ************************ > http://www.conicyt.cl/fondecyt/2013/03/15/concurso-postdoctorado-2014/ > http://pleiad.cl > http://objectprofile.com > http://bergel.eu > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

12 years, 3 months

1
0
0 0

Fwd: GSoC 2013 - Graph-ET

by Tudor Girba

And another proposal. Doru > Graph-ET > > Level: Beginner > Possible Mentor: Alecandre Bergel > Possible second mentor: Tudor Girba > > Description: > The necessity of having a chart-drawing tool integrated with Roassal is increasing day by day. > Graph-ET is a tool that allows the user to create and draw charts with small and expressive Smalltalk instructions. The user may enter a large variety of entries, and the program with parse it to fit the users need. For example, the user may use a domain of words and visualize the length of those words with just two lines of code. > The nice thing about Graph-ET is that it’s very simple to see results also the interface allows the user the play with their charts in a variety of ways. > The idea is having a kind of EyeSee but with Roassal as rendering and adding more power of desition to the user. > > Technical Details: > Graph-ET is a software that needs to draw to work, for that it mainly uses Object Profile’s Roassal to make the drawing and the interaction work. > > Benefit to the Student: > The student will learn a lot more of Smalltalk and Pharo environment. Also he will learn some chart visualization and learn to solve all the problems that come with it. Not to mention learning entry parsing. Mainly he will face with serious and critical decisions that will change the fate of his program, but that will mean significant learning process for him. > > Benefit to the Community: > The community will have the pleasure of making fast charts with small and expressive instructions; this will lead to a more simple way of making and drawing charts. > The users of Roassal will enjoy a tool that fit their needs and that work well with the software they already own. > > -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

12 years, 3 months

1
0
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #147

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/147/>

12 years, 3 months

2
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev