Re: [Pharo-dev] AioPlugin not present

[Thierry Goubier]

Hi Davide,

at one point in the past, the AioPlugin was present in the latest vm and 
not in the stable one. It seems than now this plugin is not built anymore.


Do you have any special requirements on the AioPlugin?

Regards,

Thierry

Le 22/01/2017 à 01:05, Davide Varvello via Pharo-dev a écrit :

Other hints?
TIA
Davide

[Pharo-dev] PharoSpur32Vm

[Nicolai Hess]

Where are the latest Pharo-spur-vms (32bit) are built?
I don't see them on the build server, only the buildresults at
http://files.pharo.org/vm/pharo-spur32/linux/

The latest builds on the buildserver are from the last year only.

nicolai

Re: [Pharo-dev] PharoSpur32Vm

[Clément Bera]

Hi,

I believe they're built from* https://github.com/OpenSmalltalk/vm
* using travis and appveyor. On the
gitbhub readme there are relevant links. All built artifacts are also kept
on bintray for history.



On Sun, Jan 22, 2017 at 9:25 AM, Nicolai Hess  wrote:

> Where are the latest Pharo-spur-vms (32bit) are built?
> I don't see them on the build server, only the buildresults at
> http://files.pharo.org/vm/pharo-spur32/linux/
>
> The latest builds on the buildserver are from the last year only.
>
> nicolai
>

Re: [Pharo-dev] PharoSpur32Vm

[Nicolai Hess]

2017-01-22 10:21 GMT+01:00 Clément Bera :

> Hi,
>
> I believe they're built from* https://github.com/OpenSmalltalk/vm
> * using travis and appveyor. On the
> gitbhub readme there are relevant links. All built artifacts are also kept
> on bintray for history.
>
>
>
Thank you!


>
> On Sun, Jan 22, 2017 at 9:25 AM, Nicolai Hess 
> wrote:
>
>> Where are the latest Pharo-spur-vms (32bit) are built?
>> I don't see them on the build server, only the buildresults at
>> http://files.pharo.org/vm/pharo-spur32/linux/
>>
>> The latest builds on the buildserver are from the last year only.
>>
>> nicolai
>>
>
>

Re: [Pharo-dev] AioPlugin not present

[Davide Varvello via Pharo-dev]

--- Begin Message ---
Hi Thierry,

I need it for the OSProcess. When my code calls OSProcess the warning
(http://imgur.com/a/9jhMy) appears.

It happens only once. If I close the warning window It does not happen
again, but of course if I restart the image it appears once again, so I have
to find a way to include it or another workaround

Cheers
Davide


Thierry Goubier wrote
> Hi Davide,
> 
> at one point in the past, the AioPlugin was present in the latest vm and 
> not in the stable one. It seems than now this plugin is not built anymore.
> 
> Do you have any special requirements on the AioPlugin?
> 
> Regards,
> 
> Thierry
> 
> Le 22/01/2017 à 01:05, Davide Varvello via Pharo-dev a écrit :
>> Other hints?
>> TIA
>> Davide





--
View this message in context: 
http://forum.world.st/AioPlugin-not-present-tp4929932p4930254.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

--- End Message ---

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

The list of previous projects is here:
https://github.com/pharo-project/pharo-project-proposals

On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
 wrote:
> Dear Prof Serge
>
> Thanks for the introduction.
>
> Dear Alexandre
> I have been a past Google Summer of Code student and also mentor budding
> developers in Google Code-In.
> This time, I was hoping to plug-in the loopholes which might have been
> present in last year's organisation application.
> Kindly let me know how can we collaborate further on this.
> Looking forward to your response.
> Thanks and Regards
> Jigyasa
>
>
> On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
>>
>>
>>
>>
>>
>> Envoyé de mon iPhone
>> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit :
>>
>> What do we do?
>>
>>
>>
>> We have to apply ! ;-)
>>
>> We talk with Jigyasa Grover who is doing an internship in my lab at the
>> moment and she is willing to help. Jigyasa was a student in a former Google
>> Summer of code and is involved in several open-source initiative like Women
>> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>>
>> You can find a small presentation during last FOSSASIA : "
>>
>> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>> 2016"
>>
>> https://m.youtube.com/watch?v=uLIzylxvIz4
>>
>> She has done a streaming video this morning also: http://goo.gl/UyclKP
>> http://youtube.com/watch?v=2iRG_jpOL54
>>
>> Anyone to help her setup a small team for Pharo proposal to Google Summer
>> of Code this year ?
>>
>>
>> On 20 Jan 2017, at 20:38, Alexandre Bergel 
>> wrote:
>>
>> Hi everyone-
>>
>> Google Summer of Code 2017 has officially begun! Organization applications
>> open today, Thursday January 19 and are open through Thursday, February 9th.
>> Please see our program site, official timeline and FAQ for more details.
>>
>> What makes a good organization application? Take a look at our manuals for
>> tips and best practices.
>>
>> We look forward to seeing each of your applications and kicking off
>> another great year of GSoC. If you have any questions, don’t hesitate to
>> reach out to gsoc-supp...@google.com. We’re here to help!
>>
>> Google Open Source Programs Office
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[Jigyasa Grover]

Also, a good application is equally important as the list of clearly
defined projects.

- J

On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:

> The list of previous projects is here:
> https://github.com/pharo-project/pharo-project-proposals
>
> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>  wrote:
> > Dear Prof Serge
> >
> > Thanks for the introduction.
> >
> > Dear Alexandre
> > I have been a past Google Summer of Code student and also mentor budding
> > developers in Google Code-In.
> > This time, I was hoping to plug-in the loopholes which might have been
> > present in last year's organisation application.
> > Kindly let me know how can we collaborate further on this.
> > Looking forward to your response.
> > Thanks and Regards
> > Jigyasa
> >
> >
> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
> >>
> >>
> >>
> >>
> >>
> >> Envoyé de mon iPhone
> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit
> :
> >>
> >> What do we do?
> >>
> >>
> >>
> >> We have to apply ! ;-)
> >>
> >> We talk with Jigyasa Grover who is doing an internship in my lab at the
> >> moment and she is willing to help. Jigyasa was a student in a former
> Google
> >> Summer of code and is involved in several open-source initiative like
> Women
> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
> >>
> >> You can find a small presentation during last FOSSASIA : "
> >>
> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
> >> 2016"
> >>
> >> https://m.youtube.com/watch?v=uLIzylxvIz4
> >>
> >> She has done a streaming video this morning also: http://goo.gl/UyclKP
> >> http://youtube.com/watch?v=2iRG_jpOL54
> >>
> >> Anyone to help her setup a small team for Pharo proposal to Google
> Summer
> >> of Code this year ?
> >>
> >>
> >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
> >> wrote:
> >>
> >> Hi everyone-
> >>
> >> Google Summer of Code 2017 has officially begun! Organization
> applications
> >> open today, Thursday January 19 and are open through Thursday, February
> 9th.
> >> Please see our program site, official timeline and FAQ for more details.
> >>
> >> What makes a good organization application? Take a look at our manuals
> for
> >> tips and best practices.
> >>
> >> We look forward to seeing each of your applications and kicking off
> >> another great year of GSoC. If you have any questions, don’t hesitate to
> >> reach out to gsoc-supp...@google.com. We’re here to help!
> >>
> >> Google Open Source Programs Office
> >> --
> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> >> Alexandre Bergel  http://www.bergel.eu
> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >>
> >>
> >>
> >>
> >
>
>
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>
>

Re: [Pharo-dev] AioPlugin not present

[Ben Coman]

hi David,

Maybe you could compile your own VM, adding add AioPlugin.
In my very first attempt to build the VM I found the instructions here
relatively easy .
* https://github.com/pharo-project/pharo-vm
That will give you the newest pre-opensmalltalk-vm. But maybe AioPlugin was
excluded from Linux for a reason.

However future VMs will be built from opensmalltalk-vm where you can see
plugins.int for many of the Squeak build configurations include AioPlugin.
*
https://github.com/OpenSmalltalk/opensmalltalk-vm/search?utf8=%E2%9C%93&q=AioPlugin+&type=Code

plus Pharo mac builds there have it...
*
https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/9d4e68e555ba7b712a8c92047c95a78e840048cd/build.macos32x86/pharo.stack.spur/plugins.int
*
https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/e3bc947d19a2f157cb8122396e293f5c2ba62a8f/build.macos64x64/pharo.cog.spur/plugins.int

with binaries available here...
https://bintray.com/opensmalltalk/vm/cog/201701192114#files

I don't see an opensmalltalk-vm pharo linux build yet, but I expect its in
the plan and maybe will include AioPlugin by default..

cheers -ben


On Sun, Jan 22, 2017 at 10:50 PM, Davide Varvello via Pharo-dev <
pharo-dev@lists.pharo.org> wrote:

>
>
> -- Forwarded message --
> From: Davide Varvello 
> To: pharo-dev@lists.pharo.org
> Cc:
> Date: Sun, 22 Jan 2017 06:50:01 -0800 (PST)
> Subject: Re: AioPlugin not present
> Hi Thierry,
>
> I need it for the OSProcess. When my code calls OSProcess the warning
> (http://imgur.com/a/9jhMy) appears.
>
> It happens only once. If I close the warning window It does not happen
> again, but of course if I restart the image it appears once again, so I
> have
> to find a way to include it or another workaround
>
> Cheers
> Davide
>
>
> Thierry Goubier wrote
> > Hi Davide,
> >
> > at one point in the past, the AioPlugin was present in the latest vm and
> > not in the stable one. It seems than now this plugin is not built
> anymore.
> >
> > Do you have any special requirements on the AioPlugin?
> >
> > Regards,
> >
> > Thierry
> >
> > Le 22/01/2017 à 01:05, Davide Varvello via Pharo-dev a écrit :
> >> Other hints?
> >> TIA
> >> Davide
>
>
>
>
>
> --
> View this message in context: http://forum.world.st/AioPlugin-not-present-
> tp4929932p4930254.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
>
>
>

[Pharo-dev] Pharo by Example 50 released!

[stepharong]

https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/

Super special thanks to Nicolai Hess that pushed me to do the last steps  
to release.

Thanks Nicolai your steady commits pushed me!

Stef

Re: [Pharo-dev] AioPlugin not present

[Thierry Goubier]

Hi Davide,

I do use OSProcess in some cases; last time, I just rewrote that part to 
emit a notification (and not raise a popup).


Regards,

Thierry

Le 22/01/2017 à 15:50, Davide Varvello via Pharo-dev a écrit :

Hi Thierry,

I need it for the OSProcess. When my code calls OSProcess the warning
(http://imgur.com/a/9jhMy) appears.

It happens only once. If I close the warning window It does not happen
again, but of course if I restart the image it appears once again, so I have
to find a way to include it or another workaround

Cheers
Davide

Re: [Pharo-dev] Pharo by Example 50 released!

[Sven Van Caekenberghe]

Great work, can't wait for the HTML version (to link to when answering 
questions).

Thank you !
 
> On 22 Jan 2017, at 16:53, stepharong  wrote:
> 
> https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/
> 
> Super special thanks to Nicolai Hess that pushed me to do the last steps to 
> release.
> Thanks Nicolai your steady commits pushed me!
> 
> Stef
> 

[Pharo-dev] About more precise default exception?

[stepharong]

When I read that, I thought that errorNotIndexable would raise an  
Exception different from Error.
But this is not the case and it means that people should write not so good  
tests by checking Error

instead of a concrete Exception.

[[[
MyExampleSetTest >> testIllegal
self should: [ empty at: 5 ] raise: Error.
self should: [ empty at: 5 put: #zork ] raise: Error
]]]
We even have a rule that states that we should not catch on Error


at: index
"Primitive. Assumes receiver is indexable. Answer the value of an
indexable element in the receiver. Fail if the argument index is not an
Integer or is out of bounds. Essential. See Object documentation
	whatIsAPrimitive. Read the class comment for a discussion about that the  
fact

that the index can be a float."


index isInteger ifTrue:
[self class isVariable
ifTrue: [self errorSubscriptBounds: index]
ifFalse: [self errorNotIndexable]].
index isNumber
ifTrue: [^self at: index asInteger]
ifFalse: [self errorNonIntegerIndex]

thoughts comments?

Re: [Pharo-dev] About more precise default exception?

[Clément Bera]

I agree this exception should be more specific.

By the way one needs to update all the primitive mutating objects, such as
at:put:, so that when it fails because it attempts to mutate a read-only
object a proper error is raised instead of SubscriptOutOfBounds with an
in-bound index.

Maybe an intern can create a specific error for your case, add an error for
read-only object and write / update tests for everything.

On Sun, Jan 22, 2017 at 6:28 PM, stepharong  wrote:

> When I read that, I thought that errorNotIndexable would raise an
> Exception different from Error.
> But this is not the case and it means that people should write not so good
> tests by checking Error
> instead of a concrete Exception.
>
> [[[
> MyExampleSetTest >> testIllegal
> self should: [ empty at: 5 ] raise: Error.
> self should: [ empty at: 5 put: #zork ] raise: Error
> ]]]
> We even have a rule that states that we should not catch on Error
>
>
> at: index
> "Primitive. Assumes receiver is indexable. Answer the value of an
> indexable element in the receiver. Fail if the argument index is
> not an
> Integer or is out of bounds. Essential. See Object documentation
> whatIsAPrimitive. Read the class comment for a discussion about
> that the fact
> that the index can be a float."
>
> 
> index isInteger ifTrue:
> [self class isVariable
> ifTrue: [self errorSubscriptBounds: index]
> ifFalse: [self errorNotIndexable]].
> index isNumber
> ifTrue: [^self at: index asInteger]
> ifFalse: [self errorNonIntegerIndex]
>
> thoughts comments?
>
>

Re: [Pharo-dev] AioPlugin not present

[David T. Lewis]

On Sun, Jan 22, 2017 at 05:00:04PM +0100, Thierry Goubier wrote:
> 
> Le 22/01/2017 ? 15:50, Davide Varvello via Pharo-dev a ?crit :
> >Hi Thierry,
> >
> >I need it for the OSProcess. When my code calls OSProcess the warning
> >(http://imgur.com/a/9jhMy) appears.
> >
> >It happens only once. If I close the warning window It does not happen
> >again, but of course if I restart the image it appears once again, so I 
> >have
> >to find a way to include it or another workaround
> >
> >Cheers
> >Davide
>
> Hi Davide,
> 
> I do use OSProcess in some cases; last time, I just rewrote that part to 
> emit a notification (and not raise a popup).
> 
> Regards,
> 
> Thierry

I am not sure why the AIOPlugin is not being included in the VMs.

Whatever the reason for that, the notifier about the missing plugin was
too annoying, so I got rid of it in the latest OSProcess update:

  Name: OSProcess-Base-dtl.56
  Time: 17 January 2017, 8:47:36.321587 am
  
  OSProcess 4.6.7
  
  Add nil checks in #shutDown: to prevent failures when exiting existing
  image with a VM that does not include OSPP (e.g. SqueakJS).
  
  For AIO event hander, if the AIO plugin is not present, write an error
  to console rather than interrupting the image with a notifer. Reduces the
  annoyance level if VM provider provides OSPP but neglects to include the
  AIO plugin.

Dave
 

Re: [Pharo-dev] What happened to Pharo's Window?

[Esteban Lorenzano]

it works for me (couple of bugs around in the examples)

in macOS sierra
in latest Pharo 6.0
in latest Pharo VM

Esteban

> On 21 Jan 2017, at 17:42, Aliaksei Syrel  wrote:
> 
> To not forget, OSWindow also does not work anymore.
> Ronnie has minheadless 64bit VM that solves the issue with OSWindow.
> Would be nice to have it for 32bit too.
> 
> It is great to see how VM is progressing! :)
> 
> Cheers,
> Alex
> 
> On 21 January 2017 at 17:35, Aliaksei Syrel  > wrote:
> Hi
> 
> Latest Pharo VM + image (from year 2017, middle of January) changed the way 
> how main window is managed and created (without any announcement).
> 
> Something is really messed up, because I can not create an OpenGL context.
> 
> OpenGL context created with default framebuffer:
> 
> 
> 
> If I create a headless context than screen just freezes until I resize (after 
> resize it recreates context making it current).
> Also, window is a black (or sometimes white) when launching pharo until I 
> click.
> 
> It definitely looks like Pharo window plays with OpenGL, probably it tries to 
> render morphic in a GL texture and then display it with acceleration: scaled 
> pharo world became sharper on retina and strange lines after dragged window 
> are in the past. Also, rendering performance on retina is dramatically 
> improved.
> 
> All those improvements are great, but please make GL context current 
> (glXMakeCurrent) every frame. Thanks!
>