January 2014 - Pharo-dev - lists.pharo.org

Punishment as an educational method
by Stephan Eggermont Jan. 10, 2014

Jan. 10, 2014

Igor, The way you describe the role of punishment in education is not in line with current research. Most learning happens trough copying the behavior of others, and punishment has a number of negative consequences on character development, making it a non-suitable instrument. You might want to take a look at the work done by Marshall Rosenberg on non-violent communication. Stephan

9 14

[pharo-project/pharo-core] 8e3f31: 30683
by GitHub Jan. 10, 2014

Jan. 10, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 8e3f31139722d0049780fe83f3687165e734bd0a https://github.com/pharo-project/pharo-core/commit/8e3f31139722d0049780fe83… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-10 (Fri, 10 Jan 2014) Changed paths: M Kernel.package/DateAndTime.class/README.md A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script336.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30683.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30683 12611 Update the DateAndTime class comment a bit https://pharo.fogbugz.com/f/cases/12611 http://files.pharo.org/image/30/30683.zip

1 0

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

Jan. 10, 2014

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

1 0

Pharo3 build is green!
by Marcus Denker Jan. 10, 2014

Jan. 10, 2014

FInallyâ¦ a lot of work went into this, and I thank everyone who helped! We are now running 34134 (together) for the 3 architectures...

5 4

Re: [Pharo-dev] TDD in Core
by Benjamin Jan. 10, 2014

Jan. 10, 2014

For Spec, I actually sent a mail in the mailing list when integrated explaining how to move to the new version :) But indeed, not enough documentation about it is present, this is why I am currently spending time writing some :P (but you already know that :P) I think the overall remark is good :) We should not integrate things in Pharo if they are under tested (Spec included). I think that the next month will be spent on writing more tests or Spec Ben

2 4

[pharo-project/pharo-core] a31261: 30682
by GitHub Jan. 10, 2014

Jan. 10, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: a312614e3ee8376d9f65419fb51906bb310b2d7b https://github.com/pharo-project/pharo-core/commit/a312614e3ee8376d9f65419f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-10 (Fri, 10 Jan 2014) Changed paths: M History.package/NavigationHistory.class/instance/protocol/basicAdd_.st M History.package/NavigationHistory.class/instance/protocol/replaceCurrentWith_.st M Komitter.package/KomitStagingArea.class/class/instance creation/current.st A Komitter.package/KomitStagingArea.class/class/instance creation/currentFilteredBy_.st A Komitter.package/Komitter.class/class/protocol/openAndCommitToMonticelloWorkingCopiesFilteredBy_.st A RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/packageMatchingExtensionName_includingClass_.st M RPackage-SystemIntegration.package/extension/RPackageOrganizer/instance/systemClassRecategorizedActionFrom_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script335.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30682.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Debugger.package/SpecDebugger.class/instance/updating widgets/updateCodeFromContext_.st M Spec-Tools.package/ChangeSorterApplication.class/class/menu/changeSetMenu1NewGeneration_.st M System-Announcements.package/SystemAnnouncement.class/instance/private/setTimeStamp.st Log Message: ----------- 30682 12606 moving classes from A tag B to package A-B broken https://pharo.fogbugz.com/f/cases/12606 12607 Be able to filter dirty packages to display in Komitter https://pharo.fogbugz.com/f/cases/12607 12609 Remove the last non unit test users of TimeStamp https://pharo.fogbugz.com/f/cases/12609 12608 remove unnecesary crLog in SpecDebugger https://pharo.fogbugz.com/f/cases/12608 http://files.pharo.org/image/30/30682.zip

1 0

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

Jan. 10, 2014

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

1 0

[Fwd: New request to join project pharo-contribution]
by btc＠openinworld.com Jan. 10, 2014

Jan. 10, 2014

2 1

How to handle merge conflicts?
by Nicolai Hess Jan. 10, 2014

Jan. 10, 2014

How are merge conflicts handled? If you look at issue 7542 <https://pharo.fogbugz.com/default.asp?7542> there is a merge conflict with the current version and SLICE-Issue-7542-NB-system-example-IgorStasenko.2 The current version usess Smalltalk compiler new ... and igors version uses Smalltalk compiler ... Smalltalk compiler new doesn't work, as Smalltalk compiler is alread an instance of OpalCompiler nicolai

2 1

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann Jan. 10, 2014

Jan. 10, 2014

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

1 0