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

[Stephane Ducasse]

Fixed it
Tx

On Wed, Aug 23, 2017 at 1:37 PM, Denis Kudriashov  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 :
>>
>> 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 :
>>>
>>> feedback is welcome
>>> Good reading
>>
>>
>

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

[Holger Freyther]

> On 20. Aug 2017, at 03:02, Stephane Ducasse  wrote:

Hey!


> Tx Holger
> Really tx.

appreciated but without Damien's initial Debian packaging, Estebans review, 
Norbert's drive to fix this for good and financial incentive by 2denker GmbH we 
wouldn't be here.

holger

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

[philippe.b...@highoctane.be]

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"  wrote:

> 2017-08-23 12:21 GMT+02:00 p...@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 
>> 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
>>>
>>
>>
>

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

[Dimitris Chloupis]

I read it once without knowing what double dispatch is, after reading it ,
I did not know what double dispatch is. It took several reads to understand
what double dispatch is.

My suggestion is starting with explaining as a summary what double dispatch
is , instead of leaving it for the conclusion, explain not how it works but
why we need it. Its a good idea to give a general picture to the reader
before a practical example as a map to follow the example more easily and
not be lost in the code. The code is easy to understand but the intention
is not.

Also what is a "die handle" ?

On Wed, Aug 23, 2017 at 1:54 PM Stephane Ducasse 
wrote:

> feedback is welcome
> Good reading
>

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

[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 :

> 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 :
>
>> feedback is welcome
>> Good reading
>>
>
>

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

[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 :

> feedback is welcome
> Good reading
>

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

[Denis Kudriashov]

2017-08-23 12:21 GMT+02:00 p...@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 
> 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
>>
>
>

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

[p...@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 
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
>

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

[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 :

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

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

[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/projects.md

On Wed, Aug 23, 2017 at 11:53 AM Denis Kudriashov 
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
>

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

[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.html
.

Best regards,
Denis

Re: [Pharo-dev] [Ann] Workflow

[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  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

Re: [Pharo-dev] Launcher Opening Tiny Windows

[Stephane Ducasse]

Thanks eliot.
Esteban will look at it.

Stef

On Wed, Aug 23, 2017 at 4:03 AM, Eliot Miranda  wrote:
> Hi,
>
> I think I have a fix for this.  It'll only work if the image has a
> non-zero screen size to start with.  But it arranges that if the effective
> screen size is zero (as it is for headless images) then the VM writes the
> savedWindowSize (the windows size the image had in the first place) to the
> snapshot instead of the current zero-extent headless screen size.  This is
> in commit VMMaker.oscog-eem.2265/4bbcf27fb7aab94beb77e4d517ca414d6766e34d.
> Please test and let me know if it works or not.
>
> On Tue, Aug 22, 2017 at 4:28 AM, Stephane Ducasse 
> wrote:
>>
>> Yes I experienced this problem too. I have the impression that during
>> the build the size of the window are messed up.
>>
>> Stef
>>
>> On Sun, Aug 20, 2017 at 2:44 AM, Tim Mackinnon  wrote:
>> > It's a known problem for any image that was saved in headless mode (not
>> > just launcher) - we should find a way to resolve this.
>> >
>> > Tim
>> >
>> > Sent from my iPhone
>> >
>> >> On 20 Aug 2017, at 00:35, Sean P. DeNigris 
>> >> wrote:
>> >>
>> >> Check out this screenshot.
>> >> 
>> >>
>> >> The red arrow points to an open "window" of a newly created Pharo 6.0
>> >> based
>> >> image, minimized to the point of barely being visible. Clicking on it
>> >> makes
>> >> a title bar somewhat more visible, the edges of which can then be
>> >> dragged as
>> >> any other window.
>> >>
>> >> Anyone else seeing this?
>> >>
>> >>
>> >>
>> >> -
>> >> Cheers,
>> >> Sean
>> >> --
>> >> View this message in context:
>> >> http://forum.world.st/Launcher-Opening-Tiny-Windows-tp4962615.html
>> >> Sent from the Pharo Smalltalk Developers mailing list archive at
>> >> Nabble.com.
>> >>
>> >
>> >
>>
>
>
>
> --
> _,,,^..^,,,_
> best, Eliot

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

[Norbert Hartl]

I would be in, too. It'll be on 17th of october fix? 

Norbert

> Am 21.08.2017 um 18:38 schrieb Alexandre Bergel :
> 
> 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  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
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.