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

Re: [Pharo-dev] Punishment as an educational method

by Igor Stasenko

On 9 January 2014 22:50, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > I agree. I don't believe Igor intended to mean punishment, even if > punishment is what he said. He is not native to the English language or > idioms. > > When he spoke of the child, he spoke of allowing the consequence of the > child's actions to occur. Not that the parent punished the child. This is > very valid and in my opinion often preferred. You can explain and teach. > But at some point the individual will make a choice to abide by what was > taught or explained or to possibly test the teaching and see if it is true. > Children do this all the time. Their prime thought is to test what they are > taught and to challenge it. Only after a sufficient number of confirmations > do they give a certain amount of implicit trust to the teacher or parent. > > Fire in Igor's example is a common example for teaching children. Parent's > who childproof their home generally do their children and themselves a > disservice. I am a father of 10 children, 28-4 years of age. I have never > had a child burn themselves on a heater, or hurt themselves significantly > falling down the stairs. > > Consequences, good and bad are a prime means of learning. > > Exactly. I tried to say the same, but using less words.. because i thought this is a common knowledge and i don't have to be so verbose giving it as an example/argument in the discussion. > But consequences should be appropriate for action. If we have within our > power, and sometimes we do and sometimes we don't, have the ability to > determine the consequences, then we should do so in consideration of what > we are protecting, rewarding, punishing. How do we want the standard of > behavior to be in that situation. > > Just my thoughts. > > Back to lurking. > > Jimmie > > > > > On 01/09/2014 03:30 PM, Sven Van Caekenberghe wrote: > >> I don't think Igor meant punishment as a tool, but rather experience >> something negative for yourself. >> >> I am sure that if you think back at your own development, there were >> instances where you did not listen to adults warning you and only learned >> certain things the hard way. >> >> Anyway, we're getting way off topic ;-) >> >> On 09 Jan 2014, at 22:25, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> 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 >>> >> >> > > -- Best regards, Igor Stasenko.

Jan. 10, 2014

Re: [Pharo-dev] Punishment as an educational method

by Igor Stasenko

On 9 January 2014 22:30, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I don't think Igor meant punishment as a tool, but rather experience > something negative for yourself. > > right.. punishment as consequence of your own deeds, but not punishment as a tool, which you using against someone. > I am sure that if you think back at your own development, there were > instances where you did not listen to adults warning you and only learned > certain things the hard way. > > why hard way? i think it is most easy way: you can explain for years to people why they have to be careful with fire.. instead of letting them to verify it and very fast and easy get to the same conclusion. > Anyway, we're getting way off topic ;-) > > On 09 Jan 2014, at 22:25, Stephan Eggermont <stephan(a)stack.nl> wrote: > > > 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 > > > -- Best regards, Igor Stasenko.

Jan. 10, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 10, 2014

[pharo-project/pharo-core] a31261: 30682

by GitHub

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

Jan. 10, 2014

Re: [Pharo-dev] [Fwd: New request to join project pharo-contribution]

by Marcus Denker

On 10 Jan 2014, at 02:31, btc(a)openinworld.com wrote: > I have received a couple of these messages. Should I be getting these? > Yes, everyone is getting themâ¦ but I think not anymore, as we made job creation now possible for everyone and therefor we restricted admin role to just a view, and only those get the message. > cheers -ben > > -------- Original Message -------- > Hi Ben Coman, > > You just received a join request. Etien Anne want to join pharo-contribution. > You can accept or deny this request using the following links : > Accept > Deny > > Regards, > Support team. >

Jan. 10, 2014

Re: [Pharo-dev] How to handle merge conflicts?

by Marcus Denker

On 09 Jan 2014, at 21:48, Nicolai Hess <nicolaihess(a)web.de> wrote: > How are merge conflicts handled? > Someone (the author or someone else), needs to load the SLICE, fix the conflict and then save a new version. > If you look at issue 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 > Yes, it is "Smalltalk compilerâ. In the past there was just #compilerClass. I added #compiler because this allows us to very easily parametrize this object. For that of course I changed all the old users of #compilerClass to use #compiler instead, and added the API that was on the class side of Compiler to the instance side, too. (most calls of #compilerClass already called #new, thought). This now is quite nice, I think. e.g. on the class side of instruction stream, we now have compiler "The JIT compiler needs to trap all reads to instance variables of contexts. As this check is costly, it is only done in the long form of the bytecodes, which are not used often. In this hierarchy we force the compiler to alwasy generate long bytecodes" ^super compiler options: #(+ optionLongIvarAccessBytecodes) making it explicit that the whole hierarchy is compiled differently. Marcus

Jan. 10, 2014

Re: [Pharo-dev] Pharo3 build is green!

by Noury Bouraqadi

I tested Pharo 3.0 yesterday, and I love it. Kudos for the great job. Noury On 10 janv. 2014, at 07:18, Luc Fabresse wrote: > Congrats ;-) > > #Luc > > > 2014/1/10 Tudor Girba <tudor(a)tudorgirba.com> > Thank you! > > Doru > > > On Thu, Jan 9, 2014 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > FInallyâ¦ a lot of work went into this, and I thank everyone who helped! > > We are now running 34134 (together) for the 3 architectures... > <Green.png> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury --

Jan. 10, 2014

Re: [Pharo-dev] Pharo3 build is green!

by Luc Fabresse

Congrats ;-) #Luc 2014/1/10 Tudor Girba <tudor(a)tudorgirba.com> > Thank you! > > Doru > > > On Thu, Jan 9, 2014 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> FInallyâ¦ a lot of work went into this, and I thank everyone who helped! >> >> We are now running 34134 (together) for the 3 architectures... >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Jan. 10, 2014

Re: [Pharo-dev] Pharo3 build is green!

by Tudor Girba

Thank you! Doru On Thu, Jan 9, 2014 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > FInallyâ¦ a lot of work went into this, and I thank everyone who helped! > > We are now running 34134 (together) for the 3 architectures... > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 10, 2014

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub

by Torsten Bergmann

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

Jan. 10, 2014