- Pharo-dev - lists.pharo.org

logCr and friends, why deprecation in 30?Â²
by phil＠highoctane.be Oct. 12, 2014

Oct. 12, 2014

Hello I wanted to know why we deprecated logCr etc. TIA Phil

4 4

[Pharo4] just 5 tests failing
by Marcus Denker Oct. 11, 2014

Oct. 11, 2014

Here are all the Failing tests in Pharo4, with a link to the issue tracker. We should try to get it green, not much left to do: Related to NativeBoost: ââââââââââââ ReleaseTest>>#testMethodsWithUnboundGlobals https://pharo.fogbugz.com/f/cases/13982 <https://pharo.fogbugz.com/f/cases/13982> AJx64AssemblerTests>>#testStringOps64Mnemonics https://pharo.fogbugz.com/f/cases/14033 <https://pharo.fogbugz.com/f/cases/14033> Related to GT: âââââââ ReleaseTest>>#testUndeclared https://pharo.fogbugz.com/f/cases/14168 <https://pharo.fogbugz.com/f/cases/14168> ClassTest>>#testClassRespectsPolymorphismWithTrait https://pharo.fogbugz.com/f/cases/14172 <https://pharo.fogbugz.com/f/cases/14172> ReleaseTest ââââââââ ObsoleteTest>>#testFixObsoleteSharedPools https://pharo.fogbugz.com/f/cases/14165 <https://pharo.fogbugz.com/f/cases/14165>

1 0

[pharo-project/pharo-core] e02b61: 40298
by GitHub Oct. 11, 2014

Oct. 11, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e02b61b339b6a93f43e7d05042b8de38244c30c3 https://github.com/pharo-project/pharo-core/commit/e02b61b339b6a93f43e7d050… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-11 (Sat, 11 Oct 2014) Changed paths: M Manifest-Core.package/extension/RBClassEnvironment/instance/smallLintCritics.st A Manifest-Core.package/extension/RBDoNotSendSuperInitializeInClassSideRule/class/uniqueIdentifierName.st A Manifest-Core.package/extension/RBDoNotSendSuperInitializeInClassSideRule/instance/category.st M Manifest-Core.package/extension/RBVariableEnvironment/instance/smallLintCritics.st M Monticello.package/MCPackageManager.class/class/event registration/registerInterestOnSystemChangesOnAnnouncer_.st A Refactoring-Critics.package/RBDoNotSendSuperInitializeInClassSideRule.class/README.md A Refactoring-Critics.package/RBDoNotSendSuperInitializeInClassSideRule.class/definition.st A Refactoring-Critics.package/RBDoNotSendSuperInitializeInClassSideRule.class/instance/accessing/group.st A Refactoring-Critics.package/RBDoNotSendSuperInitializeInClassSideRule.class/instance/accessing/name.st A Refactoring-Critics.package/RBDoNotSendSuperInitializeInClassSideRule.class/instance/initialization/initialize.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script298.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40298.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40298 14213 Replace Announcer>>#on:send:to:s senders in Monticello https://pharo.fogbugz.com/f/cases/14213 14098 allClassesAndTraits significantly different from allClassesAndTraitsDo: https://pharo.fogbugz.com/f/cases/14098 10288 Add a lint rule to check that class initialize method does not calls super initialize https://pharo.fogbugz.com/f/cases/10288 http://files.pharo.org/image/40/40298.zip

1 0

[pharo-project/pharo-core]
by GitHub Oct. 11, 2014

Oct. 11, 2014

Branch: refs/tags/40298 Home: https://github.com/pharo-project/pharo-core

1 0

About ways to participate in community and general negativity
by Esteban Lorenzano Oct. 11, 2014

Oct. 11, 2014

Hi, Iâm writing this because Iâm sad about what is happening in this list. Iâm seeing a lot of general negativity and non constructive ways to discuss things. Iâm also seeing more and more people using Pharo for their particular interests (which is of course a good thing) but less and less people who contribute back to Pharo. Finally, Iâm seeing more frequently an attitude of âcustomerâ, more than the conviction than this, Pharo, is also yoursâ¦ Please people, we (the pharo âcoreâ team) cannot do everything. We do not have the manpower or the resources to hire manpower. We would like, but we just do not have the resources (is already a blessing that we can work on this, for now: INRIA is paying, but what it pays is *research*, not âpharo the languageâ, so this is a collateral advantageâ¦.) So, having an OPEN SOURCE project, with limited resources means that there is a lot of things that depend on the community. It depends on the community not just to fix, but to enlarge the ecosystem in general too. So, I refuse to believe that we cannot be a cool and helpful community. I refuse to believe that general negativity and bad humor can overcome the joy of participating in this collective effort. So, here some recommendations for enhance the way we participate: - Be positive. Just âthis is a s**tâ does not help. Even if it is. - Be propositional. Just âthis is a s**tâ, and not telling what you want/prefer does not help. - Be proactive. Just âthis is a s**tâ, and not report, discuss and (at least time to time) provide a fix/enhancement does not help. In conclusion: not helping does not help :) After all, this is the âpharo-devâ list. I mean, the list of people wanting to participate from this great, community effort. cheers, Esteban, still grateful of belonging to this community

14 58

[ANN] Test Coverage with Hapao
by Alexandre Bergel Oct. 10, 2014

Oct. 10, 2014

Dear all, We are happy to release Hapao2 for Pharo. Ricard Jacas and Alejandro Infante put quite some work on Spy2 (an Ã¼ber cool profiling framework for Pharo) and Hapao2. Hapao2 is about assessing the test coverage of your code and is a major revamp of Hapao1, which was presented a couple of years ago by Vanessa. Hapao2 does not only list covered and uncovered methods, as most test coverage tool on Earth will do. Hapao gives a great visualization to easily navigate in your code, assess its complexity, and give you a great visual output telling its coverage. You need Roassal in your image: Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. (Smalltalk at: #ConfigurationOfRoassal2) load and you need S2py: MCHttpRepository location: 'http://smalltalkhub.com/mc/ObjectProfile/S2py/main' user: '' password: '' New entries will appear in the world menu: You can run the test coverage on : - the class classes you have modified, - on a particular - on a particular class category - on the last class categories you have modified - on the last packages you have modified Here is a portion of a large coverage: A technical description of Hapao may be found on http://bergel.eu/download/papers/Berg12c-HapaoSCP.pdf We are daily using Hapao to help us understand our tests. Cheers, Ricardo, Alejandro & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 11

[ANN] flow: a living full-stack #âframework for the web
by Sebastian Sastre Oct. 10, 2014

Oct. 10, 2014

Hi guys, Iâm sharing slides of my presentation at CampSmalltalkVI2014 http://www.slideshare.net/sebastianconcept/flow-39897704 >From flowâs readme at github: Flow's mission is to provide consultants, startups and software houses with a competitive Smalltalk full-stack framework that allows them to quickly deliver a demo with all the modern html5 features the market expects today (2014). The idea is that they can tactically use this framework to keep momentum up among their prospects and clients and scale things to full successful projects delivered by kickass productive teams or individuals. sebastian o/ blog: http://sebastianconcept.com LinkedIn: http://www.linkedin.com/in/sebastiansastre github: https://github.com/sebastianconcept

9 21

https://ci.inria.fr/pharo-contribution down
by Yuriy Tymchuk Oct. 10, 2014

Oct. 10, 2014

Can someone restart it?

1 1

Re: [Pharo-dev] [amber-lang] Amber 0.13 released!
by H. Hirzel Oct. 10, 2014

Oct. 10, 2014

On 10/10/14, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > These are great news. Congratulations to all! > > Any further info on how deploying works now? Is Amber now creating a single > compiled js file with the whole project? YES. Do amber init to create a project 0.13 style. This creates among a lot of other files a Gruntfile.js (http://gruntjs.com/) With grunt deploy on the command line your project is transmogrifyed into a single JavaScript file called 'the.js'. This means for deployment you only need index.html and the.js 'the.js' contains only JavaScript. No Smtk sources. A crucial feature to actually use Amber in projects. So for me this is a much larger mile stone than the modest 0.13 version number implies. --Hannes > 2014-10-10 14:17 GMT+02:00 Nicolas Petton <petton.nicolas(a)gmail.com>: > >> Hi! >> >> After three months of development we are happy to announce the release >> of Amber 0.13.1 (skipping 0.13.0 for technical reasons). The team has >> once again been busy improving Amber to make it rock more than ever! >> >> With 172 commits, this release brings several important improvements as >> well as the usual bug fixes. >> >> Highlights: >> >> * Reworked cleaner DNU handling in core. >> * `amber init` fully embraced as the way to create new project. >> * Helios IDE is extracted and is now a project on its own. >> * It is included as dev-dependency in any new project by default. >> * Movable data out of index.html: >> * list of production packages in deploy.js; >> * list of development packages in devel.js; >> * project amd mappings in local.amd.json; >> * libraries' amd mappings in lib_directory.amd.json. >> * 'Batteries included' deployment via `grunt deploy`. >> * 0.13.1 because of technical issues w/ 0.13.0 release process. >> >> Commits: https://github.com/amber-smalltalk/amber/compare/0.12.6...0.13.0 >> Issues: >> https://github.com/amber-smalltalk/amber/issues?q=is%3Aissue+is%3Aclosed+mi… >> >> API changes: >> >> - Smalltalk side: >> * String >> asSelector is now String >> asJavaScriptMethodName >> * String >> asJavaScriptSelector is now String >> >> asJavaScriptPropertyName >> * Collection >> ifEmpty:ifNotEmpty: family passes self to ifNotEmpty: >> block >> >> - JavaScript side >> * smalltalk.selector is now smalltalk.st2js >> * smalltalk.convertSelector is now smalltalk.js2st >> * Smalltalk vm is now Smalltalk core >> * boot.js's .vm is now .api >> * amber load sets' .vm is now .api >> * Internal variables smalltalk/globals/_st are now $core/$globals/$recv >> >> Additions: >> >> + smalltalk. >> + accessJavaScript >> + Object >> >> + postMessageTo: >> + postMessageTo:origin: >> + Class >> >> + heliosClass >> + SmalltalkImage >> >> + core >> + amber/boot exports >> + api >> + amber/{devel,deploy,lang} exports >> + api >> >> Removals: >> >> - ProtoObject class >> >> - heliosClass >> - Object class >> >> - heliosClass >> >> I would like to thank Herbert for all his hard work on this release. He >> has done a wonderful job as the new maintainer of Amber. Thank you! >> >> Nicolas >> -- >> Nicolas Petton >> http://nicolas-petton.fr >> >> -- >> You received this message because you are subscribed to the Google Groups >> "amber-lang" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to amber-lang+unsubscribe(a)googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Bernat Romagosa. > > -- > You received this message because you are subscribed to the Google Groups > "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to amber-lang+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

1 0

[pharo-project/pharo-core]
by GitHub Oct. 10, 2014

Oct. 10, 2014

Branch: refs/tags/40297 Home: https://github.com/pharo-project/pharo-core

1 0