- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

by Alexandre Bergel

>> âI thought that Pharo tech talk was only for core Pharo technologies. > > Why? We did have e.g. a talk about Roassal already. Keep in mind that Alexâ lecture uses > Pharo as the programming language to implement the AI stuffâ¦ Yes, I will do - a lot of programming in Pharo - a lot of visualizations in Roassal There will be some theoretical parts, that I will try to pre-digest the best I can. Alexandre

Aug. 24, 2017

Re: [Pharo-dev] [Ann] PharmIDE is renamed to TelePharo and moved to github

by Ben Coman

On Wed, Aug 23, 2017 at 4:52 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > In the team we finally agreed on the end name for project. It is now > TelePharo. > Prefix "tele" means some action on or by distance. And this is what the > project is about: to work remotely with Pharo images. > Not all people like this name. But there are no name which was good for > everybody. So it was decision. And we now continue with it. > The naming of this drew a fantastic amount of suggestions. TelePharo is fine, and good to have a concrete decision to go forward with. thx Denis. cheers -ben > > With new name project was moved to github repository > https://github.com/dionisiydk/TelePharo with all dependencies. Feel free > to fork and report bugs. > > You can find more details in my blog http://dionisiydk.blogspot.fr/ > 2017/08/pharmide-is-renamed-to-telepharo-and.html. > > Best regards, > Denis >

Aug. 24, 2017

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

by Ben Coman

On Tue, Aug 22, 2017 at 11:51 PM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Hi Marcus, > > Please, do not relaunch the build if there is a test failure. That > simply does not fix the problem, it just adds noise. There are two > problems: > > 1) we have some sporadic test failures (sometimes network, sometimes > some mutex or delay issues). They do not happen all the time and > that's why sometimes there is one or two failing tests. We should > detect these tests and fix them to be more robust > > >> Note, is there some brave soul that would like to take action here? > > 2) sometimes the vm crashes while running the tests. We should detect > the bug and fix it. > > >> Note, is there some brave soul that would like to take action here? > > Now, if we are integrating a fix, this means that the PR was **already > validated as green**. That means that the integrated commit can be > bootstrapped and tested (and all tests are green). > > Moreover, running the tests after integration (and its build color) > does not change the integration in itself: the commit was already > merged and pushed into the main branch, so even if it fails always, > it's too late. I thought the idea of CI was to merge into the main branch *after* the tests pass. Why is the PR-branch not checked out to run the tests on...? https://help.github.com/articles/checking-out-pull-requests-locally/ cheers -ben So, relaunching the build does not really change > anything (besides the impression we may have about the build). > > A complementary solution (that should go together with fixing the > tests) is to add a retry policy while running tests in the CI. > > >> Note, is there some brave soul that would like to take action here? > > Guille, on holidays from the phone. > > On 8/22/17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > [ Pharo 70 ] Build 52 PR 205 > > index-inst-var-should-move-from-Slot-to-IndexedSlot > > https://github.com/pharo-project/pharo/pull/205 > > https://pharo.fogbugz.com/f/cases/20191 > > > > Build 53: failed, redone as 54 > > > > [ Pharo 70 ] Build 54 PR 193 Integrate WebBrowser-Core package to be > able to > > open a browser on a URL > > https://pharo.fogbugz.com/f/cases/20304 > > https://github.com/pharo-project/pharo/pull/193 > > > > Build 55: failed, redone as 56 (I do not like to use this build numberâ¦ > > with builds failing, we will always get the > > question âand what was in build XX?). > > > > [ Pharo 70 ] Build 56 PR 174 > > 20260-FastTable-not-support-cell-morphs-with-stepping-animation #174 > > https://github.com/pharo-project/pharo/pull/174 > > https://pharo.fogbugz.com/f/cases/20260/ > > > > > > > > > -- > > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr> > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 > >

Aug. 24, 2017

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

by Marcus Denker

> On 24 Aug 2017, at 12:02, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > > > On Tue, Aug 22, 2017 at 8:31 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > > > On 21 Aug 2017, at 19:08, serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com> wrote: > > > > I'm not sure Pharo tech talk is the good place but would love to see such a presentation. > > > Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligenceâ > if done with Pharo would be a very nice thing todo for the tech talk. > > > > âI thought that Pharo tech talk was only for core Pharo technologies. Why? We did have e.g. a talk about Roassal already. Keep in mind that Alexâ lecture uses Pharo as the programming language to implement the AI stuffâ¦ Marcus

Aug. 24, 2017

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

by Esteban Lorenzano

> On 24 Aug 2017, at 12:02, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > > > On Tue, Aug 22, 2017 at 8:31 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > > > On 21 Aug 2017, at 19:08, serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com> wrote: > > > > I'm not sure Pharo tech talk is the good place but would love to see such a presentation. > > > Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligenceâ > if done with Pharo would be a very nice thing todo for the tech talk. > > > > âI thought that Pharo tech talk was only for core Pharo technologies. it was, but we ran out of them for the moment, so is good to present interesting things made with Pharo too :) > âBut Alex proposal is really great. indeed :) Esteban > > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ <http://www.doesnotunderstand.org/>

Aug. 24, 2017

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

by Serge Stinckwich

On Tue, Aug 22, 2017 at 8:31 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 21 Aug 2017, at 19:08, serge.stinckwich(a)gmail.com wrote: > > > > I'm not sure Pharo tech talk is the good place but would love to see > such a presentation. > > > Why not? I am sure Alex will have some code in there.. " programming, from > scratch, a small artificial intelligenceâ > if done with Pharo would be a very nice thing todo for the tech talk. > > âI thought that Pharo tech talk was only for core Pharo technologies. âBut Alex proposal is really great. -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 24, 2017

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

by Marcus Denker

Yes! https://association.pharo.org/event-2642664 > On 23 Aug 2017, at 08:39, Norbert Hartl <norbert(a)hartl.name> wrote: > > I would be in, too. It'll be on 17th of october fix? > > Norbert > >> Am 21.08.2017 um 18:38 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: >> >> Hi! >> >> I am currently giving a lecture on Neural Networks and Genetic Algorithm/Programming. >> Maybe I could turn this into an express 2 hours mini-lecture. Would this work? >> >> Anyone is interesting in programming, from scratch, a small artificial intelligence? >> >> Cheers, >> Alexandre >> >> >>> On Aug 21, 2017, at 10:32 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Hi, >>> >>> We have added dates for tech talk discussions / Demos for the rest of 2017: >>> https://association.pharo.org/events >>> >>> We need to find some topics. In the past we had often formal âtalksâ or demos about >>> a topic with discussion afterwards, but a more relaxed form of just an open discussion >>> about a topic is possible, too, >>> >>> If you like to lead one of the dates (all but the November dates are available still), this >>> would be great. >>> >>> If a date does find a topic, we keep it as an open discussion round. >>> >>> Marcus >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

Aug. 24, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Norbert Hartl

Why is that document in the account of guille? Norbert > Am 12.08.2017 um 11:47 schrieb Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > > > 2017-08-12 11:36 GMT+02:00 Holger Freyther <holger(a)freyther.de>: >> >> > On 26. Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> > >> > Hi, >> >> Hey! >> >> thank you for this HOWTO! >> >> > username := 'YOUR-USER-NAME'. >> > repository := IceRepositoryCreator new >> > url: 'git@github.com:pharo-project/pharo.git'; >> > location: ('pharo-core' asFileReference ensureCreateDirectory); >> > subdirectory:'src'; >> > createRepository. >> > repository checkoutBranch: 'development'. >> > repository register. >> > >> > fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' format: {username})). >> > repository addRemote: fork. >> > repository pushRemote: fork. >> > repository pullRemote: repository origin. >> >> I am using "pharo-mac-stable.zip" and "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" and followed your howto and run into various Iceberg issues. Where would be the best place to report them? >> >> Open Iceberg, selech "Pharo", click on Branches >> => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. >> >> Open Iceberg, double click on "Pharo" >> => DNU, #/ was sent to nil >> UndefinedObject(Object)>>doesNotUnderstand: #/ >> ... IceSavedPackage repository location seems to return nil. >> >> >> Are these known? Fogbugz? Github issues of Iceberg? > > yes, because this HOWTO is already obsolete. See: > > https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-P… > > -- Pavel > >> >> >> cheers >> holger >> >> >> >> >

Aug. 24, 2017

Re: [Pharo-dev] new chapter on double dispatch for new book :)

by Stephane Ducasse

Fixed it Tx On Wed, Aug 23, 2017 at 1:37 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Ah, it is singular and plural form of word :) > I was just confusing that DieHandleTest uses DiceHandle class. Maybe this > should be fixed > > 2017-08-23 13:33 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >> I found little mistake: >> >> In a previous chapter you implemented a small DSL to add dice and manage >> dieHandle. >> >> >> It should be dice I guess. >> >> 2017-08-23 12:53 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>> feedback is welcome >>> Good reading >> >> >

Aug. 23, 2017

Re: [Pharo-dev] [Seaside] [Ann] Workflow

by Alexandre Bergel

Yes, this is great! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 23, 2017, at 2:51 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Thanks a lot! > > Doru > > >> On Aug 23, 2017, at 10:17 AM, Max Leske <maxleske(a)gmail.com> wrote: >> >> Hi everyone, >> >> Stef has asked me whether Netstyle would release our workflow engine to the public, so here goes: >> >> Workflow (originally called "Aare") was conceived as part of an application that Netstyle developed back in the day. We can't release all of that code but we can release the engine. I've published it on Github with an MIT license (loadable via baseline): https://github.com/Netstyle/Workflow. >> >> Please note: >> - Workflow used to depend on OmniBase for storing objects (one of the main superclasses inherited from an OmniBase class for that). I've removed that dependency. >> - As this only includes the engine, there's no UI and the things shown in the whitepaper (see repository) are technically correct but are missing the appropriate model (the UI was written with Magritte and Morphic). >> - The code is from 2005 and we haven't touched it since then, so there might be a couple of hiccups. >> - We can't provide full support for the code but I'll be happy to talk to anyone interested in maintaining or improving it. >> >> >> We at Netstyle hope that Workflow may be useful to some of you. >> >> Cheers, >> Max >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- > www.tudorgirba.com > www.feenk.com > > "Presenting is storytelling." > >

Aug. 23, 2017