May 2016 - Pharo-dev - lists.pharo.org

slice/merge conflict with package AST-FFI-Pharo50Compatibility

by Nicolai Hess

I need help with issues 17696 <https://pharo.fogbugz.com/f/cases/17696/RBParser-should-not-allow-variable-…> RBParser should not allow variable names for pragma arguments 17994 <https://pharo.fogbugz.com/f/cases/17994/RBParserNode-allowed-primitive-prag…> RBParserNode: allowed primitive pragma definition can not compile for both issues I created a slice that will modify methods from package AST-FFI-Pharo50Compatibility, but merging this slices shows a merge conflict. I don't know what is wrong or how I could solve this. any help appreciated. nicolai

May 24, 2016

Re: [Pharo-dev] Screenshot of Pharo 64 bits

by Dimitris Chloupis

You guys are awesome, amazing work , thank you so much for making this reality :) On Tue, May 24, 2016 at 7:06 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks a lot! > > Doru > > > > On May 24, 2016, at 3:25 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > > > > Today I helped Esteban porting the 32 to 64 bits bootstrap to Pharo. It > looks like we have a Pharo 64 bits image on 64 bits VM running on Mac & > Linux. > > > > Here is the wonderful screenshot showing the amazing result: > > > > <Screen Shot 2016-05-24 at 3.19.23 PM.png> > > -- > www.tudorgirba.com > www.feenk.com > > "Some battles are better lost than fought." > > > > > >

May 24, 2016

Re: [Pharo-dev] strange Zinc JPEG bug

by Sven Van Caekenberghe

> On 24 May 2016, at 20:11, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > On Tue, May 24, 2016 at 7:50 PM, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? > > Any bug found in the standard image regardless of project should be reported on fogbugz, no? > > > Ah, good point. > > > > > but this works just fineâ¦ > > If I do: > > > > | imageStream | > > > > imageStream := (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream. > > > > JPEGReadWriter formFromStream: imageStream. > > > > It will give me an error âimage format not recognizedâ. > > > > ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). > > > > So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have a fallback on error trying once more by using ( > > JPEGReadWriter formFromStream: theStream ) ? > > > What's the difference? Why do we have two clasees for reading JPEGs? > > Peter One is implemented in pure Pharo code, the other is plugin based, C code calling a library, and is much faster (and presumable more capable in handling weird cases). I always assumed the fastest one was used automatically, but apparently not. This works: PluginBasedJPEGReadWriter formFromStream: (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') entity readStream. I'll have to look into this. Sven

May 24, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60033 Home: https://github.com/pharo-project/pharo-core

May 24, 2016

Re: [Pharo-dev] strange Zinc JPEG bug

by Peter UhnÃ¡k

On Tue, May 24, 2016 at 7:50 PM, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? > > Any bug found in the standard image regardless of project should be > reported on fogbugz, no? > Ah, good point. > > > but this works just fineâ¦ > > If I do: > > > > *| imageStream |* > > > > *imageStream := (ZnEasy get: > 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir… > <http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…>') > contents readStream.* > > > > *JPEGReadWriter formFromStream: imageStream.* > > > > It will give me an error âimage format not recognizedâ. > > > > ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of > JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). > > > > So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have a > fallback on error trying once more by using ( > > *JPEGReadWriter formFromStream: theStream *) ? > What's the difference? Why do we have two clasees for reading JPEGs? Peter

May 24, 2016

Re: [Pharo-dev] strange Zinc JPEG bug

by Henrik Nergaard

Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? Any bug found in the standard image regardless of project should be reported on fogbugz, no? but this works just fineâ¦ If I do: | imageStream | imageStream := (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream. JPEGReadWriter formFromStream: imageStream. It will give me an error âimage format not recognizedâ. ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have a fallback on error trying once more by using ( JPEGReadWriter formFromStream: theStream ) ? Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Peter UhnÃ¡k Sent: Tuesday, May 24, 2016 6:37 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] strange Zinc JPEG bug Hi, Offray discovered a strange Zinc bug when reading a JPEG. Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? This fails on "marker D0 cannot be handled" image := ZnEasy getJpeg: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…'. World backgroundImage: image layout: #scaled. but this works just fine image := (ImageReadWriter formFromStream: (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream). World backgroundImage: image layout: #scaled. Peter

May 24, 2016

strange Zinc JPEG bug

by Peter UhnÃ¡k

Hi, Offray discovered a strange Zinc bug when reading a JPEG. Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? This fails on "marker D0 cannot be handled" image := ZnEasy getJpeg: ' http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir… '. World backgroundImage: image layout: #scaled. but this works just fine image := (ImageReadWriter formFromStream: (ZnEasy get: ' http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream). World backgroundImage: image layout: #scaled. Peter

May 24, 2016

Re: [Pharo-dev] Screenshot of Pharo 64 bits

by Tudor Girba

Thanks a lot! Doru > On May 24, 2016, at 3:25 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Today I helped Esteban porting the 32 to 64 bits bootstrap to Pharo. It looks like we have a Pharo 64 bits image on 64 bits VM running on Mac & Linux. > > Here is the wonderful screenshot showing the amazing result: > > <Screen Shot 2016-05-24 at 3.19.23 PM.png> -- www.tudorgirba.com www.feenk.com "Some battles are better lost than fought."

May 24, 2016

Re: [Pharo-dev] Screenshot of Pharo 64 bits

by Bernardo Ezequiel Contreras

GREAT! On Tue, May 24, 2016 at 11:49 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 24 May 2016, at 16:14, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > > > > > On Tue, May 24, 2016 at 4:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > > On 24 May 2016, at 15:57, Damien Cassou <damien.cassou(a)inria.fr> > wrote: > > > > > > ClÃ©ment Bera <bera.clement(a)gmail.com> writes: > > > > > >> Today I helped Esteban porting the 32 to 64 bits bootstrap to Pharo. > It > > >> looks like we have a Pharo 64 bits image on 64 bits VM running on Mac > & > > >> Linux. > > >> > > >> Here is the wonderful screenshot showing the amazing result: > > > > > > very important step. Thank you! > > > > +100 > > > > +64 > > Haha, + (2 ** 6) then ;-) > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

May 24, 2016

[pharo-project/pharo-core] 3fc04f: 60032

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 3fc04fb53ea6c043545cea2ede8bd3f5de28de9d https://github.com/pharo-project/pharo-core/commit/3fc04fb53ea6c043545cea2e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-24 (Tue, 24 May 2016) Changed paths: M Athens-Examples.package/AthensSurfaceExamples.class/class/examples/exampleDrawForm2.st M Refactoring-Environment.package/RBProtocolEnvironment.class/instance/testing/packages.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60031.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60032.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60031.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60032.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60032 18045 Use iconNamed: instead of relying on DNU [Athens] https://pharo.fogbugz.com/f/cases/18045 18284 SmallFloat64 identityHash is answering bad value https://pharo.fogbugz.com/f/cases/18284 18242 list packages for a protocol environment does not work https://pharo.fogbugz.com/f/cases/18242 http://files.pharo.org/image/60/60032.zip

May 24, 2016