- Pharo-dev - lists.pharo.org

Jenkins build became unstable: Pharo-2.0-Tests Â» run 1,vm,win #258
by no-reply＠ci.inria.fr July 10, 2013

July 10, 2013

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=win/2…>

1 1

More manpower needed for reviewing fixes...
by Marcus Denker July 10, 2013

July 10, 2013

Hi, We mananged to nearly review (and often integrate) almost all pending fixes and enhancements. There are 4 issues left: https://pharo.fogbugz.com/f/filters/36/Review It would be nice if more people would be involved. If *you* don't comment, it might be we will do the wrong thing? Marcus

1 0

sunit failures vs errors
by Torsten Bergmann July 10, 2013

July 10, 2013

Camillo wrote: >Does anybody here distinguish failures and errors for real when doing TDD? Yes, it has a special meaning AND is very helpfull - ESPECIALLY when you start with tests first (XPStyle): Usually one writes the tests and then you try to get them from red over yellow to green: red: there is a real error, for instance a message is not yet implemented (maybe only the test was written and one uses the debugger and the "Create" functionality to create the calls) yellow: the basic calls are there/messages implemented and working (no DNU) but an expectation is not yet met since an assertion fails green: everything is OK Or to quote Kent Beck: http://www.xprogramming.com/testfram.htm <quote> "Failures and Errors The framework distinguishes between failures and errors. A failure is an anticipated problem. When you write tests, you check for expected results. If you get a different answer, that is a failure. An error is more catastrophic, a error condition you didn't check for." </quote> Please keep it separated, it is very usefull. >Besides the complexity added to the testing framework it is a burden for newcomers. Learning about Pragmas, Methods, Classes, Debugger, marking expected failures, ... is also a burden for newcomers. Will we throw them out? No! SUnit is still really simple and a pleasure to work with! Thx Torsten

2 1

OSDC.fr: 5th Open Source Developers Conference in France
by Damien Cassou July 9, 2013

July 9, 2013

Call for Papers 5th Open Source Developers Conference in France Montrouge Beffroi cultural centre, Paris, October 4 & 5, 2013 OSDC.fr objective is to gather French speaking developers from different communities around innovative technologies. After two editions on our own, we are since 2011 associated to Open World Forum and its numerous partners in order to provide the best experience to our attenddees. For the 5th edition of this conference, we invite you to gather the communities dedicated to programming based on free/libre languages such as Perl, Python, Ruby, PHP, Smalltalk & much more. The aim is to learn by exploring the universe of all languages, for many concepts and techniques aren't tied to a specific environment, and therefore allow cross-pollinations. So we invite you to join us by taking part in OSDC.fr, either by submitting a talk proposal <http://act.osdc.fr/osdc2013fr/newtalk> (preferably in French, but English is acceptable), or simply by joining us on October 4 & 5, 2013, at at Montrouge Beffroi cultural centre. Entrance is free and everyone is welcome. Talks can last 25 or 45 minutes. We'll also have a lightning talks session, where talks are limited to 5 minutes max. Here is a non-exhaustive list of possible subjects: - Themes related to programming languages such as Perl, PHP, Python, Ruby, Erlang, JavaScript, node.js, Lua, Scala, Clojure, Groovy, Haskell, C, C++, Smalltalk, Java, etc. - Dynamic compilation - Interpreters and virtual machines (LLVM, JVM, CLR, Parrot, etc) - Development tools - Development best practices - Programming experience feedback - Libraries - Making of innovative languages and their implementation - Software maintenance - Integration of different languages - Teaching techniques - Modern techniques of system administration, industrialization, distributed infrastructure (*cloud*) - Big Data, OpenData Key dates: - Deadline for submitting a talk : September 6th, 2013 - Final schedule : September, 2013 - OSDC.fr conference : October 4 & 5, 2013

1 0

[ANN] Pharo VM now building on Pharo 2.0
by Esteban Lorenzano July 9, 2013

July 9, 2013

Hi, Today I migrated the jenkins jobs for building the PharoVM to 2.0. Objectively, nothing changes for the VM users, but is important to move the infrastructure according to our yearly releases. For those who are creating their own VMs and stuff, now you can move to 2.0 too, there is no need to keep using 1.4. jenkins builds are, as always, at: https://ci.inria.fr/pharo/view/VM/job/PharoVM/ (windows build is broken due a know problem in the windows slave, not related with the VM build itself) Thanks Guille for doing the work and Camillo for the support :) Esteban

2 2

[ANN] Amber 0.11.0 released!
by Nicolas Petton July 9, 2013

July 9, 2013

Amber 0.11.0 released! * About the release Three months have passed and we are happy to announce the release of Amber 0.11.0! Some numbers about this release: 433 commits by 13 committers, increasing the number of core committers to 25. 50 unit tests were added to the kernel, bringing us to 313 unit tests in total. Since the last release 60 issues were closed, bringing us to 499 issues closed. This release includes a lot of bug fixes, improvements to the CLI, as well as a preview of the next IDE, named Helios. Amber now also uses a CI server [1]. To try the Helios, the new IDE, open the helios.html page, or evaluate in any other amber page `amber.loadHelios()`. The compiler also received some improvements, especially regarding message send optimisations and super sends. Here's the list of commits and closed issues: https://github.com/amber-smalltalk/amber/commits/master https://github.com/amber-smalltalk/amber/issues?direction=desc&sort=updated… There is a lot more to come with Helios, a stepping debugger based on the AST is in progress and currently in the 'debugger' branch on GitHub. * Installing Amber from NPM To install amber from NPM, run npm install amber * Migration from Amber 0.10.0 Amber compiled code should be compatible with Amber 0.10.0, but recompiling is needed in order to get contexts working: Compiler new recompile: (Package named: 'MyPackage') classes. (Package named: 'MyPackage') commit * API changes 0.11.0: * AnnouncementSubscription use #valuable: instead of #block: (deprecated) * AbstractCodeGenerator inherits from Object, not NodeVisitor * Object>>printString * replace >>printString with >>printOn: * replace >>storeString with >>printString * PackageLoader is now PackageHandler (>>commit: >>setupPackagenamed:prefix: >>ajaxPutAt:data: * Package>>fetch: is now Package>>load: * Package>>fetch:prefix: is now Package>>load:prefix: * Queue>>front replaced by Queue>>next * Queue>>frontIfAbsent: replaced by Queue>>nextIfAbsent: * Queue>>back: replaced by Queue>>nextPut: * smalltalk.addMethod() does not use explicit JS selector * JSObjectProxy>>canForwardMessage: replaced by use of JSObjectProxy>>lookupProperty: with asJavaScriptSelector * JSObjectProxy>>forwardMessage: replaced by explicit JSObjectProxy>>forwardMessage:withArguments: * String>>asJavaScriptSelector moved to Kernel-Objects package + Object>>asString + Object>>putOn: + String>>isVowel + Collection>>putOn: + CharacterArray>>putOn: + Stream>><< + Stream>>write + SequenceableCollection>>newStream + SequenceableCollection>>readStream + SequenceableCollection>>stream + SequenceableCollection>>streamClass + SequenceableCollection>>writeStream + Collection>>isImmutable + Stream>>nextPutString: + StringStream>>nextPutString: + JSStream>>nextPutClassRefFunction: + String>>crlfSanitized + inlined Block now also responds to >>value: + Parser: split literal into runtimeLiteral and parseTimeLiteral + Parser: write #(4 #(5 6 #()) 7) as #(4 (5 6 ()) 7) + Parser: write #(#on:do: #Object) as #(on:do: Object) + Parser: Symbols for binarie selectores + Package>>commit + AIContext>>initializeLocals + ASTInterpreter>>withBlockContext: + smalltalk.allSelectors() + Object>>isCompiledMethod + Object>>isPackage + Object>>isBehavior + ClassMoved Announcemen class + Behavior>>includesBehavior: + Environment>>classes + Environment>>allSelectors + Environment>>removeProtocol: + Environment>>renameProtocol:to:in: + CompiledMethod>>protocol: + Smalltalk>>globalJsVariables + Smalltalk>>addGlobalJsVariable: + Smalltalk>>deleteGlobalJsVariable: - Object>>storeOn: - Object>>log:block: - Object>>printNl - Compiler-IR.st >>javascriptSelector - Compiler-IR.st >>nextPutVar: - Kernel-Collections.st >>asSuperSelector - Collection>>readStream - Collection>>stream - Collection>>streamClass - Collection>>writeStream - Symbol class (replaced with String) - IRInlinedNonLocalReturn class - IRInlinedSend>>nonLocalReturnInliner - IRNonLocalReturnInliner class - Package>>dependencies - Package>>dependencies: - Package>>properties - Package>>jsProperties - Package>>jsProperties: - Package>>propertiesAsJSON - Package>>propertyAt: - Package>>propertyAt:ifAbsent: - Package>>propertyAt:put: - Browser>>ajaxPutAt:data: We hope you join us in developing Amber and having fun! Fork at github, join in #amber-lang on freenode and hop onto the mailing list. The Amber crew [1] https://travis-ci.org/amber-smalltalk/amber

2 1

[update 3.0] #30260
by Marcus Denker July 9, 2013

July 9, 2013

30260 ----- 11150 Reshaping a class does not properly propagate the modification to the subclasses of its subclasses https://pharo.fogbugz.com/f/cases/11150 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Slot-MarcusDenker.344.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/SlotTests-MarcusDenker.41.diff

2 1

How is GlorpOpenDBXDriverPoolingDriver supposed to work?
by Mariano Martinez Peck July 9, 2013

July 9, 2013

Hi guys, There is something I don't understand. The idea with GlorpOpenDBXDriverPoolingDriver is that it takes care of opening the connections and have a pool, right? Now...I am at the glorp side...each time I want to do something I instantiate a GlorpSession. Of course, I don't want to send #login to this session because that's what the pool would do if necessary. So say I just send a query with the session. I get a DNU because 'databaseDriver' is nil. As you can see, databaseDriver is set in PharoDatabaseAccessor >> loginIfError:. of course, if I send #login or #loginIfError before doing the query the pool "works"...but...I am opening a connection for each query. So I don't understand how this is supposed to work. How should I manage my Glorp sessions with this pool? Thanks, -- Mariano http://marianopeck.wordpress.com

1 1

Has anyone used a connection pool with glorp and postgres native driver?
by Mariano Martinez Peck July 9, 2013

July 9, 2013

Because I need this and I have some ideas. There are many way to implement this (integrating Glorp and the native driver for this) that I would like to see if someone already did something. So...anyone? Thanks, -- Mariano http://marianopeck.wordpress.com

1 1

[ANN] Pharo Launcher
by Damien Cassou July 9, 2013

July 9, 2013

Dear list, Erwan and I are proud to announce the first release of the Pharo Launcher, a cross-platform application that - lets you manage your Pharo images (launch, rename, copy and delete); - lets you download image templates (i.e., zip archives) from many different sources (Jenkins, files.pharo.org, and your local cache); - lets you create new images from any template. A screenshot is attached to this email. The idea behind the Pharo Launcher is that you should be able to access it very rapidly from your OS application launcher. As a result, launching any image is never more than 3 clicks away. Download: https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=b… Please report bugs on the 'Launcher' project at https://pharo.fogbugz.org You can contribute to this project. All classes and most methods are commented. There are unit tests. Please contribute! Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher Things you can do to improve the system: - check if a template is already downloaded before downloading it - add a preference mechanism (for, e.g., quit after launch, definition of your own template groups, location of downloaded templates and images) - put the launcher in the Pharo Ubuntu package so that the launcher becomes a registered appliation of the system (https://launchpad.net/~pharo/+archive/stable) - make sure the pharo launcher does not load your personal scripts (like fonts and MC configuration) - add a toolbar to enhance the discoverability of the features (currently everything is in contextual menus) - make sure rename and copy actions propose default values - make sure no debugger pops up when a user press cancels or enter an invalid name - propose multiple kinds of sorting (last used, most frequently used, alphabetically on the name) - give some information about each template (build date, pharo version) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

5 6