June 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 513ba4: 50136

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 513ba4a1f19a77826812da1c2de667b2a4bbe998 https://github.com/pharo-project/pharo-core/commit/513ba4a1f19a77826812da1c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-26 (Fri, 26 Jun 2015) Changed paths: A Jobs.package/CurrentJob.class/README.md A Jobs.package/CurrentJob.class/definition.st M Jobs.package/Job.class/README.md M Jobs.package/Job.class/class/accessing/current.st R Jobs.package/Job.class/class/examples/example.st R Jobs.package/Job.class/class/examples/example2.st A Jobs.package/Job.class/class/examples/exampleCurrentValue.st A Jobs.package/Job.class/class/examples/exampleProgress.st A Jobs.package/Job.class/instance/accessing/announcer.st A Jobs.package/Job.class/instance/accessing/lookup_ifNone_.st R Jobs.package/Job.class/instance/notification-handling/handleJobProgress_.st R Jobs.package/Job.class/instance/notification-handling/handleJobStart_.st R Jobs.package/Job.class/instance/private/basicProgress_.st A Jobs.package/Job.class/instance/private/parent.st M Jobs.package/Job.class/instance/private/prepareForRunning.st R Jobs.package/Job.class/instance/progress/announcer.st M Jobs.package/Job.class/instance/progress/progress_.st M Jobs.package/Job.class/instance/running/run.st A Jobs.package/JobAnnouncement.class/README.md A Jobs.package/JobAnnouncement.class/class/instance creation/on_.st A Jobs.package/JobAnnouncement.class/definition.st A Jobs.package/JobAnnouncement.class/instance/accessing/job.st A Jobs.package/JobAnnouncement.class/instance/accessing/job_.st A Jobs.package/JobAnnouncement.class/instance/accessing/max.st A Jobs.package/JobAnnouncement.class/instance/accessing/min.st A Jobs.package/JobAnnouncement.class/instance/accessing/progress.st A Jobs.package/JobAnnouncement.class/instance/accessing/title.st M Jobs.package/JobChange.class/definition.st R Jobs.package/JobDetector.class/README.md R Jobs.package/JobDetector.class/definition.st R Jobs.package/JobDetector.class/instance/handling/handle_.st M Jobs.package/JobEnd.class/definition.st R Jobs.package/JobNotification.class/README.md R Jobs.package/JobNotification.class/definition.st R Jobs.package/JobNotification.class/instance/handling/handle_.st R Jobs.package/JobProgress.class/README.md R Jobs.package/JobProgress.class/class/instance-creation/progress_.st R Jobs.package/JobProgress.class/class/instance-creation/title_.st R Jobs.package/JobProgress.class/class/instance-creation/title_progress_.st R Jobs.package/JobProgress.class/definition.st R Jobs.package/JobProgress.class/instance/accessing/progress.st R Jobs.package/JobProgress.class/instance/accessing/progress_.st R Jobs.package/JobProgress.class/instance/accessing/title.st R Jobs.package/JobProgress.class/instance/accessing/title_.st R Jobs.package/JobProgress.class/instance/handling/handle_.st M Jobs.package/JobStart.class/definition.st R Jobs.package/JobStartNotification.class/README.md R Jobs.package/JobStartNotification.class/class/instance creation/on_.st R Jobs.package/JobStartNotification.class/definition.st R Jobs.package/JobStartNotification.class/instance/accessing/job.st R Jobs.package/JobStartNotification.class/instance/accessing/job_.st R Jobs.package/JobStartNotification.class/instance/handling/handle_.st A KernelTests.package/JobTest.class/instance/tests/testJobAnnouncements.st R KernelTests.package/JobTest.class/instance/tests/testProgressNotification.st R KernelTests.package/JobTest.class/instance/tests/testProgressNotificationChildJob.st A Reflectivity-Tests.package/MetaLinkTest.class/instance/tests - simple/testCotrolInstead.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceSimple.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitNode_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/analyseForLinks_.st A Reflectivity.package/extension/RBProgramNode/instance/hasMetalinkInstead.st A Reflectivity.package/extension/RBProgramNode/instance/insteadHooks.st A Reflectivity.package/extension/RBProgramNode/instance/insteadLinks.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50135.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50136.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50135.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50136.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UIManager.package/extension/Collection/instance/do_displayingProgress_every_.st Log Message: ----------- 50136 15840 RF: add support for #instead links https://pharo.fogbugz.com/f/cases/15840 15833 Remove Notifications from Job implementation https://pharo.fogbugz.com/f/cases/15833 http://files.pharo.org/image/50/50136.zip

June 26, 2015

[pharo-project/pharo-core]

by GitHub

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

June 26, 2015

how to replace text in files

by Tudor Girba

Hi, How would you replace a piece of text in a file with another one and persist the change on disk? Right now, I have: file := 'path' asFileReference contents := file readStreamDo: #contents. newContents := contents copyReplaceAll: 'PATTERN' with: 'TARGET'. file ensureDelete; writeStreamDo: [ :s | s nextPutAll: newContents asString ] Any idea to make this more concise? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

June 26, 2015

Re: [Pharo-dev] [Pharo-users] Giving skype lectures to cameron students

by serge.stinckwich＠gmail.com

With YaoundÃ© ? Yes we have the same problem in my research team where we work daily with people from Cameroun and Senegal. Most of the time, the students are using Internet in a cafÃ© because at University the bandwidth is not good ... Sent from my iPhone > On 25 juin 2015, at 19:49, stepharo <stepharo(a)free.fr> wrote: > > Hi > > we are giving some skype lectures to cameron students with damien. > A fun experience, because the network is so bad that I cannot demo Pharo interactively. > But I'm learning from it. > > Stef >

June 26, 2015

Re: [Pharo-dev] Probably Metacello sucksâ¦

by stepharo

But we need a working configuration for a Thales project so it has to work. Stef Le 25/6/15 20:59, Yuriy Tymchuk a Ã©crit : > Hi Stef. > > Yes, there is âjenkinsâ baseline, but after some time it stopped working. The problem is that JB cannot really maintain configuration of the projects developed by other people, because he is not aware what has changed and needs significantly more time than the dev that work with it. > > Uko > >> On 25 Jun 2015, at 20:14, stepharo <stepharo(a)free.fr> wrote: >> >> Yuriy >> >> can you check with JB because he told me that he wrote a configuration for Wooden. >> >> Stef >> >> Le 12/6/15 13:48, Yuriy Tymchuk a Ã©crit :Yuri >>> Just a quick side note: >>> >>> my initial email was kind of a troll. Because when you ask for something about roassal and 3D, you get a reply about Roassal-Woden i.e. Roassal3D is not supported anymore, you have to use Woden instead. Now when you have to load Woden, you canât so you have to use the uber-long script on the Woden project page instead of conf. Thatâs why Iâve joked about using scripts instead of Metacello. >>> >>> Uko >>> >>> >>> >>>> On 12 Jun 2015, at 12:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> >>>>> On 12 Jun 2015, at 10:40, Stephan Eggermont <stephan(a)stack.nl> wrote: >>>>> >>>>> On 12-06-15 10:24, Esteban Lorenzano wrote: >>>>>> it was just an example of why using #stable in project dependences is a bad idea :) >>>>>> you made #releaseN.N to fix precisely my point. >>>>>> there should exist something like I say â3.*â >>>>> #'release3' always refers to the latest stable 3.*.*.* >>>> I know :) >>>> Iâm just saying that I would like to have that as a standard mechanism, not a convention. >>>> >>>> Esteban >>>> >>>>>> Iâm sorry for being obvious here, I know this is knownâ¦ problem is that Iâve seen far too much the use of metacello not for doing releases but to handle commits. >>>>> I think it mostly has to do with the need to have exact reproducible builds (which is different from the need to have working software). >>>>> That would be better handled with a (separate) SnapshotOf class i.m.o. >>>>> >>>>> Stephan >>>>> >>>>> >>>>> >>> >> > >

June 25, 2015

Re: [Pharo-dev] Probably Metacello sucksâ¦

by Yuriy Tymchuk

Hi Stef. Yes, there is âjenkinsâ baseline, but after some time it stopped working. The problem is that JB cannot really maintain configuration of the projects developed by other people, because he is not aware what has changed and needs significantly more time than the dev that work with it. Uko > On 25 Jun 2015, at 20:14, stepharo <stepharo(a)free.fr> wrote: > > Yuriy > > can you check with JB because he told me that he wrote a configuration for Wooden. > > Stef > > Le 12/6/15 13:48, Yuriy Tymchuk a Ã©crit :Yuri >> Just a quick side note: >> >> my initial email was kind of a troll. Because when you ask for something about roassal and 3D, you get a reply about Roassal-Woden i.e. Roassal3D is not supported anymore, you have to use Woden instead. Now when you have to load Woden, you canât so you have to use the uber-long script on the Woden project page instead of conf. Thatâs why Iâve joked about using scripts instead of Metacello. >> >> Uko >> >> >> >>> On 12 Jun 2015, at 12:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> >>>> On 12 Jun 2015, at 10:40, Stephan Eggermont <stephan(a)stack.nl> wrote: >>>> >>>> On 12-06-15 10:24, Esteban Lorenzano wrote: >>>>> it was just an example of why using #stable in project dependences is a bad idea :) >>>>> you made #releaseN.N to fix precisely my point. >>>>> there should exist something like I say â3.*â >>>> #'release3' always refers to the latest stable 3.*.*.* >>> I know :) >>> Iâm just saying that I would like to have that as a standard mechanism, not a convention. >>> >>> Esteban >>> >>>>> Iâm sorry for being obvious here, I know this is knownâ¦ problem is that Iâve seen far too much the use of metacello not for doing releases but to handle commits. >>>> I think it mostly has to do with the need to have exact reproducible builds (which is different from the need to have working software). >>>> That would be better handled with a (separate) SnapshotOf class i.m.o. >>>> >>>> Stephan >>>> >>>> >>>> >>> >> >> > >

June 25, 2015

Re: [Pharo-dev] Probably Metacello sucksâ¦

by stepharo

Yuriy can you check with JB because he told me that he wrote a configuration for Wooden. Stef Le 12/6/15 13:48, Yuriy Tymchuk a Ã©crit :Yuri > Just a quick side note: > > my initial email was kind of a troll. Because when you ask for something about roassal and 3D, you get a reply about Roassal-Woden i.e. Roassal3D is not supported anymore, you have to use Woden instead. Now when you have to load Woden, you canât so you have to use the uber-long script on the Woden project page instead of conf. Thatâs why Iâve joked about using scripts instead of Metacello. > > Uko > > > >> On 12 Jun 2015, at 12:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >>> On 12 Jun 2015, at 10:40, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> On 12-06-15 10:24, Esteban Lorenzano wrote: >>>> it was just an example of why using #stable in project dependences is a bad idea :) >>>> you made #releaseN.N to fix precisely my point. >>>> there should exist something like I say â3.*â >>> #'release3' always refers to the latest stable 3.*.*.* >> I know :) >> Iâm just saying that I would like to have that as a standard mechanism, not a convention. >> >> Esteban >> >>>> Iâm sorry for being obvious here, I know this is knownâ¦ problem is that Iâve seen far too much the use of metacello not for doing releases but to handle commits. >>> I think it mostly has to do with the need to have exact reproducible builds (which is different from the need to have working software). >>> That would be better handled with a (separate) SnapshotOf class i.m.o. >>> >>> Stephan >>> >>> >>> >> > >

June 25, 2015

Re: [Pharo-dev] added a BaselineCommandLineHandler to the Pharo40Inbox

by stepharo

thanks paul. We will have a look. Stef Le 19/6/15 02:36, Paul DeBruicker a Ã©crit : > The issue is: > > > https://pharo.fogbugz.com/f/cases/15802/Add-BaselineCommandLineHandler-to-l… > > > The slice with the code is in the inbox. > > > I hven't looked at Pharo 5 but would assume that this would drop right in unless there have been changes to CommandLineHandler & friends. >

June 25, 2015

Re: [Pharo-dev] the importance of your story

by stepharo

Yes doru this is reasoning in me and I should restart to work for real on Coral because we could change the face of scripting languages. Le 25/6/15 13:53, Max Leske a Ã©crit : > Thanks Doru! > >> On 25 Jun 2015, at 13:39, Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> I gave last week a talk at NDC Oslo on "Don't demo facts. Demo >> stories!". While the talk is less technical, I did exemplified the >> message by demoing Spotter in comparison with the search support from >> Eclipse. >> >> There are several things I would like to emphasize. >> >> I compared our solution with an "industry standard" one. We often >> think our system as being niche and perhaps not mature enough. We >> need to change that perception about our work. We build state of the art. >> >> One thing that I did not mention explicitly in the talk is the size >> of the implementation. The Spotter implementation is 3500 lines of >> code -- and that it is so large because it currently comes with its >> own widgets. Furthermore, the extensions average 8 lines per custom >> processor (including the method header and the pragma). This is >> orders of magnitude smaller than what is typically out there, and it >> is precisely the reason why we can compete even if we are fewer. >> >> But, to get out there and compete we have to set that high goal for >> ourselves. For example, with GT we do not want to compete. We want to >> outcompete. So can you. >> >> While details are important, high goals require us to get away from >> those details. Only polishing details will tend to limit you to >> incremental improvements. We need to jump from time to time. But, >> these jumps are hard. On the one hand, it is hard to find the right >> jump and convince people to jump with you. On the other hand, they >> are hard to predict. For example, Spotter would have not been >> predictable one year ago. >> >> Yet, dry goals are not enough to keep us going. We need stories that >> make us dream. And the beauty is that Pharo breaths such a story. We >> should not limit ourselves to that story only. For example, with GT >> we want to reinvent the developer experience by making the developer >> be able to mold visual tools to her context because that is the only >> effective way to build sustainable systems. This little point of view >> will turn the IDE upside down, and this is only possible in a system >> like Pharo. >> >> Choose your high goal and tell its story through the system that you >> build. And remember that Pharo already offers a beautiful story to >> start from. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >

June 25, 2015

Re: [Pharo-dev] Pharo 4.0 crash

by stepharo

Le 25/6/15 11:59, Sabine Manaa a Ã©crit : > Hi Steph, > > dev: Mac-iOS, here is the crashed image. Thanks We experienced some crashes too but have no idea where they come from. > prod: windows, not yet this problem > > Regards > Sabine > > 2015-06-24 21:07 GMT+02:00 stepharo [via Smalltalk] <[hidden email] > </user/SendEmail.jtp?type=node&node=4834009&i=0>>: > > Hi sabina > > on which OS are you? > > Stef > > Le 19/6/15 09:31, Sabine Manaa a Ã©crit : > > > Hi, > > > > I have crashes from time to time. Are they useful for you? > > If yes, where is the vm-dev list? > > > > Regards > > Sabine > > > > > > > > -- > > View this message in context: > http://forum.world.st/Pharo-4-0-crash-tp4832475p4833169.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > > > ------------------------------------------------------------------------ > If you reply to this email, your message will be added to the > discussion below: > http://forum.world.st/Pharo-4-0-crash-tp4832475p4833940.html > To unsubscribe from Pharo 4.0 crash, click here. > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > > > > > ------------------------------------------------------------------------ > View this message in context: Re: Pharo 4.0 crash > <http://forum.world.st/Pharo-4-0-crash-tp4832475p4834009.html> > Sent from the Pharo Smalltalk Developers mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at > Nabble.com.

June 25, 2015