[Ann] PharmIDE is renamed to TelePharo and moved to github
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.h... . Best regards, Denis
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/pr... On Wed, Aug 23, 2017 at 11:53 AM Denis Kudriashov <dionisiydk@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.h... .
Best regards, Denis
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@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@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
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@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
2017-08-23 12:21 GMT+02:00 phil@highoctane.be <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.
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@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
Well I would just subclass the TlpRemoteIDE class with the other name and delegate a connectToRemote: to connect: Indeed there is material that would be better kept in line with the current code. I was demoed another approach to remote master/slave debugging at VUB this week and they were using Seamless + TaskIt2 (so there is actully a remote taskit worker implementation) + debug stack fuel. I recommended using Beacon as well. Interesting times! Phil On Aug 23, 2017 13:29, "Denis Kudriashov" <dionisiydk@gmail.com> wrote:
2017-08-23 12:21 GMT+02:00 phil@highoctane.be <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.
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@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
On Wed, Aug 23, 2017 at 4:52 PM, Denis Kudriashov <dionisiydk@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
participants (5)
-
Ben Coman -
Denis Kudriashov -
Dimitris Chloupis -
phil＠highoctane.be -
philippe.back＠highoctane.be