August 2017 - Pharo-dev - lists.pharo.org

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

by Denis Kudriashov

Ah, it is singular and plural form of word :) I was just confusing that *Die*HandleTest uses *Dice*Handle 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 > *die*Handle. > > > 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] new chapter on double dispatch for new book :)

by Denis Kudriashov

I found little mistake: In a previous chapter you implemented a small DSL to add dice and manage *die*Handle. 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] [Ann] PharmIDE is renamed to TelePharo and moved to github

by Denis Kudriashov

2017-08-23 12:21 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Hey Denis, > > That's a decent name. At least this is settled. > > Now code that reads: > > remotePharo := TlpRemoteIDE connectTo: (....) > > is annoying with the "Remote" because it somewhat implies that the IDE is > remote. > But the IDE is local and connects to a remote. > > Maybe > > remotePharo := TlpIDE connectToRemote: (...) > > is more intention revealing. > Good point. But I made many videos where I show this name. So I don't want to rename it in nearly future. Maybe with auto deprecation of classes it can be not a problem. I want add it in Pharo 7. > > A question: is it possible to connect an image to itself? > > Like in > > remotePharo := TlpIDE connectToLocal. > > Could have interesting side effects :-) > Theoretically it can work. But right now debugger is not working is that case. Errors lead to hanging image due to infinite recursion where remote debugger requests local debugger which is remote debugger itself. I don't think it is a practical case. > > Best, > Phil > > > > On Wed, Aug 23, 2017 at 10:52 AM, 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. >> >> 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. 23, 2017

new chapter on double dispatch for new book :)

by Stephane Ducasse

feedback is welcome Good reading

Aug. 23, 2017

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

by phil＠highoctane.be

Hey Denis, That's a decent name. At least this is settled. Now code that reads: remotePharo := TlpRemoteIDE connectTo: (....) is annoying with the "Remote" because it somewhat implies that the IDE is remote. But the IDE is local and connects to a remote. Maybe remotePharo := TlpIDE connectToRemote: (...) is more intention revealing. A question: is it possible to connect an image to itself? Like in remotePharo := TlpIDE connectToLocal. Could have interesting side effects :-) Best, Phil On Wed, Aug 23, 2017 at 10:52 AM, 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. > > 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. 23, 2017

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

by Denis Kudriashov

> > In the end the important thing is the code itself and the fact you share > it , the fact it is open source and the fact it adds another very useful > tool into Pharo's arsenal. I add it to pharo wiki -> https://github.com/ > SquareBracketAssociates/PharoWiki/blob/master/contents/projects.md Thank's 2017-08-23 11:44 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > The usual bikeshed problem :) > > I use all crazy names for my projects , after all I laugh at people that > complain about weird names using a language named after the greek word for > lighthouse. But then weird names for programming languages seems to be > mandatory in the computing world. > > And dont even get me started on the term Object Orientated Programming > which must be one of the worst terms I have heard and computing is the > champion in worst terminology. > > In the end the important thing is the code itself and the fact you share > it , the fact it is open source and the fact it adds another very useful > tool into Pharo's arsenal. I add it to pharo wiki -> https://github.com/ > SquareBracketAssociates/PharoWiki/blob/master/contents/projects.md > > On Wed, Aug 23, 2017 at 11:53 AM 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. >> >> 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. 23, 2017

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

by Dimitris Chloupis

The usual bikeshed problem :) I use all crazy names for my projects , after all I laugh at people that complain about weird names using a language named after the greek word for lighthouse. But then weird names for programming languages seems to be mandatory in the computing world. And dont even get me started on the term Object Orientated Programming which must be one of the worst terms I have heard and computing is the champion in worst terminology. In the end the important thing is the code itself and the fact you share it , the fact it is open source and the fact it adds another very useful tool into Pharo's arsenal. I add it to pharo wiki -> https://github.com/SquareBracketAssociates/PharoWiki/blob/master/contents/p… On Wed, Aug 23, 2017 at 11:53 AM 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. > > 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.… > . > > Best regards, > Denis >

Aug. 23, 2017

[Ann] PharmIDE is renamed to TelePharo and moved to github

by Denis Kudriashov

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. 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.… . Best regards, Denis

Aug. 23, 2017

Re: [Pharo-dev] [Ann] Workflow

by Stephane Ducasse

Thanks a lot netstyle. I will see if I can ask students to reverse engineer and write tests for it. But may be people will do it before :) Stef On Wed, 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

Aug. 23, 2017

[Ann] Workflow

by Max Leske

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

Aug. 23, 2017