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.��


Best regards,
Denis